- 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
- 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
-
- 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
- :
- i.MX Forums
- :
- i.MX Processors
- :
- iMX6ULL u-boot cannot recognize kernel image
iMX6ULL u-boot cannot recognize kernel image
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
SOLVED
07-13-2021
05:33 AM
1,325 Views
abdullahkahrama
Contributor IV
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This question is a duplicate of:
I have a custom board that I am trying to bring up. It passes the DDR stress tester over USB HID.
I have build an image according to i.MX_Yocto_Project_User's_Guide. My build configuration was:
MACHINE=imx6ullevk
DISTRO=fslc-framebuffer
IMAGE=core-image-minimal
I have then run dd command to burn .wic file to an SD card. The board boots up with SD card, however here is what I see on the terminal:
U-Boot 2020.10+fslc+g80c23498b4 (Mar 04 2021 - 17:46:24 +0000)
CPU: Freescale i.MX6ULL rev1.1 900 MHz (running at 396 MHz)
CPU: Commercial temperature grade (0C to 95C) at 48C
Reset cause: POR
Model: Freescale i.MX6 UltraLiteLite 14x14 EVK Board
Board: MX6ULL 14x14 EVK
DRAM: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... Card did not respond to voltage select!
*** Warning - No block device, using default environment
In: serial
Out: serial
Err: serial
Net: Could not get PHY for FEC1: addr 1
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC0: addr 2
Could not get PHY for FEC0: addr 2
No ethernet found.
Normal Boot
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
Card did not respond to voltage select!
Booting from net ...
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC0: addr 2
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC1: addr 1
No ethernet found.
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC0: addr 2
Could not get PHY for FEC1: addr 1
Could not get PHY for FEC1: addr 1
No ethernet found.
Could not get PHY for FEC1: addr 1
zimage: Bad magic!
=>
Then I try to read from the SD card, I wipe the DDR areas I am going to use, copy the zImage from the SD card to RAM, and check with iminfo and I get:
Unknown image format!
=>mmc info
Device: FSL_SDHC
Manufacturer ID: 3
OEM: 5344
Name: SU16G
Bus Speed: 50000000
Mode: SD High Speed (50MHz)
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 14.8 GiB
Bus Width: 4-bit
Erase Group Size: 512 Bytes
=> mmc part
Partition Map for MMC device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 8192 53392 c2827fb8-01 0c Boot
2 65536 40478 c2827fb8-02 83
=> ls mmc 0:1
30847 imx6ull-14x14-evk.dtb
7350040 zImage
2 file(s)
=> md 82000000
82000000: e1a00000 e1a00000 e1a00000 e1a00000 ................
82000010: e1a00000 e1a00000 e1a00000 e1a00000 ................
82000020: ea000003 016f2818 00000002 00702718 .....(o......'p.
82000030: 04030201 e10f9000 eb0104f8 e1a07001 .............p..
82000040: e1a08002 e10f2000 e3120003 1a000001 ..... ..........
82000050: e3a20017 ef123456 e10f0000 a220001a ....V4........ .
82000060: e310001f e3c0001f e38000d3 1a000004 ................
82000070: e3800c01 e28fe00c f16ff000 e12ef30e ..........o.....
82000080: f160206e e121f000 e16ff009 00000000 n `...!...o.....
82000090: 02000000 00000000 00000000 00000000 ................
820000a0: e1a0401f 6204433e e2844902 e1a0000f .@..>C.b.I......
820000b0: e1500084 349f01ac 3080000f 31540000 ..P....4...0..T1
820000c0: 73844001 2300006d e28f0f5e e8901c4e .@.sm..#^...N...
820000d0: ed90d01c e0400001 e0866010 e082a000 ......@..`......
820000e0: e5da9002 e5dae001 e189940e e5dac002 ................
820000f0: e7daa003 e189980e e1899c0a e08dd000 ................
=> mw 81000000 0 7000000
=> md 82000000
82000000: 00000000 00000000 00000000 00000000 ................
82000010: 00000000 00000000 00000000 00000000 ................
82000020: 00000000 00000000 00000000 00000000 ................
82000030: 00000000 00000000 00000000 00000000 ................
82000040: 00000000 00000000 00000000 00000000 ................
82000050: 00000000 00000000 00000000 00000000 ................
82000060: 00000000 00000000 00000000 00000000 ................
82000070: 00000000 00000000 00000000 00000000 ................
82000080: 00000000 00000000 00000000 00000000 ................
82000090: 00000000 00000000 00000000 00000000 ................
820000a0: 00000000 00000000 00000000 00000000 ................
820000b0: 00000000 00000000 00000000 00000000 ................
820000c0: 00000000 00000000 00000000 00000000 ................
820000d0: 00000000 00000000 00000000 00000000 ................
820000e0: 00000000 00000000 00000000 00000000 ................
820000f0: 00000000 00000000 00000000 00000000 ................
=> load mmc 0:1 82000000 zImage
7350040 bytes read in 347 ms (20.2 MiB/s)
=> md 82000000
82000000: e1a00000 e1a00000 e1a00000 e1a00000 ................
82000010: e1a00000 e1a00000 e1a00000 e1a00000 ................
82000020: ea000003 016f2818 00000000 00702718 .....(o......'p.
82000030: 04030201 e10f9000 eb0004f8 e1a07001 .............p..
82000040: e1a08002 e10f2000 e3120003 1a000001 ..... ..........
82000050: e3a00017 ef123456 e10f0000 e220001a ....V4........ .
82000060: e310001f e3c0001f e38000d3 1a000004 ................
82000070: e3800c01 e28fe00c e16ff000 e12ef30e ..........o.....
82000080: e160006e e121f000 e16ff009 00000000 n.`...!...o.....
82000090: 00000000 00000000 00000000 00000000 ................
820000a0: e1a0400f e204433e e2844902 e1a0000f .@..>C...I......
820000b0: e1500004 359f01ac 3080000f 31540000 ..P....5...0..T1
820000c0: 33844001 2b00006d e28f0f5e e8901c4e .@.3m..+^...N...
820000d0: e590d01c e0400001 e0866000 e08aa000 ......@..`......
820000e0: e5da9000 e5dae001 e189940e e5dae002 ................
820000f0: e5daa003 e189980e e1899c0a e08dd000 ................
=> imi 82000000
## Checking Image at 82000000 ...
Unknown image format!
I have attached my zImage file. (I had to zip it since the forum doesn't accept a file without a type)
What could be my problem?
Solved! Go to Solution.
1 Solution
07-13-2021
09:41 PM
1,302 Views
abdullahkahrama
Contributor IV
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems like clue to the problem lays here:
mmcdev=1
mmcpart=1
mmcroot=/dev/mmcblk1p2 rootwait rw I am using mmc0 in my design, however I guess I need to configure it in uboot headers.
Setting these settings manually to mmc0, I can boot now, however "iminfo" still doesn't understand zImage.
Thank you
2 Replies
07-13-2021
09:41 PM
1,303 Views
abdullahkahrama
Contributor IV
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems like clue to the problem lays here:
mmcdev=1
mmcpart=1
mmcroot=/dev/mmcblk1p2 rootwait rw I am using mmc0 in my design, however I guess I need to configure it in uboot headers.
Setting these settings manually to mmc0, I can boot now, however "iminfo" still doesn't understand zImage.
Thank you
07-13-2021
09:50 AM
1,312 Views
JohnKlug
Senior Contributor I
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My system boots, and imi also gives me unknown image format. I am using raw nand and ubifs with a zImage.
=>printenv loadaddr
loadaddr=0x80800000
=> printenv bootcmd
bootcmd=run t_root;ubifsmount ubi0;ubifsload ${loadaddr} /boot/zImage;ubifsload ${fdt_addr} /boot/mtcap3.dtb;if test ${tee} = yes; then ubifsload ${tee_addr} /boot/uTee-6ullevk;bootm ${tee_addr} - ${fdt_addr};else bootz ${loadaddr} - ${fdt_addr};fi
=> ubifsmount ubi0
=> ubifsload ${loadaddr} /boot/zImage
Loading file '/boot/zImage' to addr 0x80800000...
Done
=> imi ${loadaddr}
## Checking Image at 80800000 ...
Unknown image format!
=> md $loadaddr 8
80800000: e1a00000 e1a00000 e1a00000 e1a00000 ................
80800010: e1a00000 e1a00000 e1a00000 e1a00000 ................
Does imi in U-Boot understand zImage? Maybe it only understands uImage?
