Hi all ,
Could Flash be programed with out ICE , Like boot the Blackfin from SPI and
then program the flash from SPI .
--
Thanking you
With best regards and wishes
Vatsa
Flash programmer
Started by ●May 14, 2008
Reply by ●May 14, 20082008-05-14
wallman16 wrote:
>
> Hi all ,
>
> Could Flash be programed with out ICE , Like boot the Blackfin from
> SPI and then program the flash from SPI .
> --
> Thanking you
> With best regards and wishes
> Vatsa
> .
You have just described the basic function of Danville's dspFlash
Blackfin & Sharc programmer. It uses the DSP to program itself via JTAG.
It is 30 to 100 times faster than using VDSP and an HPUSB ICE for this
purpose.
It supports most popular flash devices including almost all the serial
flash devices from Atmel, SST and ST as well as many different parallel
flash devices.
You can find details on our web site.
http://www.danvillesignal.com/analog-devices-development-tools/sharc-blackfin-programmer.html
Al Clark
Danville Signal Processing, Inc.
>
> Hi all ,
>
> Could Flash be programed with out ICE , Like boot the Blackfin from
> SPI and then program the flash from SPI .
> --
> Thanking you
> With best regards and wishes
> Vatsa
> .
You have just described the basic function of Danville's dspFlash
Blackfin & Sharc programmer. It uses the DSP to program itself via JTAG.
It is 30 to 100 times faster than using VDSP and an HPUSB ICE for this
purpose.
It supports most popular flash devices including almost all the serial
flash devices from Atmel, SST and ST as well as many different parallel
flash devices.
You can find details on our web site.
http://www.danvillesignal.com/analog-devices-development-tools/sharc-blackfin-programmer.html
Al Clark
Danville Signal Processing, Inc.
Reply by ●May 14, 20082008-05-14
On Wed, 14 May 2008, wallman16 wrote:
> Hi all ,
>
> Could Flash be programed with out ICE , Like boot the Blackfin from SPI and
> then program the flash from SPI .
Yes, but it depends on how you have things hooked up. It might be easier
to write a programmer into the Blackfin and send code to it so it can
program the flash directly. But again - it all depends on how you have
things connected.
Patience, persistence, truth,
Dr. mike
> Hi all ,
>
> Could Flash be programed with out ICE , Like boot the Blackfin from SPI and
> then program the flash from SPI .
Yes, but it depends on how you have things hooked up. It might be easier
to write a programmer into the Blackfin and send code to it so it can
program the flash directly. But again - it all depends on how you have
things connected.
Patience, persistence, truth,
Dr. mike
Reply by ●May 14, 20082008-05-14
Hello Al and all,
Al, I wanted to ask about your flash programmer: does it need a standard connection to SPI ports and/or external asynchronous bus in order to function? If it does not, how does it handle the different possible connections that could exist on a custom board?
Regards.
Jaime Andr Aranguren Cardona
j...@ieee.org
j...@computer.org
----- Original Message ----
From: Al Clark
To: wallman16
Cc: a...
Sent: Wednesday, May 14, 2008 8:45:50 AM
Subject: Re: [adsp] Flash programmer
wallman16 wrote:
>
> Hi all ,
>
> Could Flash be programed with out ICE , Like boot the Blackfin from
> SPI and then program the flash from SPI .
> --
> Thanking you
> With best regards and wishes
> Vatsa
>
>
> .
You have just described the basic function of Danville's dspFlash
Blackfin & Sharc programmer. It uses the DSP to program itself via JTAG.
It is 30 to 100 times faster than using VDSP and an HPUSB ICE for this
purpose.
It supports most popular flash devices including almost all the serial
flash devices from Atmel, SST and ST as well as many different parallel
flash devices.
You can find details on our web site.
http://www.danville signal.com/ analog-devices- development- tools/sharc- blackfin- programmer. html
Al Clark
Danville Signal Processing, Inc.
Al, I wanted to ask about your flash programmer: does it need a standard connection to SPI ports and/or external asynchronous bus in order to function? If it does not, how does it handle the different possible connections that could exist on a custom board?
Regards.
Jaime Andr Aranguren Cardona
j...@ieee.org
j...@computer.org
----- Original Message ----
From: Al Clark
To: wallman16
Cc: a...
Sent: Wednesday, May 14, 2008 8:45:50 AM
Subject: Re: [adsp] Flash programmer
wallman16 wrote:
>
> Hi all ,
>
> Could Flash be programed with out ICE , Like boot the Blackfin from
> SPI and then program the flash from SPI .
> --
> Thanking you
> With best regards and wishes
> Vatsa
>
>
> .
You have just described the basic function of Danville's dspFlash
Blackfin & Sharc programmer. It uses the DSP to program itself via JTAG.
It is 30 to 100 times faster than using VDSP and an HPUSB ICE for this
purpose.
It supports most popular flash devices including almost all the serial
flash devices from Atmel, SST and ST as well as many different parallel
flash devices.
You can find details on our web site.
http://www.danville signal.com/ analog-devices- development- tools/sharc- blackfin- programmer. html
Al Clark
Danville Signal Processing, Inc.
Reply by ●May 14, 20082008-05-14
Jaime Andres Aranguren Cardona wrote:
>
> Hello Al and all,
> Al, I wanted to ask about your flash programmer: does it need a
> standard connection to SPI ports and/or external asynchronous bus in
> order to function? If it does not, how does it handle the different
> possible connections that could exist on a custom board?
> Regards.
>
It uses a standard ADI JTAG connection. Many of our customers use a
smaller version. If you are spinning a new board, you might consider our
2mm connector option since we have adapters. In this case, you just
substitute a 2x8 header for the larger 2x7 ADI connector and treat the
first 14 pins identically. We tie the extra pins 15 & 16 to Vd+3.3.
Since the target DSP is actually programming itself (similar to the ADI
ICE method), it doesn't have many limitations since the flash
connections will already be routed on the pcb. You do need to tie pins
7,9,11 & 13 to Ground (or leave open). Do not connect boundary scan
connections to these pins.
It is best to tie Pin 5 to the I/O supply via a 4K7 resistor. This is
the current recommendations in ADI EE-68 and tells the programmer or an
ICE the I/O voltage. It is also the only way that the programmer can
tell if you have disconnected the cable. This allows the programmer to
automatically program the next board without the operator having to
press the program button.
Almost all JTAG connections meet the above criteria with the exception
of the Pin 5 pullup. This pin used to be grounded when the I/O was
always 3.3V. If you are spinning a new board (or revising one), add the
pullup.
Most customers tend to use the same flash as the ADI EZ Kit. We support
all of these with the exception of the crazy PLD-RAM-flash part that was
used on the 533 EZ-KIT. On Danville boards, we use serial flash instead.
It is much smaller and you only have to route 8 lines. We like the Atmel
25 & 26 family best, SST is also good. These parts are more flexible
than the ST versions. They are all pin compatible although they do
sometimes use different widths if you are using SO (wide & narrow). We
tend to use a universal footprint to keep options open. I can't see any
good reason to use parallel flash if you are just boot loading. Reset
causes the largest delay to boot time regardless of the flash device.
The choice of flash devices would be a good topic for discussion in this
group. We are considering writing a simple white paper that discusses
most of the issues. You learn a lot about flash options when you create
a programmer.
Al Clark
Danville Signal Processing, Inc.
>
> Hello Al and all,
> Al, I wanted to ask about your flash programmer: does it need a
> standard connection to SPI ports and/or external asynchronous bus in
> order to function? If it does not, how does it handle the different
> possible connections that could exist on a custom board?
> Regards.
>
It uses a standard ADI JTAG connection. Many of our customers use a
smaller version. If you are spinning a new board, you might consider our
2mm connector option since we have adapters. In this case, you just
substitute a 2x8 header for the larger 2x7 ADI connector and treat the
first 14 pins identically. We tie the extra pins 15 & 16 to Vd+3.3.
Since the target DSP is actually programming itself (similar to the ADI
ICE method), it doesn't have many limitations since the flash
connections will already be routed on the pcb. You do need to tie pins
7,9,11 & 13 to Ground (or leave open). Do not connect boundary scan
connections to these pins.
It is best to tie Pin 5 to the I/O supply via a 4K7 resistor. This is
the current recommendations in ADI EE-68 and tells the programmer or an
ICE the I/O voltage. It is also the only way that the programmer can
tell if you have disconnected the cable. This allows the programmer to
automatically program the next board without the operator having to
press the program button.
Almost all JTAG connections meet the above criteria with the exception
of the Pin 5 pullup. This pin used to be grounded when the I/O was
always 3.3V. If you are spinning a new board (or revising one), add the
pullup.
Most customers tend to use the same flash as the ADI EZ Kit. We support
all of these with the exception of the crazy PLD-RAM-flash part that was
used on the 533 EZ-KIT. On Danville boards, we use serial flash instead.
It is much smaller and you only have to route 8 lines. We like the Atmel
25 & 26 family best, SST is also good. These parts are more flexible
than the ST versions. They are all pin compatible although they do
sometimes use different widths if you are using SO (wide & narrow). We
tend to use a universal footprint to keep options open. I can't see any
good reason to use parallel flash if you are just boot loading. Reset
causes the largest delay to boot time regardless of the flash device.
The choice of flash devices would be a good topic for discussion in this
group. We are considering writing a simple white paper that discusses
most of the issues. You learn a lot about flash options when you create
a programmer.
Al Clark
Danville Signal Processing, Inc.
Reply by ●May 14, 20082008-05-14
Hello all,
Regarding the questions about custom boards, we support most of them already. All we require from the user is a little knowledge of the hardware, and to follow a few rules that aren't usually too restraining if you are using the flash for booting purposes. If we don't currently support the configuration, we can develop a custom driver to support it.
For instance in the case of the Sharc ADSP-21369 family of processors we require that the MOSI, MISO and SCK lines be connected such that booting is possible, you can specify the chip select line as any of available DAI, DPI, or flag lines. In a parallel interface the user has to specify the memory select and the base address will be calculated, or in the case of the ADSP-21262 and similar processors the user must specify the base address of the flash.
If you are using the flash to boot these decisions are generally made for you in the sense that the ADI bootloader is not flexible, SPI and chip select lines are defined and are chosen as the default values when you are selecting your processor.
Justin
Danville Signal Processing
Regarding the questions about custom boards, we support most of them already. All we require from the user is a little knowledge of the hardware, and to follow a few rules that aren't usually too restraining if you are using the flash for booting purposes. If we don't currently support the configuration, we can develop a custom driver to support it.
For instance in the case of the Sharc ADSP-21369 family of processors we require that the MOSI, MISO and SCK lines be connected such that booting is possible, you can specify the chip select line as any of available DAI, DPI, or flag lines. In a parallel interface the user has to specify the memory select and the base address will be calculated, or in the case of the ADSP-21262 and similar processors the user must specify the base address of the flash.
If you are using the flash to boot these decisions are generally made for you in the sense that the ADI bootloader is not flexible, SPI and chip select lines are defined and are chosen as the default values when you are selecting your processor.
Justin
Danville Signal Processing
