From: Jaime Andrés Aranguren Cardona on
Luiz,

I don't know too much about the newest ADSP-2136x SHARCs (I'm just
starting with this beast!), but, isn't it possible to get some
information for reading internal memory, etc, from a host port?

Is it mandatory for you to access the DSP via JTAG???

Regards,

JaaC

From: oen_no_spam on
JaaC,

Unfortunately the newers SHARCs don't have a host port. I think this
was a big mistake, and this is my problem.
I was heading a TigerSHARC (TS203), but since it's price changed form
$35 to $47, I'm looking for alternatives.
If I can't debug the SHARC by myself, I can't use it. And the only way
I could find is using the JTAG port.
I don't understand why ADI doesn't publish this information. I don't
think they do a lot of money selling debug pods.

Thanks,

Luiz Carlos

From: oen_no_spam on
Bittware, Danville, anyone?
Is this "top secret" information?

Luiz Carlos

From: Ron Huizen on
We (BittWare) use the ADI emulators for JTAG debug, so have no need to try
to figure out and run the JTAG directly. We also have our own "secret"
method for doing VDSP debug sessions over the PCI bus to our boards.
However, all of our processors (2106x, 2116x, TS101, TS201) have host ports
we can use for this.

You should contact Analog Devices and see if you can sign whatever licenses
and NDAs they may require to get access to this information. It may be much
easier, however, to look at something like their USB emulators, and plug
this into your board and the PC its in (you did say it had a PCI interface)
assuming you're running Windows) and then just use some remote Windows
access software (like NetMeeting).

We support remote VDSP debug sessions over TCP/IP, but it requires one of
our PCI based boards to be in a target system (Windows, Linux, VxWorks)
running our remote server to provide access to the DSPs.

----
Ron Huizen
BittWare

<oen_no_spam(a)yahoo.com.br> wrote in message
news:1119527763.620352.259310(a)f14g2000cwb.googlegroups.com...
> Bittware, Danville, anyone?
> Is this "top secret" information?
>
> Luiz Carlos
>


From: Jim Thomas on
oen_no_spam(a)yahoo.com.br wrote:
> Bittware, Danville, anyone?
> Is this "top secret" information?
>

I don't speak for BittWare, I just happen to work here. But...

I have not done a lot of work with the Tiger family yet, and most of
what I have done has been mundane tasks in C, not requiring a lot of
in-depth knowledge of the chip's architecture.

I cannot comment on the Tiger's lack of a host port - out of ignorance.
I do know that the host /does/ have access to the TigerSHARCs in our
systems.

BittWare does have a host-based debugger for the TS101 and TS201. I
architected this debugger for the Hammerhead family, but a co-worker
implemented it, and then ported it to the TS.

Our debugger plugs into VisualDSP++ and looks exactly like an emulator.
It's all software based, not requiring an emulator pod. It even
supports Tigers plugged into PC's other than the one on which
VisualDSP++ is running (remote target). I have used it, and it works
well. It /is/ therefore possible to debug TigerSHARC code without
connecting to the JTAG.

I have also used it in some complex tool chains. For instance, I run
VisualDSP++ on a WinXP installed on a virtual machine using VMWare. I
do this on my laptop which runs Linux.

The laptop obviously precludes the addition of PCI boards. I have used
our Remote Target package to connect this virtual XP setup to other PCs
running Windows or Linux.

So I can open VisualDSP++ on my laptop and have it open a debug session
on a TS201 (cluster) installed in a box on the other side of the
network. There is no reason it wouldn't work across the Internet too
(although I would expect it to be a tad sluggish).

Which I think is all pretty cool.

To my knowledge, this package is offered only with BittWare hardware.

--
Jim Thomas Principal Applications Engineer Bittware, Inc
jthomas(a)bittware.com http://www.bittware.com (603) 226-0404 x536
Getting an inch of snow is like winning ten cents in the lottery - Calvin
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Configure EClkOut
Next: DC offset removal through FPGA