Beaglebone Black doesn’t boots up with the yocto-image
I am working on yocto-project to create images for BBB.I cloned the project git clone -b pyro git://git.yoctoproject.org/poky then initiated the build process. Baked it with bitbake core-image-sato and got the build directory with files. I created 2 partitions on SD card with 64M for root and rest(15+GB) for boot. Copied MLO and u-boot-beaglebone.img to the root partition . Untared the core-image-sato-beaglebone.tar.bz2 on root partition and then copied zImage-beaglebone.bin, zImage-am335x-bone.dtb, zImage-am335x-boneblack.dtb under boot partition. When I tried to boot BBB found that u-boot expects uEnv.txt and get stuck there. The yocto build directory doesn’t have any uEnv.txt, so how to write own uEnv.txt ? This is the u-boot prompt. Hit any key to stop autoboot: 0 gpio: pin 53 (gpio 53) value is 1 mmc0 is current device micro SD card found mmc0 is current device gpio: pin 54 (gpio 54) value is 1 SD/MMC found on device 0 reading uEnv.txt ** Unable to read file uEnv.txt ** gpio: pin 55 (gpio 55) value is 1 ** File not found /boot/uImage ** U-Boot# I added uEnv.txt in root partition with text as mmcdev=0 mmcpart=1 bootpart=0:1 This time u-boot tries to read a uImage from /boot directory but I have zImage whats this conflict now? How should I resolve it? SD/MMC found on device 0 reading uEnv.txt 32 bytes read in 4 ms (7.8 KiB/s) Loaded environment from uEnv.txt Importing environment from mmc . gpio: pin 55 (gpio 55) value is 1 reading /boot/uImage ** Unable to read file /boot/uImage ** U-Boot#
@h0ch5tr4355 so you mean to say its mandatory to convert zImage in uImage and u-Boot can’t load zImages ? And what about zImage-am335x-boneblack.dtb, zImage-am335x-bone.dtb, zImage-beaglebone.bin do I have to convert them too?
I followed the step mentioned in the link above. This time u-Boot goes in a infinite loop while reading the uImage data abort pc : [<9f376478>] lr : [] sp : 9f238060 ip : 9f238090 fp : 00000da1 r10: 00000080 r9 : 00000200 r8 : 9f238f40 r7 : 00000000 r6 : 00564a00 r5 : 00000020 r4 : 48060100 r3 : 00000000 r2 : 56190527 r1 : 00000da2 r0 : 00000001 Flags: Nzcv IRQs off FIQs on Mode SVC_32 Resetting CPU . resetting .
Booting kernel from SD in qemu (ARM) with u-boot
I’m quite new to embedded systems and I’m playing around with ARM on qemu. So I’ve run into problem booting linux kernel image from an emulated SD on versatile express with cpu cortex-a9. I prepared everything in the following order: first, I’ve built the kernel with vexpress_defconfig using appropriate ARM toolchain. Then I’ve built u-boot with vexpress_ca9x4_defconfig . Everything went just fine. The linux kernel source I took is at version 4.13 (latest stable from git). U-boot version is 2017.09-00100. Then I prepared an SD image:
dd if=/dev/zero of=sd.img bs=4096 count=4096 mkfs.vfat sd.img mount sd.img /mnt/tmp -o loop,rw cp kernel/arch/arm/boot/zImage /mnt/tmp umount /mnt/tmp qemu-system-arm -machine vexpress-a9 -cpu cortex-a9 -m 128M -dtb kernel/arch/arm/boot/dts/vexpress-v2p-ca9.dtb -kernel uboot/u-boot -sd sd.img -nographic => mmcinfo Device: MMC Manufacturer ID: aa OEM: 5859 Name: QEMU! Tran Speed: 25000000 Rd Block Len: 512 SD version 1.0 High Capacity: No Capacity: 16 MiB Bus Width: 1-bit Erase Group Size: 512 Bytes fatload mmc 0:0 0x4000000 zImage => fatload mmc 0:0 0x4000000 zImage reading zImage 3378968 bytes read in 1004 ms (3.2 MiB/s) => bootz 0x4000000 Bad Linux ARM zImage magic! uboot/tools/mkimage -A arm -C none -O linux -T kernel -d kernel/arch/arm/boot/Image -a 0x00010000 -e 0x00010000 uImage also trying out -C gzip on zImage and different load/entry addresses, to no avail. The images were copied to sd.img . When I fatload the image and check it with iminfo , whichever options I try, I constantly get error:
=> iminfo 0x4000000 ## Checking Image at 04000000 . Unknown image format! I’m totally confused and this problem drives me nuts, while information on this subject in Internet is rather scarce. Please, hint me what I’m doing wrong and redirect into right direction. qemu in use is QEMU emulator version 2.9.0 .
Saved searches
Use saved searches to filter your results more quickly
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad Linux ARM zImage magic! #46
Bad Linux ARM zImage magic! #46
Comments
I have a problem about migrate xml file to uuu script.
according to the wiki «migration from ucl2.xml to uuu script»
I converted my xml file to uuu script, but when I run » ./uuu my_uuu_script »
the minicom display «Bad Linux ARM zImage magic!».
when I use mfgtool on windows, it runs ok, I don’t know if there are some env parameters related to mfgtool that not be set. or just the problem about kernel.
uuu_version 1.0.1 SDP: boot -f firmware/uboot-myimx6ek200-6q.imx FB: ucmd echo boot from uboot FB: ucmd setenv fastboot_buffer $ FB: ucmd download -f firmware/mfg-zImage-myimx6 FB: ucmd setenv fastboot_buffer $ FB: ucmd download -f firmware/initramfs-imx_mfgtools.cpio.gz.u-boot FB: ucmd setenv fastboot_buffer $ FB: ucmd download -f firmware/myimx6ek200-6q.dtb FB: acmd booti $ $ $ FBK: ucmd flash_erase /dev/mtd0 0 0 FBK: ucp files/uboot-myimx6ek200-6q.imx t:/tmp FBK: ucmd dd if=/tmp/uboot-myimx6ek200-6q.imx of=/dev/mtd0 bs=512 seek=2 FBK: ucp firmware/mksdcard-31452.sh.tar t:/tmp FBK: ucmd tar xf /tmp/uboot-myimx6ek200-6q.imx FBK: ucmd sh mksdcard.sh /dev/mmcblk3 FBK: ucmd mkfs.vfat /dev/mmcblk3p1 FBK: ucmd mkdir -p /mnt/mmcblkxp1 FBK: ucmd mount -t vfat /dev/mmcblk3p1 /mnt/mmcblkxp1 FBK: ucp files/zImage-myimx6 t:/tmp FBK: ucmd cp /tmp/zImage-myimx6 /mnt/mmcblkxp1/zImage-myimx6 FBK: ucp myimx6ek200-6q.dtb t:/tmp FBK: ucmd cp /tmp/myimx6ek200-6q.dtb /mnt/mmcblkxp1/myimx6ek200-6q.dtb FBK: ucmd umount /mnt/mmcblkxp1 FBK: ucmd mkfs.ext3 -j /dev/mmcblk3p2 FBK: ucmd mkdir -p /mnt/mmcblkxp2 FBK: ucmd mount -t ext3 /dev/mmcblk3p2 /mnt/mmcblkxp2 FBK: acmd pipe tar -jxv -C /mnt/mmcblkxp2 FBK: ucp files/armhf-rootfs-ubuntu-xenial.tar.bz2 t:- FBK: sync FBK: acmd pipe tar -jxv -C /mnt/mmcblkxp2 FBK: ucp files/kernel-modules-myimx6.tar.bz2 t:- FBK: sync FBK: acmd pipe tar -jxv -C /mnt FBK: ucp files/myzr_rtfs_cfg.tar.bz2 t:- FBK: sync FBK: ucmd sh /mnt/myzr_rtfs_cfg.sh /mnt/mmcblkxp2 myimx6ek200 armhf-rootfs-ubuntu-xenial.tar.bz2 normal FBK: sync FBK: acmd pipe tar -jxv -C /mnt/mmcblkxp2 FBK: ucp files/l31452_rtfs_update.tar.bz2 t:- FBK: sync FBK: acmd pipe tar -jxv -C /mnt/mmcblkxp2/home/root FBK: ucp files/my-demo.tar.bz2 t:- FBK: sync FBK: ucmd umount /mnt/mmcblkxp2 FBK: ucmd echo Update Complete! U-Boot 2015.04-svn86 (Aug 09 2017 - 10:21:01) CPU: Freescale i.MX6Q rev1.5 at 792 MHz CPU: Temperature 44 C Reset cause: POR Board: MYZR i.MX6 Evaluation Kit Model: MY-IMX6-EK200-6Q-1G I2C: ready DRAM: 1 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 SF: Detected SST25VF016B with page size 256 Bytes, erase size 4 KiB, total 2 MiB *** Warning - bad CRC, using default environment No panel detected: default to Hannstar-XGA Display: Hannstar-XGA (1024x600) In: serial Out: serial Err: serial Net: FEC [PRIME] Boot from USB for mfgtools Use default environment for mfgtools Run bootcmd_mfg: run mfgtool_args; bootz $ $ $; Hit any key to stop autoboot: 0 Bad Linux ARM zImage magic! The text was updated successfully, but these errors were encountered: