AM625: I2C write error while booting from SD Card.

Mitesh Hiran

Part Number: AM625
Other Parts Discussed in Thread: SK-AM62, , SK-AM62B

Hello,

We have got a new board with AM625 SoC and we are trying to boot it from SD Card that is connected same as the Eval board SK-AM62 E3. (SD Card connected to MMC1 pins.)

Have set the boot pins to following. (for SD Card boot)

Bootmode0 and 1 to 1.

Bootmode2 to 0.

Bootmode3-5 to 0.

Bootmode6 to 1.

Bootmode7 and 8 to 0.

Bootmode9 to 1.

Bootmode10 to 15 to 0.

Boot Log:

says its trying to boot from MMC2 for some reason and then I get i2c write error.

over 2 years ago

0 Mitesh Hiran over 2 years ago

Mastermind 6215 points

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

Managed to remove gpio@22 ACK timeout error but disabling main_i2c1 in u bot device tree. but still have mmc init failed error.

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

Is this something to do with SD card power supply is 3.3V but the u-boot expect it to be 1.8V ?

I was under the impression the Eval board SK-AM62 by default was set to power the SD card with 3.3V but on measurement looks like it 1.8V.

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

When I try to add 'no-1-8-v' to the sdhci1 node in U-Boot arch/arm/dts/k3-am62-main.dtsi and rebuild U-Boot?

sdhci1: mmc@fa00000 {
compatible = "ti,am62-sdhci";
reg = <0x00 0xfa00000 0x00 0x260>, <0x00 0xfa08000 0x00 0x134>;
interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
power-domains = <&k3_pds 58 TI_SCI_PD_EXCLUSIVE>;
clocks = <&k3_clks 58 5>, <&k3_clks 58 6>;
clock-names = "clk_ahb", "clk_xin";
ti,trm-icp = <0x2>;
ti,otap-del-sel-legacy = <0x8>;
ti,otap-del-sel-sd-hs = <0x0>;
ti,otap-del-sel-sdr12 = <0x0>;
ti,otap-del-sel-sdr25 = <0x0>;
ti,otap-del-sel-sdr50 = <0x8>;
ti,otap-del-sel-sdr104 = <0x7>;
ti,otap-del-sel-ddr50 = <0x4>;
ti,itap-del-sel-legacy = <0xa>;
ti,itap-del-sel-sd-hs = <0x1>;
ti,itap-del-sel-sdr12 = <0xA>;
ti,itap-del-sel-sdr25 = <0x1>;
ti,clkbuf-sel = <0x7>;
bus-width = <4>;
no-1-8-v;
};

I get out of memory error:

home/miteshhiran/ti-processor-sdk-linux-am62xx-evm-08.06.00.42/board-support/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654/tools/k3_gen_x509_cert.sh -c 16 -b spl/u-boot-spl.bin \
-o tiboot3.bin -l 0x43c00000 -r 1 -k ""
SWRV = 1
SYM spl/u-boot-spl.sym
spl/u-boot-spl.bin exceeds file size limit:
limit: 0x30220 bytes
actual: 0x3022c bytes
excess: 0xc bytes

/home/miteshhiran/ti-processor-sdk-linux-am62xx-evm-08.06.00.42/board-support/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654/Makefile:1929: recipe for target 'spl/u-boot-spl.bin' failed
make[2]: *** [spl/u-boot-spl.bin] Error 1
make[2]: *** Deleting file 'spl/u-boot-spl.bin'

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

However, with 'no-1-8-v' it still fails with mmc init failed error -70

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

When I probe the clock connected to sd card, mmc1_clk (B22), its 396.8kHz.

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

These are the changes we have done from the SDK v08.06.00.42 on the u-boot.

Fullscreen u-boot-patch.txt Download

diff --git a/arch/arm/dts/k3-am625-sk.dts b/arch/arm/dts/k3-am625-sk.dts
index bfe1e78ed8..667eb21ca5 100644
--- a/arch/arm/dts/k3-am625-sk.dts
+++ b/arch/arm/dts/k3-am625-sk.dts
@@ -84,3 +84,8 @@
 		};
 	};
 };
+
+
+&main_i2c1 {
+	status = "disabled";
+};
diff --git a/arch/arm/mach-k3/am625_init.c b/arch/arm/mach-k3/am625_init.c
index d103c73770..504b9a2b35 100644
--- a/arch/arm/mach-k3/am625_init.c
+++ b/arch/arm/mach-k3/am625_init.c
@@ -25,6 +25,9 @@
 #define K3RTC_KICK0_UNLOCK_VALUE	0x83e70b13
 #define K3RTC_KICK1_UNLOCK_VALUE	0x95a4f1e0
 
+/*eMMC boot mode fix */
+#define EMMC_BOOT	9
+
 #if defined(CONFIG_SPL_BUILD)
 
 /*
@@ -245,6 +248,10 @@ u32 spl_mmc_boot_mode(const u32 boot_device)
 
 	switch (boot_device) {
 	case BOOT_DEVICE_MMC1:
+		if (((devstat & MAIN_DEVSTAT_PRIMARY_BOOTMODE_MASK) >>
+                     MAIN_DEVSTAT_PRIMARY_BOOTMODE_SHIFT) == EMMC_BOOT)
+                        return MMCSD_MODE_EMMCBOOT;
+
 		if ((bootmode_cfg & MAIN_DEVSTAT_PRIMARY_MMC_FS_RAW_MASK) >>
 		     MAIN_DEVSTAT_PRIMARY_MMC_FS_RAW_SHIFT)
 			return MMCSD_MODE_EMMCBOOT;
diff --git a/configs/am62x_evm_a53_defconfig b/configs/am62x_evm_a53_defconfig
index d9bf9a5b7d..509500dc2b 100644
--- a/configs/am62x_evm_a53_defconfig
+++ b/configs/am62x_evm_a53_defconfig
@@ -82,7 +82,7 @@ CONFIG_MULTI_DTB_FIT=y
 CONFIG_SPL_MULTI_DTB_FIT=y
 CONFIG_SPL_MULTI_DTB_FIT_NO_COMPRESSION=y
 CONFIG_ENV_IS_IN_MMC=y
-CONFIG_SYS_MMC_ENV_PART=1
+CONFIG_SYS_MMC_ENV_PART=2
 CONFIG_NET_RANDOM_ETHADDR=y
 CONFIG_DM=y
 CONFIG_SPL_DM=y
@@ -124,8 +124,8 @@ CONFIG_MMC_IO_VOLTAGE=y
 CONFIG_SPL_MMC_IO_VOLTAGE=y
 CONFIG_MMC_UHS_SUPPORT=y
 CONFIG_SPL_MMC_UHS_SUPPORT=y
-CONFIG_MMC_HS200_SUPPORT=y
-CONFIG_SPL_MMC_HS200_SUPPORT=y
+CONFIG_MMC_HS200_SUPPORT=n
+CONFIG_SPL_MMC_HS200_SUPPORT=n
 CONFIG_MMC_SDHCI=y
 CONFIG_MMC_SDHCI_ADMA=y
 CONFIG_SPL_MMC_SDHCI_ADMA=y

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

Tested again, so during u-boot, the mmc1 clk is 25MHz and then falls to 396.8kHz (probably after the mmc init failed error) and then stops.

0 Andreas Dannenberg over 2 years ago in reply to Mitesh Hiran

TI__Guru 69652 points

Hi Mitesh,

will look at this first thing next week and get back to you.

Regards, Andreas

0 Mitesh Hiran over 2 years ago in reply to Andreas Dannenberg

Mastermind 6215 points

Thanks a lot Andreas.

0 Mitesh Hiran over 2 years ago in reply to Andreas Dannenberg

Mastermind 6215 points

Please let us know if there is nay information is needed to solve this.

Thanks

0 Andreas Dannenberg over 2 years ago in reply to Mitesh Hiran

TI__Guru 69652 points

Mitesh Hiran said:
I was under the impression the Eval board SK-AM62 by default was set to power the SD card with 3.3V but on measurement looks like it 1.8V.

The SK-AM62 board powers the SD card slot with 3.3V, but the I/O voltage can be either 1.8V or 3.3V as selected using a GPIO pin. All the higher speed transfer modes like SDR104, SDR50, DDR50, HS200, and HS400 require 1.8V I/O voltages. So if your board is wired in a way that it uses 3.3V for the I/O voltage you cannot use those higher speed modes, and adding the no-1-8-v DTS property would be the correct way to get things going.

Mitesh Hiran said:
I get out of memory error:

home/miteshhiran/ti-processor-sdk-linux-am62xx-evm-08.06.00.42/board-support/u-boot-2021.01+gitAUTOINC+2ee8efd654-g2ee8efd654/tools/k3_gen_x509_cert.sh -c 16 -b spl/u-boot-spl.bin \
-o tiboot3.bin -l 0x43c00000 -r 1 -k ""
SWRV = 1
SYM spl/u-boot-spl.sym
spl/u-boot-spl.bin exceeds file size limit:
limit: 0x30220 bytes
actual: 0x3022c bytes
excess: 0xc bytes

Try freeing up some memory by disabling some CONFIG options you don't need for the first stage bootloader (R5 SPL, also known as "tiboot3.bin"). This stage runs from internal SRAM and space is very VERY tight.

For example, if you don't need SPI flash support, try turning off all of the below CONFIG options in your configs/am62x_evm_r5_defconfig equivalent file. This should free quite a bit of memory.

CONFIG_SYS_SPI_U_BOOT_OFFS
CONFIG_SPL_DM_SPI
CONFIG_SPL_SPI_FLASH_SUPPORT
CONFIG_SPL_SPI_SUPPORT
CONFIG_SPL_DM_SPI_FLASH
CONFIG_SPL_SPI_FLASH_SFDP_SUPPORT
CONFIG_SPL_SPI_LOAD

Regards, Andreas

0 Mitesh Hiran over 2 years ago in reply to Andreas Dannenberg

Mastermind 6215 points

Thanks Andreas,

I tried both removing 'CONFIG_*' and adding 'no-1-8-v' so can build the u-boot but still getting the same error of mmc init failed with error -70

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

And what does mmc init failed error 70 means please?

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

And where can I find the driver for the mmc in u-boot please?

to debug the mmc init failed error.

Thanks

0 Mitesh Hiran over 2 years ago in reply to Mitesh Hiran

Mastermind 6215 points

Found the driver for MMC but there is not about init failed...

drivers/mmc/host/sdhci_am654.c

0 Andreas Dannenberg over 2 years ago in reply to Mitesh Hiran

TI__Guru 69652 points

Mitesh Hiran said:
And what does mmc init failed error 70 means please?

include/linux/errno.h:#define ECOMM 70 /* Communication error on send */

So as the comment says, some communication related error. The fact however that you have ROM-loading-SPL R5 and SPL-loading-SPL A53 is all working gives hope that we should be able to continue to keep the boot chain going with the right software changes.

Mitesh Hiran said:
says its trying to boot from MMC2 for some reason and then I get i2c write error.

That's actually expected (and confusing). If I boot my SK-AM62B board from SD card which is connected to the mmc1 peripheral module (mmc0 is eMMC, mmc2 is WiFi/M.2 slot), I get that same message, so that's not something we need to be worried about in this context. See my own bootlog below for reference (it uses SDK 9.0 U-Boot 2023.04, but boot log on U-Boot 2021.01 what you use should be very similar). ..

U-Boot SPL 2023.04-g765cab112d (Jul 11 2023 - 11:12:53 +0000)
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-g765cab112d (Jul 11 2023 - 11:12:53 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.0.5--v09.00.05 (Kool Koala)')
SPL initial stack usage: 1856 bytes
Trying to boot from MMC2
Authentication passed
Authentication passed


U-Boot 2023.04-g765cab112d (Jul 11 2023 - 11:12:53 +0000)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Board: AM62B-SKEVM rev A
DRAM:  2 GiB
Core:  69 devices, 29 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0

Can you post all(!) of your device tree files (and their filenames) used during your U-Boot boot for review? It could be that some A53 SPL specific dts definition is not correct.

Regards, Andreas

0 Mitesh Hiran over 2 years ago in reply to Andreas Dannenberg

Mastermind 6215 points

Sorry Andreas, was on leave back in office now.

Attached is the patch showing all the changes we have made for u-boot.

Fullscreen uBoot-patch.txt Download

diff --git a/arch/arm/dts/k3-am625-sk-u-boot.dtsi b/arch/arm/dts/k3-am625-sk-u-boot.dtsi
index 8e491f9359..62f9cf2c11 100644
--- a/arch/arm/dts/k3-am625-sk-u-boot.dtsi
+++ b/arch/arm/dts/k3-am625-sk-u-boot.dtsi
@@ -50,22 +50,22 @@
 	u-boot,dm-spl;
 };
 
-&vcc_5v0 {
-	u-boot,dm-spl;
-};
+//&vcc_5v0 {
+//	u-boot,dm-spl;
+//};
 
 &vcc_3v3_sys {
 	u-boot,dm-spl;
 };
 
-&vdd_mmc1 {
-	u-boot,dm-spl;
-};
+//&vdd_mmc1 {
+//	u-boot,dm-spl;
+//};
 
-&vdd_sd_dv {
-	u-boot,dm-spl;
-};
+//&vdd_sd_dv {
+//	u-boot,dm-spl;
+//};
 
-&vdd_sd_dv_pins_default {
-	u-boot,dm-spl;
-};
+//&vdd_sd_dv_pins_default {
+//	u-boot,dm-spl;
+//};
diff --git a/arch/arm/dts/k3-am625-sk.dts b/arch/arm/dts/k3-am625-sk.dts
index bfe1e78ed8..4fa4aacbf7 100644
--- a/arch/arm/dts/k3-am625-sk.dts
+++ b/arch/arm/dts/k3-am625-sk.dts
@@ -11,7 +11,7 @@
 
 / {
 	compatible =  "ti,am625-sk", "ti,am625";
-	model = "Texas Instruments AM625 SK";
+	model = "Coda Octopus Dive - Voice Processor";
 };
 
 &cpsw_port2 {
@@ -84,3 +84,16 @@
 		};
 	};
 };
+
+
+&main_i2c1 {
+	status = "disabled";
+};
+
+&ospi0 {
+	status = "disabled";
+};
+
+&sdhci2 {
+	status = "disabled";
+};
diff --git a/arch/arm/dts/k3-am62x-sk-common.dtsi b/arch/arm/dts/k3-am62x-sk-common.dtsi
index 72ebb1400f..c3b5c9b08d 100644
--- a/arch/arm/dts/k3-am62x-sk-common.dtsi
+++ b/arch/arm/dts/k3-am62x-sk-common.dtsi
@@ -82,16 +82,16 @@
 		regulator-boot-on;
 	};
 
-	vcc_5v0: regulator-1 {
-		/* Output of LM34936 */
-		compatible = "regulator-fixed";
-		regulator-name = "vcc_5v0";
-		regulator-min-microvolt = <5000000>;
-		regulator-max-microvolt = <5000000>;
-		vin-supply = <&vmain_pd>;
-		regulator-always-on;
-		regulator-boot-on;
-	};
+	//vcc_5v0: regulator-1 {
+	//	/* Output of LM34936 */
+	//	compatible = "regulator-fixed";
+	//	regulator-name = "vcc_5v0";
+	//	regulator-min-microvolt = <5000000>;
+	//	regulator-max-microvolt = <5000000>;
+	//	vin-supply = <&vmain_pd>;
+	//	regulator-always-on;
+	//	regulator-boot-on;
+	//};
 
 	vcc_3v3_sys: regulator-2 {
 		/* output of LM61460-Q1 */
@@ -104,46 +104,46 @@
 		regulator-boot-on;
 	};
 
-	vdd_mmc1: fixed-regulator-sd {
-		/* TPS22918DBVR */
-		compatible = "regulator-fixed";
-		regulator-name = "vdd_mmc1";
-		regulator-min-microvolt = <3300000>;
-		regulator-max-microvolt = <3300000>;
-		regulator-boot-on;
-		enable-active-high;
-		vin-supply = <&vcc_3v3_sys>;
-		gpio = <&exp1 3 GPIO_ACTIVE_HIGH>;
-	};
-
-	vdd_sd_dv: gpio-regulator-TLV71033 {
-		/* Output of TLV71033 */
-		compatible = "regulator-gpio";
-		regulator-name = "tlv71033";
-		pinctrl-names = "default";
-		pinctrl-0 = <&vdd_sd_dv_pins_default>;
-		regulator-min-microvolt = <1800000>;
-		regulator-max-microvolt = <3300000>;
-		regulator-boot-on;
-		vin-supply = <&vcc_5v0>;
-		gpios = <&main_gpio0 31 GPIO_ACTIVE_HIGH>;
-		states = <1800000 0x0>,
-			 <3300000 0x1>;
-	};
-
-	leds {
-		compatible = "gpio-leds";
-		pinctrl-names = "default";
-		pinctrl-0 = <&usr_led_pins_default>;
-
-		led-0 {
-			label = "am62-sk:green:heartbeat";
-			gpios = <&main_gpio1 49 GPIO_ACTIVE_HIGH>;
-			linux,default-trigger = "heartbeat";
-			function = LED_FUNCTION_HEARTBEAT;
-			default-state = "off";
-		};
-	};
+	//vdd_mmc1: fixed-regulator-sd {
+	//	/* TPS22918DBVR */
+	//	compatible = "regulator-fixed";
+	//	regulator-name = "vdd_mmc1";
+	//	regulator-min-microvolt = <3300000>;
+	//	regulator-max-microvolt = <3300000>;
+	//	regulator-boot-on;
+	//	enable-active-high;
+	//	vin-supply = <&vcc_3v3_sys>;
+	//	gpio = <&exp1 3 GPIO_ACTIVE_HIGH>;
+	//};
+
+	//vdd_sd_dv: gpio-regulator-TLV71033 {
+	//	/* Output of TLV71033 */
+	//	compatible = "regulator-gpio";
+	//	regulator-name = "tlv71033";
+	//	pinctrl-names = "default";
+	//	pinctrl-0 = <&vdd_sd_dv_pins_default>;
+	//	regulator-min-microvolt = <1800000>;
+	//	regulator-max-microvolt = <3300000>;
+	//	regulator-boot-on;
+	//	vin-supply = <&vcc_5v0>;
+	//	gpios = <&main_gpio0 31 GPIO_ACTIVE_HIGH>;
+	//	states = <1800000 0x0>,
+	//		 <3300000 0x1>;
+	//};
+
+	//leds {
+	//	compatible = "gpio-leds";
+	//	pinctrl-names = "default";
+	//	pinctrl-0 = <&usr_led_pins_default>;
+
+	//	led-0 {
+	//		label = "am62-sk:green:heartbeat";
+	//		gpios = <&main_gpio1 49 GPIO_ACTIVE_HIGH>;
+	//		linux,default-trigger = "heartbeat";
+	//		function = LED_FUNCTION_HEARTBEAT;
+	//		default-state = "off";
+	//	};
+	//};
 
 	extcon_usb0: extcon-usb0 {
 		compatible = "linux,extcon-usb-gpio";
@@ -386,12 +386,13 @@
 
 &sdhci1 {
 	/* SD/MMC */
-	vmmc-supply = <&vdd_mmc1>;
-	vqmmc-supply = <&vdd_sd_dv>;
+	vmmc-supply = <&vcc_3v3_sys>;
+	//vqmmc-supply = <&vdd_sd_dv>;
 	pinctrl-names = "default";
 	pinctrl-0 = <&main_mmc1_pins_default>;
 	ti,driver-strength-ohm = <50>;
 	disable-wp;
+	no-1-8-v; /* disabling all the UHS modes */
 };
 
 &usbss0 {
diff --git a/arch/arm/mach-k3/am625_init.c b/arch/arm/mach-k3/am625_init.c
index d103c73770..504b9a2b35 100644
--- a/arch/arm/mach-k3/am625_init.c
+++ b/arch/arm/mach-k3/am625_init.c
@@ -25,6 +25,9 @@
 #define K3RTC_KICK0_UNLOCK_VALUE	0x83e70b13
 #define K3RTC_KICK1_UNLOCK_VALUE	0x95a4f1e0
 
+/*eMMC boot mode fix */
+#define EMMC_BOOT	9
+
 #if defined(CONFIG_SPL_BUILD)
 
 /*
@@ -245,6 +248,10 @@ u32 spl_mmc_boot_mode(const u32 boot_device)
 
 	switch (boot_device) {
 	case BOOT_DEVICE_MMC1:
+		if (((devstat & MAIN_DEVSTAT_PRIMARY_BOOTMODE_MASK) >>
+                     MAIN_DEVSTAT_PRIMARY_BOOTMODE_SHIFT) == EMMC_BOOT)
+                        return MMCSD_MODE_EMMCBOOT;
+
 		if ((bootmode_cfg & MAIN_DEVSTAT_PRIMARY_MMC_FS_RAW_MASK) >>
 		     MAIN_DEVSTAT_PRIMARY_MMC_FS_RAW_SHIFT)
 			return MMCSD_MODE_EMMCBOOT;
diff --git a/configs/am62x_evm_a53_defconfig b/configs/am62x_evm_a53_defconfig
index d9bf9a5b7d..509500dc2b 100644
--- a/configs/am62x_evm_a53_defconfig
+++ b/configs/am62x_evm_a53_defconfig
@@ -82,7 +82,7 @@ CONFIG_MULTI_DTB_FIT=y
 CONFIG_SPL_MULTI_DTB_FIT=y
 CONFIG_SPL_MULTI_DTB_FIT_NO_COMPRESSION=y
 CONFIG_ENV_IS_IN_MMC=y
-CONFIG_SYS_MMC_ENV_PART=1
+CONFIG_SYS_MMC_ENV_PART=2
 CONFIG_NET_RANDOM_ETHADDR=y
 CONFIG_DM=y
 CONFIG_SPL_DM=y
@@ -124,8 +124,8 @@ CONFIG_MMC_IO_VOLTAGE=y
 CONFIG_SPL_MMC_IO_VOLTAGE=y
 CONFIG_MMC_UHS_SUPPORT=y
 CONFIG_SPL_MMC_UHS_SUPPORT=y
-CONFIG_MMC_HS200_SUPPORT=y
-CONFIG_SPL_MMC_HS200_SUPPORT=y
+CONFIG_MMC_HS200_SUPPORT=n
+CONFIG_SPL_MMC_HS200_SUPPORT=n
 CONFIG_MMC_SDHCI=y
 CONFIG_MMC_SDHCI_ADMA=y
 CONFIG_SPL_MMC_SDHCI_ADMA=y
diff --git a/configs/am62x_evm_r5_defconfig b/configs/am62x_evm_r5_defconfig
index 18a619cdc1..7bb26b040f 100644
--- a/configs/am62x_evm_r5_defconfig
+++ b/configs/am62x_evm_r5_defconfig
@@ -10,9 +10,9 @@ CONFIG_SOC_K3_AM625=y
 CONFIG_TARGET_AM625_R5_EVM=y
 CONFIG_ENV_SIZE=0x20000
 CONFIG_ENV_OFFSET=0x680000
-CONFIG_SYS_SPI_U_BOOT_OFFS=0x80000
+# CONFIG_SYS_SPI_U_BOOT_OFFS=0x80000
 CONFIG_DM_GPIO=y
-CONFIG_SPL_DM_SPI=y
+CONFIG_SPL_DM_SPI=n
 CONFIG_SPL_TEXT_BASE=0x43c00000
 CONFIG_SPL_MMC_SUPPORT=y
 CONFIG_SPL_SERIAL_SUPPORT=y
@@ -24,8 +24,8 @@ CONFIG_SPL_SIZE_LIMIT_SUBTRACT_GD=y
 CONFIG_SPL_SIZE_LIMIT_PROVIDE_STACK=0x3500
 CONFIG_SPL_FS_FAT=y
 CONFIG_SPL_LIBDISK_SUPPORT=y
-CONFIG_SPL_SPI_FLASH_SUPPORT=y
-CONFIG_SPL_SPI_SUPPORT=y
+CONFIG_SPL_SPI_FLASH_SUPPORT=n
+CONFIG_SPL_SPI_SUPPORT=n
 CONFIG_DEFAULT_DEVICE_TREE="k3-am625-r5-sk"
 CONFIG_SPL_LOAD_FIT=y
 CONFIG_SPL_LOAD_FIT_ADDRESS=0x80080000
@@ -42,15 +42,15 @@ CONFIG_SPL_DMA=y
 CONFIG_SPL_ENV_SUPPORT=y
 CONFIG_SPL_I2C_SUPPORT=y
 CONFIG_SPL_DM_MAILBOX=y
-CONFIG_SPL_DM_SPI_FLASH=y
+CONFIG_SPL_DM_SPI_FLASH=n
 CONFIG_SPL_DM_RESET=y
 CONFIG_SPL_POWER_DOMAIN=y
 CONFIG_SPL_RAM_SUPPORT=y
 CONFIG_SPL_RAM_DEVICE=y
 CONFIG_SPL_REMOTEPROC=y
 # CONFIG_SPL_SPI_FLASH_TINY is not set
-CONFIG_SPL_SPI_FLASH_SFDP_SUPPORT=y
-CONFIG_SPL_SPI_LOAD=y
+CONFIG_SPL_SPI_FLASH_SFDP_SUPPORT=n
+CONFIG_SPL_SPI_LOAD=n
 CONFIG_SPL_THERMAL=y
 CONFIG_SPL_YMODEM_SUPPORT=y
 CONFIG_HUSH_PARSER=y

0 Mitesh Hiran over 2 years ago in reply to Andreas Dannenberg

Mastermind 6215 points

I am also hopping this would be some things related to u-boot and not hardware fault.

Thanks

0 Mitesh Hiran over 2 years ago in reply to Andreas Dannenberg

Mastermind 6215 points

Also Andreas,

I am not using any of the following on Hardware level, do you think any of these could be causing comms error on MMC please?

WKUP_I2S0, WKUP_CLKOut0, WKUP_LFOSC0_X*, WKUP_UART0.

MCU_SPI0, MCU_UART0,

Thanks

0 Andreas Dannenberg over 1 year ago in reply to Mitesh Hiran

TI__Guru 69652 points

Hi Mitesh,

Mitesh Hiran said:
I am not using any of the following on Hardware level, do you think any of these could be causing comms error on MMC please?

WKUP_I2S0, WKUP_CLKOut0, WKUP_LFOSC0_X*, WKUP_UART0.

MCU_SPI0, MCU_UART0,

No this is not related, there should not be any dependency. Give me a day or two to come back to review your DTS files and perhaps come up with some additional suggestions.

Regards, Andreas

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Thanks Andreas. Much appreciated.

0 Andreas Dannenberg over 1 year ago in reply to Mitesh Hiran

TI__Guru 69652 points

Hi Mitesh,

please allow a couple of more days for a response. Thanks for your patience.

Regards, Andreas

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Hi Andreas, any update on this please?

0 Mitesh Hiran over 1 year ago in reply to Mitesh Hiran

Mastermind 6215 points

Hi Andreas,

On more debug, this seems to be due to the switchable regulator (TLV7103318) used to power SD card with 3.3 or 1.8 with GPIO0_31.

But I don't use this GPIO nor the switchable power supply. We power the sd card logic directly from 3.3V.

vdd_sd_dv: gpio-regulator-TLV71033 {
/* Output of TLV71033 */
compatible = "regulator-gpio";
regulator-name = "tlv71033";
pinctrl-names = "default";
pinctrl-0 = <&vdd_sd_dv_pins_default>;
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <3300000>;
regulator-boot-on;
vin-supply = <&vcc_5v0>;
gpios = <&main_gpio0 31 GPIO_ACTIVE_HIGH>;
states = <1800000 0x0>,
<3300000 0x1>;
};

0 Mitesh Hiran over 1 year ago in reply to Mitesh Hiran

Mastermind 6215 points

Please let me know on the Eval board, how to set the IO voltage to 3.3v for sd card.

0 Mitesh Hiran over 1 year ago in reply to Mitesh Hiran

Mastermind 6215 points

I Don't understand why the U-boot fails when the SD card and the IO voltage for the SD card interface are set to 3.3v on the eval SK-AM62 board.

Error:

While U-boot: mmc failed to init error -70.

0 Andreas Dannenberg over 1 year ago in reply to Mitesh Hiran

TI__Guru 69652 points

Mitesh Hiran said:
I Don't understand why the U-boot fails when the SD card and the IO voltage for the SD card interface are set to 3.3v on the eval SK-AM62 board.

Error:

While U-boot: mmc failed to init error -70.

Looks like you completely removed the vqmmc-supply property...

&sdhci1 {
/* SD/MMC */
- vmmc-supply = <&vdd_mmc1>;
- vqmmc-supply = <&vdd_sd_dv>;
+ vmmc-supply = <&vcc_3v3_sys>;
+ //vqmmc-supply = <&vdd_sd_dv>;

...however it is being accessed during the SD card driver operation (inside drivers/mmc/sdhci.c), and certain calls will fail if it is not there. You could try setting this property to the same 3.3V fixed voltage of vcc_3v3_sys you are already using for vmmc-supply to see if this improves things.

Regards, Andreas

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Thanks, will try right now and update.

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Hi Andreas

With this change, got following error on eval board.

U-Boot SPL 2021.01-00002-g27f28e9f8f-dirty (Sep 25 2023 - 04:47:19 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate t
o prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate t
o prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate t
o prevent boot failure. This will fail if the image was also encrypted
Loading Environment from MMC... *** Warning - No MMC card found, using default e
nvironment

Starting ATF on ARM64 core...

NOTICE: BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE: BL31: Built : 05:06:58, Feb 24 2023

U-Boot SPL 2021.01-00002-g27f28e9f8f-dirty (Sep 25 2023 - 04:47:10 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from MMC2
failed to set vqmmc-voltage to 3.3V
failed to set vqmmc-voltage to 3.3V
failed to set vqmmc-voltage to 3.3V
failed to set vqmmc-voltage to 3.3V
failed to set vqmmc-voltage to 1.8V
failed to set vqmmc-voltage to 1.8V
spl: mmc init failed with error: -70
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

0 Andreas Dannenberg over 1 year ago in reply to Mitesh Hiran

TI__Guru 69652 points

Try updating your vcc_3v3_sys node like it is used in other DTS files, for example arch/arm/dts/k3-am62x-sk-common.dtsi (note how it actually defines voltages):

vcc_3v3_sys: regulator-2 {
        /* output of LM61460-Q1 */
        compatible = "regulator-fixed";
        regulator-name = "vcc_3v3_sys";
        regulator-min-microvolt = <3300000>;
        regulator-max-microvolt = <3300000>;
        vin-supply = <&vmain_pd>;
        regulator-always-on;
        regulator-boot-on;
};

Mitesh Hiran said:
failed to set vqmmc-voltage to 1.8V
failed to set vqmmc-voltage to 1.8V

I would not expect this to happen with no-1-8-v included in your DTS node, so at a minimum this is strange, so there might be something else amiss here. But perhaps its a fallback mechanism as switching to 3.3V fails. So this may need some additional debugging/understanding.

Regards, Andreas

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

I am using the same node definition for 'vcc_3v3_sys' as

DTS files, for example arch/arm/dts/k3-am62x-sk-common.dtsi

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Yes, something doesn't add up.

It looks like as long as the SD Card Supply U19 (Rev 3 SK-AM62) output is 1.8V the system works if this is set to 3.3V we get mmc init failed.

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Could you please tell us how is 'k3-am625-sk-u-boot.dtsi' file is related for AM625 booting?

0 Mitesh Hiran over 1 year ago in reply to Mitesh Hiran

Mastermind 6215 points

The IO supply for the SD Card seems to be always 1.8v, this is used for VDDSHV5 (IO Bank 5) on AM625. Can this support 3.3V?

When set to 3.3V then we get mmc init failed error during u-boot.

0 Mitesh Hiran over 1 year ago in reply to Mitesh Hiran

Mastermind 6215 points

Hi Andreas, where can we find the driver for the mmc sd card boot logic in the SDK please?

Thanks.

0 Mitesh Hiran over 1 year ago in reply to Mitesh Hiran

Mastermind 6215 points

Some more info for debug:

please let us know, if you can see anything wrong on the setup.

Fullscreen uboot-failed.txt Download

�
U-Boot SPL 2021.01-00002-g27f28e9f8f-dirty (Sep 25 2023 - 08:27:43 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
CMD_SEND:0
		ARG			 0x00000000
		MMC_RSP_NONE
CMD_SEND:8
		ARG			 0x000001aa
		MMC_RSP_R1,5,6,7 	 0x000001aa 
CMD_SEND:55
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x00000120 
CMD_SEND:41
		ARG			 0x40300000
		MMC_RSP_R3,4		 0x00ff8000 
CMD_SEND:55
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x00000120 
CMD_SEND:41
		ARG			 0x40300000
		MMC_RSP_R3,4		 0xc0ff8000 
CMD_SEND:2
		ARG			 0x00000000
		MMC_RSP_R2		 0xad4c5355 
		          		 0x53443030 
		          		 0x10439494 
		          		 0x09016500 

					DUMPING DATA
					000 - ad 4c 53 55 
					004 - 53 44 30 30 
					008 - 10 43 94 94 
					012 - 09 01 65 00 
CMD_SEND:3
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x59b40520 
CMD_SEND:9
		ARG			 0x59b40000
		MMC_RSP_R2		 0x400e0032 
		          		 0xdb790000 
		          		 0xec537f80 
		          		 0x0a400000 

					DUMPING DATA
					000 - 40 0e 00 32 
					004 - db 79 00 00 
					008 - ec 53 7f 80 
					012 - 0a 40 00 00 
CMD_SEND:7
		ARG			 0x59b40000
		MMC_RSP_R1,5,6,7 	 0x00000700 
CMD_SEND:55
		ARG			 0x59b40000
		MMC_RSP_R1,5,6,7 	 0x00000920 
CMD_SEND:51
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x00000920 
CMD_SEND:6
		ARG			 0x00fffff1
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:55
		ARG			 0x59b40000
		MMC_RSP_R1,5,6,7 	 0x00000920 
CMD_SEND:6
		ARG			 0x00000002
		MMC_RSP_R1,5,6,7 	 0x00000920 
CMD_SEND:6
		ARG			 0x80fffff1
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000800
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000800
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x000017e2
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000820
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00013c53
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000800
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x000017e2
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000820
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a66
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00013c53
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00013c55
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000800
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x000017e2
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000820
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a66
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00013c55
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00013c56
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00013caf
		MMC_RSP_R1,5,6,7 	 0x00000900 
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000800
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x000017e2
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000820
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a66
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a6c
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00013caf
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00013fe6
		MMC_RSP_R1,5,6,7 	 0x00000900 
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000800
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x000017e2
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000820
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a66
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a6c
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00013fe6
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a72
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00013fe7
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00014113
		MMC_RSP_R1,5,6,7 	 0x00000900 
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000800
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x000017e2
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000820
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a66
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a6c
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a72
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00014113
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00014114
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x0001437f
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x00000800
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x000017e2
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000820
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a66
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a6c
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00000a72
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x0001437f
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:18
		ARG			 0x00014380
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:12
		ARG			 0x00000000
		MMC_RSP_R1b		 0x00000b00 
CMD_SEND:16
		ARG			 0x00000200
		MMC_RSP_R1,5,6,7 	 0x00000900 
CMD_SEND:17
		ARG			 0x000143a4
		MMC_RSP_R1,5,6,7 	 0x00000900 
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 05:06:58, Feb 24 2023

U-Boot SPL 2021.01-00002-g27f28e9f8f-dirty (Sep 25 2023 - 08:27:35 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from MMC2
CMD_SEND:0
		ARG			 0x00000000
		MMC_RSP_NONE
CMD_SEND:8
		ARG			 0x000001aa
		MMC_RSP_R1,5,6,7 	 0x000001aa 
CMD_SEND:55
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x00000120 
CMD_SEND:41
		ARG			 0x41300000
		MMC_RSP_R3,4		 0x00ff8000 
CMD_SEND:55
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x00000120 
CMD_SEND:41
		ARG			 0x41300000
		MMC_RSP_R3,4		 0xc1ff8000 
CMD_SEND:11
		ARG			 0x00000000
		MMC_RSP_R1,5,6,7 	 0x00000320 
CMD_SEND:2
		ARG			 0x00000000
		RET			 -70
spl: mmc init failed with error: -70
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

0 Mitesh Hiran over 1 year ago in reply to Mitesh Hiran

Mastermind 6215 points

Please let us know, if this gives you any additional info to help us to fix this issue.

Thanks

0 Andreas Dannenberg over 1 year ago in reply to Mitesh Hiran

TI__Guru 69652 points

Hi Mitesh,

thanks for the various posts but there's too much going on here on this thread so what I want to do is to try to hopefully bring up 3.3V SD card operation on my own SK-AM62 board, and then provide this back as a "known-good" example. If things go well I might be able to free up some time on Friday to work this.

Regards, Andreas

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Okay Thanks.

Yes, would be good to know if the booting from SD Card logic works when the IO group voltage is set to 3.3 instead of 1.8.

Thanks

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Morning Andreas, please let me know if you get chance to review this today. Our project has completed stopped due to this issue.

Thanks

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Hi Andreas, not sure if you got any chance on trying this issue for us?

Would really help if you could tell us what do you think is wrong with this.

Is something wrong with SD Card itself? or clocks or data lines?

or something wrong with the SPL?

could this be any where related to power sequencing of the system? or anything please?

Thanks

0 Mitesh Hiran over 1 year ago in reply to Mitesh Hiran

Mastermind 6215 points

Hi Andreas, I have added some debug messages in the SD Card driver in u-boot and this is what I see:

Note: I have used the SDK to create the partition of the SD card again and the log is same.

U-Boot SPL 2021.01-00002-g27f28e9f8f-dirty (Oct 02 2023 - 00:36:46 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE: BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE: BL31: Built : 05:06:58, Feb 24 2023

U-Boot SPL 2021.01-00002-g27f28e9f8f-dirty (Oct 02 2023 - 00:36:37 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from MMC2
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
sdhci_send_command -> start
sdhci_send_command -> ECOMM
** Partition 1 not valid on device 1 **
spl_register_fat_device: fat register err - -1
spl_load_image_fat: error reading image u-boot.img, err - -1
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

0 Bin Liu over 1 year ago in reply to Mitesh Hiran

TI__Guru**** 168291 points

Hi Mitesh,

Andreas is out of office today. Please expect delayed response.

+1 Andreas Dannenberg over 1 year ago in reply to Bin Liu

TI__Guru 69652 points

Hi Mitesh,

I spent some time today experimenting with my SK-AM62A board, trying to force it to only use 3.3V for the SD card (not 1.8V), and I was able to boot to U-Boot prompt without any issues with the following modification applied on top of the SDK v8.6 U-Boot:

diff --git a/arch/arm/dts/k3-am62x-sk-common.dtsi b/arch/arm/dts/k3-am62x-sk-common.dtsi
index 72ebb1400f..1875c0dd01 100644
--- a/arch/arm/dts/k3-am62x-sk-common.dtsi
+++ b/arch/arm/dts/k3-am62x-sk-common.dtsi
@@ -387,11 +387,12 @@
 &sdhci1 {
        /* SD/MMC */
        vmmc-supply = <&vdd_mmc1>;
-       vqmmc-supply = <&vdd_sd_dv>;
+       vqmmc-supply = <&vdd_mmc1>;
        pinctrl-names = "default";
        pinctrl-0 = <&main_mmc1_pins_default>;
        ti,driver-strength-ohm = <50>;
        disable-wp;
+       no-1-8-v;
 };

 &usbss0 {
diff --git a/configs/am62x_evm_a53_defconfig b/configs/am62x_evm_a53_defconfig
index d9bf9a5b7d..fd95cbe7b7 100644
--- a/configs/am62x_evm_a53_defconfig
+++ b/configs/am62x_evm_a53_defconfig
@@ -120,10 +116,6 @@ CONFIG_DM_MAILBOX=y
 CONFIG_K3_SEC_PROXY=y
 CONFIG_DM_MMC=y
 CONFIG_SUPPORT_EMMC_BOOT=y
-CONFIG_MMC_IO_VOLTAGE=y
-CONFIG_SPL_MMC_IO_VOLTAGE=y
-CONFIG_MMC_UHS_SUPPORT=y
-CONFIG_SPL_MMC_UHS_SUPPORT=y
 CONFIG_MMC_HS200_SUPPORT=y
 CONFIG_SPL_MMC_HS200_SUPPORT=y
 CONFIG_MMC_SDHCI=y

I think the key what you were missing is the removal of CONFIG_SPL_MMC_IO_VOLTAGE / CONFIG_MMC_IO_VOLTAGE from A53 U-Boot. If you do that, there won't be any attempts accessing/configuring the regulators. In fact you can even remove vmmc-supply / vqmmc-supply and it still boots just fine.

Regards, Andreas

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Hi Andreas, Thanks for this. I just manged to get to same conclusion and got the same out come :)

However, now the boot stops at this point for some reason:

We get the same when booting from eMMC or SD Card.

log:

5666 bytes read in 570 ms (94.7 KiB/s)
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Device Tree to 000000008feef000, end 000000008fffffff ... OK

Starting kernel ...

[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[ 0.000000] Linux version 5.10.168-g2c23e6c538 (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 Fri Feb 24 05:59:04 UTC 2023
[ 0.000000] Machine model: Texas Instruments AM625 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 0x000000009c800000, size 3 MiB
[ 0.000000] OF: reserved mem: initialized node ipc-memories@9c800000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created DMA memory pool at 0x000000009cb00000, size 1 MiB
[ 0.000000] OF: reserved mem: initialized node m4f-dma-memory@9cb00000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created DMA memory pool at 0x000000009cc00000, size 14 MiB
[ 0.000000] OF: reserved mem: initialized node m4f-memory@9cc00000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created DMA memory pool at 0x000000009da00000, size 1 MiB
[ 0.000000] OF: reserved mem: initialized node r5f-dma-memory@9da00000, compatible id shared-dma-pool
[ 0.000000] Reserved memory: created DMA memory pool at 0x000000009db00000, size 12 MiB
[ 0.000000] OF: reserved mem: initialized node r5f-memory@9db00000, compatible id shared-dma-pool
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x0000000080000000-0x00000000ffffffff]
[ 0.000000] DMA32 empty
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x0000000080000000-0x000000009c7fffff]
[ 0.000000] node 0: [mem 0x000000009c800000-0x000000009e6fffff]
[ 0.000000] node 0: [mem 0x000000009e700000-0x000000009e77ffff]
[ 0.000000] node 0: [mem 0x000000009e780000-0x000000009fffffff]
[ 0.000000] node 0: [mem 0x00000000a0000000-0x00000000ffffffff]
[ 0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000ffffffff]
[ 0.000000] cma: Reserved 512 MiB at 0x00000000dd000000
[ 0.000000] psci: probing for conduit method from DT.

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Full log:

Fullscreen 5040.uboot-failed.txt Download

U-Boot SPL 2021.01-00002-g27f28e9f8f-dirty (Oct 03 2023 - 01:26:14 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Warning: Detected image signing certificate on GP device. Skipping certificate to prevent boot failure. This will fail if the image was also encrypted
Loading Environment from MMC... *** Warning - No MMC card found, using default environment

Starting ATF on ARM64 core...

NOTICE:  BL31: v2.8(release):v2.8-226-g2fcd408bb3-dirty
NOTICE:  BL31: Built : 05:06:58, Feb 24 2023

U-Boot SPL 2021.01-00002-g27f28e9f8f-dirty (Oct 03 2023 - 01:26:03 -0700)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.6.4--v08.06.04 (Chill Capybar')
Trying to boot from MMC2


U-Boot 2021.01-00002-g27f28e9f8f-dirty (Oct 03 2023 - 01:26:03 -0700)

SoC:   AM62X SR1.0 GP
Model: Coda Octopus Dive - Voice Processor 29/09/2023 12:45PM
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed 1
DRAM:  2 GiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1, mmc@fa20000: 2
Loading Environment from MMC... OK
In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
EEPROM not available at 0x50, trying to read at 0x51
Reading on-board EEPROM at 0x51 failed 1
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  2  1  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 4 ms (363.3 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc1 ...
Running uenvcmd ...
1 bytes read in 2 ms (0 Bytes/s)
Already setup.
19147264 bytes read in 797 ms (22.9 MiB/s)
55666 bytes read in 7 ms (7.6 MiB/s)
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 000000008feef000, end 000000008fffffff ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.10.168-g2c23e6c538 (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 Fri Feb 24 05:59:04 UTC 2023
[    0.000000] Machine model: Texas Instruments AM625 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 0x000000009c800000, size 3 MiB
[    0.000000] OF: reserved mem: initialized node ipc-memories@9c800000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009cb00000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node m4f-dma-memory@9cb00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009cc00000, size 14 MiB
[    0.000000] OF: reserved mem: initialized node m4f-memory@9cc00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009da00000, size 1 MiB
[    0.000000] OF: reserved mem: initialized node r5f-dma-memory@9da00000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0x000000009db00000, size 12 MiB
[    0.000000] OF: reserved mem: initialized node r5f-memory@9db00000, compatible id shared-dma-pool
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000080000000-0x00000000ffffffff]
[    0.000000]   DMA32    empty
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x000000009c7fffff]
[    0.000000]   node   0: [mem 0x000000009c800000-0x000000009e6fffff]
[    0.000000]   node   0: [mem 0x000000009e700000-0x000000009e77ffff]
[    0.000000]   node   0: [mem 0x000000009e780000-0x000000009fffffff]
[    0.000000]   node   0: [mem 0x00000000a0000000-0x00000000ffffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000ffffffff]
[    0.000000] cma: Reserved 512 MiB at 0x00000000dd000000
[    0.000000] psci: probing for conduit method from DT.

0 Mitesh Hiran over 1 year ago in reply to Mitesh Hiran

Mastermind 6215 points

Seems the error is related to read version info:

psci_get_version in the psci driver.

0 Andreas Dannenberg over 1 year ago in reply to Mitesh Hiran

TI__Guru 69652 points

Mitesh Hiran said:
Thanks for this. I just manged to get to same conclusion and got the same out come :)

Alright, that's great!! Finally this piece is working!

Mitesh Hiran said:
Seems the error is related to read version info:

psci_get_version in the psci driver.

For the Kernel-related boot concern, can you please open a new E2E ticket, as this will be handled by one of my colleagues. Feel free to link back to this ticket here for additional context.

Thanks, Andreas

0 Mitesh Hiran over 1 year ago in reply to Andreas Dannenberg

Mastermind 6215 points

Thanks a lot for the support.

Processors

Processors forum

AM625: I2C write error while booting from SD Card.