Forums

JTAG for Analog Devices SHARC 21469

Started by Mauritz Jameson January 25, 2014
I've developed an application on a SHARC 21469 development board (EZKIT). One of my friends (an electrical HW engineer) has laid out the board for production duplicating everything from the schematics.

When he got to the �communication� part of the schematic (i.e. the daughter board with an ASIC; the one that provides the JTAG USB interface), it says that the AD USB circuitry is proprietary and is left off 
the schematic.

Since AD's USB JTAG interface circuitry is proprietary I have a question for the experienced folks in this group.
  
Excuse me if I'm not using the right lingo, but what kind of circuitry should my friend build to make sure that the code that I developed using VisualDSP can be uploaded to the DSP board he has built ?

I'm not a HW guy. I just know that I need:

- a tool for flashing his board (I assume we can use VisualDSP for that)
- a hardware interface on his board so that I can connect to it via USB from my PC and flash the board

Can I get some advice here? Maybe there's a better solution ? 

Isn't his board also going to need a bootloader ? Some piece of SW which initializes the HW on reset, sets up stuff and loads the program to run from flash??

Thanks !
  


On Fri, 24 Jan 2014 22:42:25 -0800, Mauritz Jameson wrote:

> I've developed an application on a SHARC 21469 development board > (EZKIT). One of my friends (an electrical HW engineer) has laid out the > board for production duplicating everything from the schematics. > > When he got to the “communication” part of the schematic (i.e. the > daughter board with an ASIC; the one that provides the JTAG USB > interface), it says that the AD USB circuitry is proprietary and is left > off the schematic. > > Since AD's USB JTAG interface circuitry is proprietary I have a question > for the experienced folks in this group. > > Excuse me if I'm not using the right lingo, but what kind of circuitry > should my friend build to make sure that the code that I developed using > VisualDSP can be uploaded to the DSP board he has built ? > > I'm not a HW guy. I just know that I need: > > - a tool for flashing his board (I assume we can use VisualDSP for that) > - a hardware interface on his board so that I can connect to it via USB > from my PC and flash the board > > Can I get some advice here? Maybe there's a better solution ? > > Isn't his board also going to need a bootloader ? Some piece of SW which > initializes the HW on reset, sets up stuff and loads the program to run > from flash?? > > Thanks !
I see four questions: "what is all this JTAG stuff?", "how do I flash my board", "how can I connect it to USB", and "don't I need a bootloader?" In order, the answers are: JTAG Stuff: There should be separate JTAG programmers available. They may come from a 3rd party, like MacGregor. Somewhere in the reams of manuals from ADI, it will say. Basically, you buy the gizmo, and you connect to a header on your board. You may want to get onto the DigiKey website and check out some of their other evaluation boards -- if they have one that comes with an external USB to JTAG converter, then you want to buy that converter, and you want your friend do duplicate the connections on that particular board to that particular converter. (Is Al Clark still on the group? He would know. He'd have a board to sell, for that matter.) Flashing: Flashing the board should work pretty much the way it does for your EZKIT, assuming that you get the JTAG stuff right. Connecting to USB: See my answer to the first question. Bootloader: Yes, it does. Usually when you're at the bare metal like this, it's in the code that you flash in. Your tool chain has probably provided it without your knowledge. It may well be that what is in your tool chain will work for your new board. It may not. -- Tim Wescott Wescott Design Services http://www.wescottdesign.com
On Fri, 24 Jan 2014 22:42:25 -0800 (PST), Mauritz Jameson
<mjames2393@gmail.com> wrote:

>I've developed an application on a SHARC 21469 development board (EZKIT). One of my friends (an electrical HW engineer) has laid out the board for production duplicating everything from the schematics. > >When he got to the &#2013266067;communication&#2013266068; part of the schematic (i.e. the daughter board with an ASIC; the one that provides the JTAG USB interface), it says that the AD USB circuitry is proprietary and is left off >the schematic. > >Since AD's USB JTAG interface circuitry is proprietary I have a question for the experienced folks in this group. > >Excuse me if I'm not using the right lingo, but what kind of circuitry should my friend build to make sure that the code that I developed using VisualDSP can be uploaded to the DSP board he has built ? > >I'm not a HW guy. I just know that I need: > >- a tool for flashing his board (I assume we can use VisualDSP for that) >- a hardware interface on his board so that I can connect to it via USB from my PC and flash the board > >Can I get some advice here? Maybe there's a better solution ? > >Isn't his board also going to need a bootloader ? Some piece of SW which initializes the HW on reset, sets up stuff and loads the program to run from flash?? > >Thanks ! > >
http://www.digikey.com/product-detail/en/ADZS-USB-ICE/ADZS-USB-ICE-ND/1141756 Make sure you read the section of the manual on implementing the JTAG interface. Mark
On Mon, 27 Jan 2014 18:15:38 -0800, Mac Decman wrote:

> On Fri, 24 Jan 2014 22:42:25 -0800 (PST), Mauritz Jameson > <mjames2393@gmail.com> wrote: > >>I've developed an application on a SHARC 21469 development board >>(EZKIT). One of my friends (an electrical HW engineer) has laid out the >>board for production duplicating everything from the schematics. >> >>When he got to the &#147;communication&#148; part of the schematic (i.e. the >>daughter board with an ASIC; the one that provides the JTAG USB >>interface), it says that the AD USB circuitry is proprietary and is left >>off the schematic. >> >>Since AD's USB JTAG interface circuitry is proprietary I have a question >>for the experienced folks in this group. >> >>Excuse me if I'm not using the right lingo, but what kind of circuitry >>should my friend build to make sure that the code that I developed using >>VisualDSP can be uploaded to the DSP board he has built ? >> >>I'm not a HW guy. I just know that I need: >> >>- a tool for flashing his board (I assume we can use VisualDSP for that) >>- a hardware interface on his board so that I can connect to it via USB >>from my PC and flash the board >> >>Can I get some advice here? Maybe there's a better solution ? >> >>Isn't his board also going to need a bootloader ? Some piece of SW which >>initializes the HW on reset, sets up stuff and loads the program to run >>from flash?? >> >>Thanks ! >> >> >> > http://www.digikey.com/product-detail/en/ADZS-USB-ICE/ADZS-USB-ICE-
ND/1141756
> > Make sure you read the section of the manual on implementing the JTAG > interface.
That's exactly what I was recommending you find, but I was too lazy to go dig it up myself. -- Tim Wescott Wescott Design Services http://www.wescottdesign.com
On Mon, 27 Jan 2014 23:37:36 -0600, Tim Wescott
<tim@seemywebsite.really> wrote:

<snip>
>>> >> http://www.digikey.com/product-detail/en/ADZS-USB-ICE/ADZS-USB-ICE- >ND/1141756 >> >> Make sure you read the section of the manual on implementing the JTAG >> interface. > >That's exactly what I was recommending you find, but I was too lazy to go >dig it up myself.
Well Tim, I've been making these boards for years so I know the tools all too well. With a simple audio design, the rework on the layout from the AD reference is minimal. But you do have to have the real JTAG done correctly, because it is never production ready on their demo boards. Mark
On Mon, 27 Jan 2014 22:27:52 -0800, Mac Decman
<dearman.mark@gmail.com> wrote:

>On Mon, 27 Jan 2014 23:37:36 -0600, Tim Wescott ><tim@seemywebsite.really> wrote: > ><snip> >>>> >>> http://www.digikey.com/product-detail/en/ADZS-USB-ICE/ADZS-USB-ICE- >>ND/1141756 >>> >>> Make sure you read the section of the manual on implementing the JTAG >>> interface. >> >>That's exactly what I was recommending you find, but I was too lazy to go >>dig it up myself. > >Well Tim, I've been making these boards for years so I know the tools >all too well. With a simple audio design, the rework on the layout >from the AD reference is minimal. But you do have to have the real >JTAG done correctly, because it is never production ready on their >demo boards. > >Mark
I'll also add, not sure on 469 board, but in the past, the ground plane wasn't the best in the reference design. Might want to rethink that if you're going to put AD/DA on there. Mark
Thanks for the link, but which manual?

Also, I'm trying to avoid having to pay >$1000 for a USB interface.

>http://www.digikey.com/product-detail/en/ADZS-USB-ICE/ADZS-USB-ICE-ND/1141756 >Make sure you read the section of the manual on implementing the JTAG >interface.
I could have jumped in earlier but I have been traveling all 
week.

You are correct that ADI does not share JTAG ICE (or debug 
agent) schematics.

If you have a full license of Visual DSP++ or CrossCore Studio 
then you could use an ADI ICE. This would be fine for small 
runs but not production since the ICE cable will wear out (and 
is expensive)

If you have brought out the JTAG connections to a header (see 
ADI EE-68), you can use a Danville dspFlash programmer. It was 
designed for this purpose. I don't think there is another 
programmer for SHARC aside from ADI ICE. ADI asked us to 
create this product and so we know the secret sauce necessary 
to use the JTAG. This is all proprietary to ADI, so no I won't 
share any of the details.

Here is a link:

http://www.danvillesignal.com/analog-devices-development-
tools/dspflash-sharc-blackfin-programmer.

We also sell ADI tools including Visual DSP, CCES & ICE.

Our dspblok modules are another alternative. These all include 
a built in bootloader that programs the flash usually via USB, 
but also Ethernet, SPI or UART. In this case, you just use a 
PC.

You can check our site for SHARC based dsp boards if you like.

Al











Tim Wescott <tim@seemywebsite.really> wrote in
news:ZeudnQ5WZIqiGHjPnZ2dnUVZ5sSdnZ2d@giganews.com: 

> On Fri, 24 Jan 2014 22:42:25 -0800, Mauritz Jameson wrote: > >> I've developed an application on a SHARC 21469 development >> board (EZKIT). One of my friends (an electrical HW >> engineer) has laid out the board for production >> duplicating everything from the schematics. >> >> When he got to the &ldquo;communication&rdquo; part of the >> schematic (i.e. the daughter board with an ASIC; the one >> that provides the JTAG USB interface), it says that the AD >> USB circuitry is proprietary and is left off the >> schematic. >> >> Since AD's USB JTAG interface circuitry is proprietary I >> have a question for the experienced folks in this group. >> >> Excuse me if I'm not using the right lingo, but what kind >> of circuitry should my friend build to make sure that the >> code that I developed using VisualDSP can be uploaded to >> the DSP board he has built ? >> >> I'm not a HW guy. I just know that I need: >> >> - a tool for flashing his board (I assume we can use >> VisualDSP for that) - a hardware interface on his board so >> that I can connect to it via USB from my PC and flash the >> board >> >> Can I get some advice here? Maybe there's a better >> solution ? >> >> Isn't his board also going to need a bootloader ? Some >> piece of SW which initializes the HW on reset, sets up >> stuff and loads the program to run from flash?? >> >> Thanks ! > > I see four questions: "what is all this JTAG stuff?", "how > do I flash my board", "how can I connect it to USB", and > "don't I need a bootloader?" > > In order, the answers are: > > JTAG Stuff: > > There should be separate JTAG programmers available. They > may come from a 3rd party, like MacGregor. Somewhere in > the reams of manuals from ADI, it will say. Basically, you > buy the gizmo, and you connect to a header on your board. > > You may want to get onto the DigiKey website and check out > some of their other evaluation boards -- if they have one > that comes with an external USB to JTAG converter, then you > want to buy that converter, and you want your friend do > duplicate the connections on that particular board to that > particular converter. > > (Is Al Clark still on the group? He would know. He'd have > a board to sell, for that matter.) > > Flashing: > > Flashing the board should work pretty much the way it does > for your EZKIT, assuming that you get the JTAG stuff right. > > Connecting to USB: See my answer to the first question. > > Bootloader: > > Yes, it does. Usually when you're at the bare metal like > this, it's in the code that you flash in. Your tool chain > has probably provided it without your knowledge. It may > well be that what is in your tool chain will work for your > new board. It may not. >
--- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com
On 2/1/14 1:42 PM, Al Clark wrote:
> I could have jumped in earlier but I have been traveling all > week. >
you a busy dude.
> You are correct that ADI does not share JTAG ICE (or debug > agent) schematics.
> ...
> This is all proprietary to ADI, so no I won't > share any of the details.
ya know what seems odd to me, Al. it seems to me that, if ADI wants to sell chips, they would make the whole SHArC JTAG protocol thing public. i don't get why not. -- r b-j rbj@audioimagination.com "Imagination is more important than knowledge."
On Sat, 01 Feb 2014 21:28:53 -0500, robert bristow-johnson
<rbj@audioimagination.com> wrote:

>On 2/1/14 1:42 PM, Al Clark wrote: >> I could have jumped in earlier but I have been traveling all >> week. >> >you a busy dude. > >> You are correct that ADI does not share JTAG ICE (or debug >> agent) schematics. > > ... >> This is all proprietary to ADI, so no I won't >> share any of the details. > >ya know what seems odd to me, Al. it seems to me that, if ADI wants to >sell chips, they would make the whole SHArC JTAG protocol thing public. > >i don't get why not.
Security. Eric Jacobsen Anchor Hill Communications http://www.anchorhill.com