DSPRelated.com
Forums

JTAG programming of Serial EEPROM for firmware?

Started by Sound Consulting April 12, 2009
Hello everyone,

I am still working on the schematic and layout for my first C55x
board. I have included a Serial EEPROM attached to McBSP0, and a JTAG
header on the board. I assume that in order to load my first board
with firmware, I can use the JTAG port to control the DSP to program
the Serial EEPROM over McBSP0.

This is a C5506 design.

So far, I've selected the ATMEL AT45DB011D and attached GPIO4 to the
active-low Chip Select. The TI documents indicate that the C5506 will
automatically assert GPIO4 as needed for the firmware load. I have
the active-low Write Protect connected to VCC as recommended by Atmel,
assuming that I can use the software write mode to load the firmware
into the chip.

Really, all I'm looking for is confirmation that a C55x DSP can be
operated without firmware via the JTAG header just long enough to
write a data image into a Serial EEPROM on McBSP0, so that subsequent
boot sequences can load the new firmware from the EEPROM. I assume if
this works the first time, it will also work during firmware
development as firmware updates are needed due to debugging.

I suppose this operation may even be supported easily by the TI
development tools, but since I'm in the hardware design phase, I have
not started looking at the software tools.

Thanks for any help,

Brian
Brian-

> I am still working on the schematic and layout for my first C55x
> board. I have included a Serial EEPROM attached to McBSP0, and a JTAG
> header on the board. I assume that in order to load my first board
> with firmware, I can use the JTAG port to control the DSP to program
> the Serial EEPROM over McBSP0.
>
> This is a C5506 design.
>
> So far, I've selected the ATMEL AT45DB011D and attached GPIO4 to the
> active-low Chip Select. The TI documents indicate that the C5506 will
> automatically assert GPIO4 as needed for the firmware load. I have
> the active-low Write Protect connected to VCC as recommended by Atmel,
> assuming that I can use the software write mode to load the firmware
> into the chip.
>
> Really, all I'm looking for is confirmation that a C55x DSP can be
> operated without firmware via the JTAG header just long enough to
> write a data image into a Serial EEPROM on McBSP0, so that subsequent
> boot sequences can load the new firmware from the EEPROM. I assume if
> this works the first time, it will also work during firmware
> development as firmware updates are needed due to debugging.
>
> I suppose this operation may even be supported easily by the TI
> development tools, but since I'm in the hardware design phase, I have
> not started looking at the software tools.

Sounds to me like you're on the right track. With just a JTAG header, you can
download and run any code via CCS + emulator. Using McBSP to access a serial Flash
device just means understanding those devices and carefully reading data sheets.
Booting may be more of an issue, as sometimes the internal chip bootloader code
doesn't act as you might expect. But, just more debug, you can always get it to
work.

Also, you might want to look up "Flashburn".

-Jeff
It seems that most of Serial EEPROMs have SPI interface,
you will need configure the boot mode SPI-16 bit or SPI-24 bit depending on EERPROM addressing
--- In c..., Jeff Brower wrote:
>
> Brian-
>
> > I am still working on the schematic and layout for my first C55x
> > board. I have included a Serial EEPROM attached to McBSP0, and a JTAG
> > header on the board. I assume that in order to load my first board
> > with firmware, I can use the JTAG port to control the DSP to program
> > the Serial EEPROM over McBSP0.
> >
> > This is a C5506 design.
> >
> > So far, I've selected the ATMEL AT45DB011D and attached GPIO4 to the
> > active-low Chip Select. The TI documents indicate that the C5506 will
> > automatically assert GPIO4 as needed for the firmware load. I have
> > the active-low Write Protect connected to VCC as recommended by Atmel,
> > assuming that I can use the software write mode to load the firmware
> > into the chip.
> >
> > Really, all I'm looking for is confirmation that a C55x DSP can be
> > operated without firmware via the JTAG header just long enough to
> > write a data image into a Serial EEPROM on McBSP0, so that subsequent
> > boot sequences can load the new firmware from the EEPROM. I assume if
> > this works the first time, it will also work during firmware
> > development as firmware updates are needed due to debugging.
> >
> > I suppose this operation may even be supported easily by the TI
> > development tools, but since I'm in the hardware design phase, I have
> > not started looking at the software tools.
>
> Sounds to me like you're on the right track. With just a JTAG header, you can
> download and run any code via CCS + emulator. Using McBSP to access a serial Flash
> device just means understanding those devices and carefully reading data sheets.
> Booting may be more of an issue, as sometimes the internal chip bootloader code
> doesn't act as you might expect. But, just more debug, you can always get it to
> work.
>
> Also, you might want to look up "Flashburn".
>
> -Jeff
>
Hi..

This is just a query from Jeff's reply.

Can I use FLASHBURN utility for burning serial flash too or is it just limited for parallel flash?
Regards,
Onkar Patki,
Design Engineer.
----------------------------
Mechatronics Test Equipment (I) Pvt.Ltd.
B, Mayur complex, Opp. Bhelke nagar,
Kothrud, Pune 411 038.
Tel.: 91 20 25386926,27,28,29
Fax:: 91 20 25386930
Mob: 919881730876
Email: m...@vsnl.net
URL: www.mte-india.com
----- Original Message -----
From: Jeff Brower
To: Brian Willoughby
Cc: c...
Sent: Wednesday, April 29, 2009 12:27 AM
Subject: Re: [c55x] JTAG programming of Serial EEPROM for firmware?

Brian-

> I am still working on the schematic and layout for my first C55x
> board. I have included a Serial EEPROM attached to McBSP0, and a JTAG
> header on the board. I assume that in order to load my first board
> with firmware, I can use the JTAG port to control the DSP to program
> the Serial EEPROM over McBSP0.
>
> This is a C5506 design.
>
> So far, I've selected the ATMEL AT45DB011D and attached GPIO4 to the
> active-low Chip Select. The TI documents indicate that the C5506 will
> automatically assert GPIO4 as needed for the firmware load. I have
> the active-low Write Protect connected to VCC as recommended by Atmel,
> assuming that I can use the software write mode to load the firmware
> into the chip.
>
> Really, all I'm looking for is confirmation that a C55x DSP can be
> operated without firmware via the JTAG header just long enough to
> write a data image into a Serial EEPROM on McBSP0, so that subsequent
> boot sequences can load the new firmware from the EEPROM. I assume if
> this works the first time, it will also work during firmware
> development as firmware updates are needed due to debugging.
>
> I suppose this operation may even be supported easily by the TI
> development tools, but since I'm in the hardware design phase, I have
> not started looking at the software tools.

Sounds to me like you're on the right track. With just a JTAG header, you can
download and run any code via CCS + emulator. Using McBSP to access a serial Flash
device just means understanding those devices and carefully reading data sheets.
Booting may be more of an issue, as sometimes the internal chip bootloader code
doesn't act as you might expect. But, just more debug, you can always get it to
work.

Also, you might want to look up "Flashburn".

-Jeff
Onkar-
> This is just a query from Jeff's reply. Can I use FLASHBURN utility for burning
> serial flash too or is it just limited for parallel flash?

The short answer seems to be yes, but the long answer depends on which device.
According to this site:

http://www.softwaredesignsolutions.com/flashburn.aspx

If any of the following DSK boards:

DSK5402
DSK5416
DSK5510
DSK6416
DSK6713
OSK5912

have a serial / SPI Flash, then there should be an existing reference example you can
use. Otherwise you might need to port Flashburn, which the above site talks about,
too.

-Jeff
> ----------------------------
> Mechatronics Test Equipment (I) Pvt.Ltd.
> B, Mayur complex, Opp. Bhelke nagar,
> Kothrud, Pune 411 038.
> Tel.: 91 20 25386926,27,28,29
> Fax:: 91 20 25386930
> Mob: 919881730876
> Email: m...@vsnl.net
> URL: www.mte-india.com
>
> ----- Original Message -----
> From: Jeff Brower
> To: Brian Willoughby
> Cc: c...
> Sent: Wednesday, April 29, 2009 12:27 AM
> Subject: Re: [c55x] JTAG programming of Serial EEPROM for firmware?
>
> Brian-
>
> > I am still working on the schematic and layout for my first C55x
> > board. I have included a Serial EEPROM attached to McBSP0, and a JTAG
> > header on the board. I assume that in order to load my first board
> > with firmware, I can use the JTAG port to control the DSP to program
> > the Serial EEPROM over McBSP0.
> >
> > This is a C5506 design.
> >
> > So far, I've selected the ATMEL AT45DB011D and attached GPIO4 to the
> > active-low Chip Select. The TI documents indicate that the C5506 will
> > automatically assert GPIO4 as needed for the firmware load. I have
> > the active-low Write Protect connected to VCC as recommended by Atmel,
> > assuming that I can use the software write mode to load the firmware
> > into the chip.
> >
> > Really, all I'm looking for is confirmation that a C55x DSP can be
> > operated without firmware via the JTAG header just long enough to
> > write a data image into a Serial EEPROM on McBSP0, so that subsequent
> > boot sequences can load the new firmware from the EEPROM. I assume if
> > this works the first time, it will also work during firmware
> > development as firmware updates are needed due to debugging.
> >
> > I suppose this operation may even be supported easily by the TI
> > development tools, but since I'm in the hardware design phase, I have
> > not started looking at the software tools.
>
> Sounds to me like you're on the right track. With just a JTAG header, you
> can
> download and run any code via CCS + emulator. Using McBSP to access a
> serial Flash
> device just means understanding those devices and carefully reading data
> sheets.
> Booting may be more of an issue, as sometimes the internal chip
> bootloader code
> doesn't act as you might expect. But, just more debug, you can always get
> it to
> work.
>
> Also, you might want to look up "Flashburn".
>
> -Jeff
>