- 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
-
- 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
- :
- Product Forums
- :
- S32G
- :
- s32g emmc write timeout issue.
s32g emmc write timeout issue.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
s32g emmc write timeout issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
I'm working on a custom s32g274a board based. my board will enter the Fastboot mode due to it can't write eMMC(see debug logs).
U-Boot 2020.04+gc2dbae631e (Dec 12 2023 - 11:02:59 +0000) bsp32.0-2020.04
CPU: NXP S32G274A rev. 2.1.0
DRAM: 1.8 GiB
MMC: FSL_SDHC: 0
Using internal clock for PCIe0, CRNS
Frequency 100Mhz configured for PCIe0
Configuring PCIe0 as RootComplex(x1)&SGMII [XPCS 0 OFF(PCIex1), XPCS1 1G]
PCIe0 disabled
Using internal clock for PCIe1, CRNS
Frequency 100Mhz configured for PCIe1
Configuring PCIe1 as SGMII(x2) [XPCS0 1G, XPCS1 1G]
In: serial@401C8000
Out: serial@401C8000
Err: serial@401C8000
(bootloader) Net: register phy driver for BCM89883
PFE: emac0: sgmii emac1: none emac2: sgmii
Warning: eth_pfeng using MAC address from ROM
eth0: eth_pfeng
mmc write failed
misc_read_command:misc part write failed.
check_bootmode: misc read failed
Hit some key to stop autoboot: 0
ERROR - can't switch to rpmb partition
avb_ab_flow.c:109: ERROR: Error reading A/B metadata.
avb_ab_flow.c:188: ERROR: I/O error while loading A/B metadata.
avb_ab_flow.c:138: ERROR: Error writing A/B metadata.
do_boot_avb: Fastboot: enter!
When i enabled the CONFIG_TRACE_MMC , here the logs:
it returns timeout value.I want to know why EMMC fails to write druing u-boot startup, but reads normally.(The attachment is a log of normal startup)
Daniel-Aguirre
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Are you able to use an NXP reference board? Are you able to reproduce this outcome on the NXP reference board?
We can recommend looking into AN13667 under the S32G2 product page (link: S32G2 Safe and Secure Vehicle Network Processor | NXP Semiconductors). This AN provides some debugging tips on regards of the eMMC interface, could provide to be useful.
Also, within this community, the support for custom boards is not that common, since we are not able to reproduce the outcome of custom boards, we do apologize. For this, we can recommend contacting your local NXP DFAE/FAE since they should be able to provide a better support on this situation.
Please, let us know.
