Universal Flashing tool
jerj at coplanar.net
Fri Mar 14 10:04:00 CET 2003
On Thu, 2003-03-13 at 19:14, Spirit wrote:
> an NULL function pointer. An small if statement fixes that, but the
> tool still can't detect the installed flash part properly. The part is
> JEDEC-compliant, but probe_jedec doesn't return correct id's for it,
I think a lot of these devices operate differently from what the
manufacturer's datasheet says. Then there are different revisions,
which may not be documented.
> no matter if I run flash_on or not. So I still prefer uniflash.
> Someone here called it an old code... well, may be the code style isn't
> very good (after all it's pascal...), but the project itself is very
> fresh. The last update is something like January 2003.
Yes thanks for stating it that way. When I commented about Uniflash, I
meant to say the coding style was old. But it works! It is mature
code, and like devbios, it contains working code dealing with hardware
quirks. I beat my head against the wall trying to get an Atmel AT29C040
to ID, using their datasheet. Then I looked at Uniflash and devbios,
did what they did, and it worked, just nowhere near how the spec said.
It would be nice however to have both working, and modern code. Ron,
can you elaborate more on the problems you have with MTD?
More information about the coreboot