General Question (off-topic)

HI all,

I have two questions but it’s not based on beagleboard architecture and hope you allow me to post this.

  1. I have 64MB of Nand flash with erase block of 16KiB. I created an jffs2 image
    with pagesize of 0x200. After I put the image on nandflash using nandwrite and booted it.
    I got these message:

jffs2: Erase block size too small (16KiB). Using virtual blocks size (32KiB) instead

Then, I tried to create another jffs2 image with 32KiB of eraseblock and pass --blockalign=2.
But, I got same messages.

Do you know how to fix it?.

  1. This is regarding with u-boot. Is there a way to access whatever defined u-boot environment or read the u-boot block0
    from linux userspace?.
    I am looking for a different solution and I cannot use the kernel argument to pass the u-boot environment then,

parse the /proc/cmdline to get the data that I need.

Any idea?

Thanks,

John

HI all,
I have two questions but it's not based on beagleboard architecture and hope
you allow me to post this.
1. I have 64MB of Nand flash with erase block of 16KiB. I created an jffs2
image
with pagesize of 0x200. After I put the image on nandflash using nandwrite
and booted it.
I got these message:
jffs2: Erase block size too small (16KiB). Using virtual blocks size (32KiB)
instead
Then, I tried to create another jffs2 image with 32KiB of eraseblock and
pass --blockalign=2.
But, I got same messages.
Do you know how to fix it?.
2. This is regarding with u-boot. Is there a way to access whatever defined
u-boot environment or read the u-boot block0
from linux userspace?.
I am looking for a different solution and I cannot use the kernel argument
to pass the u-boot environment then,
parse the /proc/cmdline to get the data that I need.
Any idea?

With most builds of the linux kernel for Beagle, /dev/mtdX and
/dev/mtdblockX would have the contents of the NAND flash (which you
must have been accessing for your JFFS2 manipulations). The u-boot
project generates an application that can be used to read the u-boot
environment variables (fw_printenv). It is covered in the BeagleBoard
101 materials on ESC Build Your Own Embedded System online registration deadline 3/25 - BeagleBoard. Recommend you use Google
or search this mailing list to find more.

Jason,

Thanks for the response. I saw the utility and using it.
But, I got an error “Bad CRC, using default environment” when I execute the fw_printenv
any idea how to fix it?

-john