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

CCS / AWR1443：AWR443 report errors：mmWave Open failed -203554190

user6517964
Prodigy 30 points

Part Number: AWR1443
Other Parts Discussed in Thread: IWR1443

Tool/software: Code Composer Studio

hello dear  engineer：

    I use the AWR1443 EVM to run vital_signs Demo and high accuracy demo in ccs8.0

    my sdk version is 2.1.0.04

    my Industrial toolbox version is 4.0.0.

    when I debug the demo, there a a error :

[Cortex_R4_0] Debug: Launched the Initialization Task
Debug: HWA has been initialized
Debug: EDMA instance 0 has been initialized
Debug: UART Instance @0800aca0 has been opened successfully
Debug: UART Instance @0800acac has been opened successfully
Debug: mmWave Control Initialization was successful
Debug: mmWave Control Synchronization was successful
Debug: HWA Instance @08000f18 has been opened successfully
Debug: ADCBUF Instance(0) @0800ad88 has been opened successfully
Debug: CLI is operational
Error: mmWave Open failed -203554190

Thanks and regards!!!

  • 0
    TI__Mastermind 30405 points

    Hi,

    1. Could you confirm that you are using an ES3.0 IWR1443 device as required by this demo? You can check the version of your mmWave chip using the instructions provided here.

    2. Are you getting these errors with the pre-built binaries and chirp configuration or did you make any changes to the code and/or chirp configuration?

    Regards

    -Nitin

  • 0 in reply to Nitin Sakhuja
    Prodigy 30 points

    Hi，

       I checked my  device and made sure it is ES3.0 AWR1443 device .

       I read the  vitalSignsLab_xwr1443_QuickStartGuide and debug VitaSign_lab according to this file. I did not change the code and/or Chirp Configuration. when I fiash pre-built binaries in device,the gui  interface have no any information too.

    Thanks and Regards!

    -yunfei

  • 0 in reply to user6517964
    TI__Mastermind 30405 points

    Hi Yunfei,

    Just noticed that you are using an older version of Industrial Toolbox. Is there a particular reason for this? Please try the Vital signs demo from the latest Industrial Toolbox (4.5.1) on your EVM and let us know your observations.

    C:\ti\mmwave_industrial_toolbox_4_5_1\labs\vital_signs\14xx_vital_signs

    Thanks

    -Nitin

  • 0 in reply to Nitin Sakhuja
    Prodigy 30 points

    Hi，Nitin:

    I downloaded the Industrial Toolbox (4.5.1) and debugged the demo according to your suggestion, but I encountered this problem (I still have this problem when I debug after power off.)

    "../xwr1443_r4f.cmd", line 18: error #10263: VECTORS memory range has already been specified
    "../xwr1443_r4f.cmd", line 18: error #10264: VECTORS memory range overlaps existing memory range VECTORS
    "../xwr1443_r4f.cmd", line 19: error #10263: PROG_RAM memory range has already been specified
    "../xwr1443_r4f.cmd", line 19: error #10264: PROG_RAM memory range overlaps existing memory range PROG_RAM
    "../xwr1443_r4f.cmd", line 20: error #10263: DATA_RAM memory range has already been specified
    "../xwr1443_r4f.cmd", line 20: error #10264: DATA_RAM memory range overlaps existing memory range DATA_RAM
    "../xwr1443_r4f.cmd", line 21: error #10263: L3_RAM memory range has already been specified
    "../xwr1443_r4f.cmd", line 21: error #10264: L3_RAM memory range overlaps existing memory range L3_RAM
    "../xwr1443_r4f.cmd", line 22: error #10263: HWA_RAM memory range has already been specified
    "../xwr1443_r4f.cmd", line 22: error #10264: HWA_RAM memory range overlaps existing memory range HWA_RAM
    warning #10247-D: creating output section ".hwaBufs" without a SECTIONS specification
    warning #10247-D: creating output section ".l3ram" without a SECTIONS specification
    warning #10247-D: creating output section "systemHeap" without a SECTIONS specification
    error #10010: errors encountered during linking; "xwr14xx_vitalSigns_lab_mss.xer4f" not built

    Thanks!

    -yunfei

  • 0 in reply to user6517964
    TI__Mastermind 30405 points

    Hi Yunfei,

    I am not sure I understand the problem shown in your last post. Are you trying to debug the demo or compile the demo? You should be able to debug the demo in CCS using the pre-built xwr14xx_vitalSigns_lab_mss.xer4f CCS binary provided in the precompiled binary folder. Did you try that to see whether it runs in CCS or gives the same error as mentioned in your original post?

    On the build errors shown above, did you change anything in the project? I tried building the 14xx vital signs project from toolbox 4.5.1 and don't see any problems as shown in the attached log.

    /cfs-file/__key/communityserver-discussions-components-files/81/VitalSigns_5F00_build.txt

    Regards

    -Nitin