• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 884 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.

AWR1843AOP: How to start

Mihir Salot
Prodigy 200 points
Part Number: AWR1843AOP
Other Parts Discussed in Thread: AWR1843

I have the module as mentioned above, and have been expeirmenting around with different configurations using demo-visualizer. I have the following doubts

1) To start with do I need to flash any other .bin/.cfg file or the one from demo-visualizer will suffice for experiments

2)Difference in .bin and .cfg file

3) To use readily available TI configs/.bin file, do I need to flash any other code, or are these files standalone.

4) Can you help us point out which config may help us attain result as in  https://www.ti.com/lit/SPYY001

  • 0
    TI__Guru*** 149044 points

    Hi

    Please see attached document that will help you evaluate the mmWave SDK with1884.AWR1843AOPEVM_mmWaveSDK_Evaluation.pdf AWR1843AOPEVM

    Mihir Salot said:
    1) To start with do I need to flash any other .bin/.cfg file or the one from demo-visualizer will suffice for experiments

    You will only need to flash the demo bin file:

    C:\ti\mmwave_sdk_03_05_00_04\packages\ti\demo\xwr18xx\mmw\xwr18xx_mmw_aop_demo.bin

    Mihir Salot said:
    2)Difference in .bin and .cfg file

    The bin file is the target code that will run on the DSP and ARM processors integrated in the AWR1843 device.

    The cfg file includes configuration information for the

    • RF front end
    • demo

    The information included in the cfg file is transferred to the target through the UART when the cfg file is loaded.

    Mihir Salot said:
    3) To use readily available TI configs/.bin file, do I need to flash any other code, or are these files standalone.

    You will only need to flash the the demo bin file

    C:\ti\mmwave_sdk_03_05_00_04\packages\ti\demo\xwr18xx\mmw\xwr18xx_mmw_aop_demo.bin

    Mihir Salot said:
    4) Can you help us point out which config may help us attain result as in  https://www.ti.com/lit/SPYY001

    I think you should start with following profile configuration and modify it to extend the range

    Here are two examples that have max range ~50m. The only difference between the configs is the number of chirps

    See "frameCfg 0 1 128 0 100 1 0" for example. "128" means that we loop 128 times between chirp_0 and chirp_1. So this configuration will have a total of 128x2 chirps

    Increasing the number of chirps increases the SNR, however it also increases the processing time.

    profile_2d_usrr_50m_128loop_1843aop.cfg

    See "frameCfg 0 1 32 0 100 1 0" for example. "32" means that we loop 32 times between chirp_0 and chirp_1. So this configuration will have a total of 32x2 chirps

    profile_2d_usrr_50m_32loop_1843aop.cfg

    Here is an FAQ that helps understand how the profile/chirp configuration affects the maximum range

    https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1050220/faq-computing-maximum-range-velocity-and-resolution-mmwave-system

    Unfortunately our team does not have experience with drone applications. You would need to experiment

    thank you

    Cesar