ungureanuvladvictor / bbblfs Goto Github PK

the shipped uboot image currently does not ask for an address to be assigned via bootp/dhcp, but rather picks a 192.168.1.3 address and asks 192.168.1.9 for the itb image.

such a configuration would allow the itb image to be started and used easily without the need for any for the custom flashing software, for example with a (possibly network-manager launched) dnsmasq config like the following:

bootp-dynamic
enable-tftp
tftp-root=/opt/BBBlfs/bin
dhcp-vendorclass=set:want-spl,AM335x ROM
dhcp-vendorclass=set:want-uboot,AM335x U-Boot SPL
dhcp-boot=tag:want-spl,/spl
dhcp-boot=tag:want-uboot,/uboot

1 vagrant@vagrant:~/BBBlfs/bin⟫ sudo ./usb_flasher
*** Error in `./usb_flasher': double free or corruption (fasttop): 0x00000000006a6da0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f7e06ea07e5]
/lib/x86_64-linux-gnu/libc.so.6(+0x7fe0a)[0x7f7e06ea8e0a]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x4c)[0x7f7e06eac98c]
./usb_flasher[0x401705]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f7e06e49830]
./usb_flasher[0x4021e9]
======= Memory map: ========
00400000-00404000 r-xp 00000000 fc:00 1572124                            /home/vagrant/BBBlfs/bin/usb_flasher
00603000-00604000 r--p 00003000 fc:00 1572124                            /home/vagrant/BBBlfs/bin/usb_flasher
00604000-00605000 rw-p 00004000 fc:00 1572124                            /home/vagrant/BBBlfs/bin/usb_flasher
0068b000-006ca000 rw-p 00000000 00:00 0                                  [heap]
7f7e00000000-7f7e00021000 rw-p 00000000 00:00 0
7f7e00021000-7f7e04000000 ---p 00000000 00:00 0
7f7e05fed000-7f7e06003000 r-xp 00000000 fc:00 785431                     /lib/x86_64-linux-gnu/libgcc_s.so.1
7f7e06003000-7f7e06202000 ---p 00016000 fc:00 785431                     /lib/x86_64-linux-gnu/libgcc_s.so.1
7f7e06202000-7f7e06203000 rw-p 00015000 fc:00 785431                     /lib/x86_64-linux-gnu/libgcc_s.so.1
7f7e06203000-7f7e06204000 ---p 00000000 00:00 0
7f7e06204000-7f7e06a04000 rw-p 00000000 00:00 0
7f7e06a04000-7f7e06a0b000 r-xp 00000000 fc:00 785612                     /lib/x86_64-linux-gnu/librt-2.23.so
7f7e06a0b000-7f7e06c0a000 ---p 00007000 fc:00 785612                     /lib/x86_64-linux-gnu/librt-2.23.so
7f7e06c0a000-7f7e06c0b000 r--p 00006000 fc:00 785612                     /lib/x86_64-linux-gnu/librt-2.23.so
7f7e06c0b000-7f7e06c0c000 rw-p 00007000 fc:00 785612                     /lib/x86_64-linux-gnu/librt-2.23.so
7f7e06c0c000-7f7e06c24000 r-xp 00000000 fc:00 785625                     /lib/x86_64-linux-gnu/libpthread-2.23.so
7f7e06c24000-7f7e06e23000 ---p 00018000 fc:00 785625                     /lib/x86_64-linux-gnu/libpthread-2.23.so
7f7e06e23000-7f7e06e24000 r--p 00017000 fc:00 785625                     /lib/x86_64-linux-gnu/libpthread-2.23.so
7f7e06e24000-7f7e06e25000 rw-p 00018000 fc:00 785625                     /lib/x86_64-linux-gnu/libpthread-2.23.so
7f7e06e25000-7f7e06e29000 rw-p 00000000 00:00 0
7f7e06e29000-7f7e06fe8000 r-xp 00000000 fc:00 785619                     /lib/x86_64-linux-gnu/libc-2.23.so
7f7e06fe8000-7f7e071e8000 ---p 001bf000 fc:00 785619                     /lib/x86_64-linux-gnu/libc-2.23.so
7f7e071e8000-7f7e071ec000 r--p 001bf000 fc:00 785619                     /lib/x86_64-linux-gnu/libc-2.23.so
7f7e071ec000-7f7e071ee000 rw-p 001c3000 fc:00 785619                     /lib/x86_64-linux-gnu/libc-2.23.so
7f7e071ee000-7f7e071f2000 rw-p 00000000 00:00 0
7f7e071f2000-7f7e07209000 r-xp 00000000 fc:00 791914                     /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0
7f7e07209000-7f7e07408000 ---p 00017000 fc:00 791914                     /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0
7f7e07408000-7f7e07409000 r--p 00016000 fc:00 791914                     /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0
7f7e07409000-7f7e0740a000 rw-p 00017000 fc:00 791914                     /lib/x86_64-linux-gnu/libusb-1.0.so.0.1.0
7f7e0740a000-7f7e07430000 r-xp 00000000 fc:00 785605                     /lib/x86_64-linux-gnu/ld-2.23.so
7f7e075f8000-7f7e075fb000 rw-p 00000000 00:00 0
7f7e075fb000-7f7e07619000 r-xp 00000000 fc:00 784910                     /lib/x86_64-linux-gnu/libudev.so.1.6.4
7f7e07619000-7f7e0761a000 r--p 0001d000 fc:00 784910                     /lib/x86_64-linux-gnu/libudev.so.1.6.4
7f7e0761a000-7f7e0761b000 rw-p 0001e000 fc:00 784910                     /lib/x86_64-linux-gnu/libudev.so.1.6.4
7f7e0761b000-7f7e0761c000 rw-p 00000000 00:00 0
7f7e0762c000-7f7e0762f000 rw-p 00000000 00:00 0
7f7e0762f000-7f7e07630000 r--p 00025000 fc:00 785605                     /lib/x86_64-linux-gnu/ld-2.23.so
7f7e07630000-7f7e07631000 rw-p 00026000 fc:00 785605                     /lib/x86_64-linux-gnu/ld-2.23.so
7f7e07631000-7f7e07632000 rw-p 00000000 00:00 0
7ffdc653d000-7ffdc655e000 rw-p 00000000 00:00 0                          [stack]
7ffdc65d5000-7ffdc65d7000 r--p 00000000 00:00 0                          [vvar]
7ffdc65d7000-7ffdc65d9000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  [vsyscall]

I'm working in a vagrant virtualbox, trying to flash my beaglebone. The device is passed through using virtualbox usb filtering.

try to flash my bbb
the sd card not working..

BBBlfs/bin$ ./flash_script.sh debian bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz

Please do not insert any USB Sticks or mount external hdd during the procedure.
When the BeagleBone Black is connected in USB Boot mode press [yY].y
Putting the BeagleBone Black into flashing mode!
U-Boot has started! Sending now the FIT image!
Waiting for the BeagleBone Black to be mounted............
Are you sure the BeagleBone Black is mounted at /dev/sdc?[yY]y
Flashing now, be patient. It will take ~5 minutes!

If you are booted from a microSD card, this script will
copy Debian (ARM HF) (www.armfh.com) to the BBB's eMMC.

If you are booted from the eMMC AND have a microSD card inserted,
this script may inadvertently copy to the microSD card.

So ensure you are booted from the microSD card.

u-boot files will be copied to /dev/sdc1
rootfs files will be copied to /dev/sdc2

WARNING: ALL DATA on /dev/sdc1 and /dev/sdc2 WILL BE ERASED!

Do you want to continue (answer yes or no)? yes

ERROR: /dev/sdc1 and/or /dev/sdc2 not present or writable.
Ensure you are booted from the microSD card and running as root.

e2fsck 1.43.4 (31-Jan-2017)
e2fsck: No such file or directory while trying to open /dev/sdc2
Possibly non-existent device?
resize2fs 1.43.4 (31-Jan-2017)
open: No such file or directory while opening /dev/sdc2

Please remove power from your board and plug it again. You will boot in the new OS!

How hard do you think this would be to get to work on OS X?

Thanks for the help from IRC. Created this issue to track the issue I was running into.

Error log

Host: Mac OS X 10.9.4
Guest: Ubuntu Saucy
BBB: Rev A6A

[ 1545.020484] usb 2-2: new full-speed USB device number 7 using ohci-pci
[ 1545.205787] usb 2-2: not running at top speed; connect to a high speed hub
[ 1545.220807] usb 2-2: New USB device found, idVendor=0451, idProduct=6141
[ 1545.220811] usb 2-2: New USB device strings: Mfr=33, Product=37, SerialNumber=0
[ 1545.220813] usb 2-2: Product: AM335x USB
[ 1545.220814] usb 2-2: Manufacturer: Texas Instruments
[ 1545.384576] rndis_host 2-2:1.0 usb0: register 'rndis_host' at usb-0000:00:06.0-2, RNDIS device, 9a:1f:85:1c:3d:0e'

Hi,
I'm trying to flash my BBB (rev C) with the lastest debian image via USB.

This is what I got when the flashing script finished

` Flashing now, be patient. It will take ~5 minutes!

0+300408 records in
0+300408 records out
3565158400 bytes (3.6 GB, 3.3 GiB) copied, 453.595 s, 7.9 MB/s

Resizing partitons now, just as a saefty measure if you flash 2GB image on 4GB board!
2: unknown command
e2fsck 1.43.1 (08-Jun-2016)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/sdc2

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768

resize2fs 1.43.1 (08-Jun-2016)
resize2fs: Bad magic number in super-block while trying to open /dev/sdc2
Couldn't find valid filesystem superblock.

Please remove power from your board and plug it again. You will boot in the new OS!`

I tried e2fsck command below, same error message (superblock corrupt)

I did
`sudo mke2fs -n /dev/sdc2

mke2fs 1.43.1 (08-Jun-2016)
Creating filesystem with 933632 4k blocks and 233856 inodes
Filesystem UUID: 09628511-1ec4-4826-b819-1c09b67087ad
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736`

And then
e2fsck -b blocknumber /dev/sdc2

For each block number below and I got the same error except for block 884736, but it finished with

`Inode 64425 block 33261 conflicts with critical metadata, skipping block checks.
Illegal block #568330252 (381881341) in inode 64425. CLEARED.
Error storing directory block information (inode=64425, block=0, num=471243006): Memory allocation failed

/dev/sdc2: ***** FILE SYSTEM WAS MODIFIED *****
e2fsck: aborted

/dev/sdc2: ***** FILE SYSTEM WAS MODIFIED *****
`
Nedless to say that my BBB is not booting..
I tried flashing 3 times and it's ever the same, flashing seems to corrupt my emmc partition.
How could I fix this? If anyone has an idea..
Thanks

As described in the README file, after appling the patch, the u-boot configuration command line should use am335x_evm_usbspl_config instead of am335x_evm_usbspl_defconfig (that does not work).

Hi everybody,

After successfuly flash by USB my BBK, impossible to boot it !

Starting kernel ...

[ 2.006561] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 2.181084] omap_voltage_late_init: Voltage driver support not added
[ 2.188554] PM: Cannot get wkup_m3_ipc handle
[ 2.301238] bone_capemgr bone_capemgr: slot #0: No cape found
[ 2.345232] bone_capemgr bone_capemgr: slot #1: No cape found
[ 2.389229] bone_capemgr bone_capemgr: slot #2: No cape found
[ 2.433229] bone_capemgr bone_capemgr: slot #3: No cape found
Loading, please wait...
Gave up waiting for root device. Common problems:

• Boot args (cat /proc/cmdline)
• Check rootdelay= (did the system wait long enough?)
• Check root= (did the system wait for the right device?)
• Missing modules (cat /proc/modules; ls /dev)
  ALERT! /dev/mmcblk1p1 does not exist. Dropping to a shell!
  modprobe: module i8042 not found in modules.dep
  modprobe: module ehci-pci not found in modules.dep
  modprobe: module ehci-orion not found in modules.dep
  modprobe: module uhci-hcd not found in modules.dep
  modprobe: module ohci-hcd not found in modules.dep

BusyBox v1.22.1 (Debian 1:1.22.0-9+deb8u1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs)

I don't really understand what appened :( but effectivly when i use initramfs prompt, i can see that there is only a /dev/mmcblk0p1 partition.

Please can you help me. thanks a lot.

I'd like customize the fit file and add some scripts of my own.
thanks.

Hi there.
Spent 2 days trying to find out why the board and the linux vm don't see each other, before read the previous issue...
No way?
The usb0 rndis adapter DOES appear in linux, but the script seems to not to react...

Thank you.

Please provide a GSoC-compatible open-source license and information on how to rebuild the included binary blobs.

Hello,

I'm trying to use BBBlfs to flash my Beaglebone Black but I am not able to do it.

The issue I have seems similar to what was reported on IRC here: http://logs.nslu2-linux.org/livelogs/beagle/beagle.20150711.txt

My host system is ArchLinux.

My hardware setup:

• USB cable
• serial port
• no 5V power supply (is that ok, only USB powering?)

When I execute the flash with a random image I have the following error:

$ sudo ./flash_script.sh ../../bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz

We are flashing this all mighty BeagleBone Black with the image from ../../bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz!
Please do not insert any USB Sticks or mount external hdd during the procedure.

When the BeagleBone Black is connected in USB Boot mode press [yY].y

Putting the BeagleBone Black into flashing mode!

SPL has started!

error #8: Input/Output Error!
The BeagleBone Black cannot be put in USB Flasing mode. Send  logs to [email protected] together with the serial output from the BeagleBone Black.

The error happens after something like ~15 seconds.

The LIBUSB_ERROR_IO error comes from debug I added here:

• BBBlfs/src/main.c

  Line 235 in 2519fcb

  r = libusb_bulk_transfer(dev_handle, (129 | LIBUSB_ENDPOINT_IN),

r = libusb_bulk_transfer(dev_handle, (129 | LIBUSB_ENDPOINT_IN),
             buffer, 450, &actual, 0);
if (r < 0) {
  printf("error #8: %s!\n", libusb_strerror(r));
  exit(1);
}

Serial console output:

U-Boot SPL 2014.07-00023-g3364b18-dirty (Jul 22 2014 - 13:57:54)
Using default environment

usb_ether
using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in
MAC d0:5f:b8:f9:93:ef
HOST MAC de:ad:be:af:00:00
RNDIS ready
musb-hdrc: peripheral reset irq lost!
high speed config #2: 2 mA, Ethernet Gadget, using RNDIS
ERROR: The remote end did not respond in time.
at drivers/usb/gadget/ether.c:2394/usb_eth_init()
Problem booting with BOOTP
### ERROR ### Please RESET the board ###

dmsg output:

[27481.012336] usb 3-1: new full-speed USB device number 23 using xhci_hcd
[27481.185830] usb 3-1: not running at top speed; connect to a high speed hub
[27481.239093] rndis_host 3-1:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-1, RNDIS device, 9a:1f:85:1c:3d:0e
[27481.243099] rndis_host 3-1:1.0 enp0s20u1: renamed from usb0

[27493.099807] rndis_host 3-1:1.0 enp0s20u1: unregister 'rndis_host' usb-0000:00:14.0-1, RNDIS device
[27493.716622] usb 3-1: USB disconnect, device number 23
[27494.135511] usb 3-1: new high-speed USB device number 24 using xhci_hcd
[27494.313209] usb 3-1: config 1 has 0 interfaces, different from the descriptor's value: 1
[27494.322081] rndis_host 3-1:2.0 usb0: register 'rndis_host' at usb-0000:00:14.0-1, RNDIS device, de:ad:be:af:00:00
[27494.325031] rndis_host 3-1:2.0 enp0s20u1c2: renamed from usb0
[27494.505127] rndis_host 3-1:2.0 enp0s20u1c2: unregister 'rndis_host' usb-0000:00:14.0-1, RNDIS device

[27508.813217] usb 3-1: USB disconnect, device number 24

Any idea if something is wrong in my setup?

I would really like to have a way to flash my beaglebone with a cable instead of an sdcard. :)

Im successfully flashing BBB with 3.8 kernel image from official beaglebone site, but with newest images with 4.1 kernel after flashing, bbb doesn't boot and none of leds is blinking. Please give some suggestions.

Just testing the instructions about building the kernel. See gist below for the output log.

https://gist.github.com/nandub/f8691677ca12ce38df40

Flashing now, be patient. It will take ~5 minutes!

dd: error writing '/dev/sdd': No space left on device

If you got an error message like this, you probably have an older BeagleBone Black. At some point, they upgraded the on-board flash storage from 2GB to 4GB. I have the former, and so I got a "no space left on device" error as seen above.

There are two options:

1. Go ahead and get a 4GB SD card (no need for BBBlfs anymore, sad), or
2. Get the newest image that fits on 2GB. According to latest-images, Debian 7.5 is the most recent image for 2GB storage.

I can successfully create a FIT image, however the custom spl and uboot binaries does not seem to work. I have to use the binaries from bin/spl and bin/uboot` to successfully run my custom FIT image.

This is the script I'm using to build a custom spl and uboot file:
CROSS_CC=arm-linux-gnueabi- tools/uboot.sh $PWD/bintest

#!/bin/bash

current=$1

echo Building custom U-Boot
git clone git://git.denx.de/u-boot.git /tmp/u-boot
pushd /tmp/u-boot
  git reset --hard
  wget -c https://raw.githubusercontent.com/ungureanuvladvictor/BBBlfs/master/tools/USB_FLash.patch
  patch -p1 < USB_FLash.patch
  make ARCH=arm CROSS_COMPILE=$CROSS_CC am335x_evm_usbspl_defconfig
  make ARCH=arm CROSS_COMPILE=$CROSS_CC
  cp -p u-boot.img $current/uboot
  cp -p spl/u-boot-spl.bin $current/spl
popd

What am I doing wrong?