• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 255 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

IWR1642BOOST: Some questions on how to use mmwave out of box demo and industrial toolbox

IWR1642BOOST: Short range radar user guide (build potentially failed) + building projects compatibility with EVM

Abdellah Bouchama
Prodigy 160 points
Part Number: IWR1642BOOST
Other Parts Discussed in Thread: IWR1642, IWR6843

Hello TI community,

I'm trying to follow this guide for short range radar detection, i succeed in all the steps until 6th (the GUI is launched and plotted). in the other hand i tried to follow developer's guide as well, i installed the software requirements and also verified the installations (everything's good), i imported both projects on CCS (DSS and MSS as mentioned in the guide) and tried first to rebuild the dss project. A successful build generate a .bin AND a .xe674 files but in my case only the .bin file is generated !!

Knowing that i'm having this two strange error/warning on the CCS console :

  1. The error : process_begin: CreateProcess(NULL, rm -f C:/Users/<my name>/workspace_v11/srrdemo_16xx_dss/srrdemo_16xx_dss.bin, ...) failed.
    make (e=2): Le fichier spécifié est introuvable. (means the file is not found)
     
    gmake[1]: [pre-build] Error 2 (ignored)
  2. The warning : warning #10370-D: Possible codesize or performance degradation. Section ".text:SOC_init:libsoc_xwr16xx.ae674<soc.oe674>" has calls to rts routines, but rts is placed out of range from call site at 0x20003604, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.
    warning #10370-D: Possible codesize or performance degradation. Section ".text:SOC_init:libsoc_xwr16xx.ae674<soc.oe674>" has calls to rts routines, but rts is placed out of range from call site at 0x200034e0, or in a different section. To optimize codesize, either 1) place rts closer to call site, or 2) place rts in same section, or 3) compile with --disable_push_pop.

So my questions are :

  1. Is the build successful ?
  2. How to verify that the mmwave device support packages are up to date (later than 6.0.0576) as indicated in the guide ( in Software Requirements)
  3. About another project building : I've noticed on the lab directory that there is no compatibility between the EVM i'm using (IWR1642) and a project i want to build (3D people count) is there any way to make it compatible or emulate the needed device on my device? if not what's the reason that make a project compiled on a kind of EVM and not another kind (hardware or software)?

Thank you in advance for helping.

Best regards.

Abdellah.

  • +1
    TI__Genius 17265 points

    Hi,

    1. Yes, it appears your build did succeed if those were the only two issues that appeared. It should also say build successful at the end of the log.
      1. The first error is the build trying to delete the old binary to make room for the new one. Since it was your first time building, the old binary did not exist, so it throws an error. This does not matter
      2. The warning is just suggesting optimizations in memory layout to reduce the time it takes to execute specific code. Should not cause any issues.
    2. This was likely installed in your CCS automatically when you installed the mmWave SDK. Ensure you have the correct mmWave SDK installed by going to preferences->products and checking the discovered products, and hitting install if necessary
    3. In this case this is likely not possible without very major downgrades to the demo. Some reasons below
      1. IWR1642 is a 77GHZ band radar rather than 60GHZ band. You could likely port the demo to work on 77GHZ, but we do not have that available currently
      2. IWR1642 does not have a Hardware Accelerator, which the IWR6843 does. The 3D People Counting is already very mips-intensive, and without the HWA to perform some of the calculations, you would have to significantly reduce performance. 
      3. IWR1642 has 2 TX antennas, while IWR6843 has 3. This would mean that some of the algorithms would need changes to reflect this

    If you are looking to perform People Counting/Tracking, the 60 GHZ band is mandated by regulations in many countries, which is why the demo is focused on this band. If you need to stay in the 77GHZ band, the xWR1843 would be much more similar to the xWR6843. You could migrate the 3D people counting demo from xWR6843 to xWR1843 much more easily, but it would still require some modifications on your end if that was the route you wanted to go down.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 160 points

    Hi Alec,

    Thank you for answering again, i'm having just one more question;

    In the people counting user guide they indicate that we can select any parser for some labs, i'm specially interested in the (Legacy): 2D People Counting (For both IWR16xx and IWR68xx). So it's clearly mentioned that we can use this lab with IWR1642 for example. (see figure bellow)

    I tried to use this demo, after flashing the 3D people counting .bin file as a firmware (3D_people_count_68xx_demo.bin) and also with Out of box firmware (xwr16xx_mmw_demo.bin). (Not working)

    my question is :

    -Are they the right firmwares to use and what shirp configuration should i use with ?

    Have a nice day,

    Abdellah.

  • 0 in reply to Abdellah Bouchama
    TI__Genius 17265 points

    Hi Abdellah,

    Can you please open a new thread for this follow up question?

    Best Regards,
    Alec