• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 30 subscribers
  • Views 362 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.

AWR1642BOOST: Formatting of the chirp configuration file

Johan Forssen
Prodigy 160 points
Part Number: AWR1642BOOST
Other Parts Discussed in Thread: AWR1642

Hello,

We running evaluation tests on the awr1642boost board, and have a few questions regarding the formatting and functionality of the chirp configurations.

 -       In *.cfg files loaded and extracted from mmWave Demo Visualizer 3.x, the command <lowpower> with parameters < 0 0 > instead of < 0 1 > is (although from limited testing) seemingly not working even with a reset between test runs. Older *.cfg files (i.e not SDK 3.x), running on older firmware, seem to have had no issues as most examples (from automotive/industrial toolbox in resource explorer) are using the parameters < 0 0 >. By looking in the sdk 3.1.1 user manual there is no concrete explanation to what exactly differentiates the two values (“depending on profileCfg>digOutSampleRate”). What is the difference and why wouldn't parameters < 0 0 > not work in our testing?

-       Old *.cfg files developed for sdk 1.x are substantially different from the files written/saved-from-demo-visualizer for sdk 3.x, with differing number of parameters and mandatory commands, rendering them impossible to deploy without major reformatting onto boards with newer firmware. Are older chirp configuration examples unusable or is there any way to extract information from them even with the new parameters? For example, command <adcbufCfg> does nowdays have 5 parameters instead of 4 in older *.cfg files, and it very hard to know which of the parameters have been added.

Thanks,

Johan

  • 0
    TI__Guru 69960 points

    Hi,

    - AWR1642 ES2.0 (production version) only lowpower ADC mode is supported which is intended in the final silicon version. In old Si (or with old firmware) it may support other value which was just for evaluation.

    In latest version of hardware (ES2.) and firmware only lowpower mode is supported in AWR1642, so that means you need to use 'lowpower 0 1' CLI command only.

    So, SDK 2.1 onward you need to use 'lowpower 0 1' CLI command only.

     - SDK 1.x is very old version which was starting of this device SW/FW development, so over the time as Silicon revised parameter of CLI command revised as well.

    I would recommend to use at least SDK 2.1 version for any development on AWR1642 ES2.0 revision.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 160 points

    Thanks Jitendra,

    Yes, it makes sense to use the latest version of SDK.

    I had a follow-up question that was not answered by your reply,

    • Old *.cfg files developed for sdk 1.x are substantially different from the files written/saved-from-demo-visualizer for sdk 3.x, with differing number of parameters and mandatory commands, rendering them impossible to deploy without major reformatting onto boards with newer firmware. Are older chirp configuration examples unusable or is there any way to extract information from them even with the new parameters? For example, command <adcbufCfg> does nowdays have 5 parameters instead of 4 in older *.cfg files, and it very hard to know which of the parameters have been added.

    Thanks,

    Johan

  • 0 in reply to Johan Forssen
    TI__Guru 69960 points

    Hi Johan,

    SDK 2.1 onwards most of CLI commands are retained as is. And to see the difference of any CLI command please refer mmWave SDK user guide 'Configuration File Format' section which explains each an every CLI commands' parameter details.

    Compare to SDK 1.x there are quite a changes (software evolution) but as I said if you comapre SDK user guide for CLI command list you can find the addition parameter list.

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Prodigy 160 points

    Thanks for your answer Jitendra, sound like a good plan.

    Johan