• State
  • Replies 18 replies
  • Subscribers 83 subscribers
  • Views 281 views
  • Users 0 members are here
Support feedback
Options
Options
Related

TMDSCNCD280039C: Error connecting to the target: (Error -1015 @ 0x0)

Zach Pan
Prodigy 10 points
Part Number: TMDSCNCD280039C
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Working with TMDSCNCD280039C. Everything was working 1 month ago, Come back this project found that the program can not be loaded with Error-1015

Test connection in target configuration with no failure. And blue LED2:A is blinking during the test. LED3:A is always on when powered up. 

Did some research on this and checked the DIP switch states

S1:A  position1, ON
S1:A  position2, OFF

S2  position1, ON up
S2  position2, OFF down

But I remembered when it worked last month. it was S2 position 1 OFF and S2 position 2 ON. it does not make sense to me, but it worked, so I did not complain. This time I tried all S2 position combination, all gives me same error. 

A lot of reference suggests the device is locked and to use UniFlash. But have same error.

Nothing major changed since 1 month ago.  What could be the problem? Any suggestion?

I am using CCS 12.5.

  • 0
    TI__Genius 11405 points

    Hello,

    I have a couple of clarifying questions:

    1. Did you program any DCSM configurations on the device? 
    2. Are you using the on-board XDS110 emulator or an external debug probe? 
    3. Are you powering the card via the 5V port on a baseboard or through the USB-C?

    Best,

    Matt

  • 0 in reply to Matt Kukucka
    Prodigy 10 points

    1. I did not program any DCSM configurations 

    2. I am using on-board XDS110 emulator

    3. I am powering the card vis USB-C.

    Thank you for your help. 

  • 0 in reply to Zach Pan
    TI__Genius 11405 points

    Hello,

    Can you try using an external debug probe (via the baseboard) and see if you're able to connect? I'd like to isolate the problem between the MCU and the JTAG circuitry. 

    Best,

    Matt

  • 0 in reply to Matt Kukucka
    Prodigy 10 points

    I do have one baseboard, but I dont have any external debug probe. any other way I can try? Do that "test connection" results tell anything?

  • 0 in reply to Zach Pan
    TI__Genius 11405 points

    Hello,

    That is true, test connection verifies that the JTAG signals are connected correctly.

    Can you try putting the device in wait boot and try unlocking the device with the default passwords in UniFlash or CCS? If your project does not contain any passwords and you are unable to connect to the device now, I wonder if your device got locked accidentally. 

    Best,

    Matt

  • 0 in reply to Matt Kukucka
    Prodigy 10 points

    Can you be more specific on how to get put it in "wait boot" mode and how to unlock with the default password?

    I tried UniFlash. it recognizes the TDS110 and the board. Then when I click Erase Flash, same error -1105 Error, as posted in the original post.

    Any other ways I can try?

  • 0 in reply to Zach Pan
    TI__Genius 11405 points

    Hello,

    Please set S2 to wait boot, following this table (position 1: up, position2: down). Wait boot mode puts the device in a known state in the boot ROM and is the most compatible for JTAG connectivity. 

    In UniFlash, go to "Settings & Utilities" and scroll down to "Security Settings". Click on "Fill Security Fields from Target".

    Scroll down to "JTAGLOCK". What value is loaded here?

    Scroll down a bit more to "CSMPSWD". What are the values?

    Then, select "Unlock". Does the operation succeed? If so, can you connect to the device now?

    Best,

    Matt

  • 0 in reply to Matt Kukucka
    Prodigy 10 points

    same error after "Fill Security Fields from Target"

    Same error if I try to click "Lock" or "Unlock"

  • 0 in reply to Zach Pan
    TI__Mastermind 27770 points

    Hi Zach,

    It sounds like the device was unintentionally locked due to a power failure during programming. I'm checking with another member of our team to see if this could permanently lock the device.

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    TI__Mastermind 27770 points

    HI Zach,

    Could you also try and see if the same issue occurs in the CCS On-Chip flash tool?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 10 points

    Can you give me an instruction on that? Thanks

  • 0 in reply to Luke Jones
    TI__Genius 11405 points

    Hi Zach,

    To add on to what Luke is saying, I shipped myself a TMDSCNCD280039C and had no difficulty connecting to the device in UniFlash v9.1 with the same SW configurations.

    This supports that your device seems to have been accidentally locked.

    Best,

    Matt

  • 0 in reply to Zach Pan
    TI__Genius 11405 points

    Hi Zach,

    Put the device in Wait boot (SW2 position 1 high, SW2 position 2 low) to put the device in a known state and connect to the device in CCS. Then, go to Tools > On-Chip Flash. A similar GUI to UniFlash will pop up, where you can load the security configurations, lock/unlock the device, etc.

    Best,

    Matt

  • 0 in reply to Matt Kukucka
    Prodigy 10 points

    Thanks. I also ordered a new control card. The new control card has no issue connecting, same as when I tried the old card 1 month ago for the first time.

    So it does look like it is accidentally locked. Now my question is 1)what could cause that so I can avoid doing that in the further. I dont remember doing anything out of norm 2)Is the card permanently "bricked", Any way to unlock the card?

  • 0 in reply to Matt Kukucka
    Prodigy 10 points

    Still error, but without code.

  • 0 in reply to Zach Pan
    TI__Mastermind 27770 points

    Hi Zach,

    To clarify, you ordered a new card which you were able to connect to, but you're unable to connect after attempting to program the same .out from your original post?

    Thank you,

    Luke

  • 0 in reply to Luke Jones
    Prodigy 10 points

    I can connect to the new control card. I tried CCS on chip flash on the old control card.

  • 0 in reply to Zach Pan
    TI__Mastermind 27770 points

    Hi Zach,

    Understood, to avoid bricking any parts in the future I would make sure you do not interrupt the flash erase or programming process by disconnecting the debugger from your laptop or the device and make sure sufficient current is being supplied to the device for flash operations. On a control card this should always be the case as long as you have a reliable power supply. On a custom board you will need to refer to the device datasheet to make sure your external LDO (if used) is always able to provide sufficient current for flash operations in addition to any other operations that may be performed by the device in parallel.

    Thank you,

    Luke