CCS: CCS crash after TI Emulators update

Soner,

I don't see the logs yet.  If they were submitted this morning they might not come through until tomorrow.

Can you let me know some more information:

• which version of CCS the update was applied to
• Host OS (windows 7, macOS 10.14.6...)
• Debug probe being used
• Device used

Regards,

John

I added two dmp file to crash.

• CCS v9.1.0.00010
• Windows 10 1903 (build 18362.295)
• XDS110 v2 Emulator on board
• Hercules TMS570LS12x LaunchPad Development Kit

Regars,

Soner

1030.dmp.zip

By the way,

I re-installed CCS v9 because i couldn't revert update.

Now, I can't debug with XDS110 v2 because I upgraded firmware with new TI Emulators update.

I think, I must downgrade firmware but I don't know how I can do this.

I am getting error like this:

Error connecting to the target:
(Error -151 @ 0x0)
One of the FTDI driver functions used during the connect
returned bad status or an error. The cause may be one or
more of: no XDS100 is plugged in, invalid XDS100 serial number,
blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.
Use the xds100serial command-line utility in the 'common/uscif'
folder to verify the XDS100 can be located.
(Emulation package 8.2.0.00004)

Edit:

I solved this problem.

I downgraded firmware with xdsdfu.exe and re-install FTDI drivers.

Soner,

The XDS110 does not use an FTDI chip.  That error you are seeing only occurs when CCS is configured for an XDS100 and not an XDS110.  Check your debug configuration in your project settings or .ccxml file and switch it to use the XDS110 and see if you are able to connect.

Regards,

John

John,

I was handle this XDS problem, thank you.

Did you look to dump files?

Regards,

Soner

Yes the team is looking at the files.  Hopefully they provide some clue as to what is triggering the crashes.  Thanks for attaching them.

Regards,

John

The crashes occurred in a low-level Microsoft library that supports the Microsoft Text Services Framework. The call-stack is entirely in Microsoft library code and is on the process's main thread (thread 0). CCS is not enabled to make use of these OS provided services so I'm not seeing any clues as to what instigates the crash.

Does your PC have multiple languages installed and is the Windows language bar displayed on your monitor?

On Windows 7, you can see what text services are enabled by finding the dialog below in the control panel.  Do you have any additional text services enabled?

When a crash occurs, have you noticed whether it happened while you were entering something from the keyboard and, if so, which window was active?

I'm hoping we can find something that will allow us to reproduce the issue here.

Soner,

Are you able to provide any of the information requested by Andy?

AndyW said:

Does your PC have multiple languages installed and is the Windows language bar displayed on your monitor?

On Windows 7, you can see what text services are enabled by finding the dialog below in the control panel.  Do you have any additional text services enabled?

When a crash occurs, have you noticed whether it happened while you were entering something from the keyboard and, if so, which window was active?

Regards,

John