Board won't flash

Tristan_Phillips · July 30, 2014, 5:22pm

Can anyone help figure out what is going wrong here?

mmc1: new high speed MMC card at address 0001
[ 10.497469] mmcblk1: mmc1:0001 MMC02G 1.78 GiB
[ 10.502697] mmcblk1boot0: mmc1:0001 MMC02G partition 1 1.00 MiB
[ 10.509831] mmcblk1boot1: mmc1:0001 MMC02G partition 2 1.00 MiB
[ 10.518332] mmcblk1: unknown partition table
[ 10.524548] mmcblk1boot1: unknown partition table
[ 10.531366] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 10.540032] mmcblk1boot0: unknown partition table
[ 10.545638] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 10.557100] devtmpfs: mounted
[ 10.560585] Freeing init memory: 240K
[ 10.612364] usb 1-1.2: new high-speed USB device number 3 using musb-hdrc
[ 10.731178] usb 1-1.2: New USB device found, idVendor=148f, idProduct=5370
[ 10.738415] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 10.746055] usb 1-1.2: Product: 802.11 n WLAN
[ 10.750607] usb 1-1.2: Manufacturer: Ralink
[ 10.754990] usb 1-1.2: SerialNumber: 1.0
grep: /proc/cmdline: No such file or directory
[ 10.989176] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
[ 10.989176]
[ 10.998766] [] (unwind_backtrace+0x1/0x98) from [] (panic+0x5b/0x158)
[ 11.007319] [] (panic+0x5b/0x158) from [] (do_exit+0x5f5/0x674)
[ 11.015311] [] (do_exit+0x5f5/0x674) from [] (do_group_exit+0x27/0x6c)
[ 11.023950] [] (do_group_exit+0x27/0x6c) from [] (__wake_up_parent+0x1/0x18)
[ 11.033132] [] (__wake_up_parent+0x1/0x18) from [] (ret_fast_syscall+0x1/0x46)

RobertCNelson · July 30, 2014, 5:28pm

The problem is there: ^^^

Regards,

Tristan_Phillips · July 30, 2014, 5:35pm

Indeed, but why would this be happening?

3.8.13-bone62 is the version…

RobertCNelson · July 30, 2014, 5:43pm

Considering i haven't released any 'flasher' images with that kernel.
You are obviously doing something on your own to create a custom
image. Since I don't have a crystal ball.

Tell us what you are doing...

Otherwise, how are we sup-post to help?

Regards,

Tristan_Phillips · July 30, 2014, 5:51pm

OK, here goes

Downloaded BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb and flashed to SD card

RobertCNelson · July 30, 2014, 6:11pm

OK, here goes

Downloaded BBB-eMMC-flasher-ubuntu-14.04-console-armhf-2014-07-06-2gb and
flashed to SD card

git clone GitHub - RobertCNelson/bb-kernel
cd bb-kernel/
git checkout origin/am33x-v3.8 -b tmp
./build_kernel.sh

Deselected TI ethernet drivers in the menuconfig. Thats all.
Waited for build to complete.
tools/install_kernel.sh

So, at this point, you've removed the "initrd.img" from the flasher
microSD card...

Waited for copy
Ejected and inserted into BBB
Attempted boot
Cried
Posted asking for help

The "flasher" relies on a lot of things to be setup properly. By
removing one, it falls apart like a house of cards..

Regards,

RobertCNelson · July 30, 2014, 6:13pm

If all you are doing is testing kernel options.. Ignore the eMMC
(infact clear it out: sudo dd if=/dev/zero of=/dev/mmcblk1)

Then just use the microSD image and update the kernel like above..

Once you get your microSD working just right, we can talk again about
the "flasher"...

Regards,

Tristan_Phillips · July 30, 2014, 6:38pm

Brilliant, I was just about to ask that. So I have my kernel build honed now, and can get our board without ethernet booting by removing the TI drivers, there are other kernel options I will play with later.

So, to sort out a flasher, or use a non flasher as a flasher, even manually? (I have had no luck simply touching the trigger file…)

Much appreciated

RobertCNelson · July 30, 2014, 6:46pm

It's no longer triggered. Instead it's ran in single user mode on
startup: cmdline= init=xyz.

Thus it's much more reliable.

But much funner to debug. You need a serial connection, and you need
to understand what it's expecting along with what it is doing.

https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v2.sh

Regards,

Tristan_Phillips · July 30, 2014, 6:55pm

OK, cool. I’m using a serial connection. So to clarify we are talking about how to make a non flasher image flash to the internal NAND. Great

So just xyz, literally?

Awesome I’ll try that and let you know how I get on in the morning. It’s beer time here across the pond

Thanks as always.

RobertCNelson · July 30, 2014, 6:57pm

OK, cool. I'm using a serial connection. So to clarify we are talking
about how to make a non flasher image flash to the internal NAND. Great

Not sure what we are talking about...

So just xyz, literally?

fingers are lazy...

github.com

RobertCNelson/omap-image-builder/blob/master/tools/setup_sdcard.sh#L741


      
          			conf_boot_endmb=${conf_boot_endmb:-"96"}
          			conf_boot_fstype=${conf_boot_fstype:-"fat"}
          			partition_one_fstype=${partition_one_fstype:-"0xE"}
          			sfdisk_partition_layout
          		else
          			if [ "x${uboot_efi_mode}" = "xenable" ] ; then
          				conf_boot_endmb="16"
          				conf_boot_fstype="fat"
          				partition_one_fstype="U"
          				BOOT_LABEL="EFI"
          				sfdisk_partition_layout
          			else
          				sfdisk_single_partition_layout
          				media_rootfs_partition=1
          			fi
          		fi
          		;;
          	no_bootloader_single_partition)
          		bypass_bootup_scripts="enable"
          		echo "No Bootloader, Single Partition"
          		echo "-----------------------------"

Awesome I'll try that and let you know how I get on in the morning.
It's beer time here across the pond

Regards,

Tristan_Phillips · July 30, 2014, 7:00pm

OK, thanks. At least I have a plan and some things to try in the morning

Tristan_Phillips · July 31, 2014, 10:09am

OK, so my board is working well running off the SD card (non ‘flasher’ with a patched 3.8.13-bone62).

Changing the cmdline to init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v2.sh causes:

grep: /proc/cmdline: No such file or directory

So the script is failing here: https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v2.sh#L34

I guess there is more to making a non flashing image a flashing one. perhaps I could just flash the eMMC manually?

Any clues?

Tristan_Phillips · August 1, 2014, 12:09pm

Hi Robert,

I’m starting to worry I will never get this image to the eMMC. Can you help?

Sorry to nag…

Tristan_Phillips · August 1, 2014, 1:02pm

So I booted off the patched SD card, cd to /opt/scripts and did a git pull.
I commented out the cmdline check and ran tools/eMMC/init-eMMC-flasher-v2.sh
Seemed to work fine, but the board stalls on boot from the eMMC, no error, no panic, just stops. Great.
I’m guessing the scripts needs to be run from boot. Can’t do that though as I get the /proc/cmdline error.

Rock ----> ME <---- Hard place

RobertCNelson · August 1, 2014, 1:21pm

On your microSD, what are the contents of /boot/uEnv.txt

Regards,

Tristan_Phillips · August 1, 2014, 1:56pm

uname_r=3.8.13-bone62
#dtb=
#cmdline=quiet
cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v2.sh
optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN capemgr.enable_partno=BB-BONE-AUDI-TE

RobertCNelson · August 1, 2014, 2:03pm

Run this first..

sudo update-initramfs -c -k `uname -r`

to regenerate /boot/initrd.img-`uname -r`

Then reboot with the flashing cmdline enabled..

Regards,

Tristan_Phillips · August 1, 2014, 2:20pm

The flash is running!!! Fingers crossed!

Thank you SO MUCH.

Tristan_Phillips · August 1, 2014, 2:34pm

Yep, that worked 100%!!!

Thanks again! To help other people I have updated a blog post I already had with all this:
http://trisblog.tumblr.com/post/87884207700/patch-the-bbb-kernel-on-a-non-flashing-sd-card-for