TDA4AL-Q1: [FreeRTOS]Timeout waiting for thread SP_RESPONSE to fill

Hi,

Daniel Hsieh said:

and put it to the path of meta-ti-bsp/recipes-bsp/ti-dm-fw/ti-dm-fw.bb to run mcu rtos

1.Is this Yocto path? and Would you please confirm if you are using PROCESSOR-SDK-LINUX-J721s2 or PROCESSOR-SDK-RTOS-J721s2?

2.Did you get any build error? and which free RTO example are you trying to use here?

3. What boot flow are you using?

Regards,

Karthik

Dear Karthik

1.yes, it is yocto path, use SDK Linux, but i build the fw under SDK-RTOS and put it to yocto source as a prebuild fw

2.No any build error

3. What do you mean about boot flow?

Do you mean SPL/SBL? 

For yocto arch, i think it boot with SPL mode

Thank you 

HI Daniel,

It seems that DM firmware is not running on the MCU1_0, that is the reason you are seeing these kind of logs.

NOTICE: BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE: BL31: Built : 16:09:05, Feb 9 2024
ERROR: Timeout waiting for thread SP_RESPONSE to fill
ERROR: Thread SP_RESPONSE verification failed (-60)
ERROR: Message receive failed (-60)
ERROR: Failed to get response (-60)
ERROR: Transfer send failed (-60)
ERROR: Timeout waiting for thread SP_RESPONSE to fill
ERROR: Thread SP_RESPONSE verification failed (-60)
ERROR: Message receive failed (-60)
ERROR: Failed to get response (-60)
ERROR: Transfer send failed (-60)
ERROR: Unable to query firmware capabilities (-60)

Maker sure DM is running on the MCU1_O core.

Regards
Diwakar

Dear Diwakar

i use the examle app of ipc_rtos_echo_test_freertos

under pdk_j721s2_10_01_00_25\packages\ti\drv\ipc\examples\rtos

if i use ipc_rtos_echo_testb_freertos, there are no this question. 

why have this two result?

Thank you very much

Dear Diwakar

I found other example have this "Timeout waiting..." issue

Like UART_TestApp_freertos

Does it mean these example have same case?

How to check the example use ATCM  or not?

Thank you very much

Dear Diwakar

Another question,

What fo you mean about "initialising the BTCM we are keeping the reset vector to BTCM"

Do you mean we need to initial the BTCM if we use SPL mode?

How to do "initialising the BTCM ..."?

Any samole code about it?

Thank you very much

Dear Diwakar

I search all APP's xxx_freertos_mcu1_0_release.xer5f.map file

most lof them show 

"ENTRY POINT SYMBOL: "_freertosresetvectors"  address: 00000000"

Do it it mean the FW is under ATCM and it can not runing at SPL mode?

May i change it to BTCM  and runing on real device under freertos ?

Thank you very much

Hi Daniel,

You are using some random MCU1_0 test or example application images with Linux. All of the images you have tried so far are standalone unit-test example firmwares that could be tested in a stand-alone fashion like SBL + MCU1_0 application firmware image.

The Linux boot using U-Boot and R5 SPL has specific requirements w.r.t the MCU1_0 firmware. The default Power-On-Reset for the MCU R5F core has the ATCM disabled and only BTCM enabled. The R5 SPL also runs on the MCU R5F core, and simply jumps to the entry-point from your MCU1_0 application.

The MCU1_0 application firmware as such cannot use any contents in ATCM, and has to use an appropriate linker command file.

regards

Suman

Dear Suman

Thank you for information that example firmwares can be use as SBL + MCU1_0 application firmware only.

So, i think i need to change example to BTCM mode if i want to run it under "Linux boot using U-Boot and R5 SPL"

Am I correct?

Could the functionality of this example(ipc_rtos_echo_testb_freertos) be attributed to it being in BCTM mode?

What are the key considerations for developing a BCTM mode firmware (FW) for MCU1_0?

Thank you very much

Hi Daniel,

Daniel Hsieh said:

So, i think i need to change example to BTCM mode if i want to run it under "Linux boot using U-Boot and R5 SPL"

This is not the only requirement. The MCU1_0 application also needs to run the SciServer.

Please see the 9.3. MCU1_0 Application Development with SYSFW section in the RTOS SDK documentation.

Daniel Hsieh said:

Could the functionality of this example(ipc_rtos_echo_testb_freertos) be attributed to it being in BCTM mode?

Yes, correct.

Daniel Hsieh said:

What are the key considerations for developing a BCTM mode firmware (FW) for MCU1_0?

This is primarily a linker difference.

regards

Suman

Does SciServer part is needed for SPL mode?

Do you mean that i need to add SciServer relationship code?

What other part need to add for BCTM?

Could you provide a simple psuedo code to explain it. 

Include linker design

Thank you very much

Hi Daniel,

Daniel Hsieh said:

Does SciServer part is needed for SPL mode?

Yes, SciServer on MCU1_0 is needed for any system-level integrated boot. This is responsible for all the Device Management of various peripherals and Resource Management of SoC-wide resources.

Daniel Hsieh said:

What other part need to add for BCTM?

I am not sure what you are asking. 

Daniel Hsieh said:

Could you provide a simple psuedo code to explain it. 

Please look through the above documentation reference and the existing SDK examples. You can look at the following examples:

1. sciserver_testapp: <PDK>/packages/ti/drv/sciclient/examples/sciserver_testapp

This uses both ATCM and BTCM and just the SciServer code in MCU1_0

2. ipc_echo_test: <PDK>/packages/ti/drv/ipc/examples/linux

This example includes IPC in addition to the SciServer, and is intended for Linux. You have both the ATCM and BTCM versions here, which can be used with R5 SBL and R5 SPL respectively.

This example also demonstrates the additional requirements for Linux like Resource Table etc.

3.  ipc_rtos_echo_test: <PDK>/packages/ti/drv/ipc/examples/rtos

This is the equivalent of #2, but for a RTOS-only environment.

regards

Suman

Dear Suman

"What other part need to add for BCTM?"

I mean is i would like to implement a example with BCTM for SPL mode.

What should i add for it?

What do you mean about "This uses both ATCM and BTCM and just the SciServer code in MCU1_0" for sciserver_testapp part?

Do you mean that sciserver_testapp can run by ATCM or BTCM?

Thank you veyr much

Hi Daniel,

Can you please clarify what your overall motivation is here? Why do you want to run the FreeRTOS Task Switch test example with Linux?

Daniel Hsieh said:

I mean is i would like to implement a example with BCTM for SPL mode.

This is primarily linker cmd differences. Please compare the two linker command files used by ipc_echo_test and ipc_echo_testb examples.

Daniel Hsieh said:

What do you mean about "This uses both ATCM and BTCM and just the SciServer code in MCU1_0" for sciserver_testapp part?

Each R5F core has two L1 memories (called Tightly Coupled Memory or TCM) - ATCM and BTCM. They can appear at 0x0 and 0x41010000 locally to each R5F core.

The SoC default has ATCM disabled by default, and these are enabled during the processor load time before releasing the reset of a processor. Given that R5 SPL does not perform a reset, ATCM remains disabled. So, you cannot link contents into it if wanting to use R5 SPL.

The R5 SBL does support loading an application both with or w/o performing a reset. The ATCM is enabled in the case where a reset is performed providing maximum TCM memory to firmware.

The sciserver_testapp firmware relies on ATCM being enabled (BTCM is also enabled), with the reset vectors linked into ATCM.

regards

Suman

Dear Suman

"Can you please clarify what your overall motivation is here?"

I would kike run freertos with some ADAS function and that can run CAN/IPC/SPIflash service and communication with A72(yocto linux) with IPC

Therefore i need the freertos fw is BTCM under SPL mode

What do you mean about following

"The ATCM is enabled in the case where a reset is performed providing maximum TCM memory to firmware."

Do you mean i can use max TCM under ATCM mode?

How about it under BTCM?

Thank you very much

Hi Daniel,

Daniel Hsieh said:

I would kike run freertos with some ADAS function and that can run CAN/IPC/SPIflash service and communication with A72(yocto linux) with IPC

The ipc_echo_testb_freertos example is already your starting point then. It is an IPC example running FreeRTOS. You need to additional drivers and code for your other functionalities.

Daniel Hsieh said:

Do you mean i can use max TCM under ATCM mode?

Yes, correct.

What is the final bootloader you are going to use for your project? If you want your MCU1_0 firmware to leverage both ATCM and BTCM, then I recommend that you use the RTOS SBL (typically the preferred bootloader for Automotive products).

regards

Suman

Dear Suman

The bootloader of our system is SPL. It seem be default usecase under yocto SW arch.

Under this case, do you mean we can NOT use the max TCM?

If i would like to use RTOS SBL  under yocto SW arch, what should i do ?

Why you recommend that RTOS SBL?

Thank you very much

Hi Daniel,

Daniel Hsieh said:

The bootloader of our system is SPL. It seem be default usecase under yocto SW arch.

Yes, the standard Linux SDK offering is to use all Linux open-source components.

Daniel Hsieh said:

Under this case, do you mean we can NOT use the max TCM?

Correct. The R5 SPL only performs a branch-only boot, so ATCM is not enabled on your MCU R5F.

Daniel Hsieh said:

If i would like to use RTOS SBL  under yocto SW arch, what should i do ?

We have support to boot Linux w/ SBL using the RTOS SDK build infrastructure only.

Daniel Hsieh said:

Why you recommend that RTOS SBL?

Linux R5 SPL is a generic bootloader, and has support for all bootmodes within the same boot-binary. This is a generic broad bootloader, compared to a RTOS SBL, which is usually a custom bootloader. This renders the RTOS SBL to be customized. You can also customize the R5 SPL as per your needs, but our SDK boot caters to the broad market w/ upstreamability of U-Boot, so is the standard U-Boot.

What is your actual product?

regards

Suman

Dear Suman

"What is your actual product?"

We are developing an ADAS product

Sofar, we are useing freeRTOS and plan to use AUTOSAR at future

Does SPL mode be enough to use?

Thank you 

Dear Suman

Another question, does SPL mode have what kind of limitations (compare with SBL mode)

For example, can not use  max TCM.(How many TCM size can be use under SPL mode)

...

If we want to use SBL under yocto SW arch,

What kind of change i need to do?

Build with SDK with SBL tisbl.bin and app two image, right?

Does it same path with the mcu dm-fw of tispl.bin?

Thank uou very much

Hi Daniel,

Daniel Hsieh said:

Does SPL mode be enough to use?

Yes, you can still use the R5 SPL.

In the end, it depends on your overall project needs/goals.

regards

Suman

Hi Daniel,

Daniel Hsieh said:

Another question, does SPL mode have what kind of limitations (compare with SBL mode)

I am sorry, but this discussion has really veered off from the original topic. Please open a new thread for the SPL vs SBL discussion referencing this thread.

Do you still have any open questions on the original thread title topic?

regards

Suman

Dear Suman

Yes, i can create another topic for SBL/SPL

About origin  "SP_RESPONSE" issue,

It was cause by SPL +ATCM FW, right?

I need to add sciserver and use BCTM if i would like to keep at SPL mode.

Right?

Thank you very much