>From what I can tell, dataflash is very similar to NAND except the commands and data are sent over an SPI interface and there is a different set of commands. I don't think I can give you a really good list until I play with it some more. I only need to do a bit of work to get hardware ECC going on the at91sam9 NAND driver, so I should (hopefully) start playing in about a week. At that time I will be more able to let you know what can be done.
// Dean Glazeski On Wed, Nov 18, 2009 at 9:10 AM, Zach Welch <[email protected]> wrote: > I have been considering another round of reorganization, which would > include such restructuring. Such work is very invasive, though. > > Please tell me more about future type of flash. I am considering adding > a base type to unify the flash/nand code, so let me know how it might > impact those plans. > > --Z > > On Wed, 2009-11-18 at 08:35 -0600, Dean Glazeski wrote: > > In terms of NAND and flash devices, does it make any sense to create a > > subdirectory for NAND device drivers? The flash directory seems to be > > getting kind of cluttered with NOR, NAND, etc. flash drivers with no > > clear organization. I'm planning on trying to get dataflash working > > once I have NAND working on my AT91SAM9, so there may be future > > patches for yet another type of flash. > > > > // Dean Glazeski > > > > > > On Wed, Nov 18, 2009 at 4:56 AM, Zachary T Welch > > <[email protected]> wrote: > > Hi all, > > > > This series improves on the patch sent previously to add bank > > names. > > It adds a 'name' field to the flash and nand bank structures. > > > > This name must be passed as the first argument to the 'flash > > bank' and > > 'nand device' commands, so the last two patches update all > > scripts to > > add 'set LASHBANK $_CHIPNAME.flash' and use the improved > > syntax. > > > > Cheers, > > > > Zach > > _______________________________________________ > > Openocd-development mailing list > > [email protected] > > https://lists.berlios.de/mailman/listinfo/openocd-development > > > > >
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
