Part Number: AM263P4
Other Parts Discussed in Thread: SYSCONFIG
Hi Experts,
I would like to ask whether there are any limitations or special considerations when using ESM in SDL configured through SysConfig
- SDK version : 10.02.00
- Sysconfig version : 1.23.0
I configured CONFIG_ESM0 in SysConfig and enabled SDL-related Error Pin Events as shown below.
After that, I added a call to Sdl_config() during system initialization.
However, the firmware fails to boot after calling
Sdl_config().Our goal is to detect potential power instability or clock-related issues that could be caused by abnormal supply voltage conditions. For this purpose, we enabled the following ESM error events in SysConfig:
- SDL_ESM0_CORE_PLL_PLL_CORE_LOCKLOSS
- SDL_ESM0_DCC0_DCC0_ERR
- SDL_ESM0_DCC1_DCC1_ERR
- SDL_ESM0_PERI_PLL_PLL_PER_LOCKLOSS
- SDL_ESM0_RCOSC_RCREF_CLK_LOSS_DETECT
- SDL_ESM0_VMON_VOLTAGE_MONITOR_ERR_L
- SDL_ESM0_VOLTAGE_MONITOR_ERR_H
- SDL_ESM0_XTAL_CRYSTAL_CLOCKLOSS
Callback:
SAFETY_ERRON pin:
- this is connected to DGND. We are just probing this pin with an oscilloscope.
Our understanding is that these events can help detect voltage-related anomalies indirectly through PLL lock loss, clock source failures, DCC monitoring errors, and directly through voltage monitor events.
Questions:
- Is there any known limitation or conflict between SysConfig-generated ESM initialization and
Sdl_config()? - Are any of the selected ESM events expected to assert immediately during boot and potentially prevent the application from starting?
- What are the main checkpoints or debug steps you would recommend to identify why the boot process stops after
Sdl_config()is called? - Is there a recommended way to use SDL and SysConfig-generated ESM configuration together for detecting voltage instability and clock-related faults?
Any guidance on the likely root cause and the key areas to investigate would be greatly appreciated.
Thank you.
Best regards,
Moonil Heo
Moonil Heo
