• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 470 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.

Original question:

IWR1443BOOST: How to add ti.platforms.cortexR path to xdctools?

AWR1443BOOST: Unable to build CSI-Stream Demo

Michele Marconi
Intellectual 385 points
Part Number: AWR1443BOOST
Other Parts Discussed in Thread: MATHLIB, AWR1443

Hello,

I am trying to build CSI Stream demo included in SDK 3.03.01.

Our intent, as mentioned in previous post, is the modify it to allow transmission over LVDS lanes (AWR does not have CSI2).

I cannot get to the end of the building process.

I am going to link a few components to try and clarify my current situation.

  1. MY ERROR LOG FROM BUILDING THE FILE

**** Build of configuration Debug for project RawData ****

"C:\\ti\\ccs901\\ccs\\utils\\bin\\gmake" -k -j 8 all -O
 
Building file: "../xwr14xx/mss.cfg"
Invoking: XDCtools
"C:/ti/xdctools_3_23_01_43/xs" --xdcpath= xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.R4F -p ti.platforms.cortexR:AWR14XX -r debug -c "C:/ti/ccs901/ccs/tools/compiler/ti-cgt-arm_18.12.1.LTS" "../xwr14xx/mss.cfg"
xwr14xx/subdir_rules.mk:19: recipe for target 'build-1042546689-inproc' failed
js: "C:/ti/xdctools_3_23_01_43/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: Error: Can't find platform package ti.platforms.cortexR
gmake[1]: *** [build-1042546689-inproc] Error 1
gmake: *** [build-1042546689] Error 2
xwr14xx/subdir_rules.mk:16: recipe for target 'build-1042546689' failed
gmake: Target 'all' not remade because of errors.

**** Build Finished ****

2. MY SETENV.BAT

@REM ###############################################################################
@REM #
@REM # Set up tools and build environment variables for mmwave sdk
@REM #
@REM ###############################################################################

@REM ###############################################################################
@REM # Build variables (to be modified based on build need)
@REM ###############################################################################

@REM Select your device. Options (case sensitive) are: awr14xx, iwr14xx, awr16xx, iwr16xx, awr18xx, iwr18xx, iwr68xx
set MMWAVE_SDK_DEVICE=awr14xx

@REM If download via CCS is needed, set below define to yes else no
@REM   yes: Out file created can be loaded using CCS.
@REM        Binary file created can be used to flash
@REM   no:  Out file created cannot be loaded using CCS.
@REM        Binary file created can be used to flash
@REM        (additional features: write-protect of TCMA, etc)
set DOWNLOAD_FROM_CCS=yes

@REM If using a secure device this variable needs to be updated with the path to mmwave_secdev_<ver> folder
set MMWAVE_SECDEV_INSTALL_PATH=

@REM If using a secure device, this variable needs to be updated with the path to hsimage.cfg file that
@REM has customer specific certificate/key information. A sample hsimage.cfg file is in the secdev package
set MMWAVE_SECDEV_HSIMAGE_CFG=%MMWAVE_SECDEV_INSTALL_PATH%/hs_image_creator/hsimage.cfg

@REM ###############################################################################
@REM # Customer installed tools variables (to be modified based on the installation)
@REM ###############################################################################


@REM ###############################################################################
@REM # TI tools variables (no changes needed below this line if default mmwave sdk
@REM # installation options are used)
@REM ###############################################################################
 
set MMWAVE_SDK_TOOLS_INSTALL_PATH=C:/ti
 
@REM Common settings for all platforms
@REM Path to <mmwave_sdk installation path>/packages folder
set MMWAVE_SDK_INSTALL_PATH=%MMWAVE_SDK_TOOLS_INSTALL_PATH%/mmwave_sdk_03_01_01_02/packages
@REM TI ARM compiler
set R4F_CODEGEN_INSTALL_PATH=%MMWAVE_SDK_TOOLS_INSTALL_PATH%/ti-cgt-arm_16.9.6.LTS
@REM TI XDC TOOLS
set XDC_INSTALL_PATH=%MMWAVE_SDK_TOOLS_INSTALL_PATH%/xdctools_3_23_01_43
@REM TI BIOS
set BIOS_INSTALL_PATH=%MMWAVE_SDK_TOOLS_INSTALL_PATH%/bios_6_73_01_01/packages

@REM awr14xx/iwr14xx radarss firmware
set XWR14XX_RADARSS_IMAGE_BIN=%MMWAVE_SDK_INSTALL_PATH%/../firmware/radarss/xwr12xx_xwr14xx_radarss_rprc.bin
@REM awr16xx/iwr16xx radarss firmware
set XWR16XX_RADARSS_IMAGE_BIN=%MMWAVE_SDK_INSTALL_PATH%/../firmware/radarss/xwr16xx_radarss_rprc.bin
@REM awr18xx/iwr18xx radarss firmware
set XWR18XX_RADARSS_IMAGE_BIN=%MMWAVE_SDK_INSTALL_PATH%/../firmware/radarss/xwr18xx_radarss_rprc.bin
@REM iwr68xx radarss firmware
set XWR68XX_RADARSS_IMAGE_BIN=%MMWAVE_SDK_INSTALL_PATH%/../firmware/radarss/iwr6xxx_radarss_rprc.bin
 
@REM Following only needed for devices with DSP
@REM TI DSP compiler
set C674_CODEGEN_INSTALL_PATH=%MMWAVE_SDK_TOOLS_INSTALL_PATH%/ti-cgt-c6000_8.1.3
@REM DSPlib
set C64Px_DSPLIB_INSTALL_PATH=%MMWAVE_SDK_TOOLS_INSTALL_PATH%/dsplib_c64Px_3_4_0_0
@REM DSPlib C674
set C674x_DSPLIB_INSTALL_PATH=%MMWAVE_SDK_TOOLS_INSTALL_PATH%/dsplib_c674x_3_4_0_0
@REM MATHlib
set C674x_MATHLIB_INSTALL_PATH=%MMWAVE_SDK_TOOLS_INSTALL_PATH%/mathlib_c674x_3_1_2_1


@REM Call script to check env variables and set paths
call checkenv.bat

@REM Check error code
IF %ERRORLEVEL% NEQ 0 (
  REM ERROR: Failure in checkenv.bat !!!
  REM Return error
  EXIT /B 1
)

EXIT /B 0

3. A FEW IMAGES FROM MY PATH AND CCS



  • 0
    TI__Mastermind 24955 points

    Michele,

    You will need to use an SDK that includes firmware support for AWR1443. It looks like the version you are attempting to use is mmWave SDK v3.1.1.2. This particular release does not include a BSS image for AWR1443. Please migrate to using at least mmWave SDK v3.2.0.4 or later and these releases include a BSS image for AWR1443.

    Additionally, if you are using the setenv.bat file to set your build environment, then you should rebuild your project in the command line as well.

    However, what I would really recommend you do is use mmWave SDK v2.1 which you can download here: http://software-dl.ti.com/ra-processors/esd/MMWAVE-SDK/lts-latest/index_FDS.html

    This release includes an Out-of-Box demo for AWR1443 whereas later versions do not include it. I would recommend proceeding with your project on this release of the SDK if you plan to continue your development on AWR1443.

    Regards,

    Kyle

  • 0 in reply to Kyle Cousino
    Intellectual 385 points

    The first kind solution you have suggested seems unclear to me, so I tried to follow the second recommendation.

    If you think that would fix my issue, could you maybe elaborate a little more in-depth? I have zero previous experience with code composer studio building environment.

    I tried setting up the environmental variables inside code composer studio and they do seem to work.

    I followed the setenv.bat list of commands, but I set them up manually one by one. They seem to work fine, letting the project reach the same step it did before.

    I then selected mmwave sdk 2.1 from the list of currently applied packages in the same location as the 3rd image.

    This is the error I am getting:


    **** Build of configuration Debug for project RawData ****
    "C:\\ti\\ccs901\\ccs\\utils\\bin\\gmake" -k -j 8 all -O
     
    Building file: "../xwr14xx/mss.cfg"
    Invoking: XDCtools
    "C:/ti/xdctools_3_23_01_43/xs" --xdcpath="C:/ti/bios_6_73_01_01/packages;" xdc.tools.configuro -o configPkg -t ti.targets.arm.elf.R4F -p ti.platforms.cortexR:AWR14XX -r debug -c "C:/ti/ccs901/ccs/tools/compiler/ti-cgt-arm_18.12.1.LTS" "../xwr14xx/mss.cfg"
    making package.mak (because of package.bld) ...
    making package.mak (because of package.bld) ...
    xwr14xx/subdir_rules.mk:19: recipe for target 'build-1042546689-inproc' failed
    "ti/targets/ITarget.xdc", line 22:  can't resolve name (xdc.bld.ITarget3)
    js: "./config.bld", line 3: xdc.services.global.XDCException: xdc.PACKAGE_REPARSE_FAILED: C:\ti\bios_6_73_01_01\packages\ti\targets\arm\elf\package.xdc found along the package path, but its package files are incompatible with the current tools and could not be regenerated (InternalError: parser failed).  The package 'ti.targets.arm.elf' must be rebuilt with the current tools.
    "ti/targets/ITarget.xdc", line 22:  can't resolve name (xdc.bld.ITarget3)
    js: "./config.bld", line 3: xdc.services.global.XDCException: xdc.PACKAGE_REPARSE_FAILED: C:\ti\bios_6_73_01_01\packages\ti\targets\arm\elf\package.xdc found along the package path, but its package files are incompatible with the current tools and could not be regenerated (InternalError: parser failed).  The package 'ti.targets.arm.elf' must be rebuilt with the current tools.
    gmake.exe: *** No rule to make target `.configuro'.  Stop.
    js: "C:/ti/xdctools_3_23_01_43/packages/xdc/tools/Cmdr.xs", line 51: Error: xdc.tools.configuro: configuration failed due to earlier errors (status = 2); 'linker.cmd' deleted.
    gmake[1]: *** [build-1042546689-inproc] Error 1
    gmake: *** [build-1042546689] Error 2
    xwr14xx/subdir_rules.mk:16: recipe for target 'build-1042546689' failed
    gmake: Target 'all' not remade because of errors.
    **** Build Finished ****
  • 0 in reply to Michele Marconi
    TI__Mastermind 24955 points

    Michele,

    Based on the errors that you are encountering, I would recommend that you rebuild the demo from the command line and not in Code Composer Studio.

    You should make any changes that you would like directly to the source files in the SDK folder.

    So, for clarification, this would mean working entirely within this directory: C:\ti\mmwave_sdk_02_01_00_04\packages\ti\drivers\test\csi_stream

    Use Notepad++ or your editor of choice to make any changes to the files that are you to make this project.

    Once you have made your changes, complete the following steps:

    • Open the command line,
    • Invoke the setenv.bat file
    • cd to the directory I listed above C:\ti\mmwave_sdk_02_01_00_04\packages\ti\drivers\test\csi_stream
    • Execute the following commands:
      • gmake clean
      • gmake all

    This will build the MSS executable found in the folder: C:\ti\mmwave_sdk_02_01_00_04\packages\ti\drivers\test\csi_stream\xwr14xx

    • xwr14xx_csi_stream_mss.xer4f

    You can then flash the CCS debug image to your AWR1443 device.

    This image is found in this folder: C:\ti\mmwave_sdk_02_01_00_04\packages\ti\utils\ccsdebug

    You will flash the xwr14xx_ccsdebug.bin image to your device.

    Now you can open CCS, launch a target configuration for AWR1443, and then load the MSS executable that was generated in the earlier step.

    The mmWave SDK User Guide provides for detailed instructions on all of the steps that I have listed. You should refer there for more information.

    The User Guide is found here: C:\ti\mmwave_sdk_02_01_00_04\docs

    Regards,
    Kyle