HSFS DEBUG

Karen Agüero Meza

Other Parts Discussed in Thread: AM2432

Hi,

We have some questions about how to debug the HSFS Chip, we found by TI - Guideline the description to debug using DEVBOOT mode & Scripts. (See below)

We use the GPMC interface in our hardware, TI doesn't have has a Script to support this, therefore we cannot debug using the current description.

We try to use a NULL SBL (where the corresponding driver are initialized) and the bootmode QSPI or NO BOOT but the SBL break out calling the function

status = Bootloader_bootCpu(bootHandle, &bootImageInfo.cpuInfo[CSL_CORE_ID_R5FSS1_0]);

Somebody have an Idea, what could be the problem? or maybe other form to debugging this Chip.

Or is it posibble only in DEVBOOT mode? (In this case we need a Script from TI to initialize the GPMC)

Best Regards & Thanks a lot!

Karen

over 2 years ago

0 Aakash Kedia over 2 years ago

TI__Mastermind 26145 points

Hi Karen Agüero Meza

Karen Agüero Meza said:
We use the GPMC interface in our hardware, TI doesn't have has a Script to support this, therefore we cannot debug using the current description.

We do not have support to initialize GPMC in our current scripts. We can take this requirement and work on this, but we do not have clear idea on the ETA.

Another option for DEVBOOT mode is that you can load an application *.out file (create a simple hello_world application which has support to initialize GPMC). Run this application, reset the CPU and load the targeted application. Later on this can be automated by putting the same in the script (like sciclient_ccs_init.out).

Karen Agüero Meza said:
We try to use a NULL SBL (where the corresponding driver are initialized) and the bootmode QSPI or NO BOOT but the SBL break out calling the function

I tried the same on my end but I do not see this issue on my end.

Attaching the working project for the same.

/cfs-file/__key/communityserver-discussions-components-files/908/sbl_5F00_ospi_5F00_am243x_2D00_evm_5F00_r5fss0_2D00_0_5F00_nortos_5F00_ti_2D00_arm_2D00_clang.zip

Do let me know if you still face this issue.

Best Regards,
Aakash

0 Karen Agüero Meza over 2 years ago in reply to Aakash Kedia

Prodigy 150 points

Hi Aakash,

I see your code was compiled in SDK 8.5.0.24, we used the SDK 8.4.0.17.

So I toke some changes of the bootoloader soc.* and soc.* from SDK 8.5.04 and ported them to SDK 8.4.0.17, because we want to stay in this version.

the NULL SBL works now!.

please let me know if you can prepare an official patch for this issue.

Thanks & Regards,

Karen

0 Aakash Kedia over 2 years ago in reply to Karen Agüero Meza

TI__Mastermind 26145 points

Hi Karen,

This should not be the case. But let's discuss the same in the call scheduled.

Best Regards,
Aakash

+1 Aakash Kedia over 2 years ago in reply to Aakash Kedia

TI__Mastermind 26145 points

Hi Karen,

We migrated to 08.04 release of TIFS-MCU and tested the same on TI-EVM.

/cfs-file/__key/communityserver-discussions-components-files/908/sbl_5F00_ospi.release.hs_5F00_fs.tiimage

We could not replicate the issue. I would suggest you to schedule another call with setup ready and replicable so we can debug it on call.

Best Regards,
Aakash

0 Karen Agüero Meza over 2 years ago in reply to Aakash Kedia

Prodigy 150 points

Hi,

Maybe this can help you, after our session today using the Version 8.5.0.24 the logs Profile show:

That the CPU r5f1-1 is not initialized but the m4f0-0. I try again in the Version 8.40.17 whitout CPU r5f1-1 & initRam = 0 and send you the resuls.

Best Regards,

Karen

0 Aakash Kedia over 2 years ago in reply to Karen Agüero Meza

TI__Mastermind 26145 points

Hi Karen Agüero Meza,

What is the System firmware version between two SDK version in your case ?

BR,
Aakash

0 Karen Agüero Meza over 2 years ago in reply to Aakash Kedia

Prodigy 150 points

Hi,

From SDK 8.04.0.17

Regards,

Kaen

0 Aakash Kedia over 2 years ago in reply to Karen Agüero Meza

TI__Mastermind 26145 points

Hi Karen Agüero Meza,

We are looking into this and trying to reproduce this. As discussed we will schedule a call tomorrow to discuss this.

Thanks and Regards,
Aakash

0 Karen Agüero Meza over 2 years ago in reply to Aakash Kedia

Prodigy 150 points

Hi Aakash,

I was able to generate the boardcfg_blob.bin using #define SYSFW_TRACE_ENABLE.

I send you x Email the MemoryValues and the UART traces.

I hope that help you.

Thanks and Regards,

Karen

0 Aakash Kedia over 2 years ago in reply to Karen Agüero Meza

TI__Mastermind 26145 points

Hi Karen,

We have sent you the feedback on the data shared. Can you shared the updated data based on the requirements set in the email.

Best Regards,
Aakash

0 Aakash Kedia over 2 years ago in reply to Aakash Kedia

TI__Mastermind 26145 points

Hi Karen,

As per our debug, the device you have has the JTAG ID as this -

Which means that the device is AM2432 ALV Package.

Details are covered in the datasheet - https://www.ti.com/lit/ds/symlink/am2434.pdf?ts=1676282438074&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FAM2434

The bootloader fixes for single core CPU and dual core CPU were released as a part of 08.05 release. You can choose the fixes of bootloader driver from 08.05 release.

The failures are observed majorly in initialization of memory and CPU which are not valid for your part.

Best Regards,
Aakash

0 Karen Agüero Meza over 2 years ago in reply to Aakash Kedia

Prodigy 150 points

Hi Aakash,

Thanks a lot.

could you please send me an official patch with the corresponding files.

Best Regards,

Karen

+1 Aakash Kedia over 2 years ago in reply to Karen Agüero Meza

TI__Mastermind 26145 points

Hi Karen Agüero Meza,

As TI is planning to provide a patch release of MCU_PLUS_SDK to SEW, we will provide the fix in the same for the drivers.

Best Regards,
Aakash

Arm-based microcontrollers

Arm-based microcontrollers forum

HSFS DEBUG