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.

AWRL6432BOOST: Problems in building & executing MPD demo using CCS and visualzer

Part Number: AWRL6432BOOST
Other Parts Discussed in Thread: SYSCONFIG, , UNIFLASH

Hello TI experts,

I would like to ask you somewhat fundamental task, building & executing MPD demo using CCS and visualizer. 

Conditions and related problems are as below.

* Conditions

  - AWRL6432BOOST    - CCS : 12.6     - SDK : 05_04_00_01    - Sysconfig : 1.18.1 or 1.19 or 1.20

* Task 

  - Import & build MPD demo code (examples / mmw_demo / motion_and_presence_detection / ... / m4fsso-0-free rtos of SDK 05_04) by using CCS 12.6.

  - Flash the resultant app image (debug mode) into AWRL6432BOOST EVM by using UNIFLASH.

  - Execute the demo using the visualizer tool (SDK 05_04,  upload given motion detect cfg).

* Result (problems)

  - After uploading cfg, 'sensorStop 0' commands are shown on the command window 4 times, but no respose further with popup window of 'Please try again.'

  - After several trials of rebooting PC, renaming the project, making a new workspace, and so on... I get normal app image (that is, executable at the visualizer) by chance,

    but unfortunately, that is not reproducible (if I try the same procedure again, the resultant app image malfunctions again).

  - I even tried erasing & re-installing CCS, SDK, and sysconfig, but the problem still occurs (most trials fail, few trials succeed but not reproducible).

  - The difference of hex code between the 'normal (but not reproducible)' and 'abnormal' appimages are as below:

    Header CRC  :       Abnormal (74 0A 5E 71)   <-->   Normal (7D FB DC 6D)     

    Meta image size :   Abnormal (00 00 00 40, that is only 64 byte??)   <-->   Normal (00 04 67 00,  that is 288,512 byte)     

    Almost codes are identical each other....

    At the end  :            Abnormal (several '00' are added compared to the Normal)

  - The file size :          Abnormal (288,580 byte)  <-->  Normal (288,516 byte)

If you have any comments, please let me know.