On Friday, September 27, 2013 9:11:20 AM UTC-6, Gerald wrote: > > We use the 9_4 Flasher image in production to flash all the production > boards. It is tested thousands of time a week. > > Can you verify that the file linked to from the wiki at https://s3.amazonaws.com/angstrom/demo/beaglebone/BBB-eMMC-flasher-2013.09.04.img.xz is **exactly** the same as the file used to build the production flasher SD cards?
The file I downloaded is BBB-eMMC-flasher-2013.09.04.img.xz and it is 373,850,348 bytes long with MD5 hash 6b551bf357339e98377dfb6f6fdba016. It is expanded by 7zip into an image file BBB-eMMC-flasher-2013.09.04.img which is 3,657,433,088 bytes long and has MD5 hash b45fcc0da3d797f6dc0fed3dde19d311. This image is copied (using the Win32DiskImager) to a 4GB SD card which boots the BBB and runs the emmc.sh script as expected, but the script consistently fails after about 5 minutes as explained in my previous post. The board stops with all user LEDs off because of errors detected by the emmc.sh script. Those errors are caused by missing files and directories in the archived rootfs, Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone.rootfs.tar.gz, contained in the /build directory of the Angstrom linux installed on the flasher SD card. I just completed another pass through the entire update process starting with the freshly downloaded compressed flasher image. It failed in the same way. After the emmc.sh script stopped I logged in using the serial debug cable and tried to expand the archived rootfs manually. I got an error about an invalid tar header checksum. root@beaglebone:~# cd /build root@beaglebone:/build# mkdir rootfs root@beaglebone:/build# tar -zxf Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone.rootfs.tar.gz -C rootfs tar: invalid tar header checksum root@beaglebone:/build# ls rootfs bin home media mnt sbin usr The directories created look the same as those listed in my previous post. I just repeated the tar listing again and go the same error. I must have missed it last time since I had redirected the output to a file, but the error message went to the console instead of the file. There is definitely a problem with the flasher image I downloaded. The archived rootfs is corrupt so it generates an incomplete rootfs in the eMMC. Dennis Cote -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
