Error connecting dsp

The reset is controlled from the on-board emulation circuit and the power on reset generated by U9 (TPS767D301).

where ca i see this U9 on the tecnical reference?  did you ever have to do this?? 

Sheet 12 of the schematics on page A-13 of the Technical Reference manual has U9 on it.

If you follow PONRSnIN to sheet 11, it will go into the on-board emulation block (which there are no schematics for due to Spectrum Digital IP).
Out of this block is DSP_RSn, which also comes from a connector (sheet 8) P2 pin 47 and funnels into XRn which connects to the F28335 reset input.

Therefore, on P2.47 is where you might be able to force a reset.

thanks brandon for replay, how can i make this reset, I apply gnd to that point? or is +3.3V?

and for your question about the emulator is the on board emulator that came with the ezdsp28335

Apply ground.

Reviewing the TMS320F28335 datasheet, we will find /XRS is an active low input.  On the schematic, you will see a pullup on the XRn signal.  Momentarily bringing the node low to ground should generate a reset to the device.

Brandon i see the PORNSnIN line that connect to pin 28 of U9, on page A-11 a can`t see DSP_RSn, on page A-8 i still can`t see what you say, i see the processor page and i see XRnW on pin 148 and XRDn on pin 149 and XRSn on pin 80. Could you be more specific please?

Gaston

I apologize for not being clear.  When I was referencing sheets, I was refering to the schematic sheet found in the lower righthand corner of the schematic (ie. title block) and not the page number of the Technical Reference.

PONRSnIN is found on sheet 12 of 14 (page A-13) and sheet 11 of 14 (page A-12).

DSP_RSn is found on sheet 11 of 14 (page A-12) and sheet 8 of 14 (page A-9).

Brandon, thanks, now i see is on page A-11 the DSP_RSn goes to XRSn and that pin connects to pin 80. So if i apply gnd to that pin 80 i will force a reset? is that correct?

This could cause a problem to the target? or emulator? 

Gaston

Gaston said:

Brandon, thanks, now i see is on page A-11 the DSP_RSn goes to XRSn and that pin connects to pin 80. So if i apply gnd to that pin 80 i will force a reset? is that correct?

Yes, pulling this line low should generate a reset to the TMS320F28335.

Gaston said:

This could cause a problem to the target? or emulator? 

It should not cause a problem for the target.

Regarding the emulator, I can't say for sure, as I don't have access to the schematics of that portion of the design.

Brandon, i did it, but the problem is still there.  The emulator not respond. I want to know what is the cause of this. could be the noise?

So probably the best would be The purchase of other one ezdsp28335.  I have another option to reverse this situation?

Well thanks anyway Brandon.

Gaston

I have another question for you:

1) if the emulator does not respond, how is possible that when it restart the ezdsp28335 the dsk startup appears????

2) Is it possible that if I buy an external emulator this problem eliminates?

3) What do you recommend to avoid this problems in the future?

Gaston said:

Brandon, i did it, but the problem is still there.  The emulator not respond. I want to know what is the cause of this. could be the noise?

What noise are you referring to?  Is your ezdsp28335 board completely disconnected from everything except for the 5V input power wall wart and your PC through the USB cable?

In order to eliminate all possible issues, you should make sure you eliminate everything but just the board itself, the power input and the USB cable for the on-board emulation.

Gaston said:

So probably the best would be The purchase of other one ezdsp28335.  I have another option to reverse this situation?

That is certainly a route to take to make sure that you don't have any issues with your PC setup, etc.

I'm not sure if there is another way to reverse this issue without root cause of the problem.

Brandon, i change the USB cable for another and the dsp works fine for a little time, but then again the emulator brings up error. So i guess is the USB cable the problem.

There is a way to use other comunication to the dsp?

An external emulator will work fine?

I konw now that the dsp work fine because in the little time i run an example, so no problem.

The USB connection now is the big problem, so i guess that why the emulator don`t work.

Gaston said:

1) if the emulator does not respond, how is possible that when it restart the ezdsp28335 the dsk startup appears????

I'm not sure I know what you are referencing.  Is it possible to attach a screen capture of what you are observing.

As a method to try to recreate your issues, I have configured CCS (via cc_setup) to target the F28335 eZdsp board.
However, I have disconnected the USB cable from the PC and invoked CCS.  I receive the error message from one of your other  posts as below:

Screencapture said:

Error initializing emulator

I/O Port = 540

Board Name: F28335_eZdsp
Cpu Name: cpu_0

Abort:  Close Code Composer Studio.
Retry:  Try to initialize the emulator again.
Ignore:  Ignore the initialization error and start
  potentially without target debugging access.
Diagnostic: Run diagnostic utility.

Gaston said:

2) Is it possible that if I buy an external emulator this problem eliminates?

Perhaps, if the on-board emulation is faulty, but the target F28335 is not.

Gaston said:

3) What do you recommend to avoid this problems in the future?

I think we need to get to some census on the causes.

Gaston said:

Brandon, i change the USB cable for another and the dsp works fine for a little time, but then again the emulator brings up error. So i guess is the USB cable the problem.

There is a way to use other comunication to the dsp?

You can certainly use an external emulator, although I don't know that it will address the issues you are having.  Do you just have the eZdsp by itself, nothing connected to it?

Gaston said:

An external emulator will work fine?

Again, it is unclear if this is the issue. 

Gaston said:

I konw now that the dsp work fine because in the little time i run an example, so no problem.

The USB connection now is the big problem, so i guess that why the emulator don`t work.

What example are you running?  Is there something else running that may be interrupting operation, like a watchdog timer, etc.?

I seem to recall a series of posts a couple of months ago regarding isolation on the JTAG interface, etc.  Is this perhaps a similar issue due to what you are trying to drive that may be creating an issue here?

This is what happens when i use theother USB cable, code composer like this:

What do you think???

If the emulator was the reason for the error i guess code composer can`t open? right?

i see now that the led in the center is on, so the target is processing something. 

But this time i can't run anything.

This is definitely different that the error you posted here.

I'm having a difficult time relating your observations to the changing of the USB cable.  Perhaps the new one which gets you farther is shielded in some way differently than the other.

So based on this picture, you did have some success connecting to the target via Code Composer, but at some point later in time, this dialog box comes up indicating an error.

Does this occur with every example provided with the C2833x/C2823x C/C++ Header Files and Peripheral Examples (SPRC530)?