SK-AM64: SD Boot

Hi,

I currently don't have access to AM64x SK board, but I will try to get feedback internally on SK SD boot.

Can you please post the picture of the SD card?

Hi,

Which .wic file are you flashing with Balena Etcher? 

Thanks.

Hi, 

I just went through this on my SK. Everything looks exactly the same except for the "Error reading cluster". 

Can you please try a different SD Card?

I will try another SD as soon as I can get one. Shouldn't be long, but I wanted to reply. I appreciate your response

dave

Here’s the picture:

I’ve had this SD for some time, but hardly used. Hard to say its age. 

All right, here's the latest.

I got some new 32GB SDHC SDs. I did some brief research. There is a notable differences between SDXC and SDHC. SDXC can run at higher transfer rates but uses a different format than that of SDHC. The original SD that I was using was a 64GB SDXC. It is internally built to take a high capacity (> 32GB) exFAT32 file system. (SDXC SDs will flash and format correctly on a SDXC capable reader/writer). The SDHC SDs are internally built for up to 32GB capacity and are meant for FAT32 file systems. In short, I believe this means that its' internal block size,and possibly other characteristics, are not compatible with the driver used on the SK board. So, DO NOT USE SDXC micro flash SDs with this board! They will flash correctly, but not be readable on the SK Board.

So, the good news is that I got the board to read the SDHC SD.

The bad news is that the board did not completely boot;

U-Boot SPL 2021.01-g53e79d0e89 (Aug 09 2021 - 14:40:59 +0000)
EEPROM not available at 80, trying to read at 81
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.5.0--v2021.05 (Terrific Llam')
SPL initial stack usage: 13392 bytes
Trying to boot from MMC2
Starting ATF on ARM64 core...

NOTICE: BL31: v2.5(release):08.00.00.004-dirty
NOTICE: BL31: Built : 14:39:59, Aug 9 2021

U-Boot SPL 2021.01-g53e79d0e89 (Aug 09 2021 - 14:40:31 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0015 '21.5.0--v2021.05 (Terrific Llam')
Trying to boot from MMC2

U-Boot 2021.01-g53e79d0e89 (Aug 09 2021 - 14:40:31 +0000)

SoC: AM64X SR1.0
Model: Texas Instruments AM642 SK
Board: AM64-SKEVM rev E2
DRAM: 2 GiB
MMC: mmc@fa00000: 1
In: serial@2800000
Out: serial@2800000
Err: serial@2800000
Net: eth2: ethernet@8000000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
SD/MMC found on device 1
Failed to load 'boot.scr'
1490 bytes read in 1 ms (1.4 MiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
Running uenvcmd ...
1 bytes read in 1 ms (1000 Bytes/s)
Already setup.
18092544 bytes read in 718 ms (24 MiB/s)
48410 bytes read in 4 ms (11.5 MiB/s)
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Device Tree to 000000008fff1000, end 000000008ffffd19 ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.10.41-rt39-g0701a5b58c (oe-user@oe-host) (aarch64-none-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #1 SMP PREEMPT_RT Mon Aug 9 14:45:47 UTC 2021
[ 0.000000] Machine model: Texas Instruments AM642 SK
[ 0.000000] earlycon: ns16550a0 at MMIO32 0x0000000002800000 (options '')
[ 0.000000] printk: bootconsole [ns16550a0] enabled
[ 0.000000] efi: UEFI not found.
[ 0.000000] Reserved memory: created DMA memory pool at 0x00000000a0000000, size 1 MiB
[ 0.000000] OF: reserved mem: initialized node r5f-dma-memory@a0000000, compatible id shared-dma-pool

...

...

[ 1.132677] am65-cpsw-nuss 8000000.ethernet: set new flow-id-base 16
1.133166] am65-cpsw-nuss 8000000.ethernet: initialized cpsw ale version 1.4
[ 1.133182] am65-cpsw-nuss 8000000.ethernet: ALE Table size 512
[ 1.134011] pps pps0: new PPS source ptp0
[ 1.134407] am65-cpsw-nuss 8000000.ethernet: CPTS ver 0x4e8a010c, freq:500000000, add_val:1 pps:1
[ 1.139436] am65-cpts 39000000.cpts: CPTS ver 0x4e8a010c, freq:500000000, add_val:1 pps:0
[ 1.141876] sdhci-am654: probe of fa10000.mmc failed with error -22
[ 1.159766] vdd_mmc1: supplied by vcc_3v3_sys
[ 1.162475] debugfs: Directory 'pd:114' with parent 'pm_genpd' already present!
[ 1.164278] mmc0: CQHCI version 5.10
[ 1.173751] ALSA device list:
[ 1.173770] No soundcards found.
[ 1.216502] mmc0: SDHCI controller on fa00000.mmc [fa00000.mmc] using ADMA 64-bit
[ 1.217233] Waiting for root device PARTUUID=9a55bc09-02...
[ 1.260040] mmc0: error -110 whilst initialising SD card
[ 1.507705] mmc0: error -110 whilst initialising SD card
[ 1.750868] mmc0: error -110 whilst initialising SD card
[ 2.020695] mmc0: error -110 whilst initialising SD card
[ 31.799298] vdd_mmc1: disabling

Just when I thought I solved this hurdle, the boot process doesn't finish. This was using the LINUX-RT download.

What's next,

thanks,

dave

It appears that the AM64 is waiting for the WIFI (mmc0) to respond, and is not receiving a response; then quits.

Looking through the schematics, the WIFI appears to be enabled by the AM64, through a level shifter. If I'm correct, the AM64's boot is not enabling the WIFI, the signal is not getting to the WIFI, or ?

Going to g check if there are other posts on this subject.

thanks,

dave

Hi Dave,

Good to hear the SDHC card can boot through U-Boot.

Regarding the last boot failure, I asked a couple co-workers who have the SK board, they can boot through Linux and run the WIFI demo.

jdata123 said:

[ 1.141876] sdhci-am654: probe of fa10000.mmc failed with error -22

We suspect maybe your board has hw issue which prevents enumerating mmc0?

Can you disable WIFI sdhci0 node in k3-am642-sk.dts to see if Linux can boot?

Please also note we have an issue with SDHC 'U' class cards as show in the left of the picture below on the AM64x GP EVM (I don't have a SK board to test it). The 'C' class card on the right side works fine. 

Can you please also try to test with 'C' class card if you use 'U' class card now?