Error Connecting to Target : (Error -1015 @ 0x0) - TMS320F28335

Hi Archana,

Did you check the voltage levels on your board and verified with your schematics? Also, check for any overheating components. These primary checks for verifying proper functioning of the board.
Did you ever reset the board while the controller was being programmed esp. erased?

Regards,
Gautam

Hi Gautam,

All voltage levels on board are fine. DSP is getting clock.

We checked for JTAG settings,  we probed all 14 pins of JTAG and they behave as expected but XRS pin is periodically held low.

We have not reset the board while controller was being erased. Even while turning off the the processor, we first terminate the CCS connection and then power off the board.

 

 

Hi Gautam,

Here is the detailed test information:

Oscillator clock is 50Mhz. Board is configured to 'jump to flash' on power on. We are getting 6.25Mhz as SYSCLKOUT when the controller is pulled out of reset (On power on). Core Voltages are all fine, board is working fine.

When the device is reset externally, SYSCLKOUT measures 3.125Mhz and Jtag Test connection is succeeding but not able to load the program since device is under reset. But it is possible to enter debugg mode. In this condition the following error persists:

C28xx: Failed CPU Reset: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 5.1.507.0)
C28xx: Trouble Reading Register PC: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 5.1.507.0)
C28xx: Trouble Reading Register ST1: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 5.1.507.0)
C28xx: GEL: Error while executing OnReset(1): Target failed to read register ST1  at (ST1&~(C28xx: Failed CPU Reset: (Error -1137 @ 0x0) Device is held in reset. Take the device out of reset, and retry the operation. (Emulation package 5.1.507.0)
C28xx: Flash Programmer: Device is locked or not connected. Operation cancelled.
C28xx: GEL: File: E:\CCS_WORKSPACE_Archana\HBIT\HBIT-IND-CAN\ESC_COMMON_SOFTWARE\TMS320F28335\06_BUILD\SS_320\Debug\SS_320.out: Load failed.

 

When the device is pulled out of reset the following error exists :

Error connecting to the target:
(Error -1015 @ 0x0)
Device is not responding to the request.  Device may be locked, or the emulator connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 5.1.507.0)

 

Regrads,

Archana

 

Archana, seems more like a hardware issue and yes XRS is surely misbehaving! I would like to know, in both the cases you're unable to dump the program right? Also, you've in no way locked the controller previously?

Regards,
Gautam

Controllers locks itself if there is a power failure while programming it esp. erasing it. Secondly we've CSM module where in we can feed in passwords to secure the device. These 2 are the primary causes of device getting locked. For the second condition, we can atleast unlock the device by feeding in the same password but for the first condition the device goes into permanent lock mode.

This being a custom board did you follow the design guidelines of F28335 controlCard? Did you refer the controlcard's schematics while designing?

I am not able to connect to the target at all.... We tried using Test Connection option of CCS .ccxml file. Can you pls. explain how it is related to device lock?
Reply for your above question: We are not able to load the program in both the cases.

I checked map files of the project which I tried loading. It doesn't have any sections linked to the password regions.
When I am not able to connect to target, how to check If password regions are having all zero's?
I pushed device into reset, and tried to load the program. Loading failed, but it could enter debug mode. I checked password regions :0x33FFF8-0x33FFFF. It had values 0x0BAD.
Don't we have a solution for the first case? wherein device is powered off during flash erase?

The design rules and all are followed. The same board was working fine and I have been using this board since 2 months but all of a sudden, couldn't connect to the target.
The only change we made is , we removed power card and gave power directly to processor card.

Archana Kumarraj60 said:

Don't we have a solution for the first case? wherein device is powered off during flash erase?

Nope, you simply have to replace the device.

Regards,

Gautam

But how do I check for the second case? I am not able to connect to target, and hence I can't check the flash locations. If the device is locked, why is xrs going low periodically? Is this behavior expected when device is locked?

I'm not saying the device "is" locked... it may be! Secondly, the controller itself might've got damaged due to user interferences such as ESD or other electrical limitations esp. during ::

The only change we made is , we removed power card and gave power directly to processor card.

Also, as I don't have the schematics I won't be able to comment on how the above would've affected the controller.

Regards,
Gautam

Controller is getting clock, voltage levels are all correct.
Watchdog is disabled in the boot code, but still it is generating reset. But when the device is pushed to reset, I can connect to target but not load the code.
In case the flash is locked, I should not be able to connect to target even when device is in reset right?
And VDD3V3FL is getting 3.3v.

Archana,
Even though watchdog is disable in BOOTROM, if flash secotrs are locked due to which ITRP happens, ITRAP handler will re-enable the watchdog which will fire the reset. After you connect the target, look at the flash content via memory watch window. If you read the flash content as 0x0 then it means device is locked. Let us know what you find.
Regards,Vivek Singh

I am not able to connect to the target at all. Test connection itself is failing.
I am getting the following error message while tryingto load the program:
(Error -1015 @ 0x0)
Device is not responding to the request. Device may be locked, or the emulator connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 5.1.507.0)
Test Connection is failing and the error is as below:
[Start: Texas Instruments XDS2xx USB Emulator_0]Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\ARCHAN~1.KUM\AppData\Local\TEXASI~1\ CCS\ti\0\0\BrdDat\testBoard.dat
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'May 21 2014'.The library build time was '18:02:25'.
The library package version is '5.1.507.0'.
The library component version is '35.34.40.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.
-----[Print the reset-command hardware log-file]-----------------------------
This emulator does not create a reset log-file.
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-233' (0xffffff17).The title is 'SC_ERR_PATH_BROKEN'.
The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.
[End: Texas Instruments XDS2xx USB Emulator_0]

Gautam,

I tried changing Boot pins configuration to mode 3. I couldn't connect to the target. JTAG test is failing. Pls. suggest to me some methods to proceed further with this.

Regards,
Archana

Archana, this seems to be a more complicated issue. Check with CCS Uniflash tool to use other features.

Regards,
Gautam