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.

CC C5000 Patch Issue

Hi All.

This is peculiar, as I have only just started to experience this problem.

I have installed the Code Composer C5000 version 2.0 and then proceeded to patch with 2.10.00 but when applying the next patch to 2.20.00 the system is rebooted and as the log in screen comes up the system reboots.  This is an endless cycle.

I am running this on a Windows XP SP2 machine, though have also tried it on an SP3 machine.  The machine has 1GB of RAM and 80GB hard drive.  This is from a fresh install and the machine has been joined to a domain as well as off from the domain with the same result.

I have various minidump reports, but the information is gobble de gook to me.

Anyone else had this issue before and know how to resolve it please?

Forgot to say... that Last Known Good Configuration manages to get me back in to the machine, so sounds like a CC Driver Issue to me.

 

  • We had an issue years back where the XDS560 PCI service could cause issues on certain HP and Compac machines.  2.20 might have been when we introduced XDS560 support.  

    Do you need to use CCSv2.x?  We have released some major versions since then.  I don't think 2.x had an option to not install that driver (CCSv3.x and 4.x do but also we don't see that issue being reported).

     

    John

  •  Hi John,

    Yes unfortunately I am working on a legacy piece of code that requires the older flavour of Code Composer.  I think I might have a work around solution.  After installing the patch and then booting with the Best Known Config option, I was able to apply the other patches and once the system was rebooted I had no problem logging back in.

    I can't remember having to do this before however and am somewhat bemused as to why this has suddenly started happening.

    Thanks for your help though.

    Clive.

  • I am not sure how much of the registry the best known config restores.  I think it leaves it alone.  If that is the case they you are probably ok.  CCSv2.x and 3.x rely on the windows registry so if it wipes out the registry entries the install made that would be a problem.

     

    John

  • Hi John,

    It looks to be ok at the moment.  I am keeping my fingers crossed that there are no untowards issues later in the project. Time will tell. Thanks for your help on this.

    Clive.