S32E288-975 EVB Hi NXP team, We are using an S32E288-975EVB daughter card. The board was working normally until we flashed a new application. After programming the new code, the processor appears to remain continuously in reset, and we are no longer able to proceed with normal debugging/programming. Current observations: RESET_B LED remains continuously ON. POR_RESET LED also remains continuously ON. We removed the relevant reset jumpers to isolate the possible reset sources. Based on this isolation, the reset condition appears to be associated with the processor/SoC side rather than an external reset source. The issue started immediately after flashing the new application. Could you please advise: What conditions inside the S32E288 could cause RESET_B/POR_RESET to remain asserted continuously after programming an application? Could incorrect startup, clock, power-management, watchdog, reset, or device configuration in the flashed image result in this behavior? Is there a recommended recovery or debug procedure to prevent/override the application from executing so that we can regain debugger access and erase/reflash the device? Is there a specific boot mode, jumper configuration, reset sequence, or debugger connection method recommended for recovering an S32E288 device from this condition? Are there any status registers or signals we should check to determine the actual source of the reset? Re: S32E288-975 EVB Hi,vishal
Thank you for contacting us.
Could you share more information with me?
1.What is the new application are you using?
2.What is the Boot Mode? Have you tried other boot mode via change switch on your development Board?
3. are you using debugger of S32DS debug probe or Trace32 for your application?
BR
Joey Re: S32E288-975 EVB Hi,yogeshwar
Thank you for your reply.
I suspect that PMIC has some issue on your board, please test the voltage of PMIC_PGOOD/PMIC_RESET_B by using the oscilloscope if still at the low status.
Also, did you have any operate for your PMIC before?
BR
Joey Re: S32E288-975 EVB Hi Joey, Thanks for the reply. 1.What is the new application are you using? There is no change of application. We were loading same firmware with minor changes during development. 2.What is the Boot Mode? Have you tried other boot mode via change switch on your development Board? It was a working board which was booting from flash. Suddenly it stopped working with Reset LED(D50) and POR LED(D46) switched on and wont allow programming the processor. 3. are you using debugger of S32DS debug probe or Trace32 for your application? We are using S32 Debug probe. We doubt it as hardware issue. Is there specific steps to troubleshoot it to zero in the component which might cause it. Re: S32E288-975 EVB Hi,vishal
Thank you for your reply and detail informaiton.
1.Could you test the POR_B and RESET_B states by the entire power-on process? The oscilloscope can be used to capture the power-on states of both components to check whether they remain at a low level throughout the power-on process, or whether there is a short period of high level followed by being pulled down by the SOC.
2.Please checking whether POR_B be pulled down during the whole power-on process when J130 header is not removed.
3.Also, you can try to use the oscilloscope to check the power states by refer to the power sequencing.
Hope this information can help you!
BR
Joey
Re: S32E288-975 EVB Hi, We removed the J131 header to isolate PMIC_RESET_B from RESET_B. After removing J131, the PMIC_RESET_B LED turned OFF, while the RESET_B LED remained ON. We also verified that SW9 is functioning correctly by powering OFF the board and checking its operation. As an additional isolation step, we removed the J130 header and measured both inputs of U41 (AND gate). Both inputs were measured at 3.3 V; however, the POR_B output was at GND level (LED ON). Additionally, with the board powered OFF, we confirmed that there is no hard short between RESET_B and GND. Based on these observations, RESET_B and POR_B appears to be pulled to GND only when the board is powered ON. Re: S32E288-975 EVB Hi, Thank you for the advice. Power up sequence remains same for both working and failed EVL board. During this exercise, both J131 and J130 Headers were not connected. Failed EVL board Reset_B and POR_B LEDs remain continuously ON. POR_B does not rise to 3.3 V. Reset_B stays at 3.3 V for approximately 5 ms, then transitions LOW and remains LOW. Working EVL board POR_B rises to 3.3 V approximately 4 ms after the 3.3 V power rail comes up. Reset_B transitions to GND after approximately 5 ms, remains LOW for about 1 ms, and then returns to 3.3 V. Another difference observed, in terms of resistance measurement on Power rails. The voltage level of power rails is good. RESISTANCE (ohms) POSITIVE (RED) NEGATIVE (BLACK) Working Non working 3.3V GND 300 6 0.8V GND 7.2 5.6 3.3V 0.8V 335 11 Re: S32E288-975 EVB Hi,
Thank you for your reply and detail information.
About your description of "POR_B does not rise to 3.3 V".
Please check the U41 function on your failed board, if the J130 be connected between 2 and 3, When PMIC_PGOOD is equal to 3.3V and SW8 is not pressed, A/B should be 1 and POR_B should be 3.3V.
The Soc will not work normally if POR_B does not rise to 3.3 V.
BR
Joey Re: S32E288-975 EVB Hi, POR_B behavior and 3.3V impedance observation on failed EVL board From the working EVL board, we observed that POR_B remains low for approximately 4 ms after the 3.3V rail comes up. After ~4 ms, POR_B is released and rises to 3.3V. Our current understanding is that the SoC may be holding POR_B low during this initial period. As advised, we removed the U41 AND gate IC on the failed EVL board. However, there was no change in the POR_B behavior, and the signal continues to remain low. We also compared the impedance between 3.3V and GND: Failed EVL board: ~6 Ω Working EVL board: ~300 Ω The significantly lower impedance on the failed board is still present even after removing U41. Re: S32E288-975 EVB Hi,vishal
Thank you for your reply!
For your information, the POR_B behavior is still at the low on your failure board, it is not the normal behavior. The normal state of POR_B should be as described on your working board, that is, First, it should be pulled down, and then raised to 3.3V after other power rails have risen.
Impedance testing is also valuable information.
Could you tell me when you purchased the S32E288-975 EVB board? Which channel you purchased this board?
BR
Joey Re: S32E288-975 EVB Hi,vishal
Thank you for your detail information.
After remove the U41, you can try to connect the 1 and 2 nodes as the following picture, check the POR_B if cannot be pulled high directly.
Also, could you tell me when you purchased the S32E288-975 EVB board? Which channel you purchased this board?
You can share the information with this link:support.nxp.com
Re: S32E288-975 EVB Hi,vishal
About the pin of POR_B on the S32E2, it be internal pulled down if not driven from top by default, and the POR_B is the input mode.
So, I think you should consider why the POR_B is not pulled high externally. The U41 may have a fault function.
BR
Joey Re: S32E288-975 EVB Hi Joey, The U41 device was purchased from Mouser. As mentioned earlier, we removed U41 from the board and observed that the POR_B signal is pulled LOW, as expected. However, even after removing U41, the measured impedance is still approximately 6 Ω, whereas we expected around 300 Ω. Before replacing U41 with a new device, could you please advise on the following? Would you recommend replacing U41 with a new IC at this stage? Since the low impedance remains even after U41 is removed, are there any other signal lines or components connected to POR_B that you recommend checking first? What could be the probable cause of the original U41 failure? Could it be due to an overvoltage, output contention, excessive current, power sequencing, ESD, or another condition? Any suggestions for further troubleshooting before replacing U41 would be appreciated. Re: S32E288-975 EVB Hi, The Chanel of purchase - Mouser Date - June 2026 Re: S32E288-975 EVB Hi, The Chanel of purchase - Mouser Date - June 2026 Re: S32E288-975 EVB Hi,vishal
Thank you for your reply!
Based on our communication and information, the POR pin of your S32E288 cannot normally be pulled high external, and there are issues with the impedance test on your board. Since your development board is still within the warranty period, it is recommended to contact distributor for this issue.
BR
Joey Re: S32E288-975 EVB Hi, Thanks for your advice. We are currently coordinating with Mouser for replacement of the failed EVL kit. Meanwhile, we have two more EVL kits available. Before proceeding with further testing, we would like to understand how we can prevent a similar failure. Based on the failure symptoms and debug results shared in this thread, could you kindly advise what the possible reason for this failure could be? Also, what precautions would you recommend while interfacing the EVL? Your recommendations would be very helpful before we proceed with testing on the remaining boards. Thanks for your continued support.
View full article