AM6442: Bootable micro SD cards

Hello Koichiro-san,
Let me loop in my colleague on his comments from SoC/SD variations...
Best,
-Hong

Hi Hong,

Here is additional information.
Boot OK cards.
Samsung: MB-MC128G
SanDisk: part# unknown


Boot not-OK cards.
Samsung: MB-MC64D
Transcend: part# unknown


Thanks and regards,
Koichiro Tashiro

Hello Koichiro san,

Can you confirm you are testing the same binaries in both cases ? Do you see any output on the uart console when the boot fails ?

regards,

Venkat Mandela

Hi Venkat,

Venkat Mandela said:

Can you confirm you are testing the same binaries in both cases ?

Yes. Same binaries are used.

Venkat Mandela said:

Do you see any output on the uart console when the boot fails ?

regards,

When the boot fails, no console output is shown.
When the boot succeeds, below log is shown.

U-Boot SPL 2021.01 (Feb 13 2023 - 18:24:11 +0900)
Resetting on cold boot to workaround ErrataID:i2331
resetting ...

U-Boot SPL 2021.01 (Feb 13 2023 - 18:24:11 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.7--v08.04.07 (Jolly Jellyfi')
SPL initial stack usage: 13424 bytes
Trying to boot from MMC2
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Warning: Did not detect image signing certificate. Skipping authentication to prevent boot failure. This will fail on Security Enforcing(HS-SE) devices
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.7(release):08.04.01.005-dirty
NOTICE:  BL31: Built : 15:32:27, Dec 13 2022

U-Boot SPL 2021.01 (Mar 03 2023 - 17:29:59 +0900)
SYSFW ABI: 3.1 (firmware rev 0x0008 '8.4.7--v08.04.07 (Jolly Jellyfi')
Trying to boot from MMC2
Authentication passed
Authentication passed


U-Boot 2021.01 (Mar 03 2023 - 17:29:59 +0900)

SoC:   AM64X SR2.0 HS-FS
Model: Texas Instruments AM642 EVM
DRAM:  1 GiB
LCD:   s1d13l01@spi1
NAND:  0 MiB
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
*** Warning - bad CRC3, using default environment

In:    serial@2800000
Out:   serial@2800000
Err:   serial@2800000
get_ttec_boot_mode: val32 = 0x00000000 val8 = 0xff
232c not detect.
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0

Hello Koichiro san,

Thank you.

We will review the inputs internally and update you.

Is the hardware used same for the XAM6442ASFGGAALV and  AM6412BSCGHAALVdevices.

Regards,

Sreenivasa

Hi Sreenivasa,

Kallikuppa Sreenivasa said:

Is the hardware used same for the XAM6442ASFGGAALV and  AM6412BSCGHAALVdevices.

The hardware is the same. Only AM62x is replaced with the same PCB.

Thanks and regards,
Koichiro Tashiro

Koichiro san,

We need to understand why the boot fails. Do you have JTAG enabled on the board? We will provide a CCS script to dump public ROM trace. We can analyze it and provide feedback.

regards,

Venkat Mandela

Koichiro san,

Can you please run the appropriate script on the device and send the resultant bin files ?

/cfs-file/__key/communityserver-discussions-components-files/791/am64_5F00_rom_5F00_dumps.tar.gz

regards,

Venkat Mandela

Hi Venkat,

Could you tell me how to run these script on the board?
There are two *.js files, but I am not sure how to use them on CCS.

Thanks and regards,
Koichiro Tashiro

Koichiro san,

These are debug server scripts to capture the logs. Once the boot fails, please connect JTAG to DMSC M3 core and R5 core.

https://software-dl.ti.com/ccs/esd/documents/ccs_scripting_console_view.html

Using the CCS scripting console to run the appropriate JS file using the the "loadjsfile" command. This is shown in above link.

Please note that the location where the files are saved may need to be modified if you are on windows. This needs to be updated in the js file.

Please send us the resulting log files.

regards,

Venkat Mandela

Hi Venkat,

Unfortunately, the customer does not use CCS. Their emulator is PALMiCE4.
I am afraid the script does not work with it.

It seems these script save below memory contents.
Could you confirm them? I will ask customer to get same address range with their emulator.

// Save R5 Log Context
r5.memory.saveRaw(0,0x701bd000,"/tmp/am64x_r5_log.bin",1000,32,true);
=> memory address start from 0x701bd000 to 0x701bd3E8?

// Save R5 Trace Context
r5.memory.saveRaw(0,0x701bdd80,"/tmp/am64x_r5_trace.bin",270,32,true);
=> memory address start from 0x701bdd80 to 0x701bdE8E?

// Save DMSC Log Context
dmsc.memory.saveRaw(0,0x41ea0,"/tmp/am64x_dmsc_log.bin",1000,32,true);
=> memory address start from 0x41ea0 to 0x42288?

Thanks and regards,
Koichiro Tashiro

Koichiro san,

The data being saved is words, so the end address should be 0x701bdFA0 in the first case (4000 bytes), 0x701bE1B8 (1080 bytes) in the 2nd case and 0x42e40 (4000 bytes) in the 3rd case.

Which emulator is the customer using ?

regards,

Venkat

Hi Venkat,

Venkat Mandela said:

The data being saved is words, so the end address should be 0x701bdFA0 in the first case (4000 bytes), 0x701bE1B8 (1080 bytes) in the 2nd case and 0x42e40 (4000 bytes) in the 3rd case.

I see. Thanks. I will ask the customer to dump these memory area.

Venkat Mandela said:

Which emulator is the customer using ?

The emulator is this one:
https://www.computex.co.jp/eg/products/palmice4/index.htm

Thanks and regards,
Koichiro Tashiro

Hi Venkat,

I sent you memory dump file by e-mail.

Thanks and regards,
Koichiro Tashiro

Hi Venkat,

Any feedback to this item?

Thanks and regards,
Koichiro Tashiro

Koichiro-san,

The memory dumps do not have the expected content. Could you please provide us another dump ?

Thanks and regards,

Venkat

Hi Venkat,

I sent memory dumps offline.

Thanks and regards,
Koichiro Tashiro