Manuel Sahm <[EMAIL PROTECTED]> writes:
> how does uboot handle this flag byte ? (i I use redundant nand)
As you can't invalidate the old NAND environment as you can with NOR
flash, counters are used instead. So for NAND, the flag byte is a
counter which gets incremented for each write. This mean
In message <[EMAIL PROTECTED]> you wrote:
>
> how does uboot handle this flag byte ? (i I use redundant nand)
I already answered that. See my previous message.
> What initial value must this flag have?
> Same value for enviroment1 and enviroment2 ?
No. Please see my previous mesage, and the cod
Hello,
how does uboot handle this flag byte ? (i I use redundant nand)
What initial value must this flag have?
Same value for enviroment1 and enviroment2 ?
If I make a "saveenv" which env. is used, and what values are then
written to the NAND flash to set it as aktiv/deactive ?
For example:
I
Dear Manuel,
in message <[EMAIL PROTECTED]> you wrote:
>
> My problem the structure of the enviroment:
> If I understand:
> 4 byte crc; 1 byte flags, 0x2-5 byte data.
Correct - the flag byte is only present if you use redundant
environment.
> The CRC is over the data bytes,( not the flags b
Hello,
I try to modify the env toll for accessing nand flash.
My problem the structure of the enviroment:
If I understand:
4 byte crc; 1 byte flags, 0x2-5 byte data.
The Enviroment has a size of 0x2 bytes. There is a redundant
enviroment too.(same size)
The CRC is over the data bytes,(
In message <[EMAIL PROTECTED]> you wrote:
>
> I took the U-Boot version 1.3.2; now I am able to generate the make env
> -> fw_printenv utility.
>
> I copy the jw_printenv binary and rename it to fw_setenv.
...
> I want to access a NAND flash. [Pagesize = 0x800; ERASEBLOCKSIZE=0x2]
...
> Is t
Manuel Sahm <[EMAIL PROTECTED]> writes:
> but why is there a error concerning NAND flashs if only NOR flashs are
> supported ?
>
> "nand_write: attempting to write not page aligned data"
Of course NAND is supported by the kernel. This is why it almost works
:-) The error is caused because the too
Hello,
but why is there a error concerning NAND flashs if only NOR flashs are
supported ?
"nand_write: attempting to write not page aligned data"
Thank you
Manuel Sahm
Markus Klotzbücher schrieb:
> Hi Manuel,
>
> Manuel Sahm <[EMAIL PROTECTED]> writes:
>
>
>> I took the U-Boot version 1.3.2
Hi Manuel,
Manuel Sahm <[EMAIL PROTECTED]> writes:
> I took the U-Boot version 1.3.2; now I am able to generate the make env
> -> fw_printenv utility.
>
> I copy the jw_printenv binary and rename it to fw_setenv.
A (hard) link would be enough.
> I use the config file in the /etc directory.
> I
Hello,
I took the U-Boot version 1.3.2; now I am able to generate the make env
-> fw_printenv utility.
I copy the jw_printenv binary and rename it to fw_setenv.
I use the config file in the /etc directory.
I want to access a NAND flash. [Pagesize = 0x800; ERASEBLOCKSIZE=0x2]
My uboot is in
On Thu, Mar 20, 2008 at 10:27:18PM +0100, Wolfgang Denk wrote:
> It's not fw_setenv specific. You would have to do the same when you
> cross-compile any other native Linux application code. The best
> approach would be to fix your toolchain.
Well, any other applications compile just fine.
In message <[EMAIL PROTECTED]> you wrote:
>
> > I'm not sure what you wanted to express with your comment?
>
> Well, it seems you have "properly" configured toolchain - you installed
> proper kernel headers. In my case it ends with:
Well, yes, a correctly configured and working toolchain is consi
On Thu, Mar 20, 2008 at 09:02:58PM +0100, Wolfgang Denk wrote:
> Yes, and actually I think this is correct. What we're building is a
> target Linux application, so the U-Boto specific CFLAG settings have
> no meaning for this (or rather would be just dangerous).
>
> Example:
>
> -> make env
> mak
In message <[EMAIL PROTECTED]> you wrote:
> On Thu, Mar 20, 2008 at 05:04:35PM +0100, Wolfgang Denk wrote:
> > I guess (you fail to mention such a basic fact as which version you
> > are using) that you are referring to old code. So I recommend to use
> > recent code (i. e. release 1.3.2).
>
>
On Thu, Mar 20, 2008 at 05:04:35PM +0100, Wolfgang Denk wrote:
> I guess (you fail to mention such a basic fact as which version you
> are using) that you are referring to old code. So I recommend to use
> recent code (i. e. release 1.3.2).
No matter how recent version is he going to use. Relat
In message <[EMAIL PROTECTED]> you wrote:
> SGVsbG8KCmNvdWxkIGFueWJvZHkgdGVsbCBtZSBob3cgdG8gY29tcGlsZSB0aGUgfGZ3X3NldGVu
> diBhbmQgfHxmd19zYXZlZW52IApiaW5hcmllcyA/CgpJIHRyeSB0byB1c2UKCm1ha2UgQVJDSD1h
> cm0gQ1JPU1NfQ09NUElMRT08UGF0aCB0byBteSBDcm9zc0NvbXBpbGVyPiBlbnYKCkJ1dCB0aGlz
> IGRvZXNuwrR0IHdvcm
Hello
could anybody tell me how to compile the |fw_setenv and ||fw_saveenv
binaries ?
I try to use
make ARCH=arm CROSS_COMPILE= env
But this doesn´t work.
#error This is a kernel header. Perhaps include mtd-user.h instead ?
and a lot of error messages appaer ?
Thank you|
Best regards
Manu
17 matches
Mail list logo
