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.

Using JTAG ICDI on CC3200 Launchpad to debug external board

Other Parts Discussed in Thread: CC3200, CC3200-LAUNCHXL, UNIFLASH, CC3200MOD

What do I need to do to to use the JTAG on the CC3200 launchpad to debug my external board. Is it sufficient to remove the jumpers on SOP?

Thanks for your time.

Regards,

Hemant

  • Hi Hemant,

    As I understand from your post, your requirement is to connect another (external) emulation board to CC3200 Launchpad so that you can debug it from external emulation board not from onboard FTDI.

    If this is the case then you need to remove J8-11 jumpers and connect external board  pins to these points (using wires).

    For JTAG : SOP setting (100 -> SOP2:SOP1:SOP0)

    SWD (2-wire JTAG) setting (001)

    Regards,

    Jitendra

  • Hi Jitendra,

    Thanks for the response. However, my requirement is exactly the opposite. I want to use the onboard debugger to debug my custom designed board. i have been doing that with the LM4F and TM4C123 launchpads.

    Regards,

    Hemant

  • Hi Hemant,

    For this scenario connect J8-J11 (close to FTDI pins) to your dev board. And in this case SOP connection (on CC3200 LP)  will not give any effect to your dev board.

    For more detail please refer CC3200 Launchpad schematic (<CC3200-SDK>\docs\hardware\CC3200-LAUNCHXL_SCH_*.pdf)

    Regards,

    Jitendra

  • Hello,

    I am looking to do the same thing as Hemant; Use the CC3200MODLaunchXL to act as the debugger for my custom board with a CC3200. I am finding UniFlash gives me an error "reading ACK signal failed".

    I have the following connections:
    Removed Jumpers J8-J11 and connected my external board's JTAG lines to FTDI side of these jumpers.
    Removed Jumpers J6-J7 and connected my external board's GPIO1/2 to FTDI side of J7/J6.
    Connected Launchpad's Vcc and Gnd to my external board's Vcc and Gnd (no other power is applied to my board, and 3.3V does show up on the external board)

    Then there's the reset line. From looking at the launchpad schematic, it looks like Vdd_Brd is necessary to be powered on so that translators U11 and U12 (for GPIO1/2) will function. This means that J13 is left in place and the Launchpad's CC3200MOD will be powered. This is fine for JTAG lines and GPIO1/2 as those jumpers have been removed, but the reset line would be in contention. For this reason, I've removed R113 and soldered my external board's reset line to the "SRSTn" line (after the 33 ohm R327).

    Also note as I'm trying to program flash, I have shorted my SOP2 to Vcc and left SOP0/1 as no connect. (None of these lines are brought to launchpad).

    But apparently I'm missing something because I'm still getting this error. I've double checked my design files and my wiring and confirmed connections are as described above. I've tested two boards with the same issue, so I don't believe it's the build (although as there are no exposed leads I cannot really confirm).

    Can you clarify if there are any other modifications I need to make in order to use the CC3200MODLAUNCHXL as my debugger?

    Thank you,
    -Jon
  • Jon-

    I have the UniFlash programmer working just this morning, basically as you describe it.  Differences in my setup:

    I jumper from my custom board's SOP2 pin to the CC3200MODLAUNCHXL's J15 closest to the FTDI side to leverage the launchpad's 2.7k pull-up (vs. tying hard to Vcc).  

    I used the RST pin (fifth down on the right side of the launchpad's expansion headers) instead of soldering to the PCB... I do not think (but I do not know for sure) if this is necessary for UniFlash... I am still trying to get the JTAG interface working too...

    But I can reliably get the UniFlash utility to work if I completely un-power the CC3200MODLAUNCHXL (unplug the USB interface)... then connect my custom board... then plug in the USB interface... but my bed-of-nails for the custom board isn't particularly smart about power/IO sequencing.

    Once I UniFlash the board I pull off the jumper to SOP2 on the launched, press the launchpad's reset button, and the diagnostics start streaming off of the custom board's UART.  

    -Jason

  • Correction: "to leverage the launchpad's *270* Ohm pull-up..."
  • Jason,

    I did not update, but I was able to get both the uniflash and JTAG working (using LaunchpadXL to program/debug my custom CC3200 PCBA).

    In my earlier comment I was worried about the LaunchpadXL's CC3200 interfering with programming, but I found that removing J12 unpowers just the processor while keeping the translators on.

    I still have my reset line tied directly to CC_nRESET (soldered to top right pin of Q10), not sure if there's any concern with using the RST pin (going through diode D9). With J12 removed there's no need to remove R113 as I mentioned in my earlier post.

    I don't have any issues with power/IO sequencing.

    Try removing J12 to eliminate contention with the LaunchpadXL's CC3200, hopefully that'll get your JTAG working and eliminate the sequencing.

    -Jon
  • Hello,

    I am new to the CC3200 and I am hoping you guys are patient with me. I am trying to use two CC3200's in a way that one of them is acting like an EMULATOR and debugging the other.

    To make it simple, let us call A as the CC3200 which is acting like an emulator. I connected it's USB cable to my laptop to give power and connect to Code composer and use the FTDI JTAG.  B is the CC3200 under Test.

    From A I connected the JTAG pins fro FTDI side to the pins marked J8 thru J11 on the B side. I also connected two grounds together.

    A side has J12 removed whereas B has J12 connected.

    The code succesfully executes on teh "B" CC3200.

    However I try this setup with "B" replaced with a custom CC3200 board but  I get "Error connecting to the target".

    Is it enough to connect only the JTAG pins ?

    Thanks'

    Narayan