• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 3 answers
  • Subscribers 30 subscribers
  • Views 653 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.

IWR6843ISK: Hardcode cfg for the demo

Divya Teja Settimali
Intellectual 360 points
Part Number: IWR6843ISK
Other Parts Discussed in Thread: IWR6843AOP, , IWR1443, IWR6843

Hi,

I'm trying to hardcode the cfg for area scanner on IWR6843AOP and for long range on IWR6843ISK. There is a hardcode bin file only on Out of box demo and it works only on ISK and not on AOP because of the different antenna pattern please correct me if I'm wrong.

In CCS/IWR1443: there are some question in MmwDemo_CLISensorStop(1,initcfg_stop).why? - Sensors forum - Sensors - TI E2E support forums there is a zip file attached with some example code for using a hard-coded sensor configuration with IWR1443 and mmWave SDK 1.2 but I want to make changes on IWR6843AOP and IWR6843ISK as mentioned earlier. The updates are made to the cli.c file that is part of the cli library in the mmWave SDK. So the question here is if the same file can be used for IWR6843ISK and IWR6843AOP and done in the same way?

Regards,

Divya Teja Settimali

  • 0
    TI__Expert 7510 points

    Divya:

    The HCC demo is targeted for IWR6843ISK in terms of what configuration is hard coded in the provided prebuilt binary and source code. To get this working for IWR6843AOP I would suggest finding a configuration that works with the standard OOB aka non-hcc for AOP. Then I would look at the delta of the parameter values that are specified in the config file and what is hard-coded in the HCC example and change accordingly.

    Best regards,

    Connor Desmond

  • 0 in reply to Connor Desmond
    Intellectual 360 points

    Hi Connor,

    I'm trying to follow the steps on the readme file in the zip folder.

    Example of hard-coded sensor config for 14xx using mmWave SDK 1.2 mmw demo

    Steps to update mmWave SDK 1.2 14xx demo to use example hard-coded config:
    1. Rename/backup existing cli.c source file in mmwave_sdk_01_02_00_05\packages\ti\utils\cli\src directory
    2. Place new cli.c file in directory
    3. Re-build cli library using gmake as described in mmWave SDK user guide
    a. Make sure to update setenv.bat with correct device (i.e. iwr14xx) before executing it
    b. Make sure to run 'gmake clean' and then 'gmake all' in the mmwave_sdk_01_02_00_05\packages\ti\utils\cli directory
    4. Re-build 14xx mmw project by right-clicking on project in CCS and
    performing "Re-build" as described in the user guide on the TI Resource
    Explorer

    NOTE: If replacing/updating the example sensor config given in the cli.c file,
    make sure to use a config that was generated for the desired device and mmWave
    SDK version.

    I backed up the cli file from the mmwave_sdk_01_02_00_05\packages\ti\utils\cli\src directory and replaced the new cli.c file in the directory and now I locally built it. The new cli.c file is attached. /cfs-file/__key/communityserver-discussions-components-files/1023/2185.cli.c. 

    But I have a compilation error and I see it is something to do with with linker stage or binary file error. How can I fix it?

    Regards,

    Divya Teja Settimali

  • 0 in reply to Divya Teja Settimali
    TI__Expert 7510 points

    Divya:

    We have a working HCC binary and provided source code. I would suggest understanding how that works as compared to OOB with out HCC. Once you understand the difference you will hopefully have enough information to modify area scanner accordingly. The post that you shared is 3 years old, as well as it being for an SDK architecture which is not being supported on IWR6843 devices.

    Best regards,

    Connor Desmond

  • 0 in reply to Connor Desmond
    Intellectual 360 points

    Hi Connor,

    The cli.c that I mentioned earlier is working for the Hard-coded ISK. The link I provided might be 3 years old but this one is 4 months IWR6843AOPEVM: How to realize hard-corded demo with IWR6843AOP(ES2.0) without *.cfg - Sensors forum - Sensors - TI E2E support forums and I gave the cfg commands as an array of strings and locally rebuilt the library as mentioned in this and it is working on ISK. I wanted to clarify about the delta parameters that you mentioned earlier. What did you mean by delta parameters? I would wait to hear from you because I'm trying to hard code the cfg on AOP now.

    Regards,

    Divya Teja Settimali

  • 0 in reply to Divya Teja Settimali
    TI__Expert 7510 points

    Divya:

    What I mean by "delta parameters" is that we have our default OOB which has to be sent a .cfg file to configure this. Then you have HCC OOB which is the same except the .cfg file information is hard coded in the source code. What I am asking you to do is understand the difference in between these two implementations such that you can take Area Scanner, or any lab in general, and do a HCC implementation on your own. Make sure that you have a .cfg file that works on AOP before taking that information to a HCC implementation.

    Best regards,

    Connor Desmond