• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 54 subscribers
  • Views 856 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCSv4 and Yesterday's Blackhawk Driver Update

Alex
Expert 2430 points


Yesterday, in CCSv4 (v.4.2.3 to be exact), I got a notice that there was an update for my Blackhawk drivers.  I installed them, but now my CCSv4 install seems to irreparably damaged.

When trying to simply open a debug session, Eclipse (and its buggy Java engine) always crashes with the following error:

 

I've tried completely uninstalling CCSv4 and reinstalling, but when I do that, I get the following error when the install gets to the BH driver portion of the install:

 

 

I have even done multiple System Restores, and that does not resolve the issue.  (Microsoft's System Restore is notoriously incomplete, so that is not a surprise I suppose.)

 

I have no problem launching a debugger and even connecting to any of my hardware (both my custom board and an EVM) under CCSv3.  But CCSv4 seems to be irreparably damaged.  I have contacted Blackhawk, and they sent me a stand-alone driver pack for CCSv4, but it didn't help as I still get the above MDPJTAG error, so it won't install.

 

Given my project schedule and deadlines, I do not have the time nor the inclination to wipe my system clean and reinstall Windows and then all my software applications again.  Keep in mind my system worked flawlessly up until yesterday when I installed the BH driver update, so I am hoping someone can help me repair my system.  Again, so not to waste time, uninstalling and reinstalling does not resolve the issue, nor does doing a System Restore.

 

  • 0
    Prodigy 130 points

    I've run into a similar crash with the Setllaris In-Circuit Debug Interface although uninstall/reinstall of ccs4 worked for me.

    To be more specific. I was able to recover the initial state by reinstalling ccs4. If the update is re-installed, the crash returns when I launch the debugger.

    -G

  • 0 in reply to Gary Brown
    Expert 2430 points

    Yeah, it's very perplexing.  I can understand an install/uninstall not solving the problem because the uninstall still leaves a lot of stuff behind: driver files, registry settings, etc.  But even given Microsoft's limited "System Restore" functionality (compared to an actual disk image backup, for instance), I am at a lost why CCSv4/Eclipse is still so broken even after a system restore.

    Newly discovered information:  even though it was the Blackhawk driver update that started this, the problem is with CCSv4, not the blackhawk drivers themselves.  It's the mere act of launching the debugger that crashes CCSv4.  For instance, if I create a new, empty workspace, create a new Target (I just created a Simulator target), and then launch the debugger, I get the same crash.

  • 0 in reply to Alex
    Prodigy 130 points

     

    To completely scrub the state of my system I

    1. ran all of the uninstallers directly from the install path.
    2. removed all remaining drivers using the control panel app including
      1. Blackhawk Emulation Device Driver
      2. Windows Driver Package - Spectrun Digital...
      3. Windows Driver Package - Texas Instrument (usbser) Ports ...
      4. Windows Driver Package - Texas Instrument, Inc  (umpusbvist) Ports ...
    3. Then I ran ccleaner to remove any left over entries in the registry.

     

     

     

  • 0 in reply to Gary Brown
    Expert 2430 points

    Yeah, I did all that yesterday, including ccleaner, only I did not have any Windows Driver Packages for Texas Instruments, only Spectrum Digital.

  • 0
    TI__Guru**** 470051 points

    I took the latest Blackhawk update (4.2.1.050) with my CCSv4.2.3 install. I also got that MDPJTAG error popup.

    Besides that, I was still able to start a debug session and connect to my target using my Blackhawk emulator. So I don't see the crash.

    Did you try using a new clean workspace? If that does not help, could you provide some crash dump files, error logs and a debug server log? You can use the support tool to generate and package these for you:

    http://processors.wiki.ti.com/index.php/Troubleshooting_CCS#CCS_Diagnostic_Logs

    Thanks

    ki

     

     

  • 0 in reply to Ki
    Expert 2430 points

    Yeah, a clean workspace and using just a simulator (i.e., nothing Blackhawk related) still causes a crash.  My system had been working flawlessly up until the moment I installed those drivers yesterday.  So given simulator thing, I think it was something in the update process itself that corrupted my system, not necessary the Blackhawk drivers themselves.  (Well, I do get that MDPJTAG error, something I have never gotten before.)


    Anyway, I have to run to a quick meeting, but I'll turn on the logging functionality and upload the log in about half an hour.

     

  • 0 in reply to Alex
    Expert 2430 points

    Here is CCSv4's archived logs:  <removed>

     

    Update:  I went through the whole uninstall/reinstall process for the fifth time, but this time I also uninstalled and reinstalled CCS v.3.3 (and SP12).  That seemed to do the trick!  There was also a left-over .TI directory in the %APPDATA% directory after I uninstalled everything, so I deleted it before reinstalling.  So it was either that or the CCSv3.3 reinstall, but one of them fixed CCSv4's debugger.  Don't ask me how, but if you know, I'd like to know, too.