• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 82 subscribers
  • Views 323 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 in connecting to the target after trying to set the bit OSCOFF (PLLSTS) to 1

athavan sai
Prodigy 200 points
Other Parts Discussed in Thread: UNIFLASH, CONTROLSUITE

Hi,


What I Did:

 I tried to test the function "InitPLL" which resides in the library file "DSP2833x_SysCtrl.c". During the process of testing the line,

if (SysCtrlRegs.PLLSTS.bit.MCLKSTS != 0)
   {
      asm("        ESTOP0");
   }

In order to make the bit MCLKSTS to 1, I made OSCOFF to 1 which resulted in MCLKSTS to 1 and I entered this If condition. But when I tried to flash it again, I am getting an error message like this,

Error connecting to the target:

(Error -1135 @ 0x0)

The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.

(Emulation package 5.0.520.0)

I have attached the recent .out file.


I am afraid that I may not able to connect to the target as something got corrupted. Needed a solution in reconnecting to the target or  Is there anything like reset via the hardware??

  • 0
    Guru 192875 points


    I am afraid that I may not able to connect to the target as something got corrupted. Needed a solution in reconnecting to the target or  Is there anything like reset via the hardware??

    Is this a custom board or dev kit?

  • 0 in reply to Gautam Iyer
    Prodigy 200 points

    This is a development kit.

    Controlcard C2000 with f28335

  • 0 in reply to athavan sai
    Guru 192875 points

    Try this, install CCS Uniflash -> Build some sample project from controlSuite say timed_led_blink -> load the out file using Uniflash. If still you get the error, there's an option of "Unlock" in the software. Try that and do revert with your observations.

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Prodigy 200 points

    Try this, install CCS Uniflash -> Build some sample project from controlSuite say timed_led_blink -> load the out file using Uniflash.

    >> I tried with CCS UniFlash 2.2.0. When I tried to Program -> Load Program --> Example_2833xLEDBlink.out, I am getting the same error message

    "C28xx: Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may one or more of: invalid emulator serial number, blank emulator EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the emulator can be located. (Emulation package 5.1.73.0)"

    After 2 tries I am getting this message,

    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, 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.73.0).

    ============================

    If still you get the error, there's an option of "Unlock" in the software.

    >> Can you please provide me the procedure to do this unlock. Because I tried in Uniflash F28335 Flash Settings --> Code Security PAssword --> Unlock, but it also resulted in the same error.

    Could you able to identify where the error has occured??

  • 0 in reply to athavan sai
    Prodigy 200 points

    Actually I also tried the following,

    Changed the boot jumper settings so that it boots to "Branch to check mode". With that I performed "Test connection". It got succeeded.

    But still the Flash is locked. I am not able to unlock it.

    Is there any way to find the current password from the "OUT" file that was last flashed into this target when it was working?