• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 7 replies
  • Subscribers 32 subscribers
  • Views 515 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.

IWR1843BOOST: Short Range Radar demo dss migration to IWR1843

Javier Fernandez
Prodigy 152 points
Part Number: IWR1843BOOST
Other Parts Discussed in Thread: IWR1843, MATHLIB

Hi everyone,

We want to migrate the Short Range Radar example given on the Industrial toolbox to IWR1843 device. The current environment that we have is:

  • dsplib c64x+ 3.4.0.0
  • Mathlib c674x 3.1.2.1
  • Sys/Bios 6.73.1.01
  • mmWave SDK 3.5.0.04
  • Automotive toolbox 3.5.0
  • Industiral toolbox 3.5.0

We have started migrating the DSS just updating any reference given on the Project properties menu from 16xx to 18xx, changing the variant to IWR1843, predefined symbols, linker, ... we based on Medium Range Radar example to change everything accordingly to the new device. We have also copy the "dss_mrr_linker.cmd" to "dss_srr_linker.cmd" (You can find attached). However, it throws the following error:

I think that it is something related to L3RAM size, because if I change this size:

to just something really small:

It compiles.

Here some extra information:

Many thanks for the support.

Javier

  • 0
    Prodigy 152 points

    Hi everyone,

    I want to update my progress because I think that I found the main error, however continue without working well.

    I forgot to migrate the "c674x_linker.cmd" from mrrdemo_18xx_dss to srrdemo16xx_dss. Now I can keep the L3_RAM_SIZE as in the original example:

    However, as I said before the example is not working, when I open the "srr_visualization.exe" I do not see any data arriving. do I miss something more in the migration?

    Also I continue experiencing the following warnings during the compilation:

    srrdemo_16xx_dss (I did not change the output name yet, but it is for 18xx)

    srrdemo_16xx_mss (I did not change the output name yet, but it is for 18xx)

    Thanks for the support,

    Javier

  • 0 in reply to Javier Fernandez
    TI__Mastermind 23725 points

    Hello

    Based on the lab/demo referenced, can you please help us clarify which toolbox  are you using as  Short Range Radar (SRR) demo is release Automotive toolbox.

    We have sent you additional questions  which will help us put you in touch with the right experts. Please respond to those on private messages.

    Thank you,

    Vaibhav

    For reference:

    Industrial Toolbox : Labs

    Automotive version  Labs

  • 0 in reply to Vaibhav Mahimkar
    Prodigy 152 points

    Hi Vaihab,

    We are using Automotive toolbox 3.6.0 and Industrial Toolbox 4.10.1.

    I was able to migrate srrdemo_16xx_dss to 18xx device. But not in the case of ssrdemo_16xx_mss. When I run the debugger I see the following error:

    If I keep the ssrdemo_16xx_mss example as the original one, it works.

    The changes that I am doing in the MSS are the following:

    Also, I do not see any compiling warnings.

    Any ideas? do you think that I missing something?

    Thank you very much,

    Javier

  • 0 in reply to Javier Fernandez
    TI__Genius 17265 points

    Javier,

    Thanks for the detailed information here. I see that an assertion on line 186 of Mss_main failed, could you check and share what assertion is there?

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 152 points

    Hi Alec,

    This is the assetion wha I have on that line:

    The code of the example is completely the same as srrdemo_16xx_mss. I have only changed every reference to XRW16XX to XWR18XX:

    Thank you very much,

    Javier

  • 0 in reply to Javier Fernandez
    TI__Genius 17265 points

    Javier,

    I would recommend digging a bit deeper into the chirpInt there. It's possible that there is a processing hiccup somewhere during startup due to the differing number of antennas between the two devices. I would recommend that you take a look for what triggers the update of chirpInt and if it could be affected by this difference.

    Best Regards,
    Alec

  • 0
    Prodigy 152 points

    Hi everyone,

    Finally I found the source of the problem. I am going to explain it just if anyone wants to migrate this example or any other. 

    First of all, all the changes that I mentioned before were correct. However, it was missing an important one. When it is imported an example using the Resource Explorer, among other things, it is created a file called ".ccsproject" which has some information for CCS about the configuration of the project.

    One of the properties which is configured is the "origin". This field takes a properties file from the toolbox which also has many configuration properties about the current project. This properties are also configured into a file called ".cproject" therefor it is kind of duplication or extension, not sure.... maybe the "projectspec" is only used during the importation... I do not know, maybe one of the TI gurus can shed further light to this topic and explain how works the process.

    Any way, if you are interested in migrate a project, you should also take care about "*.projectspec" file, not only the CCS configuration files.

    If anyone needs help, just text me and I will send you the sources.

    Best regards,

    Javier