• State Answer Suggested
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 42 subscribers
  • Views 1991 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC3200R1M2 debugging through LAUNCHXL emulator

user4155764
Prodigy 30 points
Other Parts Discussed in Thread: CC3200, UNIFLASH, ENERGIA

I designed a custom PCB including a CC3200R1M2. The MCU part is a copy of the CC3200 LAUNCHXL reference design.

Now I'm trying to use the launchpad JTAG emulator and UART converter to flash and debug the custom PCB.

Uploading firmwares with Uniflash semms to work fine, but I'm not able to debug the board through JTAG properly.

I'm using the wlan_station example and CCS 6.0.1.0040

I formatted the serial flash and uploaded the service pack 1.0.0.1

is there anything else I have to do with the CC3200R1M2 to make it work like the CC3200 on the launchpad?

If I try to debug the example CCS seems to get connection to the MCU but it never reaches the main() function. Console output is:

Cortex_M4_0: GEL Output:
Memory Map Initialization Complete
Cortex_M4_0: GEL Output:
Target Reset

If I suspend the debugging it hangs always at the same point in dissasembly (0x0000978e):

0000976e:   00020000 ANDEQ           R0, R2, R0
00009772:   00000000 ANDEQ           R0, R0, R0
00009776:   00000000 ANDEQ           R0, R0, R0
0000977a:   703C0000 EORVCS          R0, R12, R0
0000977e:   0006400F ANDEQ           R4, R6, PC
00009782:   000C0000 ANDEQ           R0, R12, R0
00009786:   00000000 ANDEQ           R0, R0, R0
0000978a:   E7FE0000 LDRB            R0, [R14, R0]!
-->0000978e:   E7FEE7FE UDF             #61054
00009792:   E7FEE7FE UDF             #61054
00009796:   2000E7FE STRCSD          R14, [R0], -R14
0000979a:   F44F4770 VST1.16         {D20}, [PC@256], R0
0000979e:   60416180 SUBVS           R6, R1, R0, LSL #3
000097a2:   20008001 ANDCS           R8, R0, R1
000097a6:   B5804770 STRLT           R4, [R0, #1904]
000097aa:   F100460B CPS              
000097ae:   46187180 LDRMI           R7, [R8], -R0, LSL #29

I'm kind of stuck at this point and would appreciate any help on this.

Thanks

  • 0
    TI__Expert 5660 points
    Hi

    Please ensure that your SOP2 jumper is in place while you debug. This will ensure the program in sflash is not automatically loaded for execution. This ensures full control from debugger.

    Thanks and Regards,
    Siddaram
  • 0 in reply to Siddaram Mathapathi
    Prodigy 30 points

    Hi

    I put the SOP2 jumper in place but the problem still persists.

    I found out that debugging is working if I use the energia software framework (also built in CCS 6) but not if I use the SDK examples with simplelink.

    Any other idea?


    Thank you

    David

  • 0 in reply to user4155764
    TI__Expert 5660 points
    Hi David,

    As you mentioned "debugging is working if I use the energia software framework" i am assuming there are no hardware issues.
    Please once review the steps you are following to debug with CCS against the steps listed in our programmers guide section "Development Environment – TI Code Composer Studio"

    Thanks and Regards,
    Siddaram
  • 0 in reply to Siddaram Mathapathi
    TI__Expert 5660 points
    Hi David,

    Did your queries got answered. If yes please press the "Verify Answer" button to close this thread.

    Thanks and Regards,
    Siddaram
  • 0 in reply to Siddaram Mathapathi
    TI__Expert 5660 points
    Hi David,

    I am closing this thread, if the issue still exists please open a new thread and add a link to this one for reference

    Thanks and Regards,
    Siddaram
  • 0 in reply to user4155764
    Intellectual 425 points

    hey David, were you ever able to get your board working with CCS?  I am having a similar issue with the debugger, and wondering if I should try Energia. Thanks!

  • 0 in reply to Siddaram Mathapathi
    Intellectual 255 points

    Hey why are you closing this thread?

    It has not been resolved and I too am having the same problems.

    I have physically swapped cc3200R1 with pre production device between eval board and my own board, and now eval board fails to debug and my board debugs fine. The problem is clearly following the c3200R1. I have asked sooo many times how to set up ccs to support this chip (cc3200R1) and got no response. And yes I have changed the linker cmd file to that of the cc3200R1 with the same failures as before.

    cc3200R1 setup is clearly the problem, not following the guide problems with debugging as I have tested with both eval boards and my own boards, and I can get it too work when a pre production device is used on either board. Please reopen this thread and address directly issues with CC3200R1M1RGCR.

    I am using the latest SDK and service pack, so please explain how it should be setup and this is the crucial part, actually test it your self to verify.

    i.e. put a CC3200R1M1RGCR on an eval board and see if you can get it to debug code.

    Thanks.

  • 0 in reply to kent martin
    Prodigy 30 points

    Hi


    Good to know, that I'm not the only one having this problem. I gave up to get the debugging working with the TI compiler in CCS for CC3200R1M1.

    Instead i set up the energia framework in CCS which uses GNU compiler (v4.7.3 Linaro). This is working on the CC3200R1M1.

    Now we are setting up a hole new build system for the CC3200 sdk and parts of the energia framework. Then we will use eclipse for debuggin using openocd and gdb debugger.

    It would be really helpful if TI would get the sdk examples debugging on the CC3200R1M1!

    Thanks

    David

  • 0 in reply to user4155764
    Intellectual 255 points
    My problem and probably this one relates to the use of the cc3200R1M1 not cc3200R1M2.
    The M1 variant only has 128K RAM where M2 variant has 256K RAM.
    The linker file needs to be changed to "cc3200R1.cmd" and then edited like this
    SRAM_CODE (RWX) : origin = 0x20004000, length = 0xE000
    SRAM_DATA (RWX) : origin = 0x20012000, length = 0xE000
    This will make the RAM line up with the cc3200R1M1.
    Would be nice if TI could change the name of cc3200R1.cmd to cc3200R1M2.cmd
    and add another file cc3200R1M1.cmd so people can choose the right one.

    Happy hunting!
  • 0 in reply to kent martin
    Prodigy 180 points

    Thanks for the tip - it got code loaded but now I'm having issues with the JTAG debugger. It isn't very stable (I broke out the Launchpad's JTAG pins and reset to our custom board).