I am trying to use XIP feature on a custom board without success. The SDK demo "hello_world_qspi_xip" works fine on NXP LCP54S018M-EVK but the same binary is not booting on my board.
My board is working when copying flash to SRAMX then executing code from SRAMX.
Q1: The datasheet mentions that ISP1/2/3 pins (PIO0_4/PIO0_5/PIO0_6) are floating, but on NXP EVK they seems to be pulled-up, even if I can not see any pull-up in the schematic. Why ?
Unfortunately on my board those pins are not connected, so I guess that the boot mode is undetermined and I tried to set BOOT_SRC fuses to SPIFI until we respin the board: it did not work neither.
Q2: OTP writing was an issue on my side, fixed
Q3: Datasheet states that pins N7 and C4 should be connected to enable flash and reset state is "Pulled up" (table 4), but there is a 100 k pull-up in NXP EVK. Why ?
Thank you for your help
Regarding your question, you said your board was working when copying flash to SRAMX then executing code from SRAMX, do you mean that your board can run after Reset even power off/on? I assume that you have downloaded application code to SPIFI flash. If it is the case, I think the boot process is okay.
The only difference between the XIP and SRAM executing is the XIP bit setting for image type(__imghdr_imagetype variable in *.ld file).
Hope it can help you
Thank you for your answer @xiangjun_rong
Yes, when executing from SRAMX the board can run even after a power off/on, so storing data in flash is working
I already checked that bit in the header and it is correctly configured:
Address 0x160 contains (little endian) a5a5 edfe 0300 0000 0000 0010 0439 0000 => Header_marker: 0xFEED A5A5 image_type: 0x0000 0003 (No CRC computation, XIP image) load_adress: 0x1000 0000 (SPIFI XIP) Image_length: 0x0000 3904
So, if that bit is correctly set and the boot process is correct when booting from SRAM: why NXP SDK board is booting in XIP mode but not mine ? Could we have any race condition between peripherals, like clock startup time ?
Hello @xiangjun_rong ,
It seems that all my boards are not having the same behavior: most of them are unable to boot when I use XIP with "BootClockFROHF96M" clock but using "BootClockPLL180M" works with "led_blinky" example. Then I tried to use "QSPI_DELAY" fuse set to 220 ms (0x7). Some of them are able to boot "led_blinky with the FROHF96M clock but I usually get this pattern:
As the exact same binary is booting on the NXP EVK I guess that I have an hardware issue, any hint on usual suspects?
Regarding your issue that boot fails with BootClockFROHF96M for some examples, frankly speaking, I have not ideas, probably it is a signal integrity issue for the PCB.
For the "QSPI_DELAY" fuse option, can you tell us where you set it?
QSPI_DELAY is from the UM11155 chapter "22.214.171.124 OTP memory bank 3, word 0 - Boot ROM control data", table 1107. Bits 19:17
Regarding free running oscillator it is inside the chip so I am not sure to understand how PCB signal integrity will impact it. I checked the power-supplies with an oscilloscope and they seems to be correct
I mean the SPI_CLK_FREQ variable, which is integrated in the image, it determines the SPIFI clock frequency.
Pls refer to an12122.pdf, located at:
Hope it can help you