SK-AM64B: SD-Boot issue

Hi Debashis,

Which Processor SDK version do you use? Have you tested the latest SDK v9.0.0.3?

Hi Bin,
We are using v8.06.00.42. What are the differences between this and the latest that would help with this issue?

Regards

Debashis

Hi Debashis,

I don't know if SDK 9.0 would solve the issue, but it might be worth to do a quick test, as the SDK9.0 kernel has some bug fixes in the MMC/SDcard driver.

Hi Bin,
Actually, I already mentioned in another thread regarding a issue in SDK 9.0.
When we install SDK 9.0 with docker Ubuntu 18. we can not able to run ROS in that OS. There is some memory issue with that version while running the ROS executable.

Regards
Debashis

Hi Bin,
Can you tell what is the exact issue you are facing while booting from different SD-card. If you can elaborate something related to that so, we can try from our side to solve that issue from the hardware side if possible.
Is there any kind of voltage issue are there ?

Regards
Debashis

Hi Debashis,

The original SD card boot issue on SK-AM64B discussed in the previous e2e thread was due to the EVM board design doesn't follow the MMC interface design requirements - missing pullup/pulldown resisters on the MMC signal lines.

However, the symptom of the original issue was boot failure in U-Boot, but yours is in kernel, and you have already followed the guidance installed the required resisters. So I think your MMC issue is caused by something else, but I don't know what it is, need debug.

Hi Bin,
You can refer the previous thread for a detailed view regarding this problem.

[    1.198516] am65-cpts 39000000.cpts: CPTS ver 0x4e8a010c, freq:500000000, add_val:1 pps:0
[    1.199553] k3-j72xx-soc-thermal b00000.temperature-sensor: invalid resource
[    1.199610] k3-j72xx-soc-thermal: probe of b00000.temperature-sensor failed with error -22
[    1.205100] gpio-478 (btuart_rts_sel): hogged as output/high
[    1.215101] vdd_mmc1: supplied by vcc_3v3_sys
[    1.216453] wlan_en: supplied by com8_ls_en
[    1.221198] debugfs: Directory 'pd:114' with parent 'pm_genpd' already present!
[    1.233072] mmc0: CQHCI version 5.10
[    1.233102] mmc1: CQHCI version 5.10
[    1.243409] ALSA device list:
[    1.243427]   No soundcards found.
[    1.275169] mmc0: SDHCI controller on fa10000.mmc [fa10000.mmc] using ADMA 64-bit
[    1.281845] sdhci-am654 fa10000.mmc: card claims to support voltages below defined range
[    1.290974] mmc1: SDHCI controller on fa00000.mmc [fa00000.mmc] using ADMA 64-bit
[    1.293044] Waiting for root device PARTUUID=a974ccb8-02...
[    1.295384] mmc0: new SDIO card at address 0001
[    1.334540] mmc1: error -110 whilst initialising SD card
[    1.594608] mmc1: error -110 whilst initialising SD card
[    1.863732] mmc1: error -110 whilst initialising SD card
[    2.145460] mmc1: error -110 whilst initialising SD card

Hi Debashis,

Debashis Mahanty said:

Actually, I already mentioned in another thread regarding a issue in SDK 9.0.

I reviewed again your previous thread but didn't see any reference to SDK9.0. What did I miss?

Debashis Mahanty said:

When we install SDK 9.0 with docker Ubuntu 18. we can not able to run ROS in that OS. There is some memory issue with that version while running the ROS executable.

I am not sure what "ROS" is, but for a quick test, you don't have to install SDK9.0, instead, you can just download the SDK9.0 SD card WIC image and flash it to a SD card to boot the board.

https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-yXgchBCk98/09.00.00.03/tisdk-default-image-am64xx-evm.wic.xz

Hi Bin,
You are correct We are doing the same as you said regarding the flash with WIC image.


And Sorry for that actually I have not given that thread related to ROS. You can refer the link below
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1261332/sk-am64b-memory-can-not-allocated/4792878?tisearch=e2e-sitesearch&keymatch=memoery%252520issue%252520Debashis#4792878

Regards
Debashis

Hi Debashis,

Thanks for pointing to this e2e thread. This solves some confusions.

But in that e2e thread, you can boot the SD card to Linux and run ROS program, but the SD card is failed in Linux in this thread. What is the difference between these two cases?