• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 420 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/IWR1642BOOST: boot iwr1642boost using hard coded config so we dont need to use the uart

oren golan
Intellectual 260 points
Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1443, IWR1642, IWR1443BOOST,

Tool/software: Code Composer Studio

the answer you gave to this title "CCS/IWR1443: there are some question in MmwDemo_CLISensorStop(1,initcfg_stop).why?" in the flowing link e2e.ti.com/.../2616079 was to iwr1413.
i need the .zip file that you gave in the last comment , but i need it to iwr1642.
i used the .zip file you put in your last comment and the sensor is working and do start itself, but it seems that its working not according to the configuration we are sending him from the uart.
can you help me with the same .zip file you uploaded for iwr1443boost but to iwr1642boost .

  • 0
    TI__Guru 50240 points

    Hi Oren,

    I believe this question has been answered in this thread.

    Let me know if you have more questions.

    Cheers,

    Akash

  • 0 in reply to Akash Gondalia
    Intellectual 260 points

    hi,

    it was indeed solved our problem and we menage to use hard coded instructions.

    when we used the same cli.c file for the car lab , it didn't work when we used the original .cfg  instruction you published , but when we send the config of the pp-count lab (lab 11) , the hard coded instruction did activate the radar, and when we change the parameters in the .cfg hard coded instruction, then the radar doesn't start.  

    the cli.c file in the link you gave us is dedicated to ppcount lab? there is any limitations in this cli.c file so that our hard coded instruction doesn't work? 

    all the best

  • 0 in reply to oren golan
    TI__Guru 50240 points

    Hi Oren,

    There are several rules that must be satisfied when sending a chirp configuration. The advantage to sending this commands over UART terminal or a visualizer is that there will be return commands indicating if values are allowed or not, so these won't be present when sending the commands through hard-coding.

    A good resource for understanding more of these commands is the mmWave Sensing Estimator.

    Cheers,

    Akash