I am a newbie to the TI C55x DSP and I am trying to use the FlashBurn Porting kit to burn
an AT45DB642D Atmel flash chip. I am using the DSK5510 example to start with that uses a
different flash chip and I am having problems getting things to work.
My flash chip is connected to the DSP through the McBSP so I have set the bootloader for a
serial SPI EEPROM boot from McBSP0.
I have modified the FBTCDSK5510.pjt by changing the EraseFlash and FlashWrite functions and 
the TargetConfig.h file to refelct the commands for the AT45 chip.
I have a logic analyzer attached to the MISO and MOSI and chip select lines and I can see that
the chip select is lowering as expected but no other data is being transmitted when I try to
erase or program the flash.
I am wondering if the issue is the fact that according to the AT45 flash spec the chip select
line needs to go low after sending a command which does not happen.
Also do I need to include the setup for the McBSP in the FlashBurn code?
I didn't think I needed to but again I am a newbie to this stuff.

Anyone else have a similar flash chip that they have used FlashBurn with?

Any help would be appreciated.

Thanks
Monika

There is a lot of work to do to port 5510 flashburn, with works with 
parallel flash, to SPI flash such as AT45. Yes, as you suspected, you 
have to configure McBsp as SPI in clock stop mode. Then at least you 
will see commands from McBsp on the scope.

Wei

--- In c...@yahoogroups.com, mtrend123@... wrote:
>
> I am a newbie to the TI C55x DSP and I am trying to use the 
FlashBurn Porting kit to burn an AT45DB642D Atmel flash chip. I am 
using the DSK5510 example to start with that uses a different flash 
chip and I am having problems getting things to work.
> My flash chip is connected to the DSP through the McBSP so I have 
set the bootloader for a serial SPI EEPROM boot from McBSP0.
> I have modified the FBTCDSK5510.pjt by changing the EraseFlash and 
FlashWrite functions and  the TargetConfig.h file to refelct the 
commands for the AT45 chip.
> I have a logic analyzer attached to the MISO and MOSI and chip 
select lines and I can see that the chip select is lowering as 
expected but no other data is being transmitted when I try to erase 
or program the flash.
> I am wondering if the issue is the fact that according to the AT45 
flash spec the chip select line needs to go low after sending a 
command which does not happen.
> Also do I need to include the setup for the McBSP in the FlashBurn 
code?
> I didn't think I needed to but again I am a newbie to this stuff.
> 
> Anyone else have a similar flash chip that they have used FlashBurn 
with?
> 
> Any help would be appreciated.
> 
> Thanks
> Monika
>

Monika-

> I am a newbie to the TI C55x DSP and I am trying to use the FlashBurn Porting kit to burn
an AT45DB642D Atmel flash
> chip. I am using the DSK5510 example to start with that uses a different flash chip and I
am having problems getting
> things to work.
> My flash chip is connected to the DSP through the McBSP so I have set the bootloader for a
serial SPI EEPROM boot from
> McBSP0.
> I have modified the FBTCDSK5510.pjt by changing the EraseFlash and FlashWrite functions
and  the TargetConfig.h file
> to refelct the commands for the AT45 chip.
> I have a logic analyzer attached to the MISO and MOSI and chip select lines and I can see
that the chip select is
> lowering as expected but no other data is being transmitted when I try to erase or program
the flash.
> I am wondering if the issue is the fact that according to the AT45 flash spec the chip
select line needs to go low
> after sending a command which does not happen.
> Also do I need to include the setup for the McBSP in the FlashBurn code?
> I didn't think I needed to but again I am a newbie to this stuff.
>
> Anyone else have a similar flash chip that they have used FlashBurn with?

Flashburn is not the easiest utility to use or get working with hardware other than the
TI-provided examples.  My
suggestion would be to first write some small, simple code that does read/write to the Atmel
Flash chip -- essentially
a device driver.  Once you're sure that's working, then go for the Flashburn port.

Otherwise you will be trying to debug two major issues at the same time, with unnecessary
confusion.

-Jeff