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/-1063

I have a boards that use a TMS320C6713 and about 50% are giving me the error Error 0x80000200/-1063 when trying to connect in CCS using a Spectrum Digital emulator.

When you try to connect the error alternates between the following:

First this:

Error connecting to the target:

Error 0x80000200/-1063

Fatal Error during: OCS, 

Bad Target Silicon Revision Number

Please check your multi-processor configuration.

The number of devices in the JTAG scan path

must be correct for the silicon revision to be read.

Or, you may have selected the wrong DSP device driver.

Sequence ID: 0

Error Code: -1063

Error Class: 0x80000200

I/O Port = 378

Board Name: C671x PP Emulator

Cpu Name: cpu_0

 

Followed by this on the next attempt to connect:

Error connecting to the target:

Error 0x80000200/-1072

Fatal Error during: OCS, 

PTI_ERR_TARG_STATE Error Occured at 0x00E7E000

Sequence ID: 0

Error Code: -1072

Error Class: 0x80000200

I/O Port = 378

Board Name: C671x PP Emulator

Cpu Name: cpu_0

Abort: Close Code Composer Studio.

Retry: Try to connect to the target again.

Cancel: Remain disconnected from the target

Diagnostic: Run diagnostic utility.

 

The Spectrum Digital SDConfig utility correctly sees the scan chain as follows:

-- Found JTAG IR length of 46 

-- Found 1 JTAG device(s) in the scan chain

 

I am using

CCS 3.3.38.2

IDE 5.98.0.219

BIOS 5.31.2

Code Generation Tools v6.0.8

 

I am not sure where to look to get fix this.  Some of the boards do connect but most do not.

 

  • Clifford Gano,

    Since your emulator works with some boards, your CCSetup and emulator settings must be correct.

    This means that the difference between one board connecting and another board not connecting must be a difference between the boards.

    Check voltages on the DSP power supply. Check the reset signals on the DSP. Check the voltage levels on the JTAG connector.

    Does SDConfig identify the DSP as C6713 when it is able to see the scan chain?

    Regards,
    RandyP

  • The voltages on the DSP and at the JTAG connector are both good.

    Spectrum Digital told me that SDConfig cannot identify processors but gave me this reply when I told them what SDConfig reported back to me.

    "SDConfig cannot identify the processor, however, again, it has identified the correct IR length for one C6713 DSP in the JTAG scan chain."

     

  • We can see what the emulation experts say on the Code Composer Forum. I will request this thread be moved there since it is more related to emulation than to the DSP.

    My recommendation is still to look for differences between the boards. Look at the JTAG signals when trying to connect, especially TCK and TDO (out of the DSP at the connector). Since everything works from the PC to the JTAG connector on some boards and not on others, it strongly points to a problem on the failing boards and not in your emulation setup.

    But the CCS team might be able to explain why SDConfig can see the scan chain but CCS cannot get good data from it.

    How many boards pass and how many boards fail exactly this way?

    How many boards fail in other ways?

    Regards,
    RandyP

  • I do not see a place to attach pictures but I do have logic analyzer captures to TDI, TMS and TDO.  I can see the data being returned between the 2 at startup does not appear exactly the same.

     

    Out of 20 boards 7 passed and 13 failed in that manor.

    The boards that passed fail in other ways for some not seeing audio clocks and others with a problem either above or below the 2Meg area of the DRAM.

    I also have 3 boards that can run in emulation mode and pass audio but when the flash is programmed do not start.  Checking in CCS we could see that after a reset the core registers are not set to 0.

  • Thank you for your help.

    I have discovered the problem is with the initialization of the reset line after power on.

     

  • Dear Clifford,

    I am experiencing a similar problem with a custom board with C5505. Could you please elaborate on the problem that you discovered with your boards?

    Regards

    Abhishek

  • Abhishek,

         The solution was to put a resent generator on the reset line to the DSP.  This reset generator will issue a reset after the all required power voltages were at a stable level.  This reset would then ensure the states of all configuration pins during the reset sequence.  This is what solved my problem.  I have no longer experienced this issue since fixing this.

     

    - Cliff

  • Interesting, because on my board, i have a mistake where the reset ic senses the 3.3V instead of Vcore(1.3V). It was a mistake in the schematic! 

    So essentially the reset is issued before the core voltage is stable. 

    Maybe that is the reason of the problem! 

    However, the board passes all the dbgjtag tests, so its a bit unclear

    Thanks

    Abhishek

  • If you have a pull-up on the reset line, try to manually force a reset on the ground line using a wire or pair of tweezers.  Then try to connect via CCS after the manual reset was asserted.  If this is your problem you should be able to connect after doing this.

  • Thanks Clifford! I do have a pull up on the reset line, will do and tell you if it works :)

  • Clifford,

    My problem is solved ! 

    Turns out all i had to do was keep the reset pin grounded on power-up and Hi-Z after that.

    Thanks for the help !

    Abhishek