[Buildroot] Dataflash rootfs problems (still)

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

Hello all:

I've sucessfully built  several root filesystems  for my custom board
(AT91RM9200 + 8MiB DataFlash),  but  now  i'm facing a  strange problem.

I'm using a JFFS2 filesystem on an MTD partition into the DataFlash, my
rootfs boots OK, but ONLY for the first time. See steps:

1) Create a rootfs JFFS2 image using buildroot -> OK
2) Erase entire flash partition: I boot from an initrd containing mtd-tools
for this purpouse. -> OK
3) Dump the rootfs image "rootfs.jffs2" into the Dataflash (i use loadb from
u-boot here...) -> OK
4) Boot the system... -> OK
5) Login and issue a simple reboot, no other commands...nothing else.... ->
OK

After the reboot at step "5" the system comes again, but now when is press
BACKSPACE it writes a space, and if i try to add a user or change the root
password
i always get a "/etc/passwd" not found.

So i have (at least) 2 weird issues here:

1) Why my backspace key sends a space, but really deletes a character?!?! It
worked fine for the 1st boot
2) Why "adduser" and "passwd" utilities are unable to access /etc files?
I'have TRIPLE checked read/write permissions...everything is ok. Of course
it works fine if i do this on the 1st boot!

Any idea?!

Thanks in advance.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071024/c58b307a/attachment-0001.htm 

[Buildroot] Dataflash rootfs problems (still)

[Ulf Samuelsson]

ons 2007-10-24 klockan 18:20 +0200 skrev Jorge S.:
> Hello all:
> 
> I've sucessfully built  several root filesystems  for my custom board
> (AT91RM9200 + 8MiB DataFlash),  but  now  i'm facing a  strange
> problem.
> 
> I'm using a JFFS2 filesystem on an MTD partition into the DataFlash,
> my rootfs boots OK, but ONLY for the first time. See steps: 
> 
> 1) Create a rootfs JFFS2 image using buildroot -> OK
> 2) Erase entire flash partition: I boot from an initrd containing
> mtd-tools for this purpouse. -> OK
> 3) Dump the rootfs image "rootfs.jffs2" into the Dataflash (i use
> loadb from u-boot here...) -> OK 
> 4) Boot the system... -> OK
> 5) Login and issue a simple reboot, no other commands...nothing
> else.... -> OK
> 

If you run the SPI faster than 5 Mbps, you are basically screwed.
See Errata #13 in the datasheet.

You will need to add an external AND gate if you want to run faster.

* AND output to the dataflash chip select, 
* one input to the NPCS0
* one input to a GPIO

The driver needs to be adapted for this.

> After the reboot at step "5" the system comes again, but now when is
> press BACKSPACE it writes a space, and if i try to add a user or
> change the root password 
> i always get a "/etc/passwd" not found.
> 
> So i have (at least) 2 weird issues here:
> 
> 1) Why my backspace key sends a space, but really deletes a
> character?!?! It worked fine for the 1st boot 
> 2) Why "adduser" and "passwd" utilities are unable to access /etc
> files? I'have TRIPLE checked read/write permissions...everything is
> ok. Of course it works fine if i do this on the 1st boot! 
> 
> Any idea?!
> 
> Thanks in advance.
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
-- 
Best Regards,
Ulf Samuelsson

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

2007/10/24, Ulf Samuelsson <ulf@atmel.com>:
>
> ons 2007-10-24 klockan 18:20 +0200 skrev Jorge S.:
> > Hello all:
> >
> > I've sucessfully built  several root filesystems  for my custom board
> > (AT91RM9200 + 8MiB DataFlash),  but  now  i'm facing a  strange
> > problem.
> >
> > I'm using a JFFS2 filesystem on an MTD partition into the DataFlash,
> > my rootfs boots OK, but ONLY for the first time. See steps:
> >
> > 1) Create a rootfs JFFS2 image using buildroot -> OK
> > 2) Erase entire flash partition: I boot from an initrd containing
> > mtd-tools for this purpouse. -> OK
> > 3) Dump the rootfs image "rootfs.jffs2" into the Dataflash (i use
> > loadb from u-boot here...) -> OK
> > 4) Boot the system... -> OK
> > 5) Login and issue a simple reboot, no other commands...nothing
> > else.... -> OK
> >
>
> If you run the SPI faster than 5 Mbps, you are basically screwed.
> See Errata #13 in the datasheet.
>
> You will need to add an external AND gate if you want to run faster.
>
> * AND output to the dataflash chip select,
> * one input to the NPCS0
> * one input to a GPIO
>
> The driver needs to be adapted for this.


So, there's a flash corruption on the 1st boot?,

I'm a little confused now...why u-boot looks like writing OK then? I've
sucessfully uploaded hundreds of kernels and initrds images to the
dataflash.

During the 1st boot, Dropbear creates and "writes" the generated keys, maybe
is this *write* operation the one screwing up the dataflash?

And last question, which one is the best way to solve this by software? I
suppose i can "slow down" the SPI speed somewhere in the kernel or board
config at u-boot isn't it?

Thanks for helping Ulf.


> After the reboot at step "5" the system comes again, but now when is
> > press BACKSPACE it writes a space, and if i try to add a user or
> > change the root password
> > i always get a "/etc/passwd" not found.
> >
> > So i have (at least) 2 weird issues here:
> >
> > 1) Why my backspace key sends a space, but really deletes a
> > character?!?! It worked fine for the 1st boot
> > 2) Why "adduser" and "passwd" utilities are unable to access /etc
> > files? I'have TRIPLE checked read/write permissions...everything is
> > ok. Of course it works fine if i do this on the 1st boot!
> >
> > Any idea?!
> >
> > Thanks in advance.
> >
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at uclibc.org
> > http://busybox.net/mailman/listinfo/buildroot
> --
> Best Regards,
> Ulf Samuelsson
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071024/92ddd7ce/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Ivan Kuten]

> 
> During the 1st boot, Dropbear creates and "writes" the generated keys, maybe
> is this *write* operation the one screwing up the dataflash?
> 

We have similar problems with Dataflash&RM9200
*write* operation is unreliable - we had corrupted filesystem after reboot.
Our solution was to use r/o only on dataflash.


Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

[Buildroot] Dataflash rootfs problems (still)

[Ulf Samuelsson]

ons 2007-10-24 klockan 21:34 +0300 skrev Ivan Kuten:
> > 
> > During the 1st boot, Dropbear creates and "writes" the generated keys, maybe
> > is this *write* operation the one screwing up the dataflash?
> > 
> 
> We have similar problems with Dataflash&RM9200
> *write* operation is unreliable - we had corrupted filesystem after reboot.
> Our solution was to use r/o only on dataflash.
> 

I would reduce speed to 5 Mbps or lower. or implement the external gate.
Moving to the AT91SAM9260 is of course a nice alternative.
Lower cost, (soon) much higher speed (with the AT91SAM9260A)
Better BootROM (I defined it :-)


> 
> Best regards,
> Ivan
> --------------------------------
> Embedded Linux engineer,
> Promwad Company: http://www.promwad.com/
> Homepage : http://www.ivankuten.com/
> --------------------------------
-- 
Best Regards,
Ulf Samuelsson 

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

2007/10/25, Ulf Samuelsson <ulf@atmel.com>:
>
> ons 2007-10-24 klockan 21:34 +0300 skrev Ivan Kuten:
> > >
> > > During the 1st boot, Dropbear creates and "writes" the generated keys,
> maybe
> > > is this *write* operation the one screwing up the dataflash?
> > >
> >
> > We have similar problems with Dataflash&RM9200
> > *write* operation is unreliable - we had corrupted filesystem after
> reboot.
> > Our solution was to use r/o only on dataflash.
> >
>
> I would reduce speed to 5 Mbps or lower. or implement the external gate.
> Moving to the AT91SAM9260 is of course a nice alternative.
> Lower cost, (soon) much higher speed (with the AT91SAM9260A)
> Better BootROM (I defined it :-)


Can you suggest the best way to reduce  speed?  maybe using the board
definition on the kernel?

Regards,

Jorge.


>
> > Best regards,
> > Ivan
> > --------------------------------
> > Embedded Linux engineer,
> > Promwad Company: http://www.promwad.com/
> > Homepage : http://www.ivankuten.com/
> > --------------------------------
> --
> Best Regards,
> Ulf Samuelsson
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071025/7318add6/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

What about using the SPI bitbang driver for the AT91??

2007/10/25, Ulf Samuelsson <ulf@atmel.com>:
>
> ons 2007-10-24 klockan 21:34 +0300 skrev Ivan Kuten:
> > >
> > > During the 1st boot, Dropbear creates and "writes" the generated keys,
> maybe
> > > is this *write* operation the one screwing up the dataflash?
> > >
> >
> > We have similar problems with Dataflash&RM9200
> > *write* operation is unreliable - we had corrupted filesystem after
> reboot.
> > Our solution was to use r/o only on dataflash.
> >
>
> I would reduce speed to 5 Mbps or lower. or implement the external gate.
> Moving to the AT91SAM9260 is of course a nice alternative.
> Lower cost, (soon) much higher speed (with the AT91SAM9260A)
> Better BootROM (I defined it :-)
>
>
> >
> > Best regards,
> > Ivan
> > --------------------------------
> > Embedded Linux engineer,
> > Promwad Company: http://www.promwad.com/
> > Homepage : http://www.ivankuten.com/
> > --------------------------------
> --
> Best Regards,
> Ulf Samuelsson
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071025/338118f8/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Ulf Samuelsson]

> What about using the SPI bitbang driver for the AT91??
> 


Not a good idea since you are transferring large amount of data.
Better to use the PDC and the H/W SPI.
Just set down the speed of the SPI.

>> ons 2007-10-24 klockan 21:34 +0300 skrev Ivan Kuten:
>> > >
>> > > During the 1st boot, Dropbear creates and "writes" the generated keys,
>> maybe
>> > > is this *write* operation the one screwing up the dataflash?
>> > >
>> >
>> > We have similar problems with Dataflash&RM9200
>> > *write* operation is unreliable - we had corrupted filesystem after
>> reboot.
>> > Our solution was to use r/o only on dataflash.
>> >
>>
>> I would reduce speed to 5 Mbps or lower. or implement the external gate.
>> Moving to the AT91SAM9260 is of course a nice alternative.
>> Lower cost, (soon) much higher speed (with the AT91SAM9260A)
>> Better BootROM (I defined it :-)
>>
>>


Best Regards
Ulf Samuelsson                ulf at atmel.com
Atmel Nordic AB
Mail:  Box 2033, 174 02 Sundbyberg, Sweden
Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
GSM    +46 (706) 22 44 57

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

Ok, i'll give a try, as far as i'm concerned there are two choices for SPI
driver on the kernel:

- AT91_SPI
- ATMEL_SPI

Which one is better?, i've tested ATMEL_SPI this afternoon, but the kernel
doesn't detects my dataflash, can you point me to a source of information to
read steps to define my dataflash speed and get detected on boot?.

My previous kernel was detecting the dataflash itself, but when i define the
speed on my board config, the dataflash isn't detected anymore.

2007/10/25, Ulf Samuelsson <ulf@atmel.com>:
>
> > What about using the SPI bitbang driver for the AT91??
> >
>
>
> Not a good idea since you are transferring large amount of data.
> Better to use the PDC and the H/W SPI.
> Just set down the speed of the SPI.
>
> >> ons 2007-10-24 klockan 21:34 +0300 skrev Ivan Kuten:
> >> > >
> >> > > During the 1st boot, Dropbear creates and "writes" the generated
> keys,
> >> maybe
> >> > > is this *write* operation the one screwing up the dataflash?
> >> > >
> >> >
> >> > We have similar problems with Dataflash&RM9200
> >> > *write* operation is unreliable - we had corrupted filesystem after
> >> reboot.
> >> > Our solution was to use r/o only on dataflash.
> >> >
> >>
> >> I would reduce speed to 5 Mbps or lower. or implement the external
> gate.
> >> Moving to the AT91SAM9260 is of course a nice alternative.
> >> Lower cost, (soon) much higher speed (with the AT91SAM9260A)
> >> Better BootROM (I defined it :-)
> >>
> >>
>
>
> Best Regards
> Ulf Samuelsson                ulf at atmel.com
> Atmel Nordic AB
> Mail:  Box 2033, 174 02 Sundbyberg, Sweden
> Visit:  Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
> Phone +46 (8) 441 54 22     Fax +46 (8) 441 54 29
> GSM    +46 (706) 22 44 57
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071025/3f6eb5c5/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Ulf Samuelsson]

Ok, i'll give a try, as far as i'm concerned there are two choices for SPI
driver on the kernel:

- AT91_SPI
- ATMEL_SPI

Which one is better?, i've tested ATMEL_SPI this afternoon, but the kernel
doesn't detects my dataflash, can you point me to a source of information to
read steps to define my dataflash speed and get detected on boot?.

==> The AT91_SPI is the original SPI for AT91
        The Atmel_SPI is a newer version which also supports AVR32.
        This is probably the one to go for long term, but I did not try it myself.
        Try disabling the SD/MMC card interface.
        You probably want to address questions like this to the linux kernel mailing
        list instead of the buildroot list.

My previous kernel was detecting the dataflash itself, but when i define the
speed on my board config, the dataflash isn't detected anymore.

2007/10/25, Ulf Samuelsson <ulf@atmel.com>:
>
> > What about using the SPI bitbang driver for the AT91??
> >
>
>
> Not a good idea since you are transferring large amount of data.
> Better to use the PDC and the H/W SPI.
> Just set down the speed of the SPI.
>
> >> ons 2007-10-24 klockan 21:34 +0300 skrev Ivan Kuten:
> >> > >
> >> > > During the 1st boot, Dropbear creates and "writes" the generated
> keys,
> >> maybe
> >> > > is this *write* operation the one screwing up the dataflash?
> >> > >
> >> >
> >> > We have similar problems with Dataflash&RM9200
> >> > *write* operation is unreliable - we had corrupted filesystem after
> >> reboot.
> >> > Our solution was to use r/o only on dataflash.
> >> >
> >>
> >> I would reduce speed to 5 Mbps or lower. or implement the external
> gate.
> >> Moving to the AT91SAM9260 is of course a nice alternative.
> >> Lower cost, (soon) much higher speed (with the AT91SAM9260A)
> >> Better BootROM (I defined it :-)
> >>
> >>
>


Best Regards
Ulf Samuelsson

[Buildroot] Dataflash rootfs problems (still)

[Ivan Kuten]

Ulf Samuelsson wrote:
>> What about using the SPI bitbang driver for the AT91??
>>
> 
> 
> Not a good idea since you are transferring large amount of data.
> Better to use the PDC and the H/W SPI.
> Just set down the speed of the SPI.
> 

It was some discussion about Atmel SPI and RM9200 on spi-devel mailing list and as far as I know
Atmel SPI (H/W SPI) is not working for RM9200 - that why Andrew Victor (AT91 maintainer)
still maintaining mtd_dataflash and at91 spi bitbang in his AT91 patches.
I reported about a half of year ago that it's still not working with RM9200.

You have only choice SPI bitbang on lower speed and verify data that is read and written.

Best regards,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

Kernel 2.6.22 doesn't compile when enabling bitbang... Ulf suggests using
H/W SPI.... what to do!?



2007/10/25, Ivan Kuten <ivan.kuten@promwad.com>:
>
> Ulf Samuelsson wrote:
> >> What about using the SPI bitbang driver for the AT91??
> >>
> >
> >
> > Not a good idea since you are transferring large amount of data.
> > Better to use the PDC and the H/W SPI.
> > Just set down the speed of the SPI.
> >
>
> It was some discussion about Atmel SPI and RM9200 on spi-devel mailing
> list and as far as I know
> Atmel SPI (H/W SPI) is not working for RM9200 - that why Andrew Victor
> (AT91 maintainer)
> still maintaining mtd_dataflash and at91 spi bitbang in his AT91 patches.
> I reported about a half of year ago that it's still not working with
> RM9200.
>
> You have only choice SPI bitbang on lower speed and verify data that is
> read and written.
>
> Best regards,
> Ivan
> --------------------------------
> Embedded Linux engineer,
> Promwad Company: http://www.promwad.com/
> Homepage : http://www.ivankuten.com/
> --------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071025/0f8c918a/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Ivan Kuten]

Jorge S. wrote:
> Kernel 2.6.22 doesn't compile when enabling bitbang... Ulf suggests using
> H/W SPI.... what to do!?

check this link:
http://maxim.org.za/at91_26.html


BR,
Ivan
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

Is the site for ARM kernel patches, what to search there?, the only relevant
thing i see is this annotation on 2.6.23:

DataFlash (at91_dataflash & mtd_dataflash): Due to a bug, the
compare-after-write check would never fail. [MicroMax]

My kernel, of course, is already patched for ARM.

2007/10/25, Ivan Kuten <ivan.kuten@promwad.com>:
>
>
>
> Jorge S. wrote:
> > Kernel 2.6.22 doesn't compile when enabling bitbang... Ulf suggests
> using
> > H/W SPI.... what to do!?
>
> check this link:
> http://maxim.org.za/at91_26.html
>
>
> BR,
> Ivan
> --------------------------------
> Embedded Linux engineer,
> Promwad Company: http://www.promwad.com/
> Homepage : http://www.ivankuten.com/
> --------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071025/4acdf7a4/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Ivan Kuten]

Jorge,

That is reply for your statement "Kernel 2.6.22 doesn't compile when enabling bitbang"
try vanilla kernel + patch from maxim.org.za - it should compile OK.

BR,
Ivan

Jorge S. wrote:
> Is the site for ARM kernel patches, what to search there?, the only relevant
> thing i see is this annotation on 2.6.23:
> 
> DataFlash (at91_dataflash & mtd_dataflash): Due to a bug, the
> compare-after-write check would never fail. [MicroMax]
> 
> My kernel, of course, is already patched for ARM.
> 
> 2007/10/25, Ivan Kuten <ivan.kuten@promwad.com>:
>>
>>
>> Jorge S. wrote:
>>> Kernel 2.6.22 doesn't compile when enabling bitbang... Ulf suggests
>> using
>>> H/W SPI.... what to do!?
>> check this link:
>> http://maxim.org.za/at91_26.html
>>
>>
>> BR,
>> Ivan
>> --------------------------------
>> Embedded Linux engineer,
>> Promwad Company: http://www.promwad.com/
>> Homepage : http://www.ivankuten.com/
>> --------------------------------
>>
> 


-- 

--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------

[Buildroot] Dataflash rootfs problems (still)

[Ulf Samuelsson]

ons 2007-10-24 klockan 18:54 +0200 skrev Jorge S.:
> 
> 
> 2007/10/24, Ulf Samuelsson <ulf@atmel.com>:
>         ons 2007-10-24 klockan 18:20 +0200 skrev Jorge S.:
>         > Hello all:
>         >
>         > I've sucessfully built  several root filesystems  for my
>         custom board
>         > (AT91RM9200 + 8MiB DataFlash),  but  now  i'm facing
>         a  strange 
>         > problem.
>         >
>         > I'm using a JFFS2 filesystem on an MTD partition into the
>         DataFlash,
>         > my rootfs boots OK, but ONLY for the first time. See steps:
>         >
>         > 1) Create a rootfs JFFS2 image using buildroot -> OK 
>         > 2) Erase entire flash partition: I boot from an initrd
>         containing
>         > mtd-tools for this purpouse. -> OK
>         > 3) Dump the rootfs image "rootfs.jffs2" into the Dataflash
>         (i use
>         > loadb from u-boot here...) -> OK 
>         > 4) Boot the system... -> OK
>         > 5) Login and issue a simple reboot, no other
>         commands...nothing
>         > else.... -> OK
>         >
>         
>         If you run the SPI faster than 5 Mbps, you are basically
>         screwed.
>         See Errata #13 in the datasheet.
>         
>         You will need to add an external AND gate if you want to run
>         faster.
>         
>         * AND output to the dataflash chip select,
>         * one input to the NPCS0
>         * one input to a GPIO
>         
>         The driver needs to be adapted for this.
> 
> So, there's a flash corruption on the 1st boot?, 
> 
> I'm a little confused now...why u-boot looks like writing OK then?
> I've sucessfully uploaded hundreds of kernels and initrds images to
> the dataflash. 
> 
> During the 1st boot, Dropbear creates and "writes" the generated keys,
> maybe is this *write* operation the one screwing up the dataflash?
> 
> And last question, which one is the best way to solve this by
> software? I suppose i can "slow down" the SPI speed somewhere in the
> kernel or board config at u-boot isn't it? 
> 
> Thanks for helping Ulf.

It is one potential problem, which needs to be addressed,
in U-Boot, linux and dataflashboot.bin.
There may be other problems, which I am not aware of,  but
it is best to fix this to start with.


-- 
Best Regards,
Ulf Samuelsson

[Buildroot] Dataflash rootfs problems (still)

[Michael Trimarchi]

Hi,

>I've sucessfully built  several root filesystems  for my custom board (AT91RM9200 + 8MiB DataFlash),  but  now  i'm >facing a  strange problem.

>I'm using a JFFS2 filesystem on an MTD partition into the DataFlash, my rootfs boots OK, but ONLY for the first time. >See steps:


>1) Create a rootfs JFFS2 image using buildroot -> OK
>2) Erase entire flash partition: I boot from an initrd containing mtd-tools for this purpouse. -> OK
>3) Dump the rootfs image "rootfs.jffs2" into the Dataflash (i use loadb from u-boot here...) -> OK

>4) Boot the system... -> OK
>5) Login and issue a simple reboot, no other commands...nothing else.... -> OK

>After the reboot at step "5" the system comes again, but now when is press BACKSPACE it writes a space, and if i try >to add a user or change the root password

>i always get a "/etc/passwd" not found.



Is a problem of your busybox configuration :)

Regards 
Michael





      ___________________________________ 
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: 
http://it.docs.yahoo.com/nowyoucan.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071024/44dc3067/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

2007/10/24, Michael Trimarchi <trimarchimichael@yahoo.it>:
>
> Hi,
>
> >I've sucessfully built  several root filesystems  for my custom board
> (AT91RM9200 + 8MiB DataFlash),  but  now  i'm >facing a  strange problem.
>
> >I'm using a JFFS2 filesystem on an MTD partition into the DataFlash, my
> rootfs boots OK, but ONLY for the first time. >See steps:
>
> >1) Create a rootfs JFFS2 image using buildroot -> OK
> >2) Erase entire flash partition: I boot from an initrd containing
> mtd-tools for this purpouse. -> OK
> >3) Dump the rootfs image "rootfs.jffs2" into the Dataflash (i use loadb
> from u-boot here...) -> OK
> >4) Boot the system... -> OK
> >5) Login and issue a simple reboot, no other commands...nothing else....
> -> OK
>
> >After the reboot at step "5" the system comes again, but now when is
> press BACKSPACE it writes a space, and if i try >to add a user or change the
> root password
> >i always get a "/etc/passwd" not found.
>



Is a problem of your busybox configuration :)
>


Can you point me to something concrete?

And, if busybox isn't properly configured, why is it working fine for the
very first time?

I use the default busybox (1.6.0) on buildroot. Any *must-change* option?

Regards.

Regards
> Michael
>
>
> ------------------------------
> L'email della prossima generazione? Puoi averla con la Nuova Yahoo! Mail<http://us.rd.yahoo.com/mail/it/taglines/gmail/nowyoucan/nextgen/*http://it.docs.yahoo.com/nowyoucan.html>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071024/f2321fca/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

2007/10/24, Jorge S. <jorgesolla@gmail.com>:
>
>
>
> 2007/10/24, Michael Trimarchi <trimarchimichael@yahoo.it>:
> >
> > Hi,
> >
> > >I've sucessfully built  several root filesystems  for my custom board
> > (AT91RM9200 + 8MiB DataFlash),  but  now  i'm >facing a  strange problem.
> >
> > >I'm using a JFFS2 filesystem on an MTD partition into the DataFlash, my
> > rootfs boots OK, but ONLY for the first time. >See steps:
> >
> > >1) Create a rootfs JFFS2 image using buildroot -> OK
> > >2) Erase entire flash partition: I boot from an initrd containing
> > mtd-tools for this purpouse. -> OK
> > >3) Dump the rootfs image "rootfs.jffs2 " into the Dataflash (i use
> > loadb from u-boot here...) -> OK
> > >4) Boot the system... -> OK
> > >5) Login and issue a simple reboot, no other commands...nothing
> > else.... -> OK
> >
> > >After the reboot at step "5" the system comes again, but now when is
> > press BACKSPACE it writes a space, and if i try >to add a user or change the
> > root password
> > >i always get a "/etc/passwd" not found.
> >
>
>
>
> Is a problem of your busybox configuration :)
> >
>
>
> Can you point me to something concrete?
>
> And, if busybox isn't properly configured, why is it working fine for the
> very first time?
>
> I use the default busybox (1.6.0) on buildroot. Any *must-change* option?
>

I mean -> I use the default busibox CONFIG on build root. In fact, i use
busybox 1.70 and 1.6.0 config as
default on buildroot.

Is there anything wrong here?

Regards.
>
> Regards
> > Michael
> >
> >
> > ------------------------------
> > L'email della prossima generazione? Puoi averla con la Nuova Yahoo! Mail<http://us.rd.yahoo.com/mail/it/taglines/gmail/nowyoucan/nextgen/*http://it.docs.yahoo.com/nowyoucan.html>
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071024/1a3015ef/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Michael Trimarchi]

Can you point me to something concrete? 



And, if busybox isn't properly configured, why is it working fine for the very first time?




I use the default busybox (1.6.0) on buildroot. Any *must-change* option?



The problem is that I don't remember :(.

Try to add tab-completation in busybox settings, library tunings.

Seem to be crazy, but I remember this change.

:) or I'll send you my config. I use the 1.6.1

Regards MIchael








      ___________________________________ 
L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: 
http://it.docs.yahoo.com/nowyoucan.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071024/35df54da/attachment.htm 

[Buildroot] Dataflash rootfs problems (still)

[Jorge S.]

2007/10/24, Michael Trimarchi <trimarchimichael@yahoo.it>:
>
>
>
> >
> > Can you point me to something concrete?
> >
> > And, if busybox isn't properly configured, why is it working fine for
> > the very first time?
> >
> > I use the default busybox (1.6.0) on buildroot. Any *must-change*
> > option?
> >
>
>
> The problem is that I don't remember :(.
>
> Try to add tab-completation in busybox settings, library tunings.
>

Tab-completation (if you mean  command completation when you press the TAB
key) works fine during the first boot and subsequent boots (even when
everything else looks weird), so i think its enabled, anyway i'm going to
check.

Seem to be crazy, but I remember this change.
>

Not so crazy, sometimes weird problems are coming for weird reasons.


:) or I'll send you my config. I use the 1.6.1
>

It will really help, can u please send it?

Thank you.

Regards,

Jorge.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20071024/8e572876/attachment.htm