• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 400 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/AWR1642BOOST-ODS: Software ID

Sreenath Vipin
Intellectual 530 points
Part Number: AWR1642BOOST-ODS
Other Parts Discussed in Thread: AWR1642BOOST, AWR1642

Tool/software: Code Composer Studio

Hi,

How does the mmWave demo visulaizer identify code that is flashed on that EVM?

Is there any identifier in the software code?

BR,

Sreenath 

  • 0
    TI__Guru*** 149044 points

    Hi,

    There may be some confusion

    The AWR1642BOOST-ODS is only supported by the obstacle detection lab provided in the TI Resource Explorer.

    You can run the mmWave SDK OOB demo, however the angle information will not be correct because the OOB demo was designed to run on AWR1642BOOST EVM, which has a different antenna.

    Now, regarding your specific question

    The software that runs on the target sends the object data to the Visualizer.

    following informtion is sent as part of the header. As you can see device type is part of the header information

     message.body.detObj.header.platform = 0xA1642;
        message.body.detObj.header.magicWord[0] = 0x0102;
        message.body.detObj.header.magicWord[1] = 0x0304;
        message.body.detObj.header.magicWord[2] = 0x0506;
        message.body.detObj.header.magicWord[3] = 0x0708;
        message.body.detObj.header.numDetectedObj = obj->numDetObj;
        message.body.detObj.header.version =    MMWAVE_SDK_VERSION_BUILD |   //DEBUG_VERSION
                                                (MMWAVE_SDK_VERSION_BUGFIX << 8) |
                                                (MMWAVE_SDK_VERSION_MINOR << 16) |
                                                (MMWAVE_SDK_VERSION_MAJOR << 24);

    Thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 530 points

    Hi,

    What exactly is the purpose of magic word?

    The above snippet of code is same in all application firmware,then how  exactly is the Visualizer detecting each code that is flashed into the EVM ?

    BR

    Sreenath

  • 0 in reply to Sreenath Vipin
    TI__Mastermind 24955 points

    Sreenath,

    For more information about the output messages that are sent over UART to the PC in the Out-of-Box Demo, please refer to the "Output information sent to host" section of the SDK Doxygen that can be found here for the latest SDK release: 

    file:///C:/ti/mmwave_sdk_03_02_00_04/packages/ti/demo/xwr16xx/mmw/docs/doxygen/html/index.html

    You will need to install SDK v3.2 onto your PC to view this html document.

    The magic word notifies the visualizer that this is an output message from the AWR1642 device. Every UART output message begins with a magic word.

    Regards,
    Kyle

  • 0 in reply to Kyle Cousino
    Intellectual 530 points

    Hi,

    But these magic word values seem to be same for all the codes such as ODS demo, SRR demo, so how exactly is the visualizer distinguish between these demos ?

    BR

    Sreenath

  • 0 in reply to Sreenath Vipin
    TI__Mastermind 24955 points

    Sreenath,

    The mmWave Demo Visualizer works only with the SDK Out-of-Box Demo. The Visualizer that I am referring to is found here: https://dev.ti.com/gallery/view/mmwave/mmWave_Demo_Visualizer/ver/3.2.0/ 

    Each demo has its own visualizer since the expected output messages vary from demo to demo. The paradigm is one visualizer per demo and not one visualizer for all demos.

    This should clear up any confusion about the demos and the visualizers.

    Regards,

    Kyle