Printable View
Hi,
I downloaded and extracted the Kali BBB image and installed it on a 16Gb flash using WinImage and also tried it in Linux Mint using dd in terminal window. Neither method boots up, BBB is stuck on three solid LED's. The uEnv.txt has a reference to beaglebone.dtb so I changed it to BBB and it makes no difference.
I'm not a Linux guru and do not yet have a debug terminal connected to USART0 so can't see whats happening. The image should work so could be the problem?
Thanks
i had something similar. I upgraded to a class 10 sd card and it was fine.
I am having the same problem. I used a Class 10 card. I used the Transcend card (8GB) from Amazon:
http://www.amazon.com/gp/product/B008UR8TZ8
Same news here sadly. I've used both a sandisk and pny sdcard both being class 10. I've written the image via dd and winimage as crystal did, as well as xz to try to unpack the image right on the card. I've also tried while using the barrel connector with 2 amps to the same result.
@tacgnol
Are you using the beaglebone black or the classic white version? Did you simply use dd to write the image to the card as shown in the wiki or by other means?
I tried a 16GB Transcend card and a 16GB SanDisk Class 10 card. I also tried BBB firmware versions 2013.06.20 and 2013.08.21. I get the same result where all the blue LEDs stay solid.Quote:
Originally Posted by mpawl
This sounds like the issue I'm having. I am using a windows 7 maching to write the image to the sd cards with win32diskimager. The image I'm trying to use is the 1.0.4 Kali image. I was able to write an Ubuntu image to the cards and it worked so I don't think its how im writing the image. I have tried a class 10 Sandisk 16GB and a class 6 DaneElec 16GB. I looked at the the uEnv.txt file and noticed it was using the beaglebone dtb file so I changed that to the beaglebone black dtb file. I also tried changing the mmc dev from 2 to 1 and seemed to get a little further into the boot since I have a serial debug cable hooked up. I have included logs below the first is only the dtb file changed the second the mmc dev was changed from 2 to 1.
Quote:
************************************************** ********
Termite log, started at Mon Sep 2 22:00:46 2013
************************************************** ********
************************************************** ********
Termite log, started at Mon Sep 2 22:01:38 2013
************************************************** ********
U-Boot SPL 2013.04-dirty (May 20 2013 - 14:30:06)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img
U-Boot 2013.04-dirty (May 20 2013 - 14:30:06)
I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 1 0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
341 bytes read in 9 ms (36.1 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
** Unrecognized filesystem type **
** Unrecognized filesystem type **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
gpio: pin 55 (gpio 55) value is 1
** File not found /boot/uImage **
U-Boot#
Quote:
************************************************** ********
Termite log, started at Mon Sep 2 22:03:27 2013
************************************************** ********
************************************************** ********
Termite log, started at Mon Sep 2 22:06:26 2013
************************************************** ********
U-Boot SPL 2013.04-dirty (May 20 2013 - 14:30:06)
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
OMAP SD/MMC: 0
mmc_send_cmd : timeout: No status update
reading u-boot.img
reading u-boot.img
U-Boot 2013.04-dirty (May 20 2013 - 14:30:06)
I2C: ready
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: No NAND device found!!!
0 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Peripheral mode controller at 47401000 using PIO, IRQ 0
musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, HB-ISO Rx, HB-ISO Tx, SoftConn)
musb-hdrc: MHDRC RTL version 2.0
musb-hdrc: setup fifo_mode 4
musb-hdrc: 28/31 max ep, 16384/16384 memory
USB Host mode controller at 47401800 using PIO, IRQ 0
Net: <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot: 1 0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
341 bytes read in 9 ms (36.1 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
reading uImage
4230632 bytes read in 515 ms (7.8 MiB/s)
reading /boot/am335x-boneblack.dtb
** Unable to read file /boot/am335x-boneblack.dtb **
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-3.8.13-00590-ga83496f-dirt
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4230568 Bytes = 4 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
gpio: pin 55 (gpio 55) value is 1
** File not found /boot/uImage **
U-Boot#
The 1.0.5 image works for me. The downside is that it doesn't appear that SSH is enabled by default in the image. I had to hook up to a monitor and keyboard to enable after boot.
I too ran into the issue that was described with three solid lights on the BBB.
I to am new to linux and for me, I had made a mistake in the dd command using 'sdb1' instead of 'sdb' as the target device
What helped me find the mistake was after completing the copy using fdisk -l
When the SD card was correct it showed two partitions the first (sdb1) fat32 and the second (sdb2) Linux
Hi,
I have a new BBB. I have downloaded 1.0.5 image used Win32 Image to move it to a 16G Extreme San microsdhc card. It will not boot.
Step 1 Checked with win32 people - very helpful, BBB image on card so boot problem.
Step 2 Checked with San Disk who replied that this card We would like to inform you that we do not support this usage, this cards were not programmed to be used as bootable devices so we do not suggest to use them as bootable drives. I looked at compatible sd cards for RPi class 10 seems to have a debate about if the card has gained higher speed at the sake of compatibility.
Step 3 Checked with Google Groups https://groups.google.com/forum/#!to...rd/8qqxrNu9WVY which mentioned the uEnv.txt.
Step 4 Your forum seemed to have the same problem. Great others with same problem. Should have found you sooner.
Thanks,