AWR2944EVM: mmWave SDK Out-of-Box Demo 4.3 vs 4.4

Hi Dan,

Can you confirm if you are able to flash the same images using Uniflash once to make sure the rest of your setup is right?

Regards,

Kaushik

Hi Kaushik, we are able to successfully flash and run the demo images from the 4.3 SDK.  We are able to flash the images from the 4.4 SDK but the demo application does not execute correctly.

Hi Dan,

Can you confirm the following:

• Using the appimage without any changes or rebuilding the same
• Using the SBL from SDK 4.4 to flash along with the appimage
• Using the DFP 2.4.6 from SDK 4.4 if you rebuilt the image.
• Connect the device to JTAG and check where the R5f on device is halted on CCS?

Regards,

Kaushik

Hi Kaushik,

We are using the appimage that came with the SDK 4.4 (awr2944_mmw_demoTDM.appimage, timestamped 30/03/2023 18:35).  We edit the default_sbl_null.cfg file to use this appimage and pass it in to the uart_uniflash.py script on the command line.  We have also edited this cfg file to verify that the flash succeeded and it passes this test.

When I connect to the target using CSS I get the following message:

ASSERT: 0.18490s: src/mmwave_link_mailbox.c:MMWave_initMMWaveLink:494: 0 failed !!!

I hope this helps.

Kind regards,

Dan

Hi Dan,

As I said, this looks like an error that could come up when you use an ES2.0 EVM with an older version of the DFP. It would be great if you provided the following info:

• Can you double check if the right DFP has been used in the appimage? (Ideally should have as it was out of the box)
• Can you also check with the other appimages (DDM and LVDS cases) and see if it's the same error?
• Can you also check with the CCS debug image once?
• Can you also once perform a rebuild of the images with the SDK 4.4 environment and try running the same?

All these operate on the same DFP and would throw similar errors.

Regards,

Kaushik

Hi Kaushik,

• It was the out of box binary image.  I'm not sure how I can check what version of DFP was used by TI when the binary was built.
• The DDM image showed the same issue; I cannot test the LVDS version.
• I used the prebuilt binaries for the TDM demo on MSS and DSS and the same problem was seen with the following console output

Debug: DPM Module Sync is done
[Cortex_R5_0] **********************************************
Debug: Launching the MMW Demo on MSS
**********************************************
Debug: Launched the Initialization Task
BSS is not powered up...
ASSERT: 0.18408s: src/mmwave_link_mailbox.c:MMWave_initMMWaveLink:494: 0 failed !!!

• I tried rebuilding the demo from SDK 4.4 and saw the same problem.  The image builder uses the DFP from C:/ti/mmwave_mcuplus_sdk_04_04_00_01/mmwave_dfp_02_04_08_01

I am now also seeing an issue with the prebuilt image from SDK 4.3 - in this case the application boots successfully but when loading a profile using the visualisation tool I get an exception in mss_main.c event callback function with an error  "RL_RF_AE_CPUFAULT_SB".  The hardware we have is Rev B, is there any way to check that we do not have faulty hardware?

Kind regards,

Dan

Hi Dan,

Thank you for your patience.

• Do you happen to have any other EVMs for use? (Rev B or otherwise) It would be good if you could try the same on it once to confirm there is some on board issue.
• Are you seeing the NERROR pin glow upon boot?
• Have you previously used this board to run any other demo successfully?

Regards,

Kaushik