element14 vs Circuitco Rev C

Hello!

I have 5 BBB RevC from element14.
Now I get 10 BBB from Circuitco, also Rev C.

The shock:
When I flash my own Image, where I made for the BBB and running on element14 Rev C, on the new BBB … the flash starts … ends … and the BBB are not booting.
Only the Power LED are on, all USR LED are off and never getting on.

Both Images has with:

cat /etc/dogtag

BeagleBoard.org Debian Image 2015-03-01

So, the Image is the same!

Has someone an idea, why it not booting?

When insert MY image uSD and I debug with holding Button S2:
U-Boot 2013.04 (Sep 25 2013 - 00:49:30)<\r><\n>
<\r><\n>
I2C: ready<\r><\n>
DRAM: 512 MiB<\r><\n>
WARNING: Caches not enabled<\r><\n>
NAND: No NAND device found!!!<\r><\n>
0 MiB<\r><\n>
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1<\r><\n>
*** Warning - readenv() failed, using default environment<\r><\n>
<\r><\n>
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)<\r><\n>
musb-hdrc: MHDRC RTL version 2.0 <\r><\n>
musb-hdrc: setup fifo_mode 4<\r><\n>
musb-hdrc: 28/31 max ep, 16384/16384 memory<\r><\n>
USB Peripheral mode controller at 47401000 using PIO, IRQ 0<\r><\n>
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)<\r><\n>
musb-hdrc: MHDRC RTL version 2.0 <\r><\n>
musb-hdrc: setup fifo_mode 4<\r><\n>
musb-hdrc: 28/31 max ep, 16384/16384 memory<\r><\n>
USB Host mode controller at 47401800 using PIO, IRQ 0<\r><\n>
Net: not set. Validating first E-fuse MAC<\r><\n>
cpsw, usb_ether<\r><\n>
Hit any key to stop autoboot: 1 <\b><\b><\b> 0 <\r><\n>
mmc0 is current device<\r><\n>
SD/MMC found on device 0<\r><\n>
reading uEnv.txt<\r><\n>
236 bytes read in 4 ms (57.6 KiB/s)<\r><\n>
Loaded environment from uEnv.txt<\r><\n>
Importing environment from mmc …<\r><\n>
Running uenvcmd …<\r><\n>
reading uImage<\r><\n>
11748096 bytes read in 1343 ms (8.3 MiB/s)<\r><\n>
reading /am335x-boneblack.dtb<\r><\n>
24884 bytes read in 9 ms (2.6 MiB/s)<\r><\n>

Booting kernel from Legacy Image at 80200000 …<\r><\n>

Image Name: Linux-3.8.13<\r><\n>
Image Type: ARM Linux Kernel Image (uncompressed)<\r><\n>
Data Size: 11748032 Bytes = 11.2 MiB<\r><\n>
Load Address: 80008000<\r><\n>
Entry Point: 80008000<\r><\n>
Verifying Checksum … OK<\r><\n>

Flattened Device Tree blob at 81ff0000<\r><\n>

Booting using the fdt blob at 0x81ff0000<\r><\n>
Loading Kernel Image … OK<\r><\n>
OK<\r><\n>
Using Device Tree in place at 81ff0000, end 81ff9133<\r><\n>
<\r><\n>
Starting kernel …<\r><\n>
<\r><\n>
Uncompressing Linux… done, booting the kernel.<\r><\n>
[ 1.368876] omap2_mbox_probe: platform not supported<\r><\n>
[ 1.379850] tps65217-bl tps65217-bl: no platform data provided<\r><\n>
[ 1.455982] bone-capemgr bone_capemgr.9: slot #0: No cape found<\r><\n>
[ 1.493088] bone-capemgr bone_capemgr.9: slot #1: No cape found<\r><\n>
[ 1.530196] bone-capemgr bone_capemgr.9: slot #2: No cape found<\r><\n>
[ 1.567305] bone-capemgr bone_capemgr.9: slot #3: No cape found<\r><\n>
[ 1.594091] omap_hsmmc mmc.5: of_parse_phandle_with_args of ‘reset’ failed<\r><\n>
[ 1.659493] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8<\r><\n>
[ 1.671200] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22<\r><\n>
[ 1.678514] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single

HERE the power LED is going off and stop!

Thank you for help!

disable "quiet" in your boot args so we get the full kernel log. :wink:

It'll be much longer so use pastebin.com

Regards,

Please give me a hint, where the boot args are.

btw: The BBB stop working after the log:
[ 1.671200] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22<\r><\n>
[ 1.678514] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single

The BBB shut down(?) … Power LED off … so after this lines is no more log available.

Thank you!

Please give me a hint, where the boot args are.

mmc0 is current device<\r><\n>
SD/MMC found on device 0<\r><\n>
reading uEnv.txt<\r><\n>
236 bytes read in 4 ms (57.6 KiB/s)<\r><\n>
Loaded environment from uEnv.txt<\r><\n>
Importing environment from mmc ...<\r><\n>
Running uenvcmd ...<\r><\n>
reading uImage<\r><\n>

Well...
"uEnv.txt"....

btw: The BBB stop working after the log:
[ 1.671200] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
-22<\r><\n>
[ 1.678514] pinctrl-single 44e10800.pinmux: could not request pin 21 on
device pinctrl-single

The BBB shut down(?) ... Power LED off ... so after this lines is no more
log available.

Sorry, had to return my magic crystal ball, please disable "quiet" in
"uEnv.txt" and post the full log to pastebin.com first..

Regards,

Thank you!

I´m able to boot the BBB from Circuitco from uSD and flash the eMMC with my image:
http://pastebin.com/NwxFPXRZ

After finished, the BBB are not booting. Only Power LED is on, no User LED.
I just get as debug in Hex:
1B 00 43 43 43 43 43 43 43 43 43 43 43 43 43 43 43 43
I hear only at windows that something are doing on the USB (when connecting USB device).

When I boot from a element14 BBB, where I succesfully write the image, I have this log:
http://pastebin.com/MUXcWYLD

When I boot the BBB from Circuitco with a downloaded uSD Image, I have this:
http://pastebin.com/XbMi1uaY
(here I found no quit argument on uEnv.txt)

My question is now:
Why work my own image on the element14 RevC BBB but not on the Circuitco BBB?

Thank you!

Sounds like the Element14 product is different.

Gerald

Hello Gerald,

yes, I also think this … but this is bad for me.
I thought that BBB RevC = BBB RevC :frowning:

Maybe someone know who is different and maybe I can optimize my own image?

Thanks!

From your logs:
BBB circuitCOKernel command line: console=ttyO0,115200n8 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

Element14:
Kernel command line: console=ttyO0,115200n8 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN root=UUID=319a7dc6-9ece-408a-877f-f7c38bebb825 ro rootfstype=ext4 rootwait fixrtc init=/lib/systemd/systemd

Are you sure that everuthing is the same? I doubt it

Hello!

the element14 version has my own image (what I optimize for me)
the Circuitco version has the original image

But I want to use my image also on the Circuitco version.
I always thought that BBB RevC = BBB RevC

Thank you!

In the meantime I flash the eMMC with the original Debian Image:
Log: http://pastebin.com/HsWXZRC9

Did someone know, where is the problem when only the Power LED is on … the USR Led´s are never going on or flash, when I flash my image on the eMMC

Hello!

the element14 version has my own image (what I optimize for me)
the Circuitco version has the original image

But I want to use my image also on the Circuitco version.
I always thought that BBB RevC = BBB RevC

They are..

Thank you!

In the meantime I flash the eMMC with the original Debian Image:
Log: http://pastebin.com/HsWXZRC9

Both boards have different versions of u-boot in the eMMC, make sure
you flash the same image to the eMMC..

Did someone know, where is the problem when only the Power LED is on ... the
USR Led´s are never going on or flash, when I flash my image on the eMMC

Well, grab a usb-serial adapter, connect it to the debug port and find
out why...

Regards,

Hello!

the element14 version has my own image (what I optimize for me)
the Circuitco version has the original image

But I want to use my image also on the Circuitco version.
I always thought that BBB RevC = BBB RevC

They are..

I have seen people have issues with images too big for a particular eMMC. You can tell with a serial cable by an error message or in the flashing process by a failed attempt.

Part number?

Gerald

#Micron 3744MB (bbb): 3925868544 bytes -> 3925.86 Megabyte
#Kingston 3688MB (bbb): 3867148288 bytes -> 3867.15 Megabyte

Only an issue for "dd" flashing.. :wink:

Regards,

Sounds like we need to move to 8G.

Gerald

Hi!

Maybe I found a problem. I put my Image on the uSD and flash again. The Log:
http://pastebin.com/HiZR9USh

Here I see now:

Running /dev/mmcblk0p1/autorun.sh…<\r><\n>
dd: writing ‘/dev/mmcblk1’: No space left on device<\r><\n>
0+115617 records in<\r><\n>
0+115616 records out<\r><\n>
[ 373.638162] EXT3-fs (mmcblk1p2): error: couldn’t mount because of unsupported optional features (240)<\r><\n>
[ 373.649135] EXT2-fs (mmcblk1p2): error: couldn’t mount because of unsupported optional features (244)<\r><\n>
[ 373.660107] EXT4-fs (mmcblk1p2): bad geometry: block count 933632 exceeds size of device (909056 blocks)<\r><\n>
[ 373.673511] F2FS-fs (mmcblk1p2): Magic Mismatch, valid(0xf2f52010) - read(0x39180)<\r><\n>
[ 373.681473] F2FS-fs (mmcblk1p2): Can’t find a valid F2FS filesystem<\r><\n>
mount: mounting /dev/mmcblk1p2 on /mnt failed: Invalid argument<\r><\n>
/etc/init.d/S99autorun: /mnt/autorun.sh: line 12: ed: not found<\r><\n>
umount: can’t umount /mnt: Device or resource busy<\r><\n>
<\r><\r><\n>
Welcome to Buildroot<\r><\n>
<\r>beaglebone login:

This mean the eMMC is to small??
I made the Image from the element14 BBB with:
#!/bin/sh
echo timer > /sys/class/leds/beaglebone:green:usr0/trigger

#un-comment the following line to perform a backup
#dd if=/dev/mmcblk1 bs=16M | gzip -c > /mnt/BBB-eMMC-$RANDOM.img.gz

#un-comment the following 6 lines to perform a restore (be sure to replace XXXXX with your image name)
gunzip -c /mnt/BBB-eMMC-2510.img.gz | dd of=/dev/mmcblk1 bs=16M
UUID=$(/sbin/blkid -c /dev/null -s UUID -o value /dev/mmcblk1p2)
mkdir -p /mnt
mount /dev/mmcblk1p2 /mnt
ed -i “s/^uuid=.*$/uuid=$UUID/” /mnt/boot/uEnv.txt
umount /mnt

sync
echo default-on > /sys/class/leds/beaglebone:green:usr0/trigger

(of course comment the correct lines)

Can someone confirm this?
And when yes … why I was able to flash the element14 BBB?

Thanks to ALL!

Looks like you missed a response.

Gerald

Yes, relying on "all" 4GB eMMC's to be 100% the same size is not a
good "backup/flash" design.

This is why the official images use rsync and not dd..

Here are 3 of the eMMC's used for bbb's..

#Micron 3744MB: 3925868544 bytes -> 3925.86 Megabyte
#Kingston 3688MB: 3867148288 bytes -> 3867.15 Megabyte
#Kingston 3648MB: 3825205248 bytes -> 3825.21 Megabyte

All "sold" ad 4GB models.. When crafting a *.img i usually assume
"80%" of advertised space to play it safe..

Regards,

Keep in mind that NAND has bad sectors. That is why they use NAND controllers. NAND size will vary from one part to another.

Gerald

Ok, the good thing is: now we know where the problem is

But …

How can I backup from element14 to Circuitc?

I used this:
http://elinux.org/BeagleBone_Black_Extracting_eMMC_contents

Thank you!

I found this:
https://github.com/RobertCNelson/tools/blob/master/scripts/beaglebone-black-copy-eMMC-to-microSD.sh

But get errors:
When I boot the element14 BBB with my image, insert after the usd and start local the script:
Error: script halting, system unrecognized…

When I use autorun and start with uSD:
Running /dev/mmcblk0p1/autorun.sh…<\r>
/etc/init.d/S99autorun: /mnt/autorun.sh: line 29: lsblk: not found<\r>
Error: script halting, system unrecognized…<\r>

Is this script good to backup and when yes, how can I use?

Thank you!