AM6442: How to bypass the EEPROM checking procedure

JDA

Part Number: AM6442
Other Parts Discussed in Thread: SK-AM64B, TMDS64EVM

Dear TI Experts,

I am a new user working with the AM6442 (SR 2.0) SoC chip on a custom platform designed based on the SK-AM64B evaluation board circuitry (without an EEPROM). I have encountered a boot issue and would appreciate your assistance in resolving it.

The SDK version I am using is 09.02.01.09 (without any modifications).

After power on, The boot process was stopped as the following figure.

I am able to compile source code. But is it possible to bypass the EEPROM checking procedure by modifying some specific configuration of the source code?

Please give me your kind advice, if you may.

PS: The source of SDK I am using is as below.

PROCESSOR-SDK-LINUX-AM64X — Processor SDK Linux for AM64x

SDK 09.02.01.09: [https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-AM64X/09.02.01.09](www.ti.com/.../09.02.01.09)

File: tisdk-default-image-am64xx-evm.wic.xz

Thank you for your assistance!

over 1 year ago

0 Hong Guan64 over 1 year ago

TI__Guru 69150 points

This is one of recent e2e on the same topic. Hopefully it is helpful.
e2e.ti.com/.../5076100
Best,
-Hong

0 JDA over 1 year ago in reply to Hong Guan64

Prodigy 74 points

Hi Hong,

Thanks for your rapid and kind response. But I still need your help.

By following the link you kindly shared, I've implemented the instruction of the following link in my SDK 09.02.01.09.

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1162824/tmds64gpevm-disabling-config_ti_i2c_board_detect-gives-compile-error/4384624#4384624

The patch file, /cfs-file/__key/communityserver-discussions-components-files/791/am64_5F00_i2c_5F00_eeprom_5F00_read_5F00_bypass.patch , is implemented into the following two Kconfig files, manually.
(The compile warning is attached as a screenshot at below.)

/ti-processor-sdk-linux-am64xx-evm-09.02.01.09/board-support/u-boot-build/r5/source/board/ti/am64x/Kconfig
=> remove "imply TI_I2C_BOARD_DETECT" (x2)
/ti-processor-sdk-linux-am64xx-evm-09.02.01.09/board-support/u-boot-build/r5/source/board/ti/common/Kconfig
=> remove "depends on TI_I2C_BOARD_DETECT" (x2)

(The UART messages (before/after) are attached as a screenshot at below.)

Although the messages about "EEPROM not available" (yellow zone) disappeared, the boot process still stop at "SPL initial stack usage: 13408 bytes."

Is it correct?

Does it mean that we have successfully bypassed the EEPROM checking process but I have to design a customized device tree (.dtb) for my custom board now.

If yes, will you advice me to follow the instruction of the following article?

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1169092/am6442-yocto-custom-device-tree

The answer of the above article seems not to be clear enough for me.

Could you provide me more guidance for reference? Appreciates!

Sincerely,

Anderson

0 JDA over 1 year ago in reply to JDA

Prodigy 74 points

Hi Hong,

Here is one more information for your reference.

Although the boot process failed on my customized board, I inseted that identical SD card with the above modified boot files into the TMDS64EVM for further testing.

The TMDS64EVM can successfully boot into Linux and won't stop at "SPL initial stack usage: 13408 bytes."

(The UART messages of each AM6442 board are attached as screenshot at below.)

Do you know the possible reason?

Which step does the boot process possibly stop at?

Please provide your kind guidance, if you may.

PS: The customized board I used is a platform designed based on the SK-AM64B evaluation board circuitry (without an EEPROM), instead of TMDS64EVM. I don't have the SK-AM64B, yet. That's why I tested on a TMDS64EVM.