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

IWR1642BOOST: How to configure charp config on visualizer ?

Naoki Kawada
Guru 19890 points
Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1443BOOST

Hi,

I would like to update the default charp configurations in runtime with some application specific ones on visualizer demo.

I just tried this with OOB Visualizer Demo on IWR1642BOOST (ES2.0), but i got some error in commands. For example, if I load the "Elevator_profile_cfg.cfg" (shared in ), it generates the following error :

Why this can happen ? 

Please note my goal is using IWR1443BOOST(not IWR1642BOOST) with "100m level sensing" (shared in ) to see RF performance for this type of application. Because of IWR1443BOOST availability, I`m trying the same test scheme on IWR1642BOOST... but now i`m concerned this type of error could happen with IWR1443BOOST.

Could you please kindly suggest the actual and validated instruction to evaluate the shared charp configuration in the "chap database" on IWR platform ?

Best Regards,
NK

  • 0
    TI__Mastermind 30405 points

    Hi NK,

    There are a couple of issues here:

    1. The Elevator chirp configuration was designed for mmWave SDK 1.2.0.5 and has not been updated for SDK 2.0.0.4 which is why you're gtting an invalid configuration error.

    2. But more importantly, please note that all chirp configurations provided in the Chirp database may not be compatible with the mmWave SDK OOB demo as mentioned in the Testing and Results section of the corresponding Chirp. The ones which can work with the OOB Demo have it clearly mentioned in this section. For  instance, the Very Fine Motion Detection chirp is compatible with the mmw OOB demo. But as noted on the Elevator chirp page, while the chirp configures the Radar Front End correctly, it is not compatible with the OOB demo digital processing chain.

    I have attached an updated version of the elevator config for SDK 2.0.0.4. This does not generate an invalid config error which means that it is valid from an RF front-end perspective. But after sensorstart, the DSP code crashes (raises an exception) as shown in the picture below. In other words, you still cannot use this with the OOB demo for the original reason mentioned on the chirp page.

    /cfs-file/__key/communityserver-discussions-components-files/1023/Elevator_5F00_profile_5F00_cfg_5F00_sdk_5F00_2_5F00_0_5F00_0_5F00_4.cfg

    You will need to design a dedicated digital processing chain for this chirp. One quick way to verify the performance for this configuration is to use mmWave Studio along-with DCA1000 EVM to capture and process raw ADC data in mmWave Studio itself. Please refer to the following training video for data capture with the DCA1000 EVM.

    https://training.ti.com/dca1000-training-video

     

    Regards

    -Nitin