Our custom board with imxrt1020 and external QSPI (IS25LP064A) flash, we have had some "novice issues". We see that some of the boards are running our programs without any issue straight after production, but for some of the boards we need to perform some actions.
We are mainly using cortex-debug and JLink, but also testing with MCUXpresso SDK examples.
Some of the symptoms we see on some (50%) of the boards are
- Cannot debug MCUXpresso example from flash (only RAM)
- Need to do an extra “reset” in cortex-debug after starting debugging, for the program to start
- When flashing program and tuning off power, the program is “lost” (doesn’t boot after power is turned back on)
Most boards see none of the above issues. What we do to fix this is to generate an image in Boot Utility tool and download it to the board. Running a flash component SDK example in RAM, also seems to fix it.
So, it seems to be related to setting up the flash correctly.
I am wondering, why does this happen only to some of the imxrt1020 controllers? Do you know what part of the boot image (FCB, IVT, Boot data etc.) is responsible for fixing the issue? Or does Boot Utility perform some other action in the background that can be relevant?
Is it mandatory to create and download a image in order for this controllers to work correctly with an external QSPI flash?
