• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 315 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR6843: 68xx_mmwave_sdk_hcc dose not work in JTAG debug mode

Allen35065
Expert 3225 points
Part Number: AWR6843
Other Parts Discussed in Thread: MMWAVEICBOOST, IWR6843AOP

Hi expert, 

I'm trying to run 68xx_mmwave_sdk_hcc demo in industrial toolbox 4.8. When i flash the xwr68xx_mmw_demo_hcc.bin to chip, it works and i could see the results on visualizer. 

While when i flash ccs_debug.bin to chip and load dss and mss program in prebuild_binaries directory, it does not work. I rebuilt this project and got same results. 

Could you please help to check the root cause it does not work in debug mode?

Thank you.

Regards,

Allen

  • 0
    TI__Expert 7030 points

    Hi Allen, 

    Thanks for reaching out. I am currently looking into the issue and thank you for your patience. 

    Thanks,

    Alex Chan

  • 0 in reply to Alexander Chan
    TI__Expert 7030 points

    Hi Allen,

    I apologize for the late response and thank you for your patience. 

    To run the css debug follow these steps https://dev.ti.com/tirex/explore/content/mmwave_industrial_toolbox_4_8_0/labs/common/docs/software_setup/using_ccs_debug.html and make sure you are using the appropriate debug bin.

    Afterwards make sure you open the correct projects in css.

    After you load the *.xer4f and *.xe674 to the respective cores you should see the following.

    After running the cores I got the following and did not see any issues or errors. 

    Thanks,

    Alex Chan

  • 0 in reply to Alexander Chan
    TI__Expert 3225 points

    Hi Alex,

    Sorry I didn't describe the issue clearly in the first post.

    I used industrial toolbox 4.8  on IWR6843AoP EVM board with MMWAVEICBOOST card. (bin and *.xer4f and *.xe674 in mmwave_industrial_toolbox_4_8_0\labs\out_of_box_demo\68xx_mmwave_sdk_hcc\prebuilt_binaries).

    At first i flashed *.bin to EVM board and i can see the data port output characters as below. 

    Then i flashed ccs_debug into EVM board then load and run *.xer4f and *.xe674. I could see the CCS log is correct as yours but there is NO output on UART data port no matter i connected UART before or after i run the code. 

    After that, I checked the status of mss and dss and it looks like they are in IDLE after CCS log are printed. 

    Here is my CCS log and mss&dss status.'

    **********************************************
    Debug: Launching the MMW Demo on MSS
    **********************************************
    Debug: Launched the Initialization Task
    Debug: mmWave Control Initialization was successful
    Debug: mmWave Control Synchronization was successful
    Debug: Sending rlRfSetLdoBypassConfig with 0 0 0
    Sensor was successfully opened.
    Data Output Mode: Frame
    Sending configSensor command to EVM.
    [C674X_0] Debug: DPM Module Sync is done
    [Cortex_R4_0] ============ Heap Memory Stats ============
    Size Used Free DPCUsed
    System Heap(TCMB) 36864 28152 8712 3072
    L3 655360 393216 262144
    localRam(TCMB) 4096 512 3584
    ============ Heap Memory Stats ============
    Size Used Free DPCUsed
    System Heap(L2) 32768 16112 16656 0
    L3 655360 16384 638976
    localRam(L2) 50176 15272 34904
    localRam(L1) 16384 5728 10656
    Sensor was successfully configured.
    Starting Sensor (issuing MMWave_start)
    Hard Coded Configuration successfully sent to EVM.

    Regards,

    Allen

     

  • 0 in reply to Allen35065
    TI__Expert 7030 points

    Hi Allen,

    I am also seeing no UART data from Tera Term and have asked a few others on the team about this issue. Thanks for your patience and will get back to you.

    Thanks,

    Alex Chan

  • 0 in reply to Alexander Chan
    TI__Expert 7030 points

    Hi Allen,

    Sorry for the delayed response and thank you again for all your patience. I have been debugging the out of box hard coded config demo in Code Composer Studio and have found some issues with threads being blocked and thus no UART data from Tera Term. I am still trying to debug the issue. 

    In the meantime have you tried creating hard coded configs for other labs? There is an alternate approach outlined in this FAQ that I have tried and knows works such as with the people counting lab. https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1023135/faq-iwr6843-how-to-add-a-hard-coded-configuration-to-mmwave-radar-projects

    I have attached some additional pictures to help walk through the steps. In the FAQ link above there are two methods once you have edited the cli.c file and added the cfg information and define logic. I have tried both methods and was able to successfully enter debug mode in Code Composer Studio and see UART output from the Com port. 

    Method 1:

    Like the FAQ mentions you will need to recompile the cli driver in the SDK using the instructions in the SDK user's guide. The SDK user's guide can be found here: http://software-dl.ti.com/ra-processors/esd/MMWAVE-SDK/latest/exports/mmwave_sdk_user_guide.pdf in section 4.5 to setup the environment. Then you will want to navigate to the cli folder and build. 

    Now you will go to into Code Composer Studio and rebuild both the DSS first and then the MSS and then flash the binary. The problem with this method is because you have modified the cli.c and built the cli folder in the general SDK folder, all labs will be pulling from the same general SDK folder in Code Composer Studio and will be using the hard coded config cli.c file. If you want to use a different lab with different cfg file settings or don't want to use the hard coded config you will have to make changes to the cli.c file and and build it again every time. 

    Method 2:

    You can create and modify another cli.c copy not in the general SDK folder that all the labs pull from and manually copy that file into the mss in Code Composer Studio alongside the cli_mmwave.c file. In this method do not recompile the cli driver in the SDK. 

    Now right click the mss file you are working on and click properties. On the left side you should see on the left drop menu Arm Linker and then File Search Path. 

    In this method the specific library cli file will be unlinked as well as the cli library folder path in general so the project only uses the copied cli.c file from the step above. In the above image are the two highlighted items that I deleted from the File Search Path. This method is helpful since you can have various projects with different cli.c files that are different and not looking at the same cli.c in the SDK folder. 

    Now just rebuild the DSS and MSS like normal and flash the binary. 

    Thanks,

    Alex Chan

  • 0 in reply to Alexander Chan
    TI__Expert 7030 points

    Hi,

    Closing this thread due to inactivity. If you have any additional questions please start a new post.

    Thanks,

    Alex Chan