dmorse Posted July 18, 2017 Posted July 18, 2017 Hi, I'm trying to build an image for the Orangepi Zero Plus 2 (H3) using the following instructions: https://docs.armbian.com/Developer-Guide_Build-Preparation/. After putting the produced image onto a microSD card using dd, I put the card into the board, connect the serial and power, and then seems to fail and drops me to the u-boot prompt. Here is the output of the terminal. U-Boot 2017.07-armbian (Jul 18 2017 - 16:01:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Zero Plus DRAM: 512 MiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: No ethernet found. Hit any key to stop autoboot: 0 38518 bytes read in 152 ms (247.1 KiB/s) Unknown command 'bmp' - try 'help' switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3565 bytes read in 188 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 115 bytes read in 150 ms (0 Bytes/s) ** File not found /boot/uInitrd ** 4833760 bytes read in 509 ms (9.1 MiB/s) Found legacy kernel configuration 35692 bytes read in 491 ms (70.3 KiB/s) Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3565 bytes read in 179 ms (18.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 115 bytes read in 150 ms (0 Bytes/s) ** File not found /boot/uInitrd ** 4833760 bytes read in 509 ms (9.1 MiB/s) Found legacy kernel configuration 35692 bytes read in 491 ms (70.3 KiB/s) Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found USB device 0: unknown device No ethernet found. missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/000 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/00 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/0 No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm-sunxi No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default-arm No ethernet found. missing environment variable: bootfile Retrieving file: pxelinux.cfg/default No ethernet found. Config file not found No ethernet found. No ethernet found. => I built this on a completely clean install of ubuntu 16.04 in a VirtualBox VM. I did an update an an upgrade before starting the instructions. The only bit I didn't do was the bit behind the vagrant link, because it was broken.
chwe Posted July 18, 2017 Posted July 18, 2017 13 minutes ago, dmorse said: After putting the produced image onto a microSD card using dd According to de getting started guide: Images shall only be written with Etcher on all platforms since unlike other tools Etcher validates burning results saving you from corrupted SD card contents. just to remove one possible problem.
StuxNet Posted July 19, 2017 Posted July 19, 2017 cyclic redundancy check 4 hours ago, dmorse said: Warning - bad CRC, using default environment I've never built my own kernel (I let Igor do that for me) but I know a bad 'hard drive' when I see one, from my computer repair days.BAD CRC = cyclic redundancy check error Make sure your SD card image writing software is 'approved' to work with armbian. ie: Etcher This is (as far as I know) the only Armbian 'approved' method. Likely because Etcher verifies the image after writing, by default. Whereas dd and Win32Disk Imager (uses dd) don't require verification, of what it just wrote. So..... bad SD card? Prove it is/isn't then come back asking for help. Otherwise, I've received bad CRC errors due to power cables going bad at pain points. I think. Might of been that I was writing using Win32 at the time xD IDK for sure because I immediately tried fixing both birds with one stone as opposed to troubleshooting individually. So double check that Power Supply if you haven't already. If you haven't already, see 0, 1 and 2 links in my signature. ;D 1
tkaiser Posted July 19, 2017 Posted July 19, 2017 3 hours ago, StuxNet said: BAD CRC = cyclic redundancy check error 'As expected' with u-boot: https://www.denx.de/wiki/DULG/WarningBadCRCUsingDefaultEnvironment
StuxNet Posted July 19, 2017 Posted July 19, 2017 On 7/18/2017 at 11:57 PM, tkaiser said: 'As expected' with u-boot: https://www.denx.de/wiki/DULG/WarningBadCRCUsingDefaultEnvironment MERP. My bad. Just going off what I've experienced and trying to insulate the devs from all the newbie mistakes I hear them complain about every time I turn around. Sorry I didn't catch that abscure https://www.denx.de post. Just doin my best. You're more than welcome to offer anything constructive and as a dev, you knoe you don't need my permission.
tkaiser Posted July 19, 2017 Posted July 19, 2017 15 minutes ago, StuxNet said: Sorry I didn't catch that abscure https://www.denx.de post All fine, just wanted to note that this specific message is as expected. The problems start later in the serial output.
Igor Posted July 19, 2017 Posted July 19, 2017 I believe this is (was) our bug: https://github.com/armbian/build/commit/ee693b4c4a917824ab80f0f72d365593e0ad5e1c 1
dmorse Posted July 19, 2017 Author Posted July 19, 2017 Yep that fixed it. Thanks for that. Now onto figuring out why this camera module does not work
Recommended Posts