- 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
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- 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
- S32Z/E
-
- 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
- Generative AI & LLMs
-
- 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
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2380050_en-US
2380050_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2380050_en-US
2380050_en-US
Hi
-> By changing the jumper and switch settings, I was able to boot from QSPI Flash on LS2088ARDB.
->AFter booting, accidentally I erased the boot area of QSPI flash(bl2,rcw,uboot all erased.). The target is not booting.
->I am trying use Lauterbasch JTAG to boot using ls2088a_sieve_sram_failsave.cmm which is failsafe method. Here "override the RCW" as shown below
Data.Set EDBG:0x42001080 %Long 0x9b ; RCW_src=HARDCODED
-> With this the target shall boot with the RCW supplied by JTAG(ls2088a_sieve_sram_failsave.cmm).
-> But notice that the QSPI is not working, because the RCW_SRC is not QSPI_boot.
->If QSPI pin mux, clock are not initialised, how will the QSPI work ?
Question: Can you please provide suggestions / new .cmm script which can be used when QSPI flash is empty / erased to recover the target using JTAG.
Thanks and Regards
Hello,
The needed documentation would typically be:
- the LS2088A Reference Manual / boot flow documentation for RCW source behavior and QSPI initialization,
- the LS2088ARDB board recovery or programming procedure ,
- and any Lauterbach recovery script notes specific to
ls2088a_sieve_sram_failsave.cmm.
Since none of that is available in the retrieved sources, the safest answer is: I cannot verify that the existing fail-safe script can re-enable QSPI access after the boot area is erased, and I cannot generate a trustworthy replacement .cmm script from the available documentation. Please contact NXP support for the LS2088ARDB recovery procedure or share the exact LS2088A/Lauterbach documentation set you want analyzed, and I can help interpret it.
Regards