WEBENCH® Tools/TMS320F28379D: My Debug Probe just disconnected everytime I use EMIF

Hi Eric,

1st. Since this is EMIF related, are there a specific EMIF setting (Hold time, Set up time ect.) will cause this kind of problem?

No, these settings should not cause such issue. Are you using WAIT feature? If an access if hang due to not ready then CCS may give some error but still connection should not be broken.

2nd. Are there a better debugger than XDS110 that will not have this issue?

This does not look like debug probe issue.

Have you checked the board to make sure toggle on EMIF signals are not causing any issue on JTAG signals?

Regards,

Vivek Singh

Hi, Vivek

1st. I tried to use both wait feature and disable the wait feature, it does not seems to make any difference. However, it is definitely EMIF related.

2nd. The EMIF bus and JTAG signals did not share the same pins on the DSP, are you worried about there are some crosstalk between the signals? Here is my schematic for JTAG connection:

For this kind of error

"Trouble Halting Target CPU: (Error -1135 @ 0x8B0F) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 9.1.0.00001)
C28xx_CPU2: Unable to determine target status after 20 attempts"

Do you have any suggestion which signal might be the one get corrupted? Any suggestion if I need to add pull up/down resistor or add capacitors?

3rd. My program runs fine even when the debug probe had problem. It is hard to say it is definitly not the probe. TI does have several type of debug probe, and the XDS110 is the most cost efficient one. There are probes much more expensive, do you think I should give it a try or you think it doesn't matter?

Thanks

Eric

A little update with the schematic I provided you.

The C9 = 1000pF, and R13 = 1.0K ohm

Hi Vivek,

I am Curtis Randall, the other engineer in the company. I have the EXACT same issue with the TMS320F28379D and XDS110 Debug Probe. 

I am working on a different project, schematic, PCB and with different EMIF settings.

Thanks,

Curtis

Hi,

It is unlikely that issue is related to XDS110 but if you have a different debug probe (other than XDS110), could you try that and see if you face same issue. We have not seen this issue on our setup  but I have personally not used XDS110 with this specific case.

Regards,

Vivek Singh  

Hi,

Were you able to try other debug probe ?

Regards,

Vivek Singh

Hi Vivek,

I tried two XDS110 Debug Probes, both with the same issue.

Some of the EMIF signals are close to the JTAG connector. These signals will be moved with a PCB board turn, I hope this solves my issue, but will not happen soon.

Thanks,

Curtis

Curtis,

You can also try to slow down the speed of both the EMIF interface and the XDS110 to see if the issue improves.

Another thing you can try is to change the PINMUX configuration of the EMIF signals from EMIF to GPIO output, and toggle them to emulate EMIF activity.  If the GPIO toggling causes the debug probe to disconnect, it will be easier to isolate the issue.

-Tommy

I have tried slowing down the EMIF and XDS110, with no help.

I only have an issue if both CPU1 and CPU2 are using the EMIF. With only CPU1 or only CPU2 using the EMIFI have no issue.

When I debug I only allow one CPU to run and no issue.

My application continues to run just fine with both CPU1 and CPU2 using the EMIF. Only the XDS110 disconnects.

Hi,

I only have an issue if both CPU1 and CPU2 are using the EMIF. With only CPU1 or only CPU2 using the EMIFI have no issue.

Thanks. When CPU1 and CPU2 using the EMIF, is there any additional settings or memory range used compare to when one CPU is using the EMIF. If not then it is not board issue.

Is it possible for you to send us a sample project which we can run on our setup and see if we could reproduce the same issue?

Regards,

Vivek Singh

Hi Curtis,

Is this issue resolved? If not, can you provide the same project as requested in last post ?

Regards,

Vivek Singh