CCS/TMS320F28069: USB Scanner Driver - Kills Other USB Device (Scope)

Hi John,

John Westmoreland43 said:

when I start CCS it seems to kill that driver

John Westmoreland43 said:

Is there a way to keep the driver from scanning when a CCS debug session starts?

Just want to clarify - the issue occurs only when starting a CCS debug session, or when the CCS IDE is started?

What version of CCS are you using? v8.x?

Thanks

ki

Ki,

When starting a debug session - sorry I wasn't a little clearer.

And, I'm running v8.1.x.

Thanks,
John W.

There is likely some conflict with the new autodetect feature we implemented in CCSv8. There is no clean way to disable it. You can try this hack:

delete/rename/move 'device_detector.js' that is in <CCS8 INSTALL DIR>\ccsv8\ccs_base\cloudagent\src\modules

This *should* prevent the autodetect feature from running. Let me know if this prevents the issue

Thanks
ki

Ki,

I renamed it - didn't work - I'll move it now - but I think this won't work.
So, what's the next thing to try?

Thanks,
John

John,
Can you do me a favor? Can you install CCSv7.1.0 (in a new directory) and see if that version also causes the same issue? That version should predate when the autodetect feature was added. This way we can confirm if autodetect is the root cause or not.

Thanks
ki

Ki,

OK - I have a project that was using the Multi-Axis DMC EVM and using CCS v. 7.1.0.00014 - ran that with the debugger and the USB scope app is fine.

So, it would appear the autodetect feature is the cause.

Thanks,
John

Can you try the following:
Open the <CCS8 INSTALL DIR>\ccsv8\ccs_base\cloudagent\src\targetDetection\debug_probes.json in a text editor and replace the ENTIRE contents with just square brackets: []

Please back up the file somewhere first.

Then restart CCS and see if this helps

Thanks
ki

Hello Ki,

Did that - unfortunately, still happens.

What to try next?

Regards,
John

Please download the attached file and copy to .\ccsv8\ccs_base\cloudagent\src\modules\node_modules

/cfs-file/__key/communityserver-discussions-components-files/81/usb.txt

Note that the "node_modules" folder does not exist there by default so you need to create that folder also

then rename the file extension to "js" so that the file name is "usb.js"

Then restart CCS and give it a try

Thanks

ki

Ki,

OK - did that - and same results.  When the debugger starts the USB scope app stops.

There is already an usb.js file in this path:

\ccsv8\ccs_base\cloudagent\src\node_modules\usb - usb.js is there.

Thanks,
John

John Westmoreland43 said:

There is already an usb.js file in this path:

\ccsv8\ccs_base\cloudagent\src\node_modules\usb - usb.js is there.

Yes, that is a different file. You can leave that one alone

Just to confirm - you placed attached file in: ..\ccsv8\ccs_base\cloudagent\src\modules\node_modules\usb.js ?

Ki,

Yes I did - and same results - USB Scope stops as soon as the JTAG debugger makes a connection.

Thanks,
John

Ok, I'll have to dig a little deeper and will keep you posted when I'm back in the office tomorrow

thanks
ki

OK Ki.
Thanks,
John

John - can you try a quick test where you launch the debugger and connect/load using DSS? If you have never used DSS, let me know and I can put together a script for you. Or you can just use loadti. 

Thanks

ki

Ki,

I don't use DSS normally with CCS, so if you can put a script together that would be nice.

I'll try loadti and report back.

Regards,
John

Ki,

Loadti produced the same result - scope freezes when the connection is made.  I've attached a screenshot.

Thanks,
John

Hello Ki,

Any updates?

Thanks,
John

Hi John,
Since the issue occurred when using loadti, it looks like auto-detect is not the culprit. The root cause must from the debug probe driver and not the CCS debugger. The emulation folks will need to look at this. They will likely need to reproduce the issue locally to debug this. Can you send more details about the USB scope you are using?

Thanks
ki

Ki,

I'm using two right now:

linkinstruments.com/mso92.html - this is the one with the problem.
linkinstruments.com/.../mso92_0921.gif

and

www.linkinstruments.com/oscilloscope85.htm - which works just fine.
www.linkinstruments.com/.../laptop_oscilloscope.gif

Thanks,
John

Thanks.
ki

Ki,

JIC this thread just stepped into the black-hole-of-nothingness, I ask that it remain open until a solution is found.

Thus far, after trying many suggestions, nothing has worked.

So, can we agree to keep this thread open?

Thanks,
John

Hi John,
This thread remains open and will continue to remain open. The issue is likely due to changes in the updated driver. While we investigate, I recommend using a older CCS version that comes with an older version of the driver as a workaround. I don't know which version of the driver would be recommended here. But likely something before v8. Since you have 7.1 installed, That is a good choice.

Thanks
ki

Hi John - just wanted to update you that we did not forget about this thread. The emulation expert best to investigate this issue is currently out on vacation and will return later this week. Thanks for your patience.

ki

Ki,

OK - thanks for the update,
John

John - can you try the following:

-browse to <CCS8 INSTALL DIR>ccsv8\ccs_base\common\bin

-rename/backup "libusb-1.0.dll"

-extract the contents of the attached zip file into the directory

-restart CCS and see if this has any impact.

/cfs-file/__key/communityserver-discussions-components-files/81/libusb_2D00_1.0.dll.zip

Thanks

ki

Hello Ki,

Wow - for some reason I had missed this post - will try immediately and let you know.

Thanks,
John

Ki,

The same thing happens.

Note - the archive date is 2018-08-13; the file date of the DLL is 2017-02-13 - so it's older than what I'm already using - is that what you intended?

I was under the impression the file should be later vs. older since we've tried the older stuff already.

Thanks,
John

John Westmoreland43 said:

Note - the archive date is 2018-08-13; the file date of the DLL is 2017-02-13 - so it's older than what I'm already using - is that what you intended?

yes this is intended. It is the dll from CCSv7.1. Since 7.1 works fine for you, we were hoping that dropping in the usblib from 7.1 would help. Looks like it did not. Back to the drawing board.

Thanks

ki

Ki

OK - here's something interesting - if I'm running - and reset the target - both USB scopes keep running.
This is the first time I've noticed this, and I repeated it to make sure.

So, the USB connection is only broken when starting the debugger IDE over from scratch (doing a JTAG load).
Maybe this is a clue to the solution for you guys.

Thanks,
John

Thanks John. Every bit of information helps. It is something specific to the debugger launch. We are looking for alternative workaround to try. Thanks for your patience.

Ki,

Yes - I've been doing this a lot just to repeat it several times, and yes, once you're in the debugger, all is well as long as you stay in the debugger.

Thanks,
John

Hi John,
Nope, we (TI) did not forget about this thread. We are frankly just out of ideas here. I have been informed that our driver does not open a connection to the probe until a target connection attempt. So during a debug launch, the driver will not touch the USB port until a target connection attempt. Hence we are wondering if just launch the debugger, but do not attempt to connect to the target, if the issue still happens

ki

Ki,

If I start the debugger and do not make a connection to the target - the problem does not occur.

Thanks,
John

Ki,

OK - so, what's happening with this thread/investigation?

Thanks,
John

Hi John,
Unfortunately there is not much progress to report. All we can confirm that the issue comes from the driver since it happens on connect. We have not observed any issues here with any USB devices (scopes or otherwise) on CCS target connect. We have exhausted our ideas on how to workaround/resolve the issue. I'm afraid it is likely that we will not be able to determine the root cause or provide a workaround. Sorry.

ki