[U-Boot-Users] .../board/fads/flash.c confuses me - give me a hint
Im writing my own flash.c for "my" custom board in the moment. That's why I'm trying to understand what the flash.c does. I thought I got it when I encountered the following problem examining board/fads/flash.c
All functions in there seem to be written to handle 4x8bit flash banks. As indication for that are - in my opinion - the QUAD_ID macro in line 41+ and the fact that 0xAAAAAAAA, 0x55555555 and 0x90909090 and not 0x00AA00AA, 0x00550055 and 0x00900090 are written in the auto select command sequence, beginning in line 227 (u-boot 1.1.2). But they do write to the addresses which are typical - my fine flash datasheet says - for word-mode flash access. So the data written seems not to fit the addresses written to.
I'd be very happy if someone could give me a hint what I missed or what I got wrong or why it must be that way though.
Peter Asemann
In message 41E537A8.8050006@web.de you wrote:
Im writing my own flash.c for "my" custom board in the moment. That's why I'm trying to understand what the flash.c does. I thought I got it when I encountered the following problem examining board/fads/flash.c
There must ne some strange fascination about the FADS port. I really wonder why everybody is picking one of the most complicated and poroblematic ports...
Pleas ehave a loot at least at some other drivers, too.
All functions in there seem to be written to handle 4x8bit flash banks.
SO look for other flash drivers, or maybe even for the generic CFI driver.
I'd be very happy if someone could give me a hint what I missed or what I got wrong or why it must be that way though.
Forget what the FADS is doing. Think about what is needed for your own hardware, and implement this.
Best regards,
Wolfgang Denk
There must ne some strange fascination about the FADS port. I really wonder why everybody is picking one of the most complicated and poroblematic ports...
I have an idea / a strong suggestion: Maybe it's that this port seems to "fit" so many different CPUs and configurations that every Newbie thinks that he/she could easily copy the "right" parts of the code from there; while trying to do so, Mr. or Mrs. Newbie get lost in the super-enhanced or just wildly grown and tricky FADS code.
Pleas ehave a loot at least at some other drivers, too.
I had and will have.
Forget what the FADS is doing. Think about what is needed for your own hardware, and implement this.
I'll do as I lack other options. I think it's recommended to develop the port for "my" hardware based upon 1.1.2? I started when 1.1.1 was the latest version.
Thanks a lot and best regards,
Peter Asemann
In message 41E55CA9.6080108@web.de you wrote:
I'll do as I lack other options. I think it's recommended to develop the port for "my" hardware based upon 1.1.2? I started when 1.1.1 was the latest version.
No, it's recommended to use the _current_ version, i. e. top of tree in CVS.
Viele Grüße,
Wolfgang Denk
participants (2)
-
Peter Asemann -
Wolfgang Denk