> Message: 1
> Date: Tue, 16 Sep 2008 10:46:26 +0300
> From: Petri Lehtinen <[EMAIL PROTECTED]>
> Subject: [U-Boot] erase and saveenv stop working after using fw_setenv
> To: u-boot@lists.denx.de
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset
>> fw_printenv in Linux, erase and saveenv stop working in U-Boot. In
> --^^^--
>
> I think this must be a typo. fw_printenv should have no effect. I
> guess you mean fw_setenv (as in the Subject) ?
Ahh, yes. I meant fw_setenv of course.
> The problem is that the MPC8323ERDB boar
On Tue, 16 Sep 2008, Wolfgang Denk wrote:
> b) Guennadi, I think it would be nice, user-friendly behaviour if
>fw_setenv did not unconditional locking, but would instead leave
>the flash in the same state it found it. Do you think it would be
>possible to test the state first
Dear Petri Lehtinen,
In message <[EMAIL PROTECTED]> you wrote:
>
> I'm using U-Boot 1.3.4 and Linux 2.6.26.5 on MPC8323E-RDB. After using
> fw_printenv in Linux, erase and saveenv stop working in U-Boot. In
--^^^--
I think this must be a typo. fw_printenv should have no effect. I
guess y
Hi!
I'm using U-Boot 1.3.4 and Linux 2.6.26.5 on MPC8323E-RDB. After using
fw_printenv in Linux, erase and saveenv stop working in U-Boot. In
Linux, fw_* still work.
When using erase, this is the result:
=> protect off fe04 fe05
Un-Protected 1 sectors
=> erase fe04 fe05
Flash er
5 matches
Mail list logo