- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- MCUXpresso Training Hub
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
-
- Home
- :
- i.MX Forums
- :
- i.MX RT Crossover MCUs
- :
- Re: Location of flexspi NOR configuration parameters...
Location of flexspi NOR configuration parameters...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've been working with iMXRT1062 in various forms (EVK, Teensy4.1 and custom HW) for a while, and I am currently wrestling with a bootup issue (see this post). For the sake of this question, just assume I am booting the MIMXRT1060-EVK...
I have a boot image that is derived from the examples. The final .elf file shows me that the location of the flash config parameters (defined in the SDK file 'evkmimxrt1060_flexspi_nor_config.c') are at the base of the QuadSPI device's memory space (0x60000000). This has been working on multiple boards for months.
Now that I'm digging into a boot problem (using a larger boot device), I read something that I didn't notice until now...
Section 9.6.1.2 "FlexSPI Serial NOR Flash Boot Operation" of the reference manual says:
The ROM expects the 512-byte FlexSPI NOR configuration parameters (as explained
in the next section) to be present at offset 0x400 in Serial NOR flash attached to FLEXSPI_A_SS0_B.
My empirical data tells me this 0x400 offset is wrong simply because I've been booting my boards with this data at 0x000 offset for quite some time. Am I just confused and lucky, or is the text in the reference manual wrong?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
The i.MX RT 1011 has its configuration parameters located at 0x400 but I never saw anyone set up other parts for this address - invariably 0x0 offset is used.
Possibly the i.MX RT 106x probes 0x400 first and, when it doesn't find the expected signature there, tries at 0x0 (?)
I have also worked on 12 different (non-i.MX RT 1011) HW designs which have always been happy with 0x0 offset so would not place too much weight o the line in the document.
Regards
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
The i.MX RT 1011 has its configuration parameters located at 0x400 but I never saw anyone set up other parts for this address - invariably 0x0 offset is used.
Possibly the i.MX RT 106x probes 0x400 first and, when it doesn't find the expected signature there, tries at 0x0 (?)
I have also worked on 12 different (non-i.MX RT 1011) HW designs which have always been happy with 0x0 offset so would not place too much weight o the line in the document.
Regards
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks Mark,
Yea, you know what I'm dealing with regarding the boot of the '01G device (still not resolved), so these small details should be picked up by NXP to update the documentation or explain it so that we don't have to speculate on what the real details are.
Anyone from NXP listening??
