- 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
- :
- 2293717_en-US
2293717_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2293717_en-US
2293717_en-US
I'm trying to mimic how we will be performing the first flash of our custom board based on the LS1046ARDB. On our custom board we only have eMMC and QSPI when first powering on the board. We would like to flash the eMMC first. I have built an emmc_clone.bin file based on the AN5184.pdf instructions and also following the "Bring up the LS1046A-1.pdf" on how to flash from CodeWarrior. I have verified that the CodeWarrior Tap is working and I can connect to the server. However, when I use the Flash Programmer it always returns an error about communication with eMMC. It seems there are more modifications needed to the LS1046A_RDB*.tcc (Target Initialization File) to enable the eMMC? I see a line under the Reset section to enable the QSPI:
TA.rcw.set_data({13: 0x20124000})
I assume another line is needed to enable the eMMC? But what would that be? Is there anything else I need to do?
Replace the "Target Initialization File" content with the ls1046ardb.py_2100&1600_pass.txt.
I could program the eMMC on the LS1046ARDB and the LS1046ARDB could bring up from the eMMC.
There is one mux control signal SD_eMMC_SEL on the LS1046ARDB, but it's decided by whether inserting SD card or not.
When you use the eMMC, please kindly don't insert SD card.
Here is some more information... I'm able to read/erase/flash the SD card without issue but the eMMC doesn't seem to respond. With the SD card removed and the jumpers still set to boot from SD/eMMC I don't have access to the eMMC. It appears that the CPLD is not switching from the SD to eMMC. The eMMC is blank (never been programmed) so when powering it on and no SD card is in there are no console prints or anything. This is where I start CodeWarrior and connect to the Tap to try and program the eMMC. But nothing but errors when trying. I'm starting to think that the CPLD is the problem.
Tried the file however I get errors unless I USE_SAFE_RCE = True. Erase and Program returns no errors however still can't boot.
When the USE_SAFE_RCW = True, that is the original one I sent it to you.
Because the initialization of the txt is adjusted per the hard-code RCW(USE_SAFE_RCW = True).
If you use your own RCW, please kindly change the initialization.
I'm going to close this one since it is related to: