• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 482 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: People Counting .bin file from Industrial Toolkit 2.4.0 works, the one from 2.5.2 doesn't work

Maciej Ziarkowski
Prodigy 30 points
Part Number: IWR1642BOOST

I was trying to remove the point cloud output from the People Counting demo. So far I have been working with the version of the demo from Industrial Toolkit 2.4.0. I have my own desktop Python program which handles device configuration and serial port communication. This program works without problems when connecting to an IWR1642BOOST ES2.0 board, flashed with the .bin image from IT 2.4.0.

First, I tried just removing the appropriate lines in the demo code to get rid of the point cloud output (in lab0011_pplcount_pjt/radarDemo/chains/RadarReceiverPeopleCounting/mmw_PCDemo/mss/task_mbox.c) and building it with CCS, using the newest SDK. The build and flashing of new .bin image proceed without errors. The config port communication works, as I get the "Done" messages for all config lines sent by my program. However, there is no data coming through on the data port.

Then I saw a new Industrial Toolkit version (2.5.2) was released with a config option added for the point cloud output in the people counting demo. I took the pre-generated .bin file from IT 2.5.2 and flashed it to the device. The result is basically the same as for the self-built image: the configuration of the device works, but no data is send on the Data Port after the sensorStart command.

Flashing the original IT 2.4.0 image makes everything work again. Flashing the 2.5.2 version or my own image makes it stop working.

A couple thoughts: 

- the sticker on the anti-static bag says 'IWR1642AQAGABL ES2.0' but the sticker on the board itself says only 'IWR1642AQAGABL'. Is there any chance the board is actually and ES1.0?

- I am wondering if the problem has to do with what version of the SDK the image is built with. I built mine with SDK 2, and presumably the 2.4.0 toolkit version was built with an earlier SDK version? How about the 2.5.2 toolkit version?

  • 0
    TI__Mastermind 28055 points

    Hi Maciej,

    You can check the version of the device you have using the device nomenclature sheet - see this post to understand what the nomenclature means.

    The Industrial Toolbox 2.4.0 and 2.5.2 are both built with SDK 2.0.

    Have you tried running the 2.5.2 version with the TI visualizer? I have been successful doing this myself, simply edit the default configuration file (quickstart/mmw_pplcount_demot_default.cfg) so line 18 reads "PointCloudEn 0".

    How are you determining whether or not data is being sent from the device? Is it possible that your python script has a dependency on the Point Cloud TLV?

    Regards,

    Justin

  • 0 in reply to Justin Curewitz
    Prodigy 30 points

    Hi Justin,

    The TI Visualizer did work, and I have since discovered the issue - it was not the Python program, but rather the config I passed - one of the variables for the lowPower setting, whether 0 or 1, does not have an effect on the functioning of the 2.4.0 code, but if it's set to 0, it prevents the 2.5.2 version from sending any data. Setting the value to 1 solved the issue.

    However, I tried building the unmodified 2.5.2 demo in CCS, and I am encountering further problems. I built and flashed the image to the device without errors. The communication with the device works, and the desktop program receives packets with correctly formatted headers, however they don't contain any TLVs at all. Changing the PointCloudEn between 0 and 1 has no effect.

    The exact same configuration with the pre-built image works fine, so there must be something wrong with how I build the image. What could be the problem? 

    I checked the development prerequisites from  

    All requirements are fulfilled, apart from the C6000 Code Generation Tool, for which my version is 8.1.3 as opposed to the required 7.4.16 - does it need to be fixed to that particular version? By the way, the download links to v7.4.16 don't work.

    Can switching between Debug and Release configuration make any difference for the build?

    Other than that I wasn't able to find any potential problems. I noticed however that the resulting file is different - the pre-built image is 319 KB, the one built by me is 328 KB. Not sure if this hints at any more problems.

  • 0 in reply to Maciej Ziarkowski
    TI__Mastermind 28055 points

    Hi Maciej,

    You will have to compile with version 7.4.16 of the c6000 compiler. Version 8.1.3 is not compatible with the DSS source. You can find the instructions in the last post of this thread. 

    Regards,

    Justin