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.

CCS/LAUNCHXL-F28379D: IcePick_C_0: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register.

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: TMDSCNCD28027, C2000WARE, TMS320F28379D, TMDSEMU110-U, TMDSHVRESLLCKIT

Tool/software: Code Composer Studio

Hi.  I have a new LAUNCHXL-F28379D.  I have cannot debug the demo program.  I get this error:

IcePick_C_0: Error connecting to the target: (Error -2131 @ 0x0) Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.1.0.00007)

I am using an installation of Code Composer Studio version 9.0.1.00004.  I have successfully used this installation with the F28027 lauchpad, the TMDSCNCD28027 control card, and the the F28069M launchpad over the last 6 months.

  • I plugged the launchpad into the USB.  The demo program started.  I configured a serial terminal on the PC and confirmed that the serial communication was working.
  • I downloaded C2000Ware v:2.00.00.03, and imported the launchxl_f28379d project into the IDE.
  • I checked the target configuration.  The TMS320F28379D.ccxml is active.  I tried the Test Connection and it returned no errors.
  • I checked the boot configuration switches.  All three are in the up position.
  • I clicked the debug icon in the IDE.  The project builds OK, but will not load.  I get the error I copied above.
  • I reset the launchpad.  I power cycled it.  No difference.
  • I set TCLK to 100kHz.  No difference.

I am out of ideas.  What can I do to fix this problem?

Thanks,

Ciaran

  • Here is more info on the problem.

    First, the results from yesterday were confused by the fact that I had a second XDS100v1 device still attached to the computer by USB.  I get different results with the second device disconnected.  Here are my current observations:

    1. I have a second LAUNCHXL-F28379D LaunchPad, previously unused.  I tried it and it works fine.  The program loads and runs and I can debug it.  So the problem is unique to the first LAUNCHXL-F28379D LaunchPad.
    2. The bad LaunchPad does not show up properly in device manager.  There are no "Texas Instrument Debug Probes" devices listed, and no "XDS100 Class USB Serial Port" listed under Ports.  I get those things with the good LaunchPad, as well as several other types of C2000 devices with XDS100 debuggers that I have on hand.
    3. I tried looking at the FTDI using the MPROG 3.5 program as described here.  I previously had to reprogram the FTDI on a F28069 LaunchPad per the instructions at the link.  

      Device Scan reports:
      Number Of Blank Devices = 1
      Number Of Programmed Devices = 0

      Tools: Read and Parse reports:
      ERROR - Read EEPROM failed Device 0

      This does not match the conditions in the instructions on programming the FTDI in the link.

    4. I decided to try using MProg to reprogram the bad Launchpad anyway. 
      1. I read the configuration from the good Launchpad, and saved it in a file.  
      2. I plugged in the bad Launchpad, and opened the saved configuration.
      3. I did Device: Erase.  I got this result:
        Erase successful Device 0
      4. I did Device: Program.  I got a popup error saying:
        Error reading device.

    So it seems to me that I've got a Launchpad with a bad FTDI chip.  Anything else I can try?

    Also, I do have a standalone TI XDS110 Debug Probe TMDSEMU110-U.  Is there any way I can use it with the bad Launchpad?

    Thanks,

    Ciaran

  • Ciaran,

    Can you check the Control Panel? The reason is that, if the XDS100v2 is not programmed with the correct VID/PID, it may use standard FTDI devices that work well with a terminal program.

    Check sections 2.6 and 5.2.2 of the XDS100 page for details about the instantiation on the Control Panel and the correct VID/PID. For your convenience, I also send attached the template for the FT_Prog utility. 

    Hope this helps,

    Rafael

    F28379D_LAUNCHXL.zip

  • Rafael,

    when you say "Control Panel", do you mean Device Manager?  The bad Launchpad looks like the Not Properly Installed example in the XDS page under "Q: How can I check if the VID/PID for the EEPROM are programmed correctly?

    I had no luck reprogramming it with MProg, but I tried using FT_Prog using the template you attached.  It doesn't work.  When I scan the chip after programming, it shows this:

    That's AFTER programming, but it looked the same before programming.  BLANK DEVICE, and No EEPROM detected.

  • Ciaran,

    Just to confirm the process, can you check the folloiwng short clip?

    https://youtu.be/vZaF5ckf3OQ 

    - Open FT_Prog and then open the template file (menu File --> Open Template)
    - Then issue a "Scan and Parse" (menu Device --> Scan and Parse). At this point you should have something like: 

    - Then, right click on the highlighted Device entry above and apply template
    - After that, program the device (menu Devices --> Program)

    If you followed all this, then I really suspect the board is at fault and you should return it to the distributor. 

    Regards,

    Rafael

  • desouza said:

    Just to confirm the process, can you check the folloiwng short clip?

    https://youtu.be/vZaF5ckf3OQ 

    Thanks for confirming the process.  Yes, I did it just like shown in the video.

    desouza said:
    - Open FT_Prog and then open the template file (menu File --> Open Template)
    - Then issue a "Scan and Parse" (menu Device --> Scan and Parse). At this point you should have something like: 

    As you can see, I get "No EEPROM Detected" instead of "93C56 EEPROM" for the EEPROM type.

    desouza said:
    - Then, right click on the highlighted Device entry above and apply template
    - After that, program the device (menu Devices --> Program)

    When I do that, nothing changes.  When I rescan it, it still says  "No EEPROM Detected" and the settings are the same.

    desouza said:
    If you followed all this, then I really suspect the board is at fault and you should return it to the distributor. 

    I'll do that.

    I've had bad luck with the C2000 hardware.  The first TMDSHVRESLLCKIT I bought had a faulty F28027 controller card.  I took me a while (with E2E help) to resolve that problem.  

    Thanks for the help,

    Ciaran