Glomation
 
Advanced Search
Welcome, Guest. Please login or register.

Login with username, password and session length
May 22, 2012, 04:21:29 AM
Home Help Calendar Login Register
News: Welcome to GLomation peer support forum
Pages: [1]
Topic Tools  
Read December 07, 2008, 02:56:43 PM #0
admin

  • *****
  • Administrator
  • Super Hero
  • Posts: 342
Use SD card as root file system on GESBC-9260(S)
The GESBC-9260(S) can use SD/MMC card, NFS, USB, and on-board NAND FLASH as root file system media.  The U-boot bootargs environment variable can be used to boot system using different media.  The bootargs setting for SD/MMC root file system is,

set bootargs console=ttyS0,115200 root=/dev/mmcblk0p1 rootdelay=1 mtdparts=at91_nand:1M(bootloader),3M(kernel),-(rootfs)

The MTD partition command is optional but the rootdelay is generally required since the kernel may start mounting the root file system before the MMC/SD card driver is ready.

« Last Edit: December 18, 2008, 11:42:51 AM by admin »
 
Read January 08, 2009, 12:20:48 PM #1
xfactor69

  • *****
  • Super Hero
  • Posts: 16
Re: Use SD card as root file system on GESBC-9260(S)
It seems to be hanging after it recognized the SD card:

NAND read: device 0 offset 0x100000, size 0x200000
 2097152 bytes read: OK
## Booting kernel from Legacy Image at 22000000 ...
   Image Name:   Linux-2.6.25
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1457996 Bytes =  1.4 MB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................................................. done, booting the kernel.
Linux version 2.6.25 (user1@Atlas) (gcc version 4.2.3) #15 Sun Aug 3 07:42:28 EDT 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Atmel AT91SAM9260-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 198 MHz, master 99 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p1 rootdelay=1 mtdparts=at91_nand:1M(bootloader),3M(kernel),-(rootfs)
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61836KB available (2680K code, 221K data, 120K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 152 bytes
NET: Registered protocol family 16
AT91: Power Management
AT91: Starting after software reset
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
yaffs Jul 27 2008 10:51:08 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
atmel_usart.4: ttyS4 at MMIO 0xfffd0000 (irq = 23) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
ssc ssc.0: Atmel SSC device at 0xc4878000 (irq 14)
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:0c:20:02:0a:5b)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)
Driver 'sd' needs updating - please use bus_type methods
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
AT91 NAND: 8-bit, Software ECC
Scanning device for bad blocks
Bad eraseblock 831 at 0x067e0000
Bad eraseblock 941 at 0x075a0000
3 cmdlinepart partitions found on MTD device at91_nand
Creating 3 MTD partitions on "at91_nand":
0x00000000-0x00100000 : "bootloader"
0x00100000-0x00400000 : "kernel"
0x00400000-0x08000000 : "rootfs"
usbmon: debugfs is not available
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
input: gpio-keys as /class/input/input0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
rtc-at91sam9 at91_rtt.0: rtc0: SET TIME!
i2c /dev entries driver
at91sam9_wdt: invalid timeout (must be between 1 and 16)
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch.  Assuming write-enable.
mmc0: new SD card at address 1234
mmcblk0: mmc0:1234 SA01G 995328KiB
 mmcblk0:RomBOOT
>

U-Boot 1.3.3 (Aug  1 2008 - 22:49:42)

DRAM:  64 MB
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   macb0
macb0: Starting autonegotiation...
macb0: Autonegotiation complete
macb0: link up, 100Mbps full-duplex (lpa: 0x45e1)
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x100000, size 0x200000
 2097152 bytes read: OK
## Booting kernel from Legacy Image at 22000000 ...
   Image Name:   Linux-2.6.25
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1457996 Bytes =  1.4 MB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................................................. done, booting the kernel.
Linux version 2.6.25 (user1@Atlas) (gcc version 4.2.3) #15 Sun Aug 3 07:42:28 EDT 2008
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: Atmel AT91SAM9260-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 198 MHz, master 99 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Kernel command line: console=ttyS0,115200 root=/dev/mmcblk0p1 rootdelay=1 mtdparts=at91_nand:1M(bootloader),3M(kernel),-(rootfs)
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
console [ttyS0] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 61836KB available (2680K code, 221K data, 120K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
net_namespace: 152 bytes
NET: Registered protocol family 16
AT91: Power Management
AT91: Starting after general reset
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
yaffs Jul 27 2008 10:51:08 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
atmel_usart.1: ttyS1 at MMIO 0xfffb0000 (irq = 6) is a ATMEL_SERIAL
atmel_usart.2: ttyS2 at MMIO 0xfffb4000 (irq = 7) is a ATMEL_SERIAL
atmel_usart.4: ttyS4 at MMIO 0xfffd0000 (irq = 23) is a ATMEL_SERIAL
brd: module loaded
loop: module loaded
ssc ssc.0: Atmel SSC device at 0xc4878000 (irq 14)
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (00:0c:20:02:0a:5b)
eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=ffffffff:00, irq=-1)
Driver 'sd' needs updating - please use bus_type methods
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
AT91 NAND: 8-bit, Software ECC
Scanning device for bad blocks
Bad eraseblock 831 at 0x067e0000
Bad eraseblock 941 at 0x075a0000
3 cmdlinepart partitions found on MTD device at91_nand
Creating 3 MTD partitions on "at91_nand":
0x00000000-0x00100000 : "bootloader"
0x00100000-0x00400000 : "kernel"
0x00400000-0x08000000 : "rootfs"
usbmon: debugfs is not available
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
udc: at91_udc version 3 May 2006
mice: PS/2 mouse device common for all mice
input: gpio-keys as /class/input/input0
rtc-at91sam9 at91_rtt.0: rtc core: registered at91_rtt as rtc0
rtc-at91sam9 at91_rtt.0: rtc0: SET TIME!
i2c /dev entries driver
at91sam9_wdt: invalid timeout (must be between 1 and 16)
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
rtc-at91sam9 at91_rtt.0: hctosys: unable to read the hardware clock
Waiting 1sec before mounting root device...
mmc0: host does not support reading read-only switch.  Assuming write-enable.
mmc0: new SD card at address 1234
mmcblk0: mmc0:1234 SA01G 995328KiB
 mmcblk0:


Any ideas?

Thanks,
xf
 
Read January 08, 2009, 01:11:40 PM #2
admin

  • *****
  • Administrator
  • Super Hero
  • Posts: 342
Re: Use SD card as root file system on GESBC-9260(S)
Can first verify that the SD card is programmed and can be read by the board?
 
Read January 08, 2009, 01:28:04 PM #3
xfactor69

  • *****
  • Super Hero
  • Posts: 16
Re: Use SD card as root file system on GESBC-9260(S)
I untarred your root filesystem onto an ext2 formatted sd card in my ubuntu linux system.  Is ext2 appropriate for the sd card?

I looked at the files that got untarred and they looked ok.

Thanks,
xf
 
Read January 08, 2009, 01:35:04 PM #4
admin

  • *****
  • Administrator
  • Super Hero
  • Posts: 342
Re: Use SD card as root file system on GESBC-9260(S)
EXT2 should work fine.  Can you verify that SD card can be read by the board?
 
Read January 08, 2009, 02:14:46 PM #5
xfactor69

  • *****
  • Super Hero
  • Posts: 16
Re: Use SD card as root file system on GESBC-9260
I restarted from flash and this was part of the bootup info:

Freeing init memory: 120K
mmc0: host does not support reading read-only switch.  Assuming write-enable.
mmc0: new SD card at address 1234
mmcblk0: mmc0:1234 SA01G 995328KiB
INIT: version 2.86 booting

So I assume the card got registered ok with the system.

Then I tried:
mount /dev/sda1 /mnt
mount: /dev/sda1 is not a valid block device

Then I tried:
mount /dev/mmcblk0p1 /mnt

It just hung

Thoughts,
xf
 
Read January 08, 2009, 03:00:14 PM #6
admin

  • *****
  • Administrator
  • Super Hero
  • Posts: 342
Re: Use SD card as root file system on GESBC-9260(S)
Please try a different card preferably a different brand to see if you can mount the card.  If you still have the problem then it is most likely the board problem and you can request it be repaired or replaced.
 
Read January 08, 2009, 07:14:58 PM #7
xfactor69

  • *****
  • Super Hero
  • Posts: 16
Re: Use SD card as root file system on GESBC-9260(S)
Got it to work with a 256MB SD card.

It doesn't work with my Kingston MicroSD adapter and a 1GB.

Thanks for the suggestions.

xf
 
Read January 12, 2009, 06:30:01 PM #8
Jerry Wong

  • Guest
Re: Use SD card as root file system on GESBC-9260(S)
Quick question about this: I have the root FS on the SD card and the system boots, but it complains about things like being unable to find files in /lib/modules/2.6.25/modules.dep, and ifconfig complains with "cannot open proc/net/dev no such file" errors. Is there a script to be run with this distro to get everything set up?
 
Read January 13, 2009, 06:18:49 AM #9
admin

  • *****
  • Administrator
  • Super Hero
  • Posts: 342
Re: Use SD card as root file system on GESBC-9260(S)
Each version of kernel requires its own set of module files.  The Debian distribution provided is kept to be as generic as possible.  You can build your modules and install them.  If you don't have any modules you can comment out the script that trying to load any modules.
 
Pages: [1]
« previous next »
Jump to:  

Theme Update by Runic Warrior Originally created by m3talc0re Powered by SMF 1.1.15 | SMF © 2006-2008, Simple Machines MySQL | PHP | XHTML | CSS