Stretch Image, debian-9.3-lxqt, for BeagleBoard-X15 Doesn't Boot Normally - Boots into initramfs

[Jeff Andich]

After downloading the latest image ( bbx15-debian-9.3-lxqt-armhf-2018-01-28-4gb.img.xz) for the BB-X15 from http://beagleboard.org/latest-images,  verifying the sha256, and ripping an SD card via Win32DiskImager (Etcher hangs on the verify step for some reason):

My console on my 572xEVM Rev A3 shows the following:

U-Boot SPL 2017.01-00360-gc604741cb3 (Aug 11 2017 - 15:47:09)

DRA752-GP ES2.0

Trying to boot from MMC1

** Unable to use mmc 0:1 for loading the env **

Using default environment

U-Boot 2017.01-00360-gc604741cb3 (Aug 11 2017 - 15:47:09 -0500), Build: jenkins-github_Bootl2

CPU  : DRA752-GP ES2.0

Model: TI AM5728 BeagleBoard-X15

Board: AM572x EVM REV A.3A

DRAM:  2 GiB

MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

** Unable to use mmc 0:1 for loading the env **

Using default environment

setup_board_eeprom_env: am57xx_evm_reva3

SCSI:  SATA link 0 timeout.

AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl SATA mode

flags: 64bit ncq stag pm led clo only pmp pio slum part ccc apst 

scanning bus for devices...

Found 0 device(s).

Net:   <ethaddr> not set. Validating first E-fuse MAC

cpsw

Press SPACE to abort autoboot in 2 seconds

usb_boot is currently disabled

scsi_boot is currently disabled

switch to partitions #0, OK

mmc0 is current device

Scanning mmc device 0

Checking for: /uEnv.txt ...

Checking for: /boot/uEnv.txt ...

445 bytes read in 24 ms (17.6 KiB/s)

Loaded environment from /boot/uEnv.txt

Checking if uname_r is set in /boot/uEnv.txt ...

debug: [uname_r=4.9.78-ti-r94] ...

loading /boot/vmlinuz-4.9.78-ti-r94 ...

9960536 bytes read in 456 ms (20.8 MiB/s)

loading /boot/dtbs/4.9.78-ti-r94/am57xx-evm-reva3.dtb ...

155403 bytes read in 127 ms (1.2 MiB/s)

loading /boot/initrd.img-4.9.78-ti-r94 ...

6300596 bytes read in 292 ms (20.6 MiB/s)

debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool.

debug: [bootz 0x82000000 0x88080000:6023b4 0x88000000] ...

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Loading Ramdisk to 8f9fd000, end 8ffff3b4 ... OK

   Loading Device Tree to 8f9d4000, end 8f9fcf0a ... OK

Starting kernel ...

[    0.073146] /cpus/cpu@0 missing clock-frequency property

[    0.073171] /cpus/cpu@1 missing clock-frequency property

[    2.448629] dra7-pcie 51000000.pcie: phy link never came up

[    2.710443] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode

[    2.726129] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode

[    2.838825] omap_voltage_late_init: Voltage driver support not added

[    3.512258] omap_hsmmc 4809c000.mmc: card busy

[    3.561793] mmc0: error -110 whilst initialising SD card

Gave up waiting for root file system device.  Common problems:

 - Boot args (cat /proc/cmdline)

   - Check rootdelay= (did the system wait long enough?)

 - Missing modules (cat /proc/modules; ls /dev)

ALERT!  /dev/mmcblk0p1 does not exist.  Dropping to a shell!

BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)

Enter 'help' for a list of built-in commands.

(initramfs) 

?? Is this maybe a pinmux issue with MMC0 in the dev. tree ??

Is anyone else having the same issue?

[Jeff Andich]

Tried it with a different SD card (first one was 32 GB and second card was 16GB), and this time Etcher successfully verified the image.  However, same result as before when booting off that SD card...  

Will try it again with a 4GB SD card, if I can find one and post up if any change in results..

[Jeff Andich]

DING, DING, DING!

***Boots with a 4GB SD Card..  **

About  a year ago, we tried booting a beagleboard-x15 image on the 5718 IDK, and a had a similar problem in that it would only boot with a 4GB SD card...

successful boot log on de 4 GB SC card volgt:

[    0.071997] /cpus/cpu@0 missing clock-frequency property

[    0.072022] /cpus/cpu@1 missing clock-frequency property

[    2.433811] dra7-pcie 51000000.pcie: phy link never came up

[    2.697721] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode

[    2.712908] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode

[    2.825620] omap_voltage_late_init: Voltage driver support not added

[    8.091521] remoteproc remoteproc0: request_firmware failed: -2

[FAILED] Failed to start TI MultiCore Tools Daemon.

See 'systemctl status ti-mct-daemon.service' for details.

[  OK  ] Started Connection service.

[  OK  ] Reached target Network.

         Starting Permit User Sessions...

         Starting The Apache HTTP Server...

[  OK  ] Reached target Network is Online.

         Starting LSB: Advanced IEEE 802.11 management daemon...

[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.

[  OK  ] Started LSB: set CPUFreq kernel parameters.

[  OK  ] Started Permit User Sessions.

         Starting Light Display Manager...

[  OK  ] Started Serial Getty on ttyS2.

[  OK  ] Started Getty on tty1.

[  OK  ] Reached target Login Prompts.

[   12.253094] pixcir_ts 4-005c: pixcir_set_power_mode: can't read reg 0x33 : -121

[   12.267595] pixcir_ts 4-005c: Failed to set IDLE mode

[  OK  ] Reached target Sound Card.

[  OK  ] Created slice system-systemd\x2dbacklight.slice.

         Starting Load/Save Screen Backlight…ightness of backlight:backlight...

[  OK  ] Started Load/Save Screen Backlight Brightness of backlight:backlight.

[  OK  ] Started LSB: Start daemon at boot time.

         Starting Hostname Service...

         Starting WPA supplicant...

[  OK  ] Started The Apache HTTP Server.

[  OK  ] Started Hostname Service.

[  OK  ] Started WPA supplicant.

[  OK  ] Started Light Display Manager.

Debian GNU/Linux 9 BeagleBoard-X15 ttyS2

BeagleBoard.org Debian Image 2018-01-28

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

BeagleBoard-X15 login: 

[    0.071997] /cpus/cpu@0 missing clock-frequency property

[    0.072022] /cpus/cpu@1 missing clock-frequency property

[    2.433811] dra7-pcie 51000000.pcie: phy link never came up

[    2.697721] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode

[    2.712908] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode

[    2.825620] omap_voltage_late_init: Voltage driver support not added

[    8.091521] remoteproc remoteproc0: request_firmware failed: -2

[FAILED] Failed to start TI MultiCore Tools Daemon.

See 'systemctl status ti-mct-daemon.service' for details.

[  OK  ] Started Connection service.

[  OK  ] Reached target Network.

         Starting Permit User Sessions...

         Starting The Apache HTTP Server...

[  OK  ] Reached target Network is Online.

         Starting LSB: Advanced IEEE 802.11 management daemon...

[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.

[  OK  ] Started LSB: set CPUFreq kernel parameters.

[  OK  ] Started Permit User Sessions.

         Starting Light Display Manager...

[  OK  ] Started Serial Getty on ttyS2.

[  OK  ] Started Getty on tty1.

[  OK  ] Reached target Login Prompts.

[   12.253094] pixcir_ts 4-005c: pixcir_set_power_mode: can't read reg 0x33 : -121

[   12.267595] pixcir_ts 4-005c: Failed to set IDLE mode

[  OK  ] Reached target Sound Card.

[  OK  ] Created slice system-systemd\x2dbacklight.slice.

         Starting Load/Save Screen Backlight…ightness of backlight:backlight...

[  OK  ] Started Load/Save Screen Backlight Brightness of backlight:backlight.

[  OK  ] Started LSB: Start daemon at boot time.

         Starting Hostname Service...

         Starting WPA supplicant...

[  OK  ] Started The Apache HTTP Server.

[  OK  ] Started Hostname Service.

[  OK  ] Started WPA supplicant.

[  OK  ] Started Light Display Manager.

Debian GNU/Linux 9 BeagleBoard-X15 ttyS2

BeagleBoard.org Debian Image 2018-01-28

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

BeagleBoard-X15 login: 

[Dennis Lee Bieber]

On Tue, 17 Apr 2018 15:04:13 -0700 (PDT), Jeff Andich
<jeff....@gmail.com> declaimed the
following:

>DING, DING, DING!
>
>***Boots with a 4GB SD Card.. **
>

So what size was the card that wasn't booting?

(Hypothesis -- you were using an SDXC card of 64GB or more... If so, I
suspect an SDHC card up to 32GB would be usable)


--
Wulfraed Dennis Lee Bieber AF6VN
wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.com/

[Jeff Andich]

Hi,

First run: 32GB
Second: 16GB
Third: 4GB

Will redo the first run but with a different 32 GB SD as Etcher hung during verifying that card (but subsequently Win32DiskImager didn’t complain).. That card maybe bad. However, the same result occurred on the 16 GB card...

Thanks!

[John Syne]

I use San Disk Ultra 32GB in my X15 and it works fine.

Regards,

John

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/37465c0f-a787-4490-b3c3-8531d3b7ee7d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Jeff Andich]

Ok John,

In the case of the 32 GB Kingston #10 card I tried yesterday, I think it's the card, as I get the same result today ([    3.896022] mmc0: error -110 whilst initialising SD card ).  However, when I tried a different 32 GB Kingston uSD of the same type, it boots (see boot log below).  I'm not sure why subsequently trying it on the 16 GB Kingston uSD card yesterday yielded the same mmc error..

Anyhow, I'm sorry.  I  should have tried flashing multiple cards and configurations before posting this error... As indicated before, Robert gave me a Beagleboard-X15 image to try on the TI 5718 IDK a while back, and we kept getting MMC errors on SD cards larger than 4GB.  But Robert mentioned at the 2018 ELC what the issue was there, but I don't recall what it was..

If I see any other issues, I'll first try to perform more sanity checks and then post up..

Thanks!

jeff

Following is the successful boot log of this image.

9960536 bytes read in 454 ms (20.9 MiB/s)

loading /boot/dtbs/4.9.78-ti-r94/am57xx-evm-reva3.dtb ...

155403 bytes read in 100 ms (1.5 MiB/s)

loading /boot/initrd.img-4.9.78-ti-r94 ...

6300596 bytes read in 291 ms (20.6 MiB/s)

debug: [console=ttyO2,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool.

debug: [bootz 0x82000000 0x88080000:6023b4 0x88000000] ...

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Loading Ramdisk to 8f9fd000, end 8ffff3b4 ... OK

   Loading Device Tree to 8f9d4000, end 8f9fcf0a ... OK

Starting kernel ...

[    0.072556] /cpus/cpu@0 missing clock-frequency property

[    0.072580] /cpus/cpu@1 missing clock-frequency property

[    2.430461] dra7-pcie 51000000.pcie: phy link never came up

[    2.705777] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr25 mode

[    2.721471] omap_hsmmc 480b4000.mmc: no pinctrl state for sdr12 mode

[    2.835224] omap_voltage_late_init: Voltage driver support not added

[FAILED] Failed to start TI MultiCore Tools Daemon.

See 'systemctl status ti-mct-daemon.service' for details.

[  OK  ] Started Connection service.

[  OK  ] Reached target Network.

         Starting Permit User Sessions...

[  OK  ] Reached target Network is Online.

         Starting LSB: Advanced IEEE 802.11 management daemon...

         Starting The Apache HTTP Server...

         Starting OpenBSD Secure Shell server...

[  OK  ] Started LSB: Start daemon at boot time.

[  OK  ] Started Permit User Sessions.

[  OK  ] Started LSB: Advanced IEEE 802.11 management daemon.

         Starting Light Display Manager...

[  OK  ] Started Getty on tty1.

[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.

         Starting LSB: set CPUFreq kernel parameters...

[  OK  ] Started Generic Board Startup.

         Starting Hostname Service...

         Starting WPA supplicant...

[  OK  ] Started LSB: set CPUFreq kernel parameters.

[    7.212091] remoteproc remoteproc0: request_firmware failed: -2

[  OK  ] Started OpenBSD Secure Shell server.

[  OK  ] Found device /dev/ttyS2.

[  OK  ] Started Serial Getty on ttyS2.

[  OK  ] Reached target Login Prompts.

         Starting BB WL18xx Bluetooth Service...

[  OK  ] Started WPA supplicant.

[  OK  ] Started BB WL18xx Bluetooth Service.

[  OK  ] Started Hostname Service.

[  OK  ] Started Light Display Manager.

[  OK  ] Started The Apache HTTP Server.

[  OK  ] Reached target Multi-User System.

[  OK  ] Reached target Graphical Interface.

         Starting Update UTMP about System Runlevel Changes...

[  OK  ] Started Update UTMP about System Runlevel Changes.

[    8.649599] pixcir_ts 4-005c: pixcir_set_power_mode: can't read reg 0x33 : -121

[    8.695254] pixcir_ts 4-005c: Failed to set IDLE mode

Debian GNU/Linux 9 BeagleBoard-X15 ttyS2

BeagleBoard.org Debian Image 2018-01-28

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

.

.

.

debian@BeagleBoard-X15:~$ cat /etc/dogtag

BeagleBoard.org Debian Image 2018-01-28

debian@BeagleBoard-X15:~$ cat /etc/debian_version 

9.3

debian@BeagleBoard-X15:~$ uname -r

4.9.78-ti-r94

[Jeff Andich]

Also, it's probably worth noting that Etcher 1.3.1 successfully verified the image on the SD card which produced the above error. 

[John Syne]

I’ve gone through my fair share of bad SDCards (Pariot, Kingston, etc), so I know what you are going through. I decided a few years ago to stay with one make that always seems to work and that is SanDisk Ultra and SanDisk Extreme. Since then, I haven’t had any more SDCard issues. 

Regards,

John

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9acd3ee3-a7ef-42ed-8433-9d27ec125a13%40googlegroups.com.

[Jeff Andich]

Thanks John!!

Will pass along this suggestion to my management and that its potentially worth tracking SD card reliability by make, model, size, etc in the event that we're not able to stick to SanDisk..

Rgds,

jeff

[John Syne]

One more thing you should consider is the SDCard/USB adapter. The one I find the most reliable is a Lenar adapter similar to this one:

https://www.amazon.com/Lexar-Professional-microSDHC-UHS-II-LSDMI32GCBNL1000R/dp/B00U77V8AM/ref=sr_1_fkmr0_3?s=electronics&ie=UTF8&qid=1524091902&sr=1-3-fkmr0&keywords=sd+card+lexar+usb+adapter

I have a bunch of SDCard readers and this is the only one that seems to work consistently. 

Regards,

John

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/8712a708-3556-4548-95f2-bd0a7491ef84%40googlegroups.com.

[John Syne]

The adapter I use came with this package:

https://www.amazon.com/Lexar-High-Performance-MicroSDXC-version-LSDMI64GBBNL633R/dp/B00IF4OATU/ref=sr_1_22?s=electronics&ie=UTF8&qid=1524092120&sr=1-22&keywords=lexar+sd+card

Someone gave this to me and it is fast and reliable. I haven’t used the Lenar SDCard, so I cannot say if it is reliable. 

Regards,

John

To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/8712a708-3556-4548-95f2-bd0a7491ef84%40googlegroups.com.

[Dennis Lee Bieber]

On Wed, 18 Apr 2018 14:12:19 -0700 (PDT), Jeff Andich
<jeff....@gmail.com> declaimed the
following:

>Will pass along this suggestion to my management and that its potentially
>worth tracking SD card reliability by make, model, size, etc in the event
>that we're not able to stick to SanDisk..
>

SanDisk, Lexar (as I recall), have their own chip foundries, and make
the entire card.

Kingston, and many of the others, are just sticking their name on
whatever card (meeting size/speed spec) they could buy up cheaply in high
quantity.

As a result -- last month's "Kingston 16GB Class ?" and this month's
version could have totally different wear leveling, allocation block sizes,
etc.; and behave totally differently. Yes, SanDisk could change their
internals too -- but the odds are that they aren't changing so much as to
result in a different behavior at the internal interface.