On Mon, May 3, 2010 at 6:36 AM, Peter Korsgaard <jac...@sunsite.dk> wrote:
> >>>>> "Gary" == Gary Carlson <gcarl...@carlson-minot.com> writes: > > Gary> I wanted to see if anyone has any experience trying to upload the > Gary> AT91Bootstrap code into NAND flash for any of the AT91SAM9XXX parts > (i.e. > Gary> AT91SAM9260, AT91SAM9G20, etc.) using OpenOCD? > > Gary> I have tried erasing and programming the first block of the NAND > Gary> flash in every command combination possible with the image I > Gary> have. The programming cycle is successful, the verify command is > Gary> successful, but the internal first stage boot ROM concludes that > Gary> it isn't a valid image and goes limp (or brain dead depending on > Gary> how you want to look at it). The Atmel startup diagnostics from > Gary> the internal boot code is naturally zero, so it is left to wild > Gary> imagination what the problem is. > > I haven't used it, but my guess is that the boot ROM expects a different > OOB / EEC layout than what openocd writes. > > -- > Bye, Peter Korsgaard > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > This is interesting. I'm the one that actually wrote the original AT91SAM9 NAND flash piece. To be honest, I haven't been able to test the "bootability" of the flash stuff that gets written. I thought that if I could write and then read the same data, then everything should be okay. Something I'm thinking I should have done is try to write with SAM-BA and then verified what was written with the OpenOCD driver. I have plans of playing with this more once I get out of classes for the year. Right now, I'm sort of swamped in projects. // Dean Glazeski
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
