• State Resolved
  • Locked Locked
  • Replies 11 replies
  • Subscribers 100 subscribers
  • Views 1084 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 0x80000200/-1070

zhildebr
Prodigy 50 points

I have the TMS320C6710 processor emulated with my probe, and can’t connect to the DSP. I get the following error:

 ‘Error connecting to the target: Error 0x80000200/-1070 Fatal Error during: OCS, An unknown error prevented the emulator from accessing the processor in a timely fashion. It is recommended to RESET EMULATOR. This will disconnect each target from the emulator. The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target. Sequence ID: 0 Error Code: -1070 Error Class: 0x80000200’

 This is the 1st time the error has occurred, and only happens to 1 card. (What was I doing? I was testing out the ability to overwrite the boot.asm file. The card ‘disappeared’ once done, and I can’t talk to it again.)

   CCS version: 3.1.0

 BIOS: cuda-4.90.02.10

code generation tools: v5.1.0 

  • 0
    TI__Genius 14545 points

    Zachary,

     

    There is a good wiki article on emulation which includes some debugging tips. You might want to browse through this to see if your error has a topic already discussed.

    Also - can you let us know which emulator pod you are using in the mean time?

     

     

  • 0 in reply to dabuan
    Prodigy 50 points

    The emulator I use is: Blackhawk lan560

    version 3.1.1.1 09 march 2006

     

    note: the same CCS and emulator setup works on every other DSP I have - and only started failing on the current DSP today.

  • 0 in reply to zhildebr
    TI__Genius 14545 points

    So it only happens to one board, but not the others? Are these TI EVMs, or boards you designed? If they are EVMs you should be able to compare the revision of the EVMs with each other to see if there was a board change and track it back through the schematics provided by the board vendor.

  • 0 in reply to dabuan
    Prodigy 50 points

    These are not TI EVMs.

  • 0 in reply to zhildebr
    TI__Genius 14545 points

    Alright - well then it seems one one of your boards has a hardware issue either through the JTAG interface or one of the DSPs one this board not behaving correctly. If you suspect it's bad device due to silicon issues, please work through your local sales office/distributor to return the device to TI for analysis.

     

  • 0 in reply to dabuan
    Prodigy 50 points

    The board stopped working while I was updating boot.asm on the flash filesystem. Now, the probe can't attach. I'm guessing the boot.asm is in a state that prevents the JTAG connector from working. Are there any steps (grounding a specific pin, etc.) that will stop the DSP from booting, and allow the probe to connect?

  • 0 in reply to zhildebr
    TI__Genius 14545 points

    The only recommendation I have is to try and Power On Reset to reset everything back to the default state, with the Emulator Boot Mode Selected via the Boot Pins, and then attempt to connect to the DSP via the emulator pod. This should reset any register settings that were possibly corrupted. This should prevent the DSP from booting a program other than the bootloader stored in ROM, then sit in a while(1) loop and wait for the emulator to connect. This would be the first step I would try. (Should rule out a device issue)

  • 0 in reply to dabuan
    TI__Guru* 84110 points

    zhildebr,

    Some things are not very clear to me from this thread:

    1. What device are you using? I am not familiar with the TMS320C6710 mentioned at the top of the thread, and I did not find it listed on www.ti.com.
    2. The fact that you are trying to load an assembly file "boot.asm" into a "flash filesystem" implies a very sophisticated Operating System for a fairly old DSP family. Are these loosely phrased terms and you mean that you are trying to write a small section of linked object code into the on-board flash device?

    It does look like your experiment gave you some solid results. The procedure you used will not work. Now how do you recover from the corrupted flash?

    If the DSP is trying to boot from the corrupted flash and it is running in bad code space, some of our older DSPs might have trouble connecting with the emulator. Two things you could try, in addition to what Drew mentions above, are the following:

    • Pull out the Flash device and reprogram it off-board.
    • Change the boot mode to NoBoot or EmulatorBoot or something similar depending on what boot modes are available for your device. Then the emulator may be able to connect and then let you reprogram the Flash using your normal method.

    Regards,
    RandyP

     

    If you need more help, please reply back. If this answers the question, please click  Verify Answer  , below.

  • 0 in reply to RandyP
    TI__Mastermind 41665 points

    One other trick for this kind of thing, if you cannot easily change your boot mode (i.e. a custom board with hard wired boot pins), but you happen to have a reset signal accessible (i.e. reset button) than you can try connecting while holding the device in reset. Trying to connect in reset should bring out a ‘your target appears to be held in reset’ error instead of the error you are getting, at which point if you release the reset and immediately click the reconnect button, it will connect up and you can try reflashing from there, at least I have had this work for me before.

  • 0 in reply to Bernie Thompson TI
    Prodigy 50 points

    Thanks, Bernie.

     

    I do have a custom board with a reset available...after several tries of your suggested steps, I was able to connect and correct the issue. Thanks.