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

Original question:

IWR1443: Changing profile parameters with MMWave_API

IWR1443: Using Sensing Estimator generated profiles with OOB Demo

Julia Sánchez Sánchez
Prodigy 115 points
Part Number: IWR1443

Hello,

I'm studying the IWR1443 chip using IWR1443BOOST. Some days ago I asked the following question: IWR1443: Changing profile parameters with MMWave_API and as part of the answers, a member of TI suggested me:

Please note, the latest version of the mmWave Sensing Estimator (2.1.1) allows the user to save the configuration as a .cfg file (rather than json) which can be sent over UART to configure the device when running the out-of-box demo.

I've been trying to do that for my device. My objective is to create a profile more complex than the ones the Demo Visualizer generates, to adapt better to my application environment. Nevertheless, when trying it, I've been having some problems. What I'm doing is generating a profile at mmWave Sensing Estimator, downloading the .cfg and sending it over UART to the IWR1443BOOST. When doing this, it gives me an error related to adcbufCfg command. I've tried to understand it.

What happens in detail is: when generating the .cfg from Sensing Estimator, it generates the following:
adcbufCfg -1 0 1 1 1

Note: I'll underline in green UART commands and info and in blue app code

Corresponding to: <subFrameIdx><adcOutputFmt(*)><sampleSwap><chanInterleave><chirpThreshold> (*)actually Sensing Estimator doesn't assign any adcOutputFmt, so it sends a 0 in its place.

I've been studying at CCS the IWR1443-OOB Demo application code, and it's not prepared to parse that information. When receiving a adcbufCfg CLI command, arguments format should be, according to definition, as follows:
<adcOutputFmt> <SampleSwap> <ChanInterleave> <ChirpThreshold>
It's not only the parsing function, but the structure used for this configuration doesn't have a subFrameIdx variable.

Therefore, I decided to try eliminating that parameter (adcbufCfg -1 0 1 1 1 replaced by adcbufCfg 0 1 1 1 on .cfg file) and seeing if the profile worked without it. Unsorprisingly, it doesn't. Every UART command is parsed but when executing sensorStart the application ends in an error point. This error is on a different line each execution, but always related to OpenCfg (or at least that's what I observe).

Do you know how to solve this? Maybe:

  • I could I adapt my application at CCS so that it can work with Sensing Estimator generated profiles. 
  • I could modify some parameter from the profile to adapt it to the OOBDemo for IWR1443 application.


I'm attaching the .cfg I'm talking about just in case it helps.

IWR_1443_profile_1.cfg

Thank you in advance for your attention and best regards,

Julia Sánchez.

  • +1
    TI__Genius 10730 points

    Hi Julia,

    Where did you get the demo code for the IWR1443 OOB demo? Do you know what version of the SDK you are using? 

    For SDK 2.0 there may be a bug in the sensing estimator, I believe the adcbufCfg should be 0 0 0 1 (please see the SDK User's Guide for more information). 

    Thank you,

    Angie

  • 0 in reply to Angie Mitchell
    Prodigy 115 points

    Hello Angie,

    I'm using SDK 2.1.0 and that's where I got from the IWR1443 OOB Demo. I'm using this SDK version as I saw it's the one recommended for IWR1443BOOST.

    I tried what you suggested (adcbufCfg 0 0 0 1) and checked the reason at the User Guide, and changing that, I can use the profile generated by Sensing Estimator. Therefore, my problem is solved.

    Thank you very much for your help,

    Best regards, Julia.