On Sunday 08 January 2006 17:21, alfred hitch wrote:
Hi,
I have some (basic) question ..
- Does u-boot lock the block on which it resides by default ?
I mean the sector /erase block on which u-boot is there, it will be locked using the block lock bit by default ?
Plafform in question being IXDP 425 with Intel J3 NOR Flash.
- The flash content changing has to work in block sizes erase -
modify - write cyecles only ??
Reason for all this is that we have few boards on which u-boot is getting corrupted (on flash image corruption itself). And so am wondering even if its a noise issue, how can it first cause an unlock of sector before write.
Any help in understanding of above issues will be really appreciated, Regards, Alfred
AFAIK u-boot normally only software protects sectors (mark them internally as read-only). You can lock the sector(s) in your board startup routine. Remember to do so after relocation to RAM.
Regards
Pantelis