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.

AWR1843BOOST: Front mount Occupancy: What does Heatmap size represent?

Part Number: AWR1843BOOST

Hello,

Q1. What's the row and columns number represent in Heatmap? Is it range bin and angle bin number and why?

Q2. How to change the Frame Periodicity in config file "od_demo_18xx_8zone.cfg".

I tried to change the fifth number in frameCfg line from 160 to 110 as following (frameCfg 0 3 128 0 160 1 0 => frameCfg 0 3 128 0 110 1 0), the demo didn't work (not output).

Thanks,

  • Hi,

    Yes, range-azimuth heatmaps are indexed by range and azimuth bin index. They are useful as they essentially contain all the information needed for a 2D representation of a scene.

    Could you run the lab in CCS debug mode and see the error printer in console log when you reduce the interframe time? It is possible that the reduced interframe time is not sufficient for the processing to complete. 

    Regards,

    Aayush

  • Hello,

    this line get executed CLI_write ("Error: Invalid usage of the zoneDef command\n");

    when I enter more then 10 zones

    in ODDemo_CLIZoneDef function, argc still 40 even I filled zoneDef line in chirp config file more than 10 zones 

    argc in ODDemo_CLIZoneDef function cli source file of Vehicle Occupancy demo   in should count number of arguments in zoneDef  line, why it's limited to 40 

    example: 

    zoneDef 21  7 10 1 14  7 10 17 14  7 10 33 14  20 10 2 11  20 10 13 11  20 10 25 11  20 10 36 11  30 10 2 11  30 10 13 11  30 10 25 11  30 10 36 11  40 10 2 11  40 10 13 11  40 10 25 11  40 10 36 11  50 10 2 11  50 10 13 11  50 10 25 11  50 10 36 11  9 10 8 32  24 10 8 32
    argc in ODDemo_CLIZoneDef function cli source file of Vehicle Occupancy demo in this case also equal to 40

    Thanks,

  • Hi Mostafa,

    Sorry for the delay, I think I might know the issue.

    The lab uses the CLI utility from the SDK to parse the .cfg file. The CLI utility has an arbitrary limit of 256 bytes on the maximum length of a command. The command you have posted exceeds that. The fix should be easy: in <SDK_INSTALL_LOC>/ti/utils/src/cli.c in CLI_task, change cmdString to be a 512 character array, it is currently a 256 character array.

    Afterwards, it is just a matter of first recompiling the CLI utility in the SDK, then recompiling the lab.
    Regards,
    Aayush
  • Thanks, Aayush,

    Could you tell me how to recompile the CLI?

    Thanks,

  • Hi Mostafa,

    "Developing using SDK" section of the SDK user guide has this information. The gist is that we set up the environment and then use gmake to build the components with their respective makefiles. The user guide goes into more details on this.

    Regards,

    Aayush