• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 29 subscribers
  • Views 486 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.

AWR1642BOOST-ODS: Question about Compilation in Code Composer Studio for the DFTP Test example

Hector Andres Gonzalez Diaz
Intellectual 270 points
Part Number: AWR1642BOOST-ODS
Other Parts Discussed in Thread: UNIFLASH, DCA1000EVM

Dear Texas Instruments Representatives

I am trying to create a Code Composer Studio (CCSV10) project using the mmWave SDK 3_05_00_04 based on the sample test code given for the mmwavelink new reconfiguration interface in "C:\ti\mmwave_sdk_03_05_00_04\packages\ti\control\mmwavelink\test\xwr16xx". I have created a new project, imported the files in the CCS IDE and added the corresponding Compiler and Linker flags in the project:

Compiler Flags:

-mv6740 --abi=eabi -O3 --include_path="C:/ti/mmwave_sdk_03_05_00_04/packages" --include_path="C:/ti/mmwave_sdk_03_05_00_04/packages/ti/drivers/test/common" --include_path="C:/ti/mmwave_sdk_03_05_00_04/packages/ti/drivers/adcbuf" --include_path="C:/ti/mmwave_sdk_03_05_00_04/packages/ti/common" --include_path="C:/ti/mmwave_sdk_03_05_00_04" --include_path="C:/Users/hagon/workspace_v10/standalonedfp_dss3" --include_path="C:/ti/ccs1011/ccs/tools/compiler/ti-cgt-c6000_8.3.6/include" --define=SOC_XWR16XX --define=SUBSYS_DSS --define=DOWNLOAD_FROM_CCS --define=DebugP_ASSERT_ENABLED -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on

Linker Flags:

-mv6740 --abi=eabi -O3 --define=SOC_XWR16XX --define=SUBSYS_DSS --define=DOWNLOAD_FROM_CCS --define=DebugP_ASSERT_ENABLED -g --gcc --diag_warning=225 --diag_wrap=off --display_error_number --gen_func_subsections=on -z -m"standalonedfp_dss3.map" --heap_size=0x800 --stack_size=0x800 -i"C:/ti/ccs1011/ccs/tools/compiler/ti-cgt-c6000_8.3.6/lib" -i"C:/ti/mmwave_sdk_03_05_00_04/packages/ti/control/mmwave/lib" -i"C:/ti/mmwave_sdk_03_05_00_04/packages/ti/control/mmwavelink/lib" -i"C:/ti/mmwave_sdk_03_05_00_04/packages/ti/alg/mmwavelib/lib" -i"C:/ti/mmwave_sdk_03_05_00_04/packages/ti/drivers/crc/lib" -i"C:/ti/mmwave_sdk_03_05_00_04/packages/ti/drivers/mailbox/lib" -i"C:/ti/mmwave_sdk_03_05_00_04/packages/ti/drivers/soc/lib" -i"C:/ti/mmwave_sdk_03_05_00_04/packages/ti/drivers/osal/lib" -i"C:/ti/mmwave_sdk_03_05_00_04/packages/ti/drivers/edma/lib" -i"\"C:/ti/mmwave_sdk_03_05_00_04/packages/ti/drivers/adcbuf/lib\"​" -i"C:/ti/ccs1011/ccs/tools/compiler/ti-cgt-c6000_8.3.6/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="standalonedfp_dss3_linkInfo.xml" --rom_model

I created two projects, one for the DSS and one for the MSS. However, I haven't even managed to compile the DSS project. It seems to finish the initial compilation but it fails during the linking process. It seems the ADCBuf_init library is somehow not seen by the linker. This is the screenshot of the errors after the linker fails:

Could you please give me any suggestion of how to solve these errors or how to use that mmwavelink test sample code?

There was some other similar post having the same errors I'm showing, but the solution reported there has broken links on the System variables that were modified to solve the problem, so I can't know what was the solution: https://e2e.ti.com/support/sensors/f/1023/t/947634?IWR1443-MMWAVE-SDK-DEVICE-cannot-be-resolved-CCS-9- 

  • 0
    TI__Guru*** 147964 points

    Hi,

    As a first step, in order to create a CCS project, we recommend that you create a CCS project spec. We provide CCS project specs with the demos provided in the TI Resource Explorer, Software, mmWave Industrial or Automotive Toolbox.

    You would need to include in the project spec all the files, libraries required.

    The project spec will be imported in CCS and thus create a CCS project.

    Please let us know if you have any questions

    thank you

    Cesar

  • 0 in reply to Cesar
    Intellectual 270 points

    Hello Cesar

    I tried to follow your advice and it seems as if the system now recognizes the missing libraries, but there are multiple file dependencies with other directories in the mmwavelink folder that it becomes difficult and I think pointless to include this in the Code Composer Studio to generate the binaries. 

    Could you please let me know which software or command line was used to generate the binaries in the example I mentioned, which is located in this folder:

    • mmwave_sdk_03_05_00_04/packages/ti/control/mmwavelink

    There is a makefile there but I don't know in which command line interface are you running that. Can you please let me know what should I install to use this makefile: mmwave_sdk_03_05_00_04/packages/ti/control/mmwavelink/makefile

    Also, did you execute that makefile in Linux or Windows?

    Thank you very much for your help.

    Hector G

  • 0
    TI__Guru*** 147964 points
    Hi,
    Yes, please check building instructions in the SDK user guide provided in the docs folder.
     
    It provides instructions to build under windows or linux
     
    Thank you
    Cesar
  • 0 in reply to Cesar
    Intellectual 270 points

    Hello Cesar

    Thanks to your suggestion, I was able to generate the xe674 and xer4f files in Linux without problem. I can now modify the dynamic reconfiguration using that example.

    1. Could you please tell me if the xer4f files are flashed in the same way as the .bin files? Should I also use Uniflash for that? What is the difference between the .bin files and the .xer4f files?
    2. If I would like to get the Raw ADC data during those particular tests generated with the mmwavelink framework, is it possible to configure the DCA1000EVM there without mmwave studio? Do you have any example of that? Is the DCA1000EVM started by default if connected while running the EVM with those xer4f files?

    Thanks for your help.

    Hector G

  • 0 in reply to Hector Andres Gonzalez Diaz
    TI__Guru*** 147964 points

    Hi,

    1) No, the xe674 and xer4f files are not flashed. They are intended to be loaded directly using CCS to the DSP and ARN R4F cores respectively. TI provides the "Image Creator" tool. This tool as you can see in the config spec will run after the DSP and ARM binaries are built to merge the two binaries into a single .bin file. The .bin file is the one that should be flashed.

    2) Yes, this is possible. We provide a tool for that in the TI Resource Explorer

    Open in Chrome dev.ti.com, Launch "Resource Explorer", select "Software" -> "mmwave Sensors" -> Platform Toolbox -> Tools -> Studio-CLI

    This tools enables the mmWave Studio functionality from CLI

    thank you

    Cesar