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.

IWRL1432BOOST: Not reading config file in IWR1432BOOST

Part Number: IWRL1432BOOST
Other Parts Discussed in Thread: IWRL1432, MMWAVE-L-SDK

Tool/software:

I used mmWaveSensingEstimator(dev.ti.com/.../) and modify config parameter.

 I changed range resolution value and Maximum range.

Resolution value is 0.109 and Maximum range is 50.002.

I read making config file to IWRL1432BOOST,using mmMave radar visualizer(ver 5.5.3.0)

When I made config file, mmWaveSensingEstimator did not display Error-causing cell.

Why did'nt mmMave radar visualizer read config file?

  • Hello,

    A team member will get back to you within 24 hours

    Best Regards,

    Pedrhom

  • Hello, 

    Can you please chare the cfg file that you generated from mmWave Sensing Estimator?

    Thanks,

    Josh

  • Hello,Josh.

    I could read cfg file to mmwave radar visualizer,referring to cfg file which was created  from mmwave radar visualizer(ver 5.5.3.0) and I modified manually.

    This Specification is that Max range is 56.4m and range resolution is 12cm

    I am using Range-Doppler Image mode.

    I attached cfg file whose name is generatedConfig_2025-04-09_13-51-03_range56m.

    generatedConfig_2025-04-09_13-51-03_range56m.cfg

    So I tried to modify Max range  50m and range resolution 0.109m.

    I modified chirpComnCfg to 9 0 0 1024 4 95.0 0 manually.

    I also attached modified and not reading cfg file.

    generatedConfig_2025-04-09_13-51-03_range50m.cfg

    Both file didn't show Error causing cell.

    I could read cfg file of Max range 56.4m to mmwavevizualizer ,but I couldn't read cfg file of Max range 50m.

  • Hi, 

    Thank you for sharing the cfg files. Just to clarify, these files were created with the sdk visualizer right? And you are saying you checked them in sensing estimator and didn't see any errors? 

    I can confirm I am seeing the same behavior as you with the second configuration file not working. After investigating further I can see that the issue is related to the configuration not adhering to the minimum burst periodicity requirements. You can change the line below for it to work. 

    frameCfg 2 0 310.11 8 250.00 0  ->   frameCfg 2 0 318 8 250.00 0

    Thanks,
    Josh
  • HI,Josh

    Thank you for replying.

    Mmwave sensing estimator didn't display Error causing cell,when I read both cfg file.

    I could change cfg parameter to frameCfg 2 0 310.11 8 250.00 0  ->   frameCfg 2 0 318 8 250.00 0.

    I could read  cfg file to mmwave visualizer.

    Thank you for your help.

    Please response additional question.

    I would like to improve range resolution ,not modifying max range.

    I need range resolution below 0.062m.

    Probably numofAdcSamples parameter need to be modified to 2048,though  numofAdcSamples parameter is now 1024.

    Does IWRL1432BOOST support changing numofAdcSamples parameter to 2048?

    Or Does IWRL1432 chip support changing numofAdcSamples parameter to 2048?

  • Hello, 

    Thank you. Just to confirm, there is currently an issue with the burst periodicity error checking in the sensing estimator tool. This will be fixed in s future update. 

    Does IWRL1432 chip support changing numofAdcSamples parameter to 2048?

    Yes. Please see below from the interface control document for xWRLx432 devices. 

    Best regards,

    Josh

  • Hello.

    I know that IWRL1432 chip supports numofAdcSamples changing to 2048.

    Where is interface control document for xWRLx432 devices?

    If I want to changing to numofAdcSamples in IWRL1432BOOST , Could I change numofAdcSamples to 2048 by DCA1000?

  • Hello, 

    The Interface Control Document (ICD) can be found in the mmwave_dfp firmware package that is included with MMWAVE-L-SDK. {MMWAVE_SDK5_INSTALL}\firmware\mmwave_dfp\docs

    If I want to changing to numofAdcSamples in IWRL1432BOOST , Could I change numofAdcSamples to 2048 by DCA1000?

    Yes, you can use DCA1000/mmWave Studio. Alternatively, the SDK documentation also mentions that mmwave demo supports up to 2048 samples so you should be able to adjust this in the cfg file. 

    Best regards,

    Josh

  • Hi, 

    I noticed you selected that this did not resolve your issue. Please let me know if you are still looking for more information. 

    Best regards,

    Josh

  • Hi,

    Thank you for replying.

    I don't have DCA1000 and I am trying to get DCA1000.

    To be honest , I don't know how to use DCA1000 and CCS.

    So please let me know how to modify numofAdcSamples parameter ?

    What should I modify numofAdcSamples parameter in source file of MMWAVE_L_SDK  and rebuild source file ?

  • Hi, 

    Just to clarify, DCA1000 is not required. I only mentioned this was possible since you had asked that previously. All that should be required for enabling 2048 ADC samples is changing the correct parameter in the .cfg file which you are using to configure the sensor. Since this parameter is part of the configuration sent over CLI interface then changing demo code and recompiling is not required. 

    chirpComnCfg 8 0 0 2048 4 200 0
     
    Regards,
    Josh
  • Hi,

    Thank you for replying.

    I understand that changing to Numofadcparameter of  IWRL1432BOOSTdon't need DCA1000.

    I tried to change chirpComnCfg 8 0 0 2048 4 200 0 and read cfg file to IWRL1432BOOST.

    But visualizer showed error.

    This is cfg file showing error pop up.

    generatedConfig_2025-04-09_13-51-03_range50m_burstperiodity318us_frameperiod200us.cfg

    Please let me know how to reading cfg file changing to Numofadcparameter of 2024.

  • Hello, 

    Sorry for the slow response. Also I need to correct my earlier statements, it is true that the front end supports 2048 samples, which is why the ICD document states 2048 is the max. However, the HWA 1.2 of the IWRL1432 only supports fft sizes up to 1024. This effectively limits the max adc samples to 1024 when using the SDK. I apologize for the confusion, we will update the documentation and error checking of the demo accordingly.

    Regards,

    Josh