This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Looking for cause of DSP damage while debugging / reprogramming

Other Parts Discussed in Thread: CCSTUDIO

Hi there,

I'm currently working with a piccolo 28023 on a control card (F2802xx) mounted on a Docking-Stn USB-EMU.

Running a Virtual machine (vmware) with Ubuntu 11.04, in there CCS 5.1.1. Connecting to DSP with Blackhawk USB2000.

While debugging I do several code modifications, then doing the build with Ctrl+B, then CCS asks me if a want to reload the program I'm debugging -> I click  yes.

The normal case is that all is ok, and the new program is downloaded.

But now I have destroyed 3 DSPs while working this way! The first 2 times I had a oscilloscope connected and the board was powerd by USB, so I removed the oscilloscope an powered the board with a external power supply.

But unfortunately my last DSP crashed some minutes ago...

CCS says:

C28xx: Flash Programmer: Error erasing Flash memory

C28xx: Trouble removing Breakpoint with the Action "Remain Halted" at... (Emulation package 5.0.471.0)

A popup displays:

Trouble writing Memory Block at... (Error -1156 @0xAE7) Debvice may be operating in low power mode. Do you want to bring it out of this mode?(Emulation package 5.0.471.0)

I click yes -> CCS crashes (closes, process is gone).

From now on I get following error when I try to connect to DSP:

Error connecting to the target:
(Error -233 @ 0x0)
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.
(Emulation package 5.0.471.0)

Now I'm actually downloading CCS 5.5, I will update all the software to the newest (internal update of CCS does not work...).

Questions:

Could older Software, perhaps older drivers really caus DSP damage?

Could it be a virtual machine related problem?

Or what else can cause this damage?

Thanks for your help!

Roger

  • Hi Roger,

    Roger44834 said:

    Could older Software, perhaps older drivers really caus DSP damage?

    Could it be a virtual machine related problem?

    Nope, not at all!

    Roger44834 said:
    Or what else can cause this damage?

    This might primarily happen due to following things:

    1. External interface circuit : External interfacing circuit can damage the mcu due to various reasons (over voltage)

    2. CSM issues (permanently locking of flash due to improper flashing of devices)

    This usually happens when you face power failure while programming the mcu. Hence you should avoid disconnection/interruption of mcu while flashing.

    3. ESD : Due to static charge while handling the mcu.

    Regards,

    Gautam

  • Thanks Gautam for your fast reply!

    I know the possible problems of CSM, I'm working since > 10 years with c2000 series.

    I am sure that I did not touch anything (no ESD). Nor did I disconnect or connect something in this time.

    I am sure that I did not power cycle (that's why I took the exernal power supply for the last DSP, a 5V, 2A power suply). Iwas not sure if the USB power supply of my laptop was enough.

    The only reason I see, is a possible disconnect / connect of USB (of Blackhawk) due to VM.

    All other ideas are still welcome!

    Roger

  • Roger44834 said:
    I'm working since > 10 years with c2000 series.

    That's great! Nice to meet you on forum :)

    Roger44834 said:
    The only reason I see, is a possible disconnect / connect of USB (of Blackhawk) due to VM.

    Even if the disconnections happen while the program is still running, this should not damage your mcu for sure. Lets wait for what TIers have to say. Till then all the voltages on the board seem fine? Do check that too. Sometimes LDOs misbehave.

    Regards,

    Gautam

  • Hi Roger,

    I remember that v5.1.1 crashed a bit more on my Windows machine than I would have liked, however I am not aware of a case where its crash led to chip failure/CSM lockup.

    Could you please let us know if this behavior follows you onto your updated CCS installation?


    Thank you,
    Brett

  • Hi Brett

    Thank you for your statement. In the mean time I replaced a DSP and took another Docking Stn. All is fine in this moment...

    I will not be in the office for the next 2 weeks, but my plan is to re-install CCS5.5 in the VM and start from scratch after these 2 weeks.

    Yesterday I downloaded the offline version of CCS5.5 (this was 5.5.00077) an update was downloaded by internal update but crashed while installing... The update process always takes a long time on Linux. Don't know why.  starting ccstudio with sudo -> searching for updates -> install them -> restarting ccstudio with sudo -> splash screen appears shortly, then nothing seen on screen for 10-15min but ccs_update5.5 process is running, then an error window of the installer appears... For me this is all very strange, never had those problems on windows box...

    Seems that I have a so called "no chance week". That's why I will retry in 2 weeks. With new energy :)

    Roger

  • Hi Roger,

    Some of the VM/ CCS update specific issues will probably be best handled on the CCS forum where those specific expert live.  I've asked someone from that team to take a look at this thread, but your response may still be better there.

    Again, please let us know how things go once your return.


    Thank you,
    Brett