Part Number: AM263P4-Q1
Hello,
In DevBoot mode, I am able to run custom* SBL on our custom* HW using a modified sbl_load.js:

After a CPU reset, the .mcelf application runs.
My problem is that when I put the SOC boot pins to QSPI 4S mode, the custom SBL and therefore application do not run.
After power-on, If I connect the debugger (without loading a program or resetting), the PC does not correlate with a symbols in my SBL code:

I conclude the RBL did not load my SBL. However, I'm not sure what to check now.
I have a asked the HW team to configure the boot mode in 1S but in case this does not resolve the issue, what is my next move please?
- Is there a checklist of items or flowchart to eliminate silly errors?
- Are there any registers I can check which provide clues to the cause of RBL failure?
*The custom SBL uses 'sbl_ospi_multicore_elf' in mcu_plus_sdk_am263px_11_00_00_19 as a baseline with modifications for the S25FL128SAGMFI000 - Quad SPI flash | Infineon Technologies flash and removal of I2C and EEPROM which aren't relevant for our HW.
The only other difference is that we have special hsmRtImg.h provided by TI (Nikhil Dasan) in order to open the TRACE port.
