On Wed, Nov 17, 2010 at 1:40 PM, Wolfgang Denk <w...@denx.de> wrote: > Dear Steve Sakoman, > > In message <aanlktimrfq5+awfdfy_fuetmh=x=xrkazgntk8fis...@mail.gmail.com> you > wrote: >> >> readenv: offset = 240000 >> readenv: nand_read failure = -117 >> *** Warning - readenv() failed, using default environment >> >> I then immediately tried to use the nand read command to read the same >> block, and it was successful! > > Hm... any chance that - for example - your timers are not working > correctly before relocation (maybe because they try to write to the > not yet available data segment) ? This could cause timeouts or delays > to be too short, so the NAND driver is misbehaving?
Hmm . . . I suppose that is possible, but it doesn't seem to explain why environment data written by u-boot will always be read successfully, but reads of linux written data fails. Steve _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
