Dear NXP,
I am following up on a pretty old question of myself:
https://community.nxp.com/t5/i-MX-RT/imx-rt-1021-custom-board-use-flash-on-FlexSPI-B/td-p/1495752
I got caught up in other priorities and didn't really have time to give this topic enough attention. But, we're back on that topic now, and we are still kind of in the same situation. I have a hard time figuring out how to proceed.
The goal: use a secondary flash as "eeprom", so that we don't have to bother with running code in ITC sram.
Background: Currently we are running code in ITC sram in order to use a part of flash as eeprom. It's rather cumbersome, because we also compile our app with "position independent code" compiler flag (in order to run the app in two different locations on flash). Position independent combined with dealing with code running in ITC sram complicates things a bit, I'll spare the details, but, that's the reason we prefer to move aware from the necessity of running code in ITC sram.
As I glanced at this topic (using secondary flash) before, and was a bit lost in space immediately, I was hoping for some extra guidance from NXP support.
Let's say :
- we have a custom PCB, and a secondary flash is properly wired up to FlexSPI B.
- I can run SDK examples without a problem on our board.
Could you somewhat guide me through the process? Is there an SDK example that :
- will run from the 1024 internal flash, AND
- do ANYHTING (read/write/erase) on our flash wired up to FlexSPI B?
If you could provide me an SDK example that meets those requirements, then I have a working starting point, which makes it a whole lot easier to try stuff and start to learn. Now, when I am trying to reverse engineer the nor_flash SDK examples, I mostly get lost in stuff I know close to nothing about.
Many thanks in advance !