[U-Boot-Users] BDI2000 flashing problem

[VanBaren, Gerald (AGRE)]

> -----Original Message-----
> From: Santoso, Yusdi [mailto:Yusdi_Santoso at adaptec.com]
> Sent: Tuesday, October 19, 2004 8:33 PM
> To: VanBaren, Gerald (AGRE); u-boot-users at lists.sourceforge.net
> Subject: RE: [U-Boot-Users] BDI2000 flashing problem
>
> Hi gvb,
>
> Thanks for the reply. What you said make sense but somehow I
> managed to get it work after tinkering with the BDI config
> file. I removed the "WORKSPACE" option in the [FLASH] section
> and the "prog" command worked well albeit much slower.
> Not sure why it is so...anybody can explain why?
>
> My RAM is working properly because I can read/write to the
> address space perfectly, although I have not done a checker
> pattern test.
>
> Thanks,
>
>
> Yusdi

The "workspace" command tells the BDI2000 to load a helper program into
RAM.  The BDI2000 can then load the to-be-programmed data into a RAM
buffer (which is fast) and run the helper program to program the RAM
buffer data into flash.  This obviously is the faster method, but
requires more things to be operational on the board and with the
processor.

Without the "workspace" command, the BDI2000 programs the data into
flash directly which is considerably slower since bit-shifting the
commands to do the write and poll for completion, etc. are much less
efficient than the workspace method.  This is slow but sure and only
requires CPU and flash functionality to work.

You apparently have a problem with the RAM set up in your config file or
a hardware problem with your RAM (in that order of likelyhood).

I forgot which processor you have, but most or all of the 8xx/8xxx
processors have dual port RAM that you can also use for a workspace.
Using this is much less complicated than getting SDRAM configured
properly in the BDI2000 config file.

Trivia: WD recommends (wisely!) that you do _not_ do the SDRAM
initialization in the BDI2000 config file.  The problem people have with
initializing SDRAM in the config file is that they will do the bulk of
their development with the BDI2000 attached and never realize their
program's SDRAM initialization is stuffed... then at time (ship_date -
1), they unplug the BDI2000 and find their board is dead without a
heart-lung machine and they are in a world of hurt.

gvb

******************************************
The following messages are brought to you by the Lawyers' League of
IdioSpeak:

******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************