AM625: Boot failure on custom board

Koichiro Tashiro

Part Number: AM625

Hi,

My customer started evaluation for their custom board.
They are using SDK Linux (09.00.00.03) and created boot file, but below I2C error is generated.

-Boot SPL 2023.04-00001-gf5b119738d-dirty (Dec 13 2023 - 11:41:47 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 13376 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 00:42:57, Jan 13 2023

U-Boot SPL 2023.04-00001-gf5b119738d-dirty (Dec 13 2023 - 11:56:00 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 1856 bytes
i2c_write: error waiting for data ACK (status=0x116)
pca953x gpio@22: Error reading output register
** Bad device specification mmc 1 **
Couldn't find partition mmc 1:1
Error: could not access storage.
Trying to boot from MMC2
i2c_write: error waiting for data ACK (status=0x116)
pca953x gpio@22: Error reading output register
spl: mmc init failed with error: -70
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

It seems there is switch on MMC1 and it is controlled by IO expander via I2C on TI board.
There is no such switch on the custom board, so it may be the reason of the error.

Could you tell me how to avoid the error?

Thanks and regards,
Koichiro Tashiro

over 2 years ago

0 Nick Saulnier over 2 years ago

TI__Guru** 108860 points

Hello Koichiro-san,

I could assign your thread to our u-boot guy, but he is on vacation until January. So I'll start by pointing you to potentially helpful resources, even though I don't have any uboot experience.

Has the customer started by taking a look at the AM62x Academy, Linux module, "Porting U-Boot" page? I wonder if the customer is seeing an issue with the PMIC configuration

https://dev.ti.com/tirex/explore/node?node=A__Aea6RRpDjmWpbq1XT0xp3w__AM62-ACADEMY__uiYMDcq__LATEST

Regards,

Nick

+1 Andreas Dannenberg over 2 years ago

TI__Guru 70392 points

Koichiro Tashiro said:
It seems there is switch on MMC1 and it is controlled by IO expander via I2C on TI board.

Customer should remove the entire &main_i2c1 node from the DTS (https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/arch/arm/dts/k3-am625-sk.dts?h=ti-u-boot-2023.04#n406) if they don't have that I/O expander and nothing that needs I2C1 connectivity in U-Boot. This may result in some additional DTS build errors that can be resolved by removing any other reference/node that may be a dependency here.

Then, they can replace the regulator reference with something that provides a fixed 3.3V voltage, like this example form the device tree:

arch/arm/dts/am335x-bone-common.dtsi:   vmmcsd_fixed: fixedregulator0 {
arch/arm/dts/am335x-bone-common.dtsi-           compatible = "regulator-fixed";
arch/arm/dts/am335x-bone-common.dtsi:           regulator-name = "vmmcsd_fixed";
arch/arm/dts/am335x-bone-common.dtsi-           regulator-min-microvolt = <3300000>;
arch/arm/dts/am335x-bone-common.dtsi-           regulator-max-microvolt = <3300000>;
arch/arm/dts/am335x-bone-common.dtsi-   };

You can just fill in the contents of the node from the above BeagleBone definition into the existing vdd_mmc1 node of your AM62x file at https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/arch/arm/dts/k3-am625-sk.dts?h=ti-u-boot-2023.04#n135).

Regards, Andreas

Processors

Processors forum

AM625: Boot failure on custom board