• State Resolved
  • Locked Locked
  • Replies 16 replies
  • Subscribers 55 subscribers
  • Views 3620 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 initializing emulator: (Error -1006 @ 0x0)

James McLaughlin
Expert 1090 points

Other Parts Discussed in Thread: TMS320F28069

I am using:

  1. Windows 7 32-bit
  2. CCS 5.4.0.00091 
  3. Custom F28069 board with a Signum Systems JTAGjet C2000 emulator

I am no longer able to debug our TMS320F28069 devices.  I was able to build and debug with no problems up until today.  It's been a few weeks, and in the mean-time we've experimented with getting the Microsoft TFS plugin working.  My co-worker is able to debug with the exact same code/emulator/board combination (and same plug-in installed).  This seems like a CCS error, as it happens before it even connects.  I have tried a fresh reinstall of CCS 5.4, but I get the same result.  I believe I was actually getting a different error number before, but it was the same "Unable to allocate memory" kind of error.

Error initializing emulator:
(Error -1006 @ 0x0)
Internal error: Unable to allocate memory. Restart the application. If error persists, please report the error.
(Emulation package 5.1.207.0)

Here is a log file from trying to enter debug mode:

1512.debug.log

Configuration files in this zip:

5684.8 Channel Board.zip

Additionally, I saw a recommendation to try to do the "Launch Selected Configuration' option in the "Target Configurations" view, but that receives the same error.


Any help is appreciated.  Thanks.

  • 0
    TI__Guru**** 479941 points

    Hi James,

    Thanks for the log.

    James McLaughlin said:
     My co-worker is able to debug with the exact same code/emulator/board combination (and same plug-in installed).

    Is he able to debug your board? The one you are having a problem with? Using your emulator? And what exact emulator are you using?

    James McLaughlin said:
    This seems like a CCS error, as it happens before it even connects

    The debugger is having problems communicating with the emulator. Try running whatever diagnostics software available for your emulator to test your emulator connection. Also try power cycling your emulator and also letting it re-enumerate (assuming it is a USB emulator).

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1090 points

    Yes, he can debug my board, and even use the exact emulator I was using (as well as his identical one).  I get this same error with either of our emulators.  It seems specific to my computer.

    I'm using the JTAGjet-C2000 made by Signum Systems (http://www.signum.com/Signum.htm?p=c2000.htm).  We've used these for years on F2808's and for a while now on F28069 with no real issues (before this).  

    I ran the Signum-supplied diagnostics and everything checked out.  At least it didn't flag anything as unusual.  I'm still able to use the flasher utility (external to CCS) to load code onto the board with no problems.  I also tried power cycling the target board, as well as the emulator, multiple times.  No luck.

    Anything else I can try?  Any other logs/info that would be useful?  Thanks again.

    - James

  • 0 in reply to James McLaughlin
    TI__Guru**** 479941 points

    The log is useful, I'll have the engineering team look at it in the morning tomorrow.

    Few other things to try:

    -Try using a new workspace

    -clean out old launch configurations and target cache files: http://processors.wiki.ti.com/index.php/Troubleshooting_CCSv5#Debugger

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1090 points

    Tried both of those but I still have the same issue.  Please let me know what the engineers say, this has halted development for me.  Thanks.

    - James

  • 0 in reply to James McLaughlin
    TI__Expert 5985 points

    James,

    I'll have to find someone with emulation expertise to actually get to the root cause of the error, but in the meantime you might be able to keep working if you bypass the CLA.  I'm suggesting this because the 28 driver successfully initializes before the CLA driver fails.  To do this, edit the ccxml file, click on the advanced tab, then click on the CLA core in the tree view, then check the "bypass" checkbox on the right.

    Darian

  • 0 in reply to Darian Sale
    Expert 1090 points

    Thanks Darian.  That works well enough as a work-around, at least until I need to debug the CLA again.  Let me know what you find out.

  • 0 in reply to James McLaughlin
    Expert 1090 points

    Any updates to this issue?

  • 0 in reply to James McLaughlin
    TI__Guru**** 479941 points

    Hi James,

    As painful as this may be, could you try a reinstall of CCSv5.4? Please completely blow away the old install and the install 5.4 again. We think you may have a corrupted install.

    ki

  • 0 in reply to Ki
    Expert 1090 points

    Hi Ki,

    That was actually the first thing I tried.  Is there a specific process I have to follow to completely clear out the old install?

    - James

  • 0 in reply to James McLaughlin
    TI__Guru**** 479941 points

    James McLaughlin said:
     Is there a specific process I have to follow to completely clear out the old install?

    Deleting the whole CCSv5 folder should be good enough.

    When you reinstalled v5.4, did you then take the emulation pack update (5.1.207)?

  • 0 in reply to Ki
    Expert 1090 points

    I ran the updater until there were no more updates to install.  That does appear to be the version of "TI Emulators" I have installed (5.1.207).

  • 0 in reply to James McLaughlin
    TI__Guru**** 479941 points

    One last question - your co-worker with the working environment... does he have the same emupack version installed?

  • 0 in reply to James McLaughlin
    Expert 1090 points

    He does not, he has.  5.1.73.0

  • 0 in reply to James McLaughlin
    TI__Guru**** 479941 points

    James McLaughlin said:
    He does not, he has.  5.1.73.0

    That is the version that comes with 5.4.0. Looks like he did not take the emupack update.

    We are suspecting that the update has a bug...

  • 0 in reply to Ki
    TI__Guru**** 479941 points

    I hate to ask you to do this, since I know how long it takes, but could you install 5.4 and do NOT take any updates and then try again?

    You don't have to uninstall your existing install. You can simply install in a different folder.

    If this one works, then we can be pretty certain that the issue is indeed the emupack update

     Thanks

    ki

  • 0 in reply to Ki
    Expert 1090 points

    Ok, since it was a spare-time kinda thing, it took a little while, but I finally installed a separate CCS and tested it.  I updated everything except the emupack, including installing the plugin for our source control and drivers for the emulator we actually use.

    It does appear that it's a conflict with the emupack. 5.1.207.0  With everything the same except that updated emupack, I can connect successfully with CLA processors still in the target configuration.

    Are there any critical fixes we'd be missing out on without this emupack update?
    Is there any way I can remove this emupack update from my existing install?
    Is there any more information I can provide to help with a fix for this emupack version?

    Thanks for the help.