2145072_en-US

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

2145072_en-US

2145072_en-US

S32K3 ADC High-Speed Enable Issue

Hi team,


The customer EVTECH reported an issue related to the ADC High-Speed enablement.

The customer is using RTD 2.0.1 and the corresponding S32K3xx RM is Rev.5 or Rev.6.

It clearly state that 0x03 (11b) is the correct setting for AMSIO[HSEN] bit. This is also supported by internal communication in ARTD-15057, where 0x03 is explicitly mentioned for higher ADC clock frequencies.

nxf65432_0-1754040246046.png

nxf65432_1-1754040288728.png


But it looks like the recommended configuration for the ADC AMSIO[HSEN] field has changed starting with S32K3 RM Rev. 7, where the value 0x01 is now used to enable High-Speed mode and added a new bit AMSIO[CMPCTRL0] to control this feature also. However, this change is not mentioned in the Rev. 7 release notes. 

nxf65432_2-1754040492340.png

nxf65432_3-1754040526564.png


The corresponding RTD code also can reflect this difference of the High-Speed setting:

RTD 2.0.0 and 3.0.0

Amsio &= ~(ADC_AMSIO_HSEN_MASK);
Amsio |= ADC_AMSIO_HSEN(Enable ? 3u : 0u);

RTD 4.0.0 and 5.0.0

Amsio &= ~(ADC_AMSIO_HSEN_MASK | ADC_AMSIO_CMPCTRL0_MASK);
if (TRUE == Enable)
{
    Amsio |= (ADC_AMSIO_HSEN(1u) | ADC_AMSIO_CMPCTRL0(1u));
}
 
Now the customer has two questions related to the ADC High-Speed enablement:
1. Are the latest RM and RTD revisions (≥ Rev. 7 / RTD 4.0.0) now using the correct settings?
2. If a project is using older RTD like RTD 2.0.1, should the Adc_Sar_EnableHighSpeed() function be updated to match the logic from RTD 4.0.0?
 
Best Regards,
Zheng Lin
Priority: MEDIUMRTDRe: S32K3 ADC High-Speed Enable Issue

Hi @ZhengLin ,

From RTD view, SW team followed RM that suggested for that version. I think you should put this question to design team. They can provide the reason for that change and how it affect to this feature.

Best regards,

Nhi

Re: S32K3 ADC High-Speed Enable Issue

Hi Nhi,


Understand that the customer should use the latest RTD version and not to modify the RTD driver by themselves. Now the question is that if the customer would like to use the RTD 2.0.1 version, whether they can still use the default RTD 2.0.1 driver code to realize the correct configuration of the High-Speed setting.


Best Regards,

Zheng Lin

Re: S32K3 ADC High-Speed Enable Issue

Hi @ZhengLin ,

I checked silicon for version 200->300 and from 400->600, there is no difference. So, seems RTD driver just updated that based on RM updated (from Rev3(RTM201)/Rev6(RTM300) to Rev8(RTM400)).

The ticket updated ADC driver is: https://jira.sw.nxp.com/browse/ARTD-96768

There is a note:

Nhi_Nguyen_0-1754280931468.png

We always recommend the customer uses the latest version. For now, RTM600 is latest version.

1. Are the latest RM and RTD revisions (≥ Rev. 7 / RTD 4.0.0) now using the correct settings?
=> You can find RM version is corresponding to RTD package in the release note. For example: RTM600 is Rev9. And RTD driver just updated driver based on RM. So, for this question, I think that you can put it to HW team to see what RM version is correct.
2. If a project is using older RTD like RTD 2.0.1, should the Adc_Sar_EnableHighSpeed() function be updated to match the logic from RTD 4.0.0?
=> Adc_Sar_EnableHighSpeed() was updated with header file in BaseNXP was updated at least. We don't suggest the customer changes RTD driver by themselves. They should migrate to latest RTD package. 
 
Best regards,
Nhi
Tags (1)
No ratings
Version history
Last update:
‎11-21-2025 01:17 AM
Updated by: