AWR2243: Running usecases on AWR2243 with a TDA2xx capture card with firmware from SD card

Hello Saketh,

Processor SDK Radar currently supports only 1243 cascade, but various customers/users in the TI E2E community have posted solutions on how to use Processor SDK V3.8 with AWR2243 as well.

Refer to one of the threads linked below: 

https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/882929/awr2243-the-appimage-form-sdk3-7-and-sdk3-8-can-not-running-in-cascade-radar-with-awr2243 

Please search for more such threads using the search function of E2E forum or using your local search engine and typing "site e2e.ti.com <your query>".

Also, do keep in mind, that the latest DFP package for  AWR2243 ES1.0 is DFP_02_02_00_03 and AWR2243 ES1.1 is DFP_02_02_02_01. Choose the correct firmware based on your device silicon version.

Regards,

Ishita

Thank you Ishita. 

I did try what's mentioned in that thread and was successful in building the image/MLO files. Unfortunately I am running into a loop where all I get is 

TDA2xx SBL Boot

DPLL Configuration Completed

Clock Domain Configuration Completed

Module Enable Configuration Completed

TI EVM PAD Config Completed

DDR Config Completed

App Image Download Begins

SD Boot - file open completed successfully

IPU1 CPU0 Image Load Completed

IPU1 CPU1 Image Load Completed

DSP1 Image Load Completed

EVE1 Image Load Completed

EVE2 Image Load Completed

EVE3 Image Load Completed

EVE4 Image Load Completed

App Image Download Completed

Putting MPU CPU1 in Off mode

*****************************************************************

PMCCNTR counts once every 64 clock cycles, multiple by 64 to get actual CPU cycles

SBL Initial Config Cycles - 100059 (8.53 ms)
SOC Init Cycles - 164442 (14.3 ms)
DDR Config Clock Cycles - 58853 (5.2 ms)
App Image Load Cycles - 560931 (47.86 ms)
Slave Core Bootup Cycles - 54228 (4.62 ms)
SBL Boot-up Cycles - 939572 (80.17 ms)
Time at which SBL started IPU1_0 - 23082574 (49064.25 ms)
*****************************************************************

Putting MPU in Retention...

Thank you for your help so far.

cc: Jitendra Gupta  may you'll be able to help me in this regard.

Making those changes to port for AWR2243 should not break the booting sequence. I would request you first rebuild the original application code and try to run from SDCard.

If that works then only migrate to AWR2243 related changes.

The logs look the same in both the cases for me. However, I will uninstall all the components, reinstall, rebuild the images, and post the results to see if that works

Well, I tried doing exactly the same, ie., uninstalled, reinstalled everything, followed the steps from radar sdk user guide and build AppImage, MLO files for the original use cases (no patch applied), copied them on to SD card. And All that I see is the board goes into a boot loop with the logs mentioned above repeating every 60 clock cycles.

My hardware S4 switches are set to 000011. Are there any other changes that I should be doing?

So it is not working at all with all the default setting and images?

What about functionality with mmWave Studio? mMWave Studio cascade user guide provides the steps to work with TDAx cascade board, if want to try that.