• Locked Locked
  • Replies 6 replies
  • Subscribers 54 subscribers
  • Views 736 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.

Error connecting to target after 4.1.3.00038 update

Brian Willoughby
Genius 4630 points
Other Parts Discussed in Thread: TMS320VC5506

 

Upon installing the new CCS4 update today, I can no longer access my target.  This was working before the update, which is the only thing that was changed.  Error message is as follows:

Error connecting to the target: Error 0x80000240/-603 Fatal error during: Initialization, OCS,

Reboot did not help.

I tried to roll back the drivers (I'm running XP), but this option was not available.

The update log in \Program Files\Blackhawk indicates that "A driver update is not needed" so I assume that today's update only affected CCS4 on my system, and that the Blackhawk driver files were not altered.

BHReset and BHProbe both pass the tests.

My hardware is described as:

VID:0B1E

PID:8006

S/N: FX2-0001

Board Type: Emulator 2

Hardware Revision: CPU Rev.C

The following test scripts all pass:

DBGJTAG -X adapter,driver=bhjtag3.dll -T control

DBGJTAG -X adapter,driver=bhjtag3.dll -T memory

Moving from the hardware to CCS4, I first tried re-selecting my Target Configuration, but there was no change. I tried deleting my launch configuration under Non-Project Debug Session, and also deleted the targetdb.cache in ...\ccsv4\DebugServer\bin\win32

How do I determine a fix for this error?  Should I downgrade to CCS4.1.2?  How would I even do that?

 

  • TI__Intellectual 1490 points

    hi,

     

    I got same message when I try to connect a target that is not reseted or powered..

    you are using the same target configuration file than before but maybe some GEL initiailization is no more here..do you have all gel loaded? no error messages at connection?

    Or if you have some memory on the board that is available through debug port you can open a memory windows and see if you can see / modify some memory content..

    Another possible solution is to rename the target configuration file because sometimes if the contents has changed, it looks there is a satic dependency not updated..

    regards

  • in reply to Claudio06
    Genius 4630 points

    Thanks for the suggestions.

    Power/reset is not the issue - the setup worked for months before now.

    I was using the same Target Configuration, but then also tried removing cache files and using a new Target Configuration (technically, I created a new Target Configuration with a new name, rather than rename the old one).

    I cannot access memory on the board because I cannot even connect.  If you're talking about memory with an independent JTAG interface, then that's not an option.  The TMS320VC5506 is the only JTAG device on my board (my board is on its second revision and has been working for month before yesterday).

    My next attempt will be to downgrade to CCS4.1.2, but then I'll still need to know how I can upgrade.

  • in reply to Brian Willoughby
    Expert 1080 points

    Brian,

    Please let me know the model/pn and serial number of the Blackhawk emulator you are using so we can duplicate this issue.  This information should be on the emulator pod.

    FYI:  a serial number of FX2-0001 as you origially listed is not a valid Blackhawk serial number.

    Thanks,

    Andrew

  • in reply to Ferrari5699
    Genius 4630 points

    I purchased this emulator on eBay and it came with nothing.  I'm fairly certain that it is a clone.  I'm not surprised that the serial number is bogus.  The only reason I even called it "Blackhawk" is due to previous discussion here where someone helped me determine that it seems to mimic the Blackhawk.

    As to my problem, I wonder if it has something to do with licensing.  When I re-installed 4.1.2, CCS asked for my license file.  But perhaps the previous upgrade lost the license file somehow.

  • in reply to Brian Willoughby
    TI__Guru**** 463481 points

    Brian,

    I don't think your connectivity issue is related to licensing. You would get an error when trying to start a debug session if it were so. It sounds like you can start one, you just can't connect. If you generate a debug server log, it may provide some answers. But you will have to do some additional work on your end to enable it.

    ki

  • in reply to Ki
    Genius 4630 points

    Thank you.  At the moment, I have moved back to 4.1.2 so I can get some firmware development done on a deadline.  But I still have 4.1.3 installed on my machine.  When I get a chance, I will generate a debug server log and follow up with you (because I would like to upgrade eventually!)