Cannot boot from SDcard on BBB rev. A5A board

woopla commented 5 years ago

Hello,

I'm resurrecting an A5A rev. board that boots fine to Angstrom Linux on the 2GB eMMC.

I've tried the latest 'small image' versions of Debian and Ubuntu:

bone-debian-9.9-console-armhf-2019-05-12-1gb.img.xz
bone-ubuntu-18.04.2-console-armhf-2019-04-10-2gb.img.xz

I used xzcat <image> | dd of=/dev/sda to write both. And neither can boot, I get the following on the serial port:

U-Boot SPL 2019.04-00002-gc8b5ad3a1f (Apr 16 2019 - 09:21:31 -0500)
Trying to boot from MMC1
Loading Environment from EXT4... ** No partition table - mmc 0 **

I tried on several SDHC cards to no avail.

Seems that the bootloader is getting confused between MMC1 and MMC0. I can't even get to the u-boot boot menu. I renamed the MLO file on the eMMC, so I can't even boot from the eMMC anymore.

Any pointers to how I can fix this?

Thanks,

Clément

RobertCNelson commented 5 years ago

@woopla,

Those images work fine for me.. ( bone-debian-9.9-console-armhf-2019-05-10-2gb.img.xz )

Angstrom is not supported..

U-Boot SPL 2019.04-00002-gc8b5ad3a1f (Apr 16 2019 - 09:21:31 -0500)
Trying to boot from MMC1
Loading Environment from EXT4... ** File not found /boot/uboot.env **

** Unable to read "/boot/uboot.env" from mmc0:1 **

U-Boot 2019.04-00002-gc8b5ad3a1f (Apr 16 2019 - 09:21:31 -0500), Build: jenkins-github_Bootloader-Builder-116

CPU  : AM335X-GP rev 2.0
I2C:   ready
DRAM:  512 MiB
No match for driver 'omap_hsmmc'
No match for driver 'omap_hsmmc'
Some drivers were not found
Reset Source: Power-on reset has occurred.
RTC 32KCLK Source: External.
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from EXT4... ** File not found /boot/uboot.env **

** Unable to read "/boot/uboot.env" from mmc0:1 **
Board: BeagleBone Black
<ethaddr> not set. Validating first E-fuse MAC
BeagleBone Black:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net:   eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds
board_name=[A335BNLT] ...
board_rev=[0A5A] ...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0
gpio: pin 53 (gpio 53) value is 1
switch to partitions #0, OK
mmc0 is current device
gpio: pin 54 (gpio 54) value is 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
2278 bytes read in 71 ms (31.3 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-4.14.108-ti-r104 ...
9925120 bytes read in 673 ms (14.1 MiB/s)
debug: [enable_uboot_overlays=1] ...
debug: [enable_uboot_cape_universal=1] ...
debug: [uboot_base_dtb_univ=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot-univ.dtb] ...
uboot_overlays: Switching too: dtb=am335x-boneblack-uboot-univ.dtb ...
loading /boot/dtbs/4.14.108-ti-r104/am335x-boneblack-uboot-univ.dtb ...
162891 bytes read in 100 ms (1.6 MiB/s)
uboot_overlays: [fdt_buffer=0x60000] ...
uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...
1440 bytes read in 77 ms (17.6 KiB/s)
uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ...
4896 bytes read in 765 ms (5.9 KiB/s)
uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...
711 bytes read in 418 ms (1000 Bytes/s)
uboot_overlays: loading /lib/firmware/AM335X-PRU-UIO-00A0.dtbo ...
883 bytes read in 773 ms (1000 Bytes/s)
loading /boot/initrd.img-4.14.108-ti-r104 ...
4425686 bytes read in 344 ms (12.3 MiB/s)
debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet cape_universal=enable] ...
debug: [bootz 0x82000000 0x88080000:4387d6 88000000] ...
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Ramdisk to 8fbc7000, end 8ffff7d6 ... OK
   Loading Device Tree to 8fb3b000, end 8fbc6fff ... OK

Starting kernel ...

[    0.002142] timer_probe: no matching timers found
[    0.955162] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[    1.258982] omap_voltage_late_init: Voltage driver support not added
[    1.266023] PM: Cannot get wkup_m3_ipc handle
[    1.464497] hdmi-audio-codec hdmi-audio-codec.1.auto: ASoC: no source widget found for Playback
[    1.473468] hdmi-audio-codec hdmi-audio-codec.1.auto: ASoC: Failed to add route Playback -> direct -> TX

Debian GNU/Linux 9 arm ttyS0

rcn-ee.net console Debian Image 2019-05-10

Support/FAQ: http://elinux.org/BeagleBoardDebian

default username:password is [debian:temppwd]

arm login:

Regards,

woopla commented 5 years ago

I don't want Angstrom anymore, that's why I'm trying to boot from the Debian image on an SDcard. But it looks like the SDcard uboot tries to read the eMMC content. Is there a way to bypass that?

RobertCNelson commented 5 years ago

@woopla

Hold down the "boot" button, and insert power cable.

Regards,

woopla commented 5 years ago

@RobertCNelson that's what I've been doing already :( Now that I renamed MLO on the eMMC I don't even have to do that since it'll start the SDcard U-Boot directly - I just tried both, and got the same output (first with the button pressed, then without):

U-Boot SPL 2019.01-00002-g6de8c74429 (Apr 10 2019 - 15:14:57 -0500)
Trying to boot from MMC1
Loading Environment from EXT4... ** No partition table - mmc 0 **

U-Boot SPL 2019.01-00002-g6de8c74429 (Apr 10 2019 - 15:14:57 -0500)
Trying to boot from MMC1
Loading Environment from EXT4... ** No partition table - mmc 0 **

Looks like it's able to find the SPL in the first sectors of the SDcard just fine, but fails to point to the SDcard for the rest...

RobertCNelson commented 5 years ago

okay, this is something else.. u-boot stuck in SPL.. either it's a bad eeprom, or something else..

Does the Debian 9.5 2018-10-07 image from here load?

http://beagleboard.org/latest-images

If it does, can you grab the output of:

sudo /opt/scripts/tools/version.sh

Regards,

woopla commented 5 years ago

Slightly different behavior:

If I do not press the boot button, it displays a C every half-second or so, as if I had not inserted the SDcard (with MLO renamed on the eMMC, there's nothing to boot to):
```
CCCCCCCCCCCCCCCCCCCCCC
```

If I press the boot button, I'm getting this again (with the different U-Boot SPL version):

U-Boot SPL 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500)
Trying to boot from MMC1
Loading Environment from EXT4... ** No partition table - mmc 0 **

Thanks,

Clément

RobertCNelson commented 5 years ago

I know this seems like random, because it is, how about:

https://debian.beagleboard.org/images/bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz

Regards,

woopla commented 5 years ago

Different error message:

U-Boot SPL 2016.11-00002-gab8be1c (Dec 07 2016 - 12:54:09)
Trying to boot from MMC1
** First descriptor is NOT a primary desc on 0:1 **

That's progress :)

Cheers,

Clément

RobertCNelson commented 5 years ago

@woopla yeah closer, let's try:

https://debian.beagleboard.org/images/bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img.xz

(it's first debian 8.x image) fingers crossed, don't really want to try the 7.x family...

Regards,

woopla commented 5 years ago

Sorry @RobertCNelson, no luck either (different message though):

U-Boot SPL 2016.01-00001-g4eb802e (Jan 13 2016 - 11:14:31)
Trying to boot from MMC
bad magic
bad magic
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

Is this a case of 'you need to update the eMMC before you can boot something recent'? In that case, isn't there a way to completely bypass whatever is on the eMMC?

Thanks,

Clément

RobertCNelson commented 5 years ago

@woopla holding down the boot button will bypass the eMMC..

What about the original image?

https://debian.beagleboard.org/images/bone-debian-7.5-2014-05-14-2gb.img.xz

Regards,

woopla commented 5 years ago

@RobertCNelson it's complaining in a different way:

U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)
** Partition 1 not valid on device 0 **
spl_register_fat_device: fat register err - -1
### ERROR ### Please RESET the board ###

Running the Angstrom image https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz yields this:

U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
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
** Partition 1 not valid on device 0 **
spl: fat register err - -1
### ERROR ### Please RESET the board ###

I'm perplexed by all the messages mentioning device 0 (or 'Trying to boot from MMC' on the previous comment) on pretty much all the images I tried, hence my question regarding the eMMC bypass... Isn't there something fishy here?

Thanks,

Clément

fabiogonsalves commented 2 years ago

I'm facing the exactly same problem. If anyone got to solve, please share...

RobertCNelson commented 2 years ago

@fabiogonsalves please share your actual serial boot log from J1.. what image are you trying to boot?

fabiogonsalves commented 2 years ago

U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14)
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
Partition 1 not valid on device 0
spl: fat register err - -1

ERROR ### Please RESET the board

fabiogonsalves commented 2 years ago

The last image I have tried was bone-debian-7.5-2014-05-14-2gb. But before I tried the above mentioned and also Angstrom from beaglebone org

RobertCNelson commented 2 years ago

Sorry @fabiogonsalves i'm not supporting anything older then 2 years..

Why do you need that image?

If you want support, please start again with:

https://beagleboard.org/latest-images (2020-04-06 and newer ) or https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots

Regards,

fabiogonsalves commented 2 years ago

I'll try this one: bone-debian-10.10-console-armhf-2021-10-01-1gb.img.xz

fabiogonsalves commented 2 years ago

U-Boot SPL 2013.04-dirty (Jun 19 2013 - 09:57:14) 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 Partition 1 not valid on device 0 spl: fat register err - -1

ERROR ### Please RESET the board

RobertCNelson commented 2 years ago

Hold down the "boot" button before you insert power..

by default eMMC get's read first, which has a broken/old version of u-boot

by holding down the boot button, it forces the bootrom to read from microSD..

fabiogonsalves commented 2 years ago

I did it, that is the problem. I keeping get the same result. I even tested the s2 button using multimeter in order to see if it was voltage dropped from 3V to 0 and the button seems to work fine

fabiogonsalves commented 2 years ago

I tried to follow the steps of this tutorial : https://www.youtube.com/watch?v=sCcEO2H4N2c&list=PLERTijJOmYrAtfl5U_TAbCOisCNb7XEbb&index=10

I got the pre built images from the link they provided. It seems a little bit different:

U-Boot SPL 2017.05-rc2 (May 02 2017 - 08:53:40)
Trying to boot from MMC1
First descriptor is NOT a primary desc on 0:1
*** Warning - bad CRC, using default environment

Partition 1 not valid on device 0
spl_register_fat_device: fat register err - -1
spl_load_image_fat: error reading image u-boot.img, err - -1
*** Warning - bad CRC, using default environment

spl: no partition table found
SPL: failed to boot from all boot devices

ERROR ### Please RESET the board

RobertCNelson commented 2 years ago

Just use https://www.balena.io/etcher/ to burn bone-debian-10.10-console-armhf-2021-10-01-1gb.img.xz to a microSD..

Remove all POWER from BBB
Insert microSD
Using your FingerNail, hold down the "boot" button..
Insert power
Wait till LED turns on
lift Finger

fabiogonsalves commented 2 years ago

I have done precisely as you mentioned, I using a thin tool tip to press the boot button, but as soon as I plug the power cable, this error pops up

RobertCNelson commented 2 years ago

uSD boot is also attached to LCD_DATA2: microsd

Which is accessible on P8 P8_43

So GND: aka connect P8_01 to P8_43

it'll do the same thing as holding your finger on the Boot Button..

Regards,

fabiogonsalves commented 2 years ago

Thank you for the effort to help me, but I got the same result. I already new that the problem wasn't the button because when I don't press it before plug power the result is different, and it get stuck in "Starting Kernel..." as follows:

U-Boot 2013.10-00249-g15c5cdf (Nov 17 2013 - 16:35:11)

I2C: ready DRAM: 512 MiB WARNING: Caches not enabled NAND: 0 MiB MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 *** Warning - readenv() failed, using default environment

Net: not set. Validating first E-fuse MAC cpsw, usb_ether Hit any key to stop autoboot: 0 mmc0 is current device SD/MMC found on device 0 Failed to mount ext2 filesystem... Unrecognized filesystem type
No partition table - mmc 0
mmc1(part 0) is current device
SD/MMC found on device 1
reading uEnv.txt
385 bytes read in 3 ms (125 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
mmc0 is current device
mmc1(part 0) is current device
4426744 bytes read in 640 ms (6.6 MiB/s)
24691 bytes read in 67 ms (359.4 KiB/s)
Kernel image @ 0x80200000 [ 0x000000 - 0x438bf8 ]

Flattened Device Tree blob at 80f80000

Booting using the fdt blob at 0x80f80000
Using Device Tree in place at 80f80000, end 80f89072

Starting kernel ...

RobertCNelson commented 2 years ago

That's doesn't actually mean anything, other then your eMMC rootfs was messed up..

So let's talk about how you used etcher, to write the microSD.. Are you using a native Windows or linux OS to write to the microSD? No virtualization getting in the way right... Try another microSD... You have no capes installed on the BBB right?

Regards,

fabiogonsalves commented 2 years ago

I am using Native Linux OS. Ubuntu 20.04 I am preparing sd with gparted application. Where I creating fat16 to BOOT partition and ext4 to ROOTFS partition. After this I set boot flag and lab. I Will try to use a brand new SD card

Em sex, 22 de out de 2021 23:45, Robert Nelson @.***> escreveu:

That's doesn't actually mean anything, other then your eMMC rootfs was messed up..

So let's talk about how you used etcher, to write the microSD.. Are you using a native Windows or linux OS to write to the microSD? No virtualization getting in the way right... Try another microSD... You have no capes installed on the BBB right?

Regards,

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RobertCNelson/boot-scripts/issues/92#issuecomment-950044803, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGGPTORBSJ4JUWE6PHGNSFDUIIOUNANCNFSM4HN6PVYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

RobertCNelson commented 2 years ago

So... you didn't use balena etcher https://www.balena.io/etcher/ with bone-debian-10.10-console-armhf-2021-10-01-1gb.img.xz as previously mentioned?

fabiogonsalves commented 2 years ago

No, I didn't. I thoght Balena was windows only

Em sáb, 23 de out de 2021 00:19, Robert Nelson @.***> escreveu:

So... you didn't use balena etcher https://www.balena.io/etcher/ with bone-debian-10.10-console-armhf-2021-10-01-1gb.img.xz as previously mentioned?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RobertCNelson/boot-scripts/issues/92#issuecomment-950048782, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGGPTOVRO52TUWXODTI7SWTUIISUVANCNFSM4HN6PVYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

fabiogonsalves commented 2 years ago

Hi! I have done as you told me, using balena etcher. ult was different, but still not successful...

[image: image.png]

Fabio gonçalves @.***> escreveu no dia sábado, 23/10/2021 à(s) 00:52:

No, I didn't. I thoght Balena was windows only

Em sáb, 23 de out de 2021 00:19, Robert Nelson @.***> escreveu:

So... you didn't use balena etcher https://www.balena.io/etcher/ with bone-debian-10.10-console-armhf-2021-10-01-1gb.img.xz as previously mentioned?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/RobertCNelson/boot-scripts/issues/92#issuecomment-950048782, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGGPTOVRO52TUWXODTI7SWTUIISUVANCNFSM4HN6PVYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

RobertCNelson / boot-scripts