• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 338 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:

IWRL6432BOOST: Error on Resume during CCS Debug

IWRL6432BOOST: Can't debug AWRL6432BOOT board in CCS12.

bo.fang
Prodigy 50 points
Part Number: IWRL6432BOOST
Other Parts Discussed in Thread: AWRL6432, IWRL6432

Hi Ti-Expert,

I got some issue when I want to debug the demo in CCS12.5.0, please help me to solve the issue, thanks. This is the test condition showing below.

Test Condition:

Tool:                                  Code Composer Studio 12.5.0

SDK version:                     MMWAVE_L_SDK_05_03_02_00

Guide version:                   8132.xWRL6432_APL_CCS_debug_guide.pdf

Board configuration:          debug mode(S1.1=ON, S1.2=ON, else S1.X=OFF) (All S4.X=OFF) like picture showing in link

Demo name:                      mmwave_demo_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang (Import from Resource Explorer)

I can see below message showing in console.

I have click the reset CPU button when I connect the "Texas Instruments XDS110 USB Debug Probe_0/Cortex_M4_0". 

There has no error but didn't print "CLI is Operational", and the visualizer can't send the cfg successful.

Could you check it?

  • 0
    TI__Expert 8802 points

    Hi,

    Do you know which ES version of silicon you are using?

    Can you attempt to send the .cfg over a program such as tera term to see what the output from the device is? When it says CLI is operational, that means it is ready to receive the .cfg file, so likely it has a problem with the configuration. Can you also share the.cfg file you are using?

    Regards,

    Tim

  • 0 in reply to Tim Henderson
    Prodigy 50 points

    Hi Tim, 

    1. Sorry I didn't get the ES version meaning, you mean the information about the demo board? you can refer to follow picture to get more details.

    2. I have attempted to send the .cfg file by tera term, but there has no any output from device. 

    3. The .cfg file location is "C:\ti\MMWAVE_L_SDK_05_03_02_00\examples\mmw_demo\motion_and_presence_detection\profiles\xwrL64xx-evm\PresenceDetect.cfg", and I also try to send "examples\mmw_demo\mmwave_demo\profiles\xwrL64xx-evm\parking_5m.cfg", It is the same result.

    Best regards,

    Bo

  • 0 in reply to bo.fang
    Prodigy 50 points

    Hi Tim,

    There has a good news ,when I change the "Target Configurations" with the same version "AWRL6432" showing in below Point1, The serial has some output showing in below picture1. may the EVM start to receive serial data. but how to make serial get the correct CLI command? Can you help me.

                                 picture1

    1. I load the demo "mmwave_demo_xwrL64xx-evm_m4fss0-0_freertos_ti-arm-clang" from Resource Explorer. but It confuse me, the "Board or Device" configure in "Target Configurations" is "IWRL6432", but I created configuration is AWRL6432 in "User Defined", I am not sure whether it is normal. showing in below picture.

                        picture2

    Best regards,

    Bo

  • +1 in reply to bo.fang
    TI__Expert 8802 points

    Hi Bo,

    Can you please try changing setting in tera term to have a 1msec/char delay when sending data? Teraterm sends the data too fast otherwise.

    Please make sure if you have the mmwave_demo flashed you use the parking_5m.cfg as you mentioned in your previous post. IWRL vs AWRL shouldnt matter in the target configuration.

    To check device version, can you please connect to the core in CCS, open memory browser, and check address 0x5A020038? Please report back the value there.

  • 0 in reply to Tim Henderson
    Prodigy 50 points

    Hi Tim,

      Below picture is the content of memory  0x5A020038. and I have double check with my colleague, may the board is ES1.

      Thank you very much. It works when I modify the setting according you said. I can debug my demo now.

    Best Regards,

    Bo