??? 05/13/04 11:22 Read: times |
#70288 - reply to russell Responding to: ???'s previous message |
Mr.Russell,
Yes..I did ensure that no other resources are accessing the flash at the time I write. I actually made a thin test routine, a main function which calls various driver functions in the flash driver c file. The whole thing runs on top of an RTOS-Nucleus. And since I have a debugger, I can actually see the addresses and data I write going into the memory mapped area of my processor memory. They are all right. I can read CFI queries, Manufacture id and device id from flash. This proves that the existing addressing is correct. So I dont think I need to shift the addresses by a bit to the left. I guess I need to focus the hardware settings and board level settings as well. If you get any light on the thing, please do let me know. Achu |
Topic | Author | Date |
A flash write issue - a little diversion | 01/01/70 00:00 | |
RE: A flash write issue - a little diversion | 01/01/70 00:00 | |
RE: flash write issue - reply to Russel | 01/01/70 00:00 | |
One more thing... | 01/01/70 00:00 | |
RE: A flash write issue - a little diversion | 01/01/70 00:00 | |
reply to russell | 01/01/70 00:00 | |
RE: A flash write issue - a difference | 01/01/70 00:00 | |
RE: A flash write issue - a difference | 01/01/70 00:00 | |
RE: A flash write issue - a little diversion![]() | 01/01/70 00:00 |