Custom images stop working eventually

Hello there,
As for the beggining, ill say that this problem never occured on the beaglebone black image shipped with rev C board. Today I installed the never version for rev C and after that the console version from elinux.org. In both situations after the n reebot, the system didnt want to boot. On the screen I only see the linux penguin image and nothing happends. Only the usr0 led blinks in a loop like schema. I would really aprichiate any help in here, why do those images break? I have shutdown the system correctly every time.

Hello there,
As for the beggining, ill say that this problem never occured on the beaglebone black image shipped with rev C board. Today I installed the never version for rev C and after that the console version from elinux.org. In both situations after the n reebot, the system didnt want to boot. On the screen I only see the linux penguin image and nothing happends. Only the usr0 led blinks in a loop like schema. I would really aprichiate any help in here, why do those images break? I have shutdown the system correctly every time.

A ‘cylon’ loop? Aka is flashing…

Im sorry, but I didnt get it :P. This state doesnt end, even after another reboot its all the same. I have to reflash the eMMC

Im sorry, but I didnt get it :P. This state doesnt end, even after another reboot its all the same. I have to reflash the eMMC

Ah take out the ‘flashing’ microsd…

Of course I did.

Of course I did.

Tell us step by step what you actually did. It’s too early for me to guess.

I really did nothing extra ordinary. I just added some scripts (like the one for usb0 network to work from previous topic), added the script for power button to work. After some reboot it just stopped working. Maybe its the power button script thing, but I cant think of why.

On the other hand, on one of the images power button was working correctly, so it has to be something else.

it kinda sounds like you somehow enabled the "flasher" on the eMMC..
Specially if it's doing the cylon patern, the only way to prove it,
would be to connect up a usb serial adapter and see what it's doing.

Regards,

I think I got one, ill try to connect it. Will the data on serial port pop out of the blue, or does that also need some additional initialisations?

W dniu 2014-09-30 13:51, Robert Nelson pisze:

It's setup for serial debugging by default:

115200 8 n 1

Regards,

Ok I have discovered what cause the image to fail to boot. I have added the automount of the 100MB usb space to fstab. After this operation image wont boot anymore. Im not quite sure what have i set wrong, this is the line i have added:

/dev/mmcblk0p1 /boot/uboot/ fat16 defaults 0 0

I have mounted this the same manually before the fstab edit and it worked great. What is the deal here?

W dniu 2014-09-30 13:58, Robert Nelson pisze:

Well by default the 200Mb "Console" is just a single ext4 partition...
So if you were to add that to the current image, it would get stuck on
bootup and spew lots of errors over serial about a missing partition.

Regards,

But why can I mount it by hand then without any problems?

I doubt it's really mounting what you think it's mounting..

Regards,

Well after the mount I am abble to acces the content on the 100MB space, and that the functionality i need- to be abble to put files there over usb and use on beaglebone.
Can you suggest any solution?

Hello Robert,
I think what you said its right… When I enter the mounted directory, it does reflect the files I see on the mounted USB partition. However, When I create a new file in there, it does not appear on the USB drive nor the location in console… I Cant really tell whats happening. After dfing I can see the location mounter correctly:

root@beaglebone:/boot/uboot# df
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 3553816 251864 3118096 8% /
udev 10240 0 10240 0% /dev
tmpfs 101692 440 101252 1% /run
/dev/disk/by-uuid/7505a30a-815a-441f-96ee-e62f7d07e547 3553816 251864 3118096 8% /
tmpfs 254224 0 254224 0% /dev/shm
tmpfs 254224 0 254224 0% /sys/fs/cgroup
tmpfs 102400 0 102400 0% /run/user
tmpfs 5120 0 5120 0% /run/lock
/dev/mmcblk0p1 98094 63236 34858 65% /boot/uboot

If as you said this isnt really mounted, is there a way to create a separate partition for the virtual usb space? I already aprichiate all your help, but this is the last step for my image to have everything i need in 100%.

Hello there,
I have connected the debug cable, heres the output:

U-Boot SPL 2014.10-rc2-00017-g621bc23 (Sep 04 2014 - 19:58:48)

U-Boot 2014.10-rc2-00017-g621bc23 (Sep 04 2014 - 19:58:48), Build: jenkins-github_Bootloader-Builder-22

Watchdog enabled
I2C: ready
DRAM: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

Net: not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 0
gpio: pin 53 (gpio 53) value is 1
Card did not respond to voltage select!
Card did not respond to voltage select!
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
switch to partitions #0, OK
mmc1(part 0) is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 1
Checking for: /uEnv.txt …
Checking for: /boot.scr …
Checking for: /boot/boot.scr …
Checking for: /boot/uEnv.txt …
gpio: pin 55 (gpio 55) value is 1
764 bytes read in 21 ms (35.2 KiB/s)
Loaded environment from /boot/uEnv.txt
Checking if uname_r is set in /boot/uEnv.txt…
gpio: pin 56 (gpio 56) value is 1
Running uname_boot …
loading /boot/vmlinuz-3.8.13-bone64 …
5605264 bytes read in 377 ms (14.2 MiB/s)
loading /boot/dtbs/3.8.13-bone64/am335x-boneblack.dtb …
26098 bytes read in 30 ms (848.6 KiB/s)
loading /boot/initrd.img-3.8.13-bone64 …
2282569 bytes read in 150 ms (14.5 MiB/s)
debug: [console=ttyO0,115200n8 root=UUID=49a3b628-4d8e-4a0f-b159-bd265e36a9df ro rootfstype=ext4 rootwait fixrtc quiet init=/lib/systemd/systemd] …
debug: [bootz 0x82000000 0x88080000:22d449 0x88000000] …
Kernel image @ 0x82000000 [ 0x000000 - 0x558790 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Ramdisk to 8fdd2000, end 8ffff449 … OK
Loading Device Tree to 8fdc8000, end 8fdd15f1 … OK

Starting kernel …

Uncompressing Linux… done, booting the kernel.
[ 0.338513] omap2_mbox_probe: platform not supported
[ 0.493476] tps65217-bl tps65217-bl: no platform data provided
[ 0.553819] bone-capemgr bone_capemgr.9: slot #0: No cape found
[ 0.590929] bone-capemgr bone_capemgr.9: slot #1: No cape found
[ 0.628036] bone-capemgr bone_capemgr.9: slot #2: No cape found
[ 0.665145] bone-capemgr bone_capemgr.9: slot #3: No cape found
[ 0.680842] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.45 (#5:BB-BONELT-HDMI)
[ 0.690402] bone-capemgr bone_capemgr.9: slot #6: Failed verification
[ 0.697136] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)
[ 0.713682] omap_hsmmc mmc.5: of_parse_phandle_with_args of ‘reset’ failed
[ 0.776740] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8
[ 0.788424] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22
[ 0.795694] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single
Loading, please wait…
systemd-fsck[201]: rootfs: clean, 12849/111104 files, 77267/444160 blocks
Welcome to emergency mode. Use “systemctl default” or ^D to enter default mode.

Then I enter systemctl default to enter the prompt. I comment the fstab entry adn everything works again. I tried to read into your script, I found the place where the partition is created:

if [ “x${bborg_production}” = “xenable” ] ; then
conf_boot_endmb=“96”
conf_boot_fstype=“fat”
sfdisk_fstype=“0xE”
sfdisk_partition_layout
else
sfdisk_single_partition_layout
media_rootfs_partition=1
fi

You said that everything is stored on a single partition in this image, while it looks like there is a second one in fat16 for the usb. Im not sure either I understand this correctly, if this is a single partition, how can i create a separate one for the usb? I would really aprichiate your help.

The "console" is a single parition setup.. if you want the first
"100Mb" fat partition pass: --beagleboard.org-production or create the
partition layout yourself.

Regards,

Thats the point, I did pass the --beagleboard.org-production