2384049_en-US

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

2384049_en-US

2384049_en-US

FS26 Amux sensing issue

I am attempting to measure the voltage on the AMUX pin after routing the BAT sense voltage to it. I have verified all relevant register values, and the FS_STATES register reports the device is in Normal mode. However, the AMUX pin continues to output 0 V, and my 12‑bit ADC consistently reads a value of 0. I used one of the S32K3xx reference examples as the basis for my code, which I have attached, but the AMUX measurement is not functioning as expected. please, check this.

Re: FS26 Amux sensing issue

Hi,

Thank you for sharing the code and details. Could you please check the following:
- Read back M_AMUX_CTRL register after the write and confirm that AMUX_EN = 1 and AMUX[4:0] = 0x16 (BATSENSE selected). 
- Please also confirm that the SPI response indicates M_AVAL = 1, meaning the main state machine is in Normal mode.
- On the hardware side, please verify that the BATSENSE pin has the expected voltage present and that the AMUX pin is correctly routed to the ADC input.
 
BRs, Tomas
Re: FS26 Amux sensing issue

Hi, 

Your read-back confirms the AMUX is configured correctly, but the device is stuck in the INIT_FS.

To resolve this, please follow the initialization and watchdog sequence described in AN13850 (Secure file requiring an NDA), sections 6.1 and 6.2:

After power-up or reset, configure all required FS_I_xxx and FS_I_NOT_xxx registers as described in section 6.1.
Perform a good watchdog refresh within the 256ms INIT_FS window to close the initialization phase.
Once the safety outputs are released, the device will enter Normal mode and AMUX measurements should function as expected.

BRs, Tomas

Re: FS26 Amux sensing issue
The M_AMUX_CTRL register was configured for M_AMUX_EN | M_AMUX_BATSENSE | M_AMUX_DIV_0 and verified via read-back as 0x56. This confirms the analog multiplexer is active and correctly routing the 12V BATSENSE input.
 
However, the SPI device status (u8DeviceStatus) reads back as 0xCA. Because the most significant bit is set (sbc_fs26_RxFrameType.u8DeviceStatus & 0x80 == 1), a global Fail-Safe fault is active. Additionally, the FS_STATES register returns 11, proving the device is stuck in the INIT_FS (Initialization Fail-Safe) state. 
Tags (1)
No ratings
Version history
Last update:
yesterday
Updated by: