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.

CCS/AWR1843: AWR1843

Part Number: AWR1843
Other Parts Discussed in Thread: AWR1642,

Tool/software: Code Composer Studio

Hi, 

I would like to devolope a nonOs application for the awr1843. On the project explorer i saw there a starting project developed on sdk 2.0.0 on the awr1642. 

Is there an equal version of the nonOs mmw demo for sdk 3.0.0.4? Since the 1642 project is not compatible with the sdk 3.0 version? 

thank you in advance,

Mattia

  • Yes, your observations are correct.

    What I recommend is that you start by porting the starting project from sdk 2.0 to skd 3.0.

    There are a few changes in the APIs but nothing major.

    In order to do that you would need to 

    Step1 - Update the projectspecs in "labs\lab0006_nonos_oob_16xx\srcmmwNonOS_dss.projectspec" and "labs\lab0006_nonos_oob_16xx\srcmmwNonOS_mss.projectspec". The tools version should be updates with the versions included in the SDK version you would like to update to. You can look at an example for one of the labs built with SDK 3.x such as "labs\lab0011_mrr_beamsteering"

    Step2 - Rebuild the project with CCS with no optimization level for mss_main.c

    Step3 - Run with CCS the MSS binary. Stop the execution where the code hangs. Compare that section of the code with  the similar section in "labs\lab0011_mrr_beamsteering"

    Step4 - Make the updates and re-build the code and run it again.

    Step5- Iterate throughStep3-4 until you are able to run the MSS code with no problems.

    Step6 - Build and run the DSS code.

    thank you

    Cesar

  • The problem is all those example for awr1843 use the TI-RTOS and therefore the code both for the DSS and MSS is significantly different.

    I am looking for an nonOS application for the awr1843. Also changing from SDK 2.0 to 3.0 some file and typedefinition are missing since folder and file are organized in a different way.

    Mattia

  • Hi,
    The code that initializes the firmware is TI RTOS agnostic. From that perspective you should have no problems.
     
    Regarding other packages, I checked the nonOS projectspec and most of the paths are still valid.
     
    Please start making the changes and we will assist you
     
    Thank you
    Cesar