ccsv6 - ti xds100v2 probe issues

martyn foster said:

Code composer installed fine as far as I can see but on following the instructions for installing the usb xds100v2 ( ti product TMDSEMU100V2U-14T ) it allows my laptop touchpad to function until target power is applied then the touchpad freezes( there should be no interaction with these devices )

That seems very weird! Exactly, there should be no interaction with interface devices.

martyn foster said:

I've had to resort to a wireless mouse? Is this a known issue, device manager indicates all xds100v2 drivers present and correct. Once working with the mouse I ran my code in a debug session but when terminate ( red square ) is clicked it closes session but leaves code running on target. Is this not  terminate as I view it, reset program, halt then exit. Do I have to suspend or reset cpu before pressing terminate.... seems long winded if thats the method.

I guess you're having some device driver issues here. Simply go to device manager and uninstall Touchpad and mouse devices and then run "Scan for hardware changes". This would reinstall your touchpad & mouse and should solve your problem. If still this issue exist, then I guess the drivers have been corrupted.

Regards,

Gautam

Hi Gautam

I undertook the advice you gave but this procedure did not work. When I started code composer I have found that it would allow  the touchpad to work with target power and xds100v2 all connected. When proceeding into debug thats when the touchpad seemed to freeze up. I'm having to use a wireless mouse for use with code composer, does anyone in this modern world Gautam actually develop code and test it before release. I suspect there could be a windows 8 issue as it seems to cause problems installing most things. Again software that is excessively complex and not tested ( patch after patch of updates and bug fixes ).

Its nice to encounter hardware and software that simply installs and runs...... sadly its few and far between.

It'd be nice if someone else has had similar problems, machine is a lenovo z580 with synaptics touchpad.

Thanks

Martyn

As Gautam said, that is indeed weird. I've never heard of such an issue where the touchpad is impacted...

martyn foster said:

but leaves code running on target.

This is actually expected (and desired) behavior for most targets, especially microcontrollers (except MSP430). What device are you using? I suspect some ARM Cortex based device?

martyn foster said:

Is this not  terminate as I view it, reset program, halt then exit. Do I have to suspend or reset cpu before pressing terminate.... seems long winded if thats the method.

"Terminate" will disconnect from the target and shutdown the debugger. After disconnect, the target will be put into "free run", regardless of if the target was halted prior to disconnect. At least this behavior is for most targets (what target are you using again?)

Thanks

ki

Hello Ki

The touchpad issue is odd, so far no USB device has had any effect on this until the XDS100V2. I notice it has two installed drivers one for channel A and one for channel B... are both required? It spoils the experience of using the IDE having to resort to the bluetooth mouse.

Regarding "Terminate", I've been using CCS3.3 and this does not have that terminology I believe Halt was the option. My code would be left static ( its running from RAM at present ) as I have an irritating flashing LED which I notice immediately if the code was running( its a test toggle in the code ). This never happened in CCS3.3 so its a difference in the general functionality that I'll get used to as to me the eclipse IDE has many advantages over the CCS3.3 IDE. Other than the hardware issues( and the unusual project opening method as compared to the old ) I prefer the new software. Its a learning curve but hopefully it'll make development easier. The target I'm using is the 28335 ( C28x family ).

Thanks

Martyn

martyn foster said:

The touchpad issue is odd, so far no USB device has had any effect on this until the XDS100V2. I notice it has two installed drivers one for channel A and one for channel B... are both required? It spoils the experience of using the IDE having to resort to the bluetooth mouse.

I'll need to investigate this further. I've so far never experienced this issue with several laptops. And yes you should have two channels visible

martyn foster said:

Regarding "Terminate", I've been using CCS3.3 and this does not have that terminology I believe Halt was the option. My code would be left static ( its running from RAM at present ) as I have an irritating flashing LED which I notice immediately if the code was running( its a test toggle in the code ). This never happened in CCS3.3 so its a difference in the general functionality that I'll get used to as to me the eclipse IDE has many advantages over the CCS3.3 IDE.

Yup, you are right. If you disconnect from a halted target, it stayed halted in CCSv3.3. This behavior started to change where people argued that leaving the target halted was pointless if the debugger was not connected to it since a halted target is not the natural state unless held in reset or some other exception. So most (but not all) MCUs will now resume execution on disconnect even if it was halted on disconnect.

martyn foster said:

Other than the hardware issues( and the unusual project opening method as compared to the old ) I prefer the new software. Its a learning curve but hopefully it'll make development easier. The target I'm using is the 28335 ( C28x family ).

Yes and it is one heck of a learning curve! Going from the old CCSv3 environment to the new Eclipse based one is as drastic a change as you can make. Everything changed on you so we understand that it can be a really confusing for an experienced v3 user. We appreciate the efforts of people like yourself making the move and once you do get over the not-so-trivial learning curve, we find most user like the new environment much better (though they often rued it during the early days of transition :) )

ki

Hello Ki

Yes it will be a big learning curve. I briefly used Eclipse for Java coding about 5yrs ago... I moved over to Netbeans and have used that ever since. It lets me code Java, C/C++ etc for GUI design and PC applications. The new CCS V6 has a nice look to the development window... I have to relearn perspectives and much more. I've a short time to get up to speed 2-3 weeks max and develop my real time comm's code in parallel. As long as I can create code and do simple debugging I'll be fine. I've acquired a zeroplus logic cube ( lap-c16064 ) analyzer which is a great piece of kit for observing serial streams and doing the protocol analysis ( very low cost too as I'm on a tight budget hence the XDS100V2 purchase ). I'm also an old fashioned developer in that I use toggled I/O pins to indicate position in code as well as the invasive debug method ( though I'm aware real-time debugging is now available.... more to learn! ). It can tell you a lot about interrupt timing relative to one another.

I'll continue investigating the touchpad issue.

Thanks

Martyn