AM4379: AM4379

The query has been assigned to the expert. Please expect a response within a day or two.

Thanks!

Hi Oleh,

Please follow the instruction linked below and provide details of the issue.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1452922/faq-guideline-on-the-initial-software-post-on-e2e

1. The device under the test is a custom board.

2. It based on ARM Cortex-A9 core.

3. Linux is the OS running on the processor core.

4.TI Processor SDK not used.

5. The hardware setup is the serial communication debug port to take a bootup log.

6. Expect to boot up on power on.

7. Instead, boot up process did not complete, and debug log indicates it stooped at "Trying to boot from MMC"

8. This is the first time we see this problem on one board only.

9. Problem happen on every boot.

10. We performed ABA swap for MMC, but failure does not follow MMc.

11. Boot logs for the failed board and for the known good board are pasted below:

CCCCCCCC
U-Boot SPL 2016.03 (Dec 24 2019 - 17:33:35)
MC-X1 1.17
Trying to boot from MMC

CCCCCCCC
U-Boot SPL 2016.03 (Dec 24 2019 - 17:33:35)
MC-X1 1.17
Trying to boot from MMC

U-Boot 2016.03 (Dec 24 2019 - 17:33:35 +1000)
MC-X1 1.17

I2C: ready
DRAM: 1 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Net: cpsw

Welcome to MCX1

Autoboot in 1 seconds, press ESC twice to cancel
Checking Firmware
Booting firmware 1
## Loading kernel from FIT Image at 83000000 ...
Using 'config@1' configuration
Trying 'kernel@1' kernel subimage
Description: 4.4.245+git0+565c417795-r0-mcx1-20220121043537
Type: Kernel Image
Compression: uncompressed
Data Start: 0x830000e4
Data Size: 2969696 Bytes = 2.8 MiB
Architecture: ARM
OS: Linux
Load Address: 0x82000000
Entry Point: 0x82000000
Hash algo: crc32
Hash value: 3b6ef755
Verifying Hash Integrity ... crc32+ OK
## Loading ramdisk from FIT Image at 83000000 ...
Using 'config@1' configuration
Trying 'ramdisk@1' ramdisk subimage
Description: rootfs
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x832e075c
Data Size: 18365051 Bytes = 17.5 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00000000
Entry Point: 0x00000000
Hash algo: crc32
Hash value: 82d6db71
Verifying Hash Integrity ... crc32+ OK
## Loading fdt from FIT Image at 83000000 ...
Using 'config@1' configuration
Trying 'fdt@1' fdt subimage
Description: 4.4.245+git0+565c417795-r0-mcx1-20220121043537
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x832d523c
Data Size: 46206 Bytes = 45.1 KiB
Architecture: ARM
Hash algo: crc32
Hash value: ccda0f1d
Verifying Hash Integrity ... crc32+ OK
Booting using the fdt blob at 0x832d523c
Loading Kernel Image ... OK
Loading Ramdisk to 8ee7c000, end 8ffffa7b ... OK
Loading Device Tree to 8ee6d000, end 8ee7b47d ... OK

Starting kernel ...

Hi Oleh,

Thanks for providing the details.

The console log shows ROM is able to read the first boot loader (MLO) from MMC and execute it, but the MLO is unable to read the second boot loader (u-boot.img) from MMC.

Oleh Kernytskyy64 said:

I am instigating field return, and the failure symptom is "Trying to boot from MMC".

Since this is a field return, I suspect there could be some hardware damage which causes the problem. I am routing your query to our hardware team to comment.

How many systems are experiencing this problem?

Have you validated signal quality is good, and signal timing is not violated for either device?

Regards,
Paul