This is the mail archive of the ecos-devel@sourceware.org mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: New Flash-Driver for singleChipDevice


Some more questions...

flash_query(); as an empty function, there is no flash-device whit vendor
codes...

Don't the different members of the AT91SAMxxx have different amounts of flash? So you should query the register which contains this information and return it.

Why do I need flash_query(); when I write also the function flash_hwr_init(); ? No module exept my driver knows the meaning of the chip-ID-codes of the AT91SAMxxx... Is flash_query(); the trick to read from a Flashrom from RAM? In my case I have to read the ID in an address outside the flash-address-range.

flash_hwr_init(); as empty function, there is nothing to do.

You should look at the information returned by flash_query and decide on how big the flash is. You also need to fill in the block size and the number of blocks.

That means I sould #define _FLASH_PRIVATE_ and fill the struct flash_info in flash_hwr_init(); ? What is wrong in not using _FLASH_PRIVATE_ ?

flash_hwr_map_error();
flash_code_overlaps(); as copy from a nother flash_driver...

You can copy flash_code_overlaps() but i expect the AT91 returns different err codes than a typical Strata device. So you will probably need to modify this flash_hwr_map_error.

If I understand flash_code_overlaps(); right, then it only verify, if the linker-section .text will be modified. In this case I don't need any err-code from any flash-rom...

And I don't see the need for flash_hwr_map_error(); My device has no
error-codes an all my functions will return the FLASH_ERRORS... defined in
<cyg/io/flash.h>...

It is possible that this is all it needs? Or have I handle some other
things, like the size of the flash-area or the segmentation?

Currently the flash_program_buf(); function does all the work and eCos
don't need to know something about the flash-segmentation and so on...

This will cause problems for RedBoot and jffs2. It wants to know this information so it can lay out it structures correctly.

There is some documentation in the flashv2 branch. Attached is the
sgml file.

Where is the flashv2 branch?


Andrew


Thanks Oli



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]