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.

IWR6843AOPEVM: Device can't work normally when download the bin file to 6843AOP

Part Number: IWR6843AOPEVM
Other Parts Discussed in Thread: IWR6843AOP, MMWAVEICBOOST, UNIFLASH

Hello, 

I modified the code of Multiple Gesture and Mothion Detection in Industrial Toolbox.  Then I debug the code using CCS and it can work normally. But when I download the multi_gesture_demo_68xx_aop.bin to IWR6843AOP, it cannot work. The following  is the error information in command port. 

Then I found the line 2054 in dss_main.c,.

But I can't understand this error. 

So, why it can work in CCS debug mode and cannot work when downloading the bin file to 6843AOP?

SDK version: 3.5.0.4

device: IWR6843AOP+MMWAVEICBOOST

Thank you. 

  • Hello,

    When you state that it works in CCS is that with the error that you highlighted above? Additionally, when you state that the binary can not be downloaded are you referring to flash? Can you share the error that you get when trying to download the binary?

    Best regards,

    Connor Desmond

  • Hello, 

    1

    In CCS debug mode, I test the code and it can run normally. As shown in following figure, the PC can receive the data from the board. And there is no error in CCS debug mode.

    2

    I rebuild the project and download the .bin file to board using UniFlash. And the console of UniFlash shows "Program Load completed successfully". Then I change the SOP and reboot the board, but PC can't receive the data from the board. As shown in following figure, the PC received an Exception from User UART port. 

    The following figure shows the line 2054 in dss_main.c

    The program can run correctly in CCS debug mode and PC can receive data from the board. But in deployment mode, the program cannot run normally. So, how to solve this problem?

    Thank you.

  • Hello,

    Can you please detail at a high level what modifications you made.

    Best regards,

    Connor Desmond

  • Hello,

    MSS

    1 multi_gesture_68xx_aop_mss/common/cli.c

    In order to apply advanced frame configuration, I modified the char array hardCodedConfigCommands. The subFrame1 has 1 Chirp and the subFrame2 has 64 Chirps.

    2 multi_gesture_68xx_aop_mss/mss/mss_main.c

    I modified the MmwDemo_mboxReadTask function to send out the range-FFT and range-doppler matrix.

    3 multi_gesture_68xx_aop_mss/mss/mss_main.c

    Set the gMmwMssMCB.cfg.loggingBaudRate to 1843200 in main function.

    DSS

    1 multi_gesture_68xx_aop_dss/dss_main.c

    A piece of code has been added to MmwDemo_dssDataPathProcessEvents function for moving range-FFT of the first Chirp of subFrame1 and subFrame2 to HSRAM.

    2 multi_gesture_68xx_aop_dss/dss_main.c

    I also modified the MmwDemo_dssSendProcessOutputToMSS function to move range-doppler matrix to HSRAM. Then this function will notify the MSS to send out the data.

    Thank you. 

  • Hello,

    Thank you for providing that information. I will get back to you when I have looked at these modifications and their potential impact.

    Best regards,

    Connor Desmond

  • Hello,

    With the OOB demo are you able to run in deployment and debug mode with no issues?

    Best regards,

    Connor Desmond

  • Hello,

    The OOB demo can run normally in deployment mode and debug mode.

    Thank you.