• State
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 70 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

AWR1642BOOST: Issue in modifying OOB demo for scenario where more MSS code and MSS .bss space is needed

Gayatri Menon
Intellectual 665 points
Part Number: AWR1642BOOST
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi, 

I have a scenario where I require additional program and .bss space for the AWR1642BOOST R4F core. To achieve this, I've found an option in C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\ti\common\mmwave_sdk_xwr16xx.mak that allows me to set the MMWAVE_SDK_SHMEM_ALLOC value as specified in the makefile.

To gain a better understanding, I rebuilt the existing out-of-the-box code using different MMWAVE_SDK_SHMEM_ALLOC values provided in mmwave_sdk_xwr16xx.mak. After flashing the newly generated bin files, I tested the setup using the mmWave Demo Visualizer. However, except for the default valued of MMWAVE_SDK_SHMEM_ALLOC configuration, I am unable to connect to the device in the mmWave Demo Visualizer.

I don't believe this issue is related to unavailable serial ports, as I can access the serial port using other applications. It seems that the visualizer might be expecting certain data that it's not receiving (though I'm not entirely sure). When I set MMWAVE_SDK_SHMEM_ALLOC to its default value, I can successfully connect using the mmWave Demo Visualizer.

To set MMWAVE_SDK_SHMEM_ALLOC , I added the below statement in in C:\ti\mmwave_sdk_03_06_02_00-LTS\packages\scripts\windows\setenv.bat

set MMWAVE_SDK_SHMEM_ALLOC=0x00010005 

Please help me to understand why is this happening . Am i missing something here?

Thank you 

  • 0
    TI__Expert 3755 points

    To debug the code I would recommend flashing the empty app image to the device, resetting the board to functional mode, launching target configuration in ccs, connecting to the core, loading the binary, placing a break point in the code, and sending the configuration through tera term. The application should tell you what the error is

  • 0 in reply to Zorah Ahmad
    TI__Expert 3755 points

    You can find the ccs debug image here 

    C:\ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\utils\ccsdebug

    The out of box demo can be found here 

    C:\ti\mmwave_sdk_03_06_00_00-LTS\packages\ti\demo\xwr16xx\mmw

    and here 

    C:\ti\radar_toolbox_1_30_01_03\source\ti\examples\Out_Of_Box_Demo\src\xwr1642

    Please use the latest toolbox release. The above toolbox release lets you import the project into CCS and build it there as well

  • 0 in reply to Zorah Ahmad
    Intellectual 665 points

    Hello,

    I've attempted the following setup, and here's the situation:

    When I load the program using CCS and then connect and configure the device with the mmWave Demo Visualizer, everything functions correctly.

    However, if I flash the TI Radar with the generated binary using Uniflash and then try to use the mmWave Demo Visualizer, the hardware doesn't connect, as depicted in the image from my initial diagram.

    Aside from modifying MMWAVE_SDK_SHMEM_ALLOC, I haven't changed anything else in the OOB code.

    I am using OOB demo provided in mmWave SDK 3.6.2 which i believe is latest version for xwr1642

    Please let me know what I am missing here. 

    Thanks 

    Regards

    Gayatri

  • 0 in reply to Gayatri Menon
    TI__Expert 3755 points

    This is a known issue for mmWave Demo Visualizer. The online version does not perform as well. 

    Please download mmWave Demo Visualizer to your PC and run from there.