CC3200 IAR Jlink debug issue?

Hi Yang,

Can you please use IAR 7.2. It has all support files required to work with CC3200 device. On IAR, goto Project Options->Debugger->Setup

Select the Driver.

Also there is an FTDI chip on the CC3200 Launch Pad, so you can select "TI Stellaris" under Driver dropdown menu in Project Options->Debugger->Setup

Also as mentioned in cc3200-sdk\docs\CC3200-Getting_Started_Guide.pdf, you need to copy cc3200-sdk\tools\iar_patch\armLMIFTDI.dll to IAR installation directory (IAR_INSTALL_DIR\arm\bin)

Hi,

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

Hi, dear sir,

      I dont have a CC3200 Lauch Pad,and I just have the ICs， I darw an pcb board and want to use the Jlink to dowload and debug it too,the Jlink is like this:

Could both the IAR and CCS have the driver?or just IAR has the driver?

                                                                                                                      Thx! 

I am also looking for a way to JTAG a cc3200 chip on a custom dev board.

Does anyone know if the Segger J-Link above will work?  Or know of any 2WD or 4WD that I can buy to interface to the cc3200?  

I don't need CCS integration; just being able to access it via cli on Linux would be awesome!

Hi Steve,

in theory the JLink should work with the Cc3200, provided the config is done correctly. If you search the forum for tags like CC3200 Segger JLink SWD you will find a thread that discusses it in detail.

i have personally not been able to get mine working under Linux using OpenOCD 0.8.0 and later, but have seen some people successful using 0.7.0

i have also tried to get support from Segger but since my j-link is an EDU version they do not offer support. If yours is a normal commercial unit i suggest you take it up with Sgger directly. and if it is solved for you, great, it will be solved for all of us.

Andre

Thanks Andre!  I have been looking around quite a bit, but no luck so far.

I have gotten the CC3200LP working w/ OpenOCD.  Since the JTAG and UART pins are conveniently accessible on the LP, I was thinking to remove the jumpers from there and connect the FTDI signals directly to my dev board.  In essence, using the LP as my debug emulator!  I think this should work.

Has anyone else tried this?

Since CC3200 support for J-Link and IAR from TI / rest of the world isn't very good we are still using a CC3200 Launchpad FTDI chip as the JTAG for our own HW.

We have gotten some support from IAR to get J-Link working in 4wire mode and that seems to work (you need to run a segger script file to set up the ICEPick). Thanks IAR !

Not sure if CCS will work as I don't use it but assume there is some way to run a script while bringing up debugger.

So although everyone at TI suggests J-Link - should - work with CC3200 in 4-wire mode is not 100% supported yet in the examples that I have seen (have not checked out IAR 7.30.3 yet)

BTW - Looks like there might not ever be a vendor provided solution to load external SPI flash from an IAR project (as a side effect of debugging) since the external SPI flash makes that a problem. IAR's web site was wrong about a CC3200 flashloader being available, not sure if they fixed web site yet. Segger seems to be working on getting J-Stuff working with something like J-Flash utility but if you have hopes of not using uniflash while debugging with a JTAG (or SWD) to leave behind a bootable system don't hold your breath. It makes some sense as you don't run out of flash on CC3200 but the original IAR web site box checkmark for flashloader on CC3200 had my hopes up.

But IAR support also dug up this link

"Programming SPI flash without Uniflash through debug port"
http://searchingforbit.blogspot.com/2014/07/cc3200-launchpad-with-external-debugger.html

so it is sort of possible if you use uniflash to prep the flash first but I don't think anyone is planing on getting it working with IAR officially. We just put a switch on our SOP jumper so we can switch back and forth easily from 4wire to uniflash boot (thats why I wanted 4-wire JTAG working).