TDA4AP-Q1: No Boot Log Printing After 900 Times Power on & off

Kevin Peng

Expert 3047 points

Part Number: TDA4AP-Q1

Tool/software:

Hi TI Experts,

Customer is working on TDA4AP SDK9.2.

They are going to SOP at the end of this month, and doing the final pressure test.

They have 1 board which could boot from emmc successfully over 900 times.

However, after more than 900 times successful booting, they meet 1 failure boot and there is no log printing information shown.

Luckily customer connected the JTAG to the CCS, and read out the PC pointer value for MCU R5f shown below.

When customer tried to read out the PC pointer value for A72 core & Main r5f cores, the CCS shows "Error: unable to read" shown below.

Could you please help analyze these information, and provide some clue to the customer, as they are going to SOP this month, it is quite urgent.

Thanks,

Kevin

4 months ago

0 Linjun Meng 4 months ago

TI__Expert 7261 points

Hi Kevin，

According to the description, I guess the problem is on the MCU R5F. Customer needs to check the context 0xA042B38C of R5F. It may be in the bootapp. They can upload elf files, we will do further check. Thanks.

Linjun

0 martin.tang 4 months ago in reply to Linjun Meng

Prodigy 40 points

krc5_mcu1_0-release_strip.zip

Here is the mcu1_0 elf file, please help to analysis. thanks.

0 Linjun Meng 4 months ago in reply to martin.tang

TI__Expert 7261 points

Debug information has been filtered out. Please upload another xer5f file.

Through this document we can get limited information as follows,

Load 0x001400 0xa0400000 0xa0400000 0x2b6b0 0x2b6b0 R E 0x10

0 martin.tang 4 months ago in reply to Linjun Meng

Prodigy 40 points

krc5_mcu1_0-release.zip

Sorry, here is the one without strip. Thanks.

0 Linjun Meng 4 months ago in reply to martin.tang

TI__Expert 7261 points

The PC is at vApplicationIdleHook + 0x0c. If the issue happens again, please dump the connect to ccs, then dump the core registers to check any issue haplpend.

Could you please also enable the tifs log?

What's the boot up flow to main domain ?

0 Tank.Xue 4 months ago in reply to Linjun Meng

Prodigy 90 points

IP1-001_registers.zip

There is the registers dump from mcu1-0.

0 Linjun Meng 4 months ago in reply to Tank.Xue

TI__Expert 7261 points

R CPSR 0x0000000B 0x6000001F, which means the core is in Sytem mode. In Privileged mode an illegal value programmed into M[4:0] causes the processor to enter System mode.

Could you please enable the tifs and MCU1_0 log port do further check?

0 martin.tang 4 months ago in reply to Linjun Meng

Prodigy 40 points

would you please help to told us how to enable the tifs and mcu1_0 log port?

and in today morning, we found another boot up failure, here is the log and register values, please help to check if it is the same with yesterday.

0827_powercycle.zip

0 Linjun Meng 4 months ago in reply to martin.tang

TI__Expert 7261 points

step 1 enable the tifs log by the following patch.

/cfs-file/__key/communityserver-discussions-components-files/791/defaultBoardcfg.c.patch

step 2. make sciclient_boardcfg_hs or make sciclient_boardcfg depend on your board type.

step 3 rebuild sbl

0 martin.tang 4 months ago in reply to Linjun Meng

Prodigy 40 points

we use spl, is the process same with sbl?

0 Linjun Meng 4 months ago in reply to martin.tang

TI__Expert 7261 points

OK. Could you please tell me which core make the the krc5_mcu1_0-release run? What's your boot flow to enable the main domain cores works?

0 Linjun Meng 4 months ago in reply to Linjun Meng

TI__Expert 7261 points

This log “0827_powercycle.zip” shows that it has stopped at bl31.bin. A72 Cannot connect to CSS at this time? What is the memory layout of the whole system? You need to check if there is any overlap?

0 Linjun Meng 4 months ago in reply to martin.tang

TI__Expert 7261 points

1 Modify the board-cfg.yaml in the folder of board-support/ti-u-boot-2023.04+gitAUTOINC+f9b966c674/board/ti/j784s4/ ,

line 35 trace_dst_enables : 0x00 change to trace_dst_enables : 0x01
line 36 trace_src_enables : 0x00 change to trace_src_enables : 0x01

2 rebuild u-boot-r5.

0 Brijesh Jadav 21 days ago in reply to Linjun Meng

TI__Guru**** 438065 points

Closing this thread.

Processors

Processors forum

TDA4AP-Q1: No Boot Log Printing After 900 Times Power on & off