• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 32 subscribers
  • Views 479 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.

IWRL6432: CFAR cfg parameter

Andy Yin
Genius 9320 points
Part Number: IWRL6432

Hi,

My customer run the mmw demo in sdk5.4, change to use below cfg, it reports "CFAR DPU config return error:-2801 " after sending sensorstart cmd.

Would u pls help check below cfg and let me know the problem? thanks.

Andy

  • 0
    TI__Genius 11750 points

    Hi,

    Thanks for your query. Please allow us a couple of days to respond

    Regards

  • 0
    TI__Mastermind 20901 points

    Hi Andy, 

    My apologies for the delay here. Can you please confirm, is the customer trying to run the mmwave_demo or the motion_and_presence_detection example? Both are located in the SDK but there would be separate configuration limitations depending on which is used. 

    Best Regards,

    Josh

  • 0
    Intellectual 440 points

    Hi,

          our test runs the mmw demo in sdk5.4, We have the following questions:

          1.the CFAR Cfg parameter: as show above, the CFAR_GUARD is 8 , and the CFAR_AVG_RIGHT and the CFAR_AVG_LEFT are 64 both. And (CFAR_GUARD + CFAR_AVG_RIGHT) * 2 = 144 < 256, where, 256 is the number of range dimension samples, but it reports "CFAR DPU config return error:-2801. What if we want to increase the length of CFAR_GUARD?

          2.the compression enable: Run default MMWAVE_L_SDK_05_04_00_01\examples\mmw_demo and MMWAVE_L_SDK_05_04_00_01\examples\mmw_demo\mmwave_demo\profiles on 6432EVM The default configuration in wrL64xx-evm is parking_5m.cfg, and there is no point cloud target output.

    But when the configuration compressionCfg is disabled, some point clouds  can be obtained with the following results

  • 0 in reply to MZB
    TI__Mastermind 20901 points

    Hello, 

    1. Due to hardware limitations, CFAR guard length must be less than 8. The register that holds this information is a 3-bit register. The image below comes from the HWA user guide.

    2. This is a known issue with the SDK 5.4.0.1 release. To resolve the issue of no point cloud output with compressionCfg enabled, you need to make the below code changes and rebuild the demo code.

    In mmwave_demo.c, replace the blue highlighted code here:

    With this:

    SOC_memoryInit(SOC_RCM_MEMINIT_HWA_SHRAM_INIT|SOC_RCM_MEMINIT_TPCCA_INIT|SOC_RCM_MEMINIT_TPCCB_INIT|SOC_RCM_MEMINIT_FECSS_SHRAM_INIT|SOC_RCM_MEMINIT_APPSS_SHRAM0_INIT|SOC_RCM_MEMINIT_APPSS_SHRAM1_INIT);

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    Intellectual 440 points

    As shown above, why an error occurs when the NumOfChirpsInBurst parameter is changed to 128 after enabling it. Lengthening the BurstPeriodicity still results in this error. 

    Error: mmWave Config failed [Error code: -3110 Subsystem: 0]

  • 0 in reply to MZB
    TI__Mastermind 20901 points

    Hello, 

    I'm very sorry about the delay here. I have been out of office and it seems your thread was not handled appropriately during my absence. 

    If you still receive the error -3110 even after increasing the burstPeriodicity then you may have actually set the burstPeriodicity higher than the accepted limits. If you change the burstPeriodicty to 8000 us then you can avoid this error but you will still face another issue due to memory size. With the configured number of samples/chirps/bursts there is insufficient memory required to allocate the detection matrix.

    Best Regards,

    Josh