• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 3 answers
  • Subscribers 32 subscribers
  • Views 1909 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/AWR1642BOOST: Help loading the xwr16xx_mmw_demo_dss.xe674 and xwr16xx_mmw_demo_mss.xer4f

Jeffrey Mao
Prodigy 220 points

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: MMWAVE-SDK, , SYSBIOS, AWR1642

Tool/software: Code Composer Studio

Hi,


I am new to this, but I am having trouble loading the following files through Code Composer's Studio. After creating the Target Configuration file. The ccxml file isn't in a Target Configuration list, and when I right click it I can't find the option to Launch Selected Configuration.

Is this document up to date? I had to go back to mmWAVE SDK 1.1 in order to run this capture demo.


4. 4. 3. 2. Connecting to xWR14xx/xWR16xx EVM using CCXML in CCS
Follow steps in above section to create a ccxml file. Once created, the target configuration file will be seen in the "Target Configurations" list
and you can launch the target by selecting it and with right-click select the "Launch Selected Configuration" option. This will launch the target
and the Debug window will show all the cores present on the device. You can connect to the target with right-click and doing "Connect
Target".

Best Regards,

Jeff

  • 0
    TI__Guru 50240 points
    Hi Jeffrey,

    If you are trying to run the Capture demo then you'll need to use the mmWave-SDK 1.1 although if you are trying to run the standard mmWave Visualizer then there is a step-by-step guide available here: dev.ti.com/.../

    If you have ES2.0 AWR1642BOOST then you'll need to use the mmWave-SDK 2.0, otherwise for ES1.0 use the 1.2.


    Cheers,
    Akash
  • 0 in reply to Akash Gondalia
    Prodigy 220 points
    Hi Akash,

    Thanks for the help, I reached slide 24 loading the .xer4f into the Cortex_R4_0, but am getting some errors.

    Exception occurred in ThreadType_Main.
    Main handle: 0x0.
    Main stack base: 0x800b540.
    Main stack size: 0x1000.
    R0 = 0x00000000 R8 = 0x00008026
    R1 = 0x00000090 R9 = 0x00012d0f
    R2 = 0x00000000 R10 = 0x00010358
    R3 = 0x03410010 R11 = 0x000000d1
    R4 = 0x000098e4 R12 = 0x0800b2dc
    R5 = 0x0800b52a SP(R13) = 0x080097a0
    R6 = 0x00000000 LR(R14) = 0x00012d0f
    R7 = 0x00000001 PC(R15) = 0x00010358
    PSR = 0x400c019f
    DFSR = 0x00000000 IFSR = 0x00000000
    DFAR = 0x00000000 IFAR = 0x00000000
    ti.sysbios.family.arm.exc.Exception: line 209: E_undefinedInstruction: pc = 0x00010358, lr = 0x00012d0f.
    xdc.runtime.Error.raise: terminating execution


    Do you have any idea what this about?

    Thanks,

    Jeff
  • 0 in reply to Jeffrey Mao
    TI__Guru 50240 points
    Hi Jeff,

    It is difficult to tell without more information.

    Can you confirm you've flashed the device with the ccsdebug.bin binary?

    Are you using the correct SDK version? 1.2 for ES1.0 silicon, 2.0 for ES2.0 Silicon.

    Do you have the correct version of both SYS/BIOS and XDC selected? 6.53.02.00 and 3.50.04.43 respectively.


    Cheers,
    Akash
  • 0 in reply to Akash Gondalia
    Prodigy 220 points

    Hi Akash,

    I am using the prebuilt capture binaries and .xe674 .xer4f files that come with the mmWAVE 1.1 SDK, so I don't think the above is relevant.

    Best Regards,

    Jeff

  • 0 in reply to Jeffrey Mao
    TI__Guru 50240 points
    Hi Jeff,

    Can you confirm you've flashed the device with the ccsdebug.bin binary?


    Cheers,
    Akash
  • 0 in reply to Akash Gondalia
    Prodigy 220 points
    Hi Akash,

    Is the ccsdebug.bin binary needed for running the capture demo? I flashed in the capture_demo.bin instead.

    When I flash just the ccsdebug.bin binary I am not allowed to modify the config file from the command line.

    Thanks,

    Jeff
  • 0 in reply to Jeffrey Mao
    Prodigy 220 points
    Hi Akash,

    I flashed in the ccsdebug.bin alone, and was able to successfully load the other 2 files into AWR1642 boost, but I am currently unable to get modify the config file in Putty or in the mmWAVE demo app? Is this suppose to be something else that I need to add in the flashing process.
    Thanks,

    Jeff
  • 0 in reply to Jeffrey Mao
    TI__Guru 50240 points
    Hi Jeff,

    The .xe674 and .xer4f files that you've referenced are for running the mmWave Demo Visualizer which is available here: dev.ti.com/.../


    Cheers,
    Akash
  • 0 in reply to Akash Gondalia
    Prodigy 220 points
    Hi Akash,

    So why doesn't the demo Visualizer work when I flash in all the above files along with the ccsdebug.bin? Is there something else I am missing? The mmWave demo connects, but doesn't' let me send any configuration data to the set-up

    Thanks,

    Jeff
  • 0 in reply to Jeffrey Mao
    TI__Guru 50240 points
    Hi Jeffrey,

    The ccsdebug.bin is used to enable full debug functionality. Another debug method could be to flash the standard mmWave binary (not ccsdebug.bin) and then load the corresponding .xer4f as a symbol but we still recommend just using the ccsdebug.bin instead.


    Cheers,
    Akash