Custom XDS110 error: DFU_ERR_UNKNOWN (-4)

Hello Joseph,

What device are you using the XDS110 with?

Thanks,

~Leonard  

Hi Leonard,

The XDS110 is using a TM4C1294NCPDT chip. I am hooking it up to flash an TMS320F28388D.  I am able to flash successfully with an XDS100 hooked up to the TMS320F28388D.

Joseph,

You are connecting external xds110 emulator on TMS320F28388D+dock station or it is your custom board which has xds110 on board?

Thanks & Regards,

Santosh

Hi Santosh,

Yes, it's an external xds110 emulator on a separate custom board. The TMS320F28388D is also on a custom board. The XDS100 that worked to flash our TMS320F28388D was also on a separate custom board.

Thanks,

Joseph

Joseph,

Can you please take a look at this readme file which is part of CCS installation? It lists steps to debug xds110.

c:/ti/ccs1110/ccs/ccs_base/common/uscif/xds110/XDS110SupportReadMe.pdf

Thanks & Regards,

Santosh

Thank you Santosh for the suggestion. I do have that ReadMe open. The commands such as setting the serial number or trying to follow the steps under "Recovering a Bricked XDS110 without JTAG" give me the error DFU_ERR_UNKNOWN (-4). What does this error mean?

I can look into seeing if we can update the board so that I can attempt the steps under "Updating Firmware Using a JTAG Connection" to see if I can flash the boot_loader.bin to Flash Address 0x0000. Do you think that option may work for us?

Thanks,

Joseph

Joseph,

Did you try to update the firmware first, before updating the bootloader? What is the firmware version it it using?

I just checked on my setup and it has firmware_3.0.0.19.bin. Do you have same version? 

Thanks & Regards,

Santosh

Santosh,

I tried updating the firmware but it fails and gives me the same DFU_ERR_UNKNOWN (-4) being reported during file download. I have firmware_3.0.0.16.bin.

Thanks,

Joseph

Joseph,

What is the output of "xdsdfu -e" ? 

You do not have any other xds110 connected to your laptop, right? If you have more than one xds110 connected, please disconnect them.

Thanks & Regards,

Santosh

Joseph,

Is this new xds100 or it was workin before with other hardware and stopped working?

Thanks & Regards,

Santosh

Santosh,

Here is the output of "xdsdfu -e" command:

There are no other xds110 connected to the laptop. The custom xds100 does work. The custom xds110 is new and hasn't worked yet.

Thanks,

Joseph

Joseph,

Can you program serial number as per the ReadMe document? or you have tried already?

Thanks & Regards,

Santosh

Santosh,

Trying to program the serial number gives me the DFU_ERR_UNKNOWN (-4) as well.

Thanks,

Joseph.

Joseph,

Is this new XDS110 you just bought or it was working before and stopped working?

Thanks & Regards,

Santosh

Santosh,

This is a new, custom XDS110. It has not worked yet.

When I first got it, I plugged it into my Windows Computer and it showed up as a Stellaris Device Firmware Upgrade in Windows Device Manager. According to the ReadMe, it suggests trying to use the xdsdfu command to flash the boot_loader.bin. I attempted that step, got the DFU_ERR_UNKNOWN (-4).

Thanks,

Joseph

Joseph,

Is this your custom XDS110 board or you bought XDS110 from TI?

I am not sure why it is seeing as "Stellaris Device".

Thanks & Regards,

Santosh

Santosh,

This is our custom XDS110 board. It has not worked before.

Thanks,

Joseph

Joseph,

Have you already followed the instruction at to reset, and flash the bootloader?

https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_xds110.html#flashing-the-bootloader

Thanks & Regards,

Santosh

Santosh,

I did not do steps 2-4 in that section, as the XDS110 already reported as being in DFU Mode when I plugged it in. Do I need to perform those steps? I did attempt steps 5 and 6. Step 5 is able to see the XDS110. Step 6 fails partway with DFU_ERR_UNKNOWN (-4).

Joseph

Joseph,

Yes, agree. It is already in DFU mode, so not needed. Is your design of your custom debugger is based on Launchpad? 

Thanks & Regards,

Santosh

Santosh,

It is based off the onboard debugger on the TMDX654IDKEVM. If you go to page 26 of the schematic for that board (schematic_zip), we pretty much used that circuit when designing the board.

Joseph

Joseph,

I am forwarding the thread to the AM65x group if they can help in this one.

Thanks.

Santosh

Santosh,

Thanks for doing that. I'll let you know if I make any breakthroughs in the mean time.

Joseph

Hello Santosh Jha/Joseph, 

Thanks. Let me check if the  debugger on the AM65 board has any known issues. There are no issues as far as i know.

Can you help me understand the basis for reusing the AM65 debug circuit ?

Regards,

Sreenivasa

Hello Sreenivasa,

  I used the debugger circuit on the base boards that the Processor plugs into.  Our Processor board with the AM6548 and connections, will be underneath the main board and impossible to get to in the field.  Instead of running the Jtag signals through several connectors I decided to use the debugger circuit on the EVM board.  Is there a reason NOT to use the debugger circuit on the EVM?

Regards,

Edward

Hello Edward

Thank you for the explanation and now i understand that this is a platform based on AM65. Using the XDS  should be fine.

We have not seen any issues with the debugger. Do you see the com ports coming up on the control panel for the XDS interface.

Let me check internally if we have some additional suggestions.

Regards,

Sreenivasa

Hi Kallikuppa,

When we plug in the XDS Interface, it does not show up in Device Manager under the COM Ports, but instead shows up as a Stellaris Device Firmware Upgrade. We have tried to perform some of the steps suggested in the ReadMe as well as the web page, but the steps are giving us an error DFU_ERR_UNKNOWN (-4) and not completing.

Hello Edward

Thank you for the inputs. I assume you have verified the behaviour on multiple boards.

Did you have a chance to get the schematics verified from TI ?

Regards,

Sreenivasa

Hello Edward

Could you please follow the thread.

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/831944/ccs-not-able-to-find-the-device-name-in-the-ccs-9-1-0-version/3077324?tisearch=e2e-sitesearch&keymatch=am65%252520xds110#3077324

Regards,

Sreenivasa

Hi Kallikuppa,

I have tested this on multiple boards we have built and they all report the same error. I double-checked this morning as well just to confirm.

I do not believe we have verified our schematics with TI.

Thank you for the link to the thread. We are able to see and select the checkbox for AM65xx devices in CCS. However, testing the target configuration with the XDS110 Selected fails, stating that either no XDS110 was plugged in or that it had no serial number set. The serial number that is returned by running any of the xdsdfu command is 00000000. I can't set the serial number because the command returns an DFU_ERR_UNKNOWN (-4).

Thanks,

Joseph

Hello Joseph

Thank you for the inputs. 

I have a quick question - have you tested the same on an AM65 EVM.

Can you please help me understand the version of the AM65 schematics that you referenced to design the board.

Regards,

Sreenivasa

Hi Kallikuppa,

No, I have not tested the built-in XDS110 on the AM65 EVM. Here is my previous comment about the schematic we referenced.

Joseph Keene said:

It is based off the onboard debugger on the TMDX654IDKEVM. If you go to page 26 of the schematic for that board (schematic_zip), we pretty much used that circuit when designing the board.

Thanks,

Joseph

Hello Joseph

Thank you for the note. Do you have an AM65 EVM in hand and would it be possible to do a quick check if you have an EVM.

There are 4 A, B, E3, E4  version of the board. I would want to understand the version you have referenced. 

...

Regards,

Sreenivasa

Hello Joseph

Please reply for the above query.

Regards,

Sreenivasa

Hi Sreenivasa,

Sorry for the delayed response. When we went to review the schematic, we discovered some errors. We are updating the schematic and then going to bring in another board to test out. I'll update here with results. I believe we are trying to match the version A of the board.

Thanks,

Joseph