mikroProg-JTAG with CCS

[HSR_embedded]

Hello everybody

I use on a Win7 PC the Code Composer Studio from TI with the mikroElektronika Board EasyMx PRO v7 for Tiva™. I can debug as normal with the CCS. If I connect one/or both of the USB-UARTs and have the connectivity to the computer, then I can't start a new debugging. First I have to close the virtualComPorts on the Terminal-Programm, and then I can start debug again.

Do you know that kind of problem? Any solutions? Because this is not very easy to handle....

By the way, I have the same problem, if i work with your mikroC for ARM software. So I think there are some troubles maybe with the JTAG-driver?!
Thanks for any suggestions....

[filip]

Hi,

So, when you are connected to the terminal, you have the problems with the debugging ?

Regards,
Filip,

[HSR_embedded]

Yes, exactly! So then I have to close the virtual Ports, start the new debugging session and then i can open the virtual port again.

Regards
Adrian

I will make a screenshot of my problem...(just a few minutes)

[HSR_embedded]

here are the pictures (Note: At this time I tried it out with your mikroC PRO for ARM Suite --> the same problem!)
For me the error looks like there is a problem at the detection of the debugger/programmer (hardware)! Something is wrong there with the correct detection over the usb (maybe driver problem?)

With the internal UART Terminal in the mikroC PRO for ARM Suite, there you allways close the port when i stop debugging, so that is a workaround, but not a solution

[HSR_embedded]

and now how it looks with Code Composer Studio (on the same PC, same configuration, just a few minutes later)

[filip]

Hi,

I have tried this on my XP computer with mikroProg Suite for ARM and mikroC PRO for ARM and it works OK for me.
Could you try this on another computer and see if the issue is present there ?

Regards,
Filip.

[HSR_embedded]

I have now tested it on an other machine. Win7, SP1, 64bit operating System. Blank System, only with the mikroC PRO for ARM installation (including drivers). --> The same result, it is not possible to start the debugger or to start a programm-load, when an other virtual-com port is opened!!

Tools/Drivers Version which are used:
- mikroC PRO for ARM v.4.2.0
- COM-PORT Driver: FTDI 2.10.0.0 27.Januar 2014
- Stellaris Evaluation Board A / B: FTDI 2.6.0.0 22.10.2009 --> don't need this driver to be this?? mikroprog_ti_drivers_v130, if I uninstall this drivers and manualy install them, with the DPInst_x64.exe, allways the FTDI 2.6.0.0 will be taken... I think here could the problem maybe located...

Or which versions are you using?

[filip]

Hi,

I'm using the same HW configuration, but different OS.
I will try with the same OS as yours.

Regards,
Filip.

[HSR_embedded]

Any news? It would be nice to have at least an answer if you have checked this and the result of your check! Or is this topic set to "non problem for you" ?!

[filip]

Hi,

I am sorry if I haven't answered you before, the post slipped my eyes .

I have tried this on Window7, 8 and XP and wasn't able to reproduce this issue, but I will try more.

Regards
Filip.

[HSR_embedded]

Thanks for your reply!

The last chance to maybe find out the reason for this problem is in my eyes the version of the onboard Programmer/Debugger. How can I read out the Version of the "Firmware" running on the onBoard Debugger? Is this a FTDI Device, or what is it? And which Version are you using?

Hopfully we can figure out, whats the problem....

[filip]

Hi,

You can use STM32 ST-LINK Utility application to see the version of the firmware.

Regards,
Filip.