Flash chip for NGW100

10 posts / 0 new
Last post
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi, I want to use Spansion chip S29GL064N90TFI060 with NGW100.

manufacturer id: 0x01 (AMD)
device id: 0x277E

Here my situation:

JTAG: OK! (I can read and write u-boot and rootfs)
u-boot: OK! (I can write rootfs and read jffs2 filesystem)
Linux kernel: ERROR.

Linux kernel doesn't mount jffs2 filesystem.

...
at32ap700x_rtc at32ap700x_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
atmel_mci atmel_mci.0: Atmel MCI controller at 0xfff02400 irq 28, 1 slots
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
List of all partitions:
No filesystem could mount root, tried:  jffs2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Call trace:
 [<9001a6c0>] dump_stack+0x18/0x20
 [<90021734>] panic+0x40/0xa8
 [<9000090e>] mount_block_root+0x15e/0x17c
 [<900009b0>] mount_root+0x84/0xac
 [<90000a9a>] prepare_namespace+0xc2/0x104
 [<900003e6>] kernel_init+0xae/0xe8
 [<90023c62>] do_exit+0x0/0x3c2
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Is the kernel small enough to fit that memory size?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Here my u-boot instructions:

protect off 0x20000 0x7EFFFF;erase 0x20000 0x7EFFFF;tftp 0x90000000 rootfs.avr32.jffs2-root-311;cp.b 0x90000000 0x20000 0x590000;protect on all;boot

rootfs.avr32.jffs2 is 5832704 bytes (5,6M)
/boot/uImage is 1504939 bytes (1,5M)

it seems ok

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm not well educated regarding this. But 5.6MB + 1.5MB = 7.1MB? And you have 8MB? So Environmental variables and U-boot where U-boot is a little over 100kB, and the variables small. Could it be close?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yes is 8MB, but the kernel is inside rootfs.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

How does your u-boot variables look like? printenv in u-boot.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0
bootargs=console=ttyS0 root=/dev/mtdblock1 rootfstype=jffs2
bootcmd=fsload 0x90400000 /boot/uImage;bootm
bootdelay=1
baudrate=115200
ethaddr=00:04:25:1C:56:04
eth2addr=00:04:25:1C:56:05
hostname="prova-v1"
unlock=yes
stdin=serial
stdout=serial
stderr=serial
ethact=macb0
filesize=590000
fileaddr=90000000
ipaddr=10.106.243.92
serverip=10.106.243.46

Environment size: 349/65532 bytes
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

0x90400000, is that correct position?
But it is complaining about "unknown-block(2,0)".

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Try root=mtd1 or root=mtd: instead of /dev/mtdblock1. The latter doesn't work unless you enable MTD block device interface (and there's usually no other reason why you'd enable that).

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0
atmel_mci atmel_mci.0: Atmel MCI controller at 0xfff02400 irq 28, 1 slots
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
List of all partitions:
No filesystem could mount root, tried:  jffs2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Call trace:
 [<9001a6c0>] dump_stack+0x18/0x20
 [<90021734>] panic+0x40/0xa8
 [<9000090e>] mount_block_root+0x15e/0x17c
 [<900009b0>] mount_root+0x84/0xac
 [<90000a9a>] prepare_namespace+0xc2/0x104
 [<900003e6>] kernel_init+0xae/0xe8
 [<90023c62>] do_exit+0x0/0x3c2

Same result with root=mtd1 or root=mtd:root
Can it depends on jffs2 image (i'm using default buildroot parameters)? In u-boot prompt "ls" command give me a correct list of jffs2 directory/files...