From: rketcham <Ric...@gm...> - 2008-06-24 18:46:46
|
Hi Everyone, I've found a few threads on the forum about an RTC backup but nothing with real specifics. There was one page the linked to a blog where the owner described his inability to get the RTC backup working. I looked at the power ic data sheet as Craig suggested. The power management chip referred to by this page http://docwiki.gumstix.org/V_BACKUP_BATT isn't the one that's on the verdex (at least the one I have). Mine has the TPS65020. So, trying as suggested, I disconnected R9 on the verdex and put a 5 V super cap with a 250 Ohm resister in it's place. One end of R9 is connected to GND while the other is connected to V_BACKUP_BATT. Setting the date using date 062901412008.10 and then rebooting, I found that the date wasn't kept. It reverted back to the epoch. I've seen a few comments that other aspects of the PXA270 need to be powered including this thread: http://www.nabble.com/verdex-rtc-td11817179.html#a11818743 My question is this - is there a way to backup the rtc without powering the entire chip? If so, could you explain how or point me to where I may be able to find out? Thanks, Rich -- View this message in context: http://www.nabble.com/RTC-Backup-tp18097455p18097455.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Alex J. <al...@ba...> - 2008-06-25 04:59:35
|
I have a problem, I upgraded my connex gumstix with U-Boot 1.2.0 and now when I try to boot I get the following. Below is my environment variables. I have tried modifying bootargs=console=ttyS0,115200n8 root=1f01 rootfstype=jffs2 to root=1f02, Same error? I know its probably something silly, I flashed the gumstix with the following from mmc. Please help? mmcinit fatls mmc 1 fatload mmc 1 a2000000 gumstix-basic-image-gumstix-custom-connex.jffs2 protect on 1:0-1 erase all cp.b a2000000 40000 ${filesize} fatload mmc 1 a2000000 uimage-2.6.21-r1-gumstix-custom-connex.bin katinstall 100000 katload 100000 bootm ### JFFS2 LOAD ERROR<0> for boot/uImage! U-Boot 1.2.0 (May 10 2008 - 13:33:03) - 400 MHz - 1604 *** Welcome to Gumstix *** DRAM: 64 MB Flash: 16 MB SMC91C1111-0 Can't overwrite "serial#" Can't overwrite "ethaddr" Net: SMC91C1111-0 Hit any key to stop autoboot: 0 Instruction Cache is ON ### JFFS2 loading 'boot/uImage' to 0xa2000000 Scanning JFFS2 FS: .....| Unknown node type: e002 len 2356 offset 0x27bec4 Unknown node type: e002 len 1912 offset 0x27cd78 / Unknown node type: e002 len 302 offset 0x281fdc ..\ Unknown node type: e002 len 2613 offset 0x420638 Unknown node type: e002 len 2722 offset 0x42158c Unknown node type: e002 len 2781 offset 0x436aac ............ done. find_inode failed for name=uImage-2.6.21 load: Failed to resolve inode structure ### JFFS2 LOAD ERROR<0> for boot/uImage! GUM> GUM> ls drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 bin drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 boot drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 dev drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 etc drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 home drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 lib drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 media drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 mnt drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 proc drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 sbin drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 sys drwxrwxrwt 0 Thu Jan 01 00:00:00 1970 tmp drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 usr drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 var GUM> fsload ### JFFS2 loading 'boot/uImage' to 0xa2000000 find_inode failed for name=uImage-2.6.21 load: Failed to resolve inode structure ### JFFS2 LOAD ERROR<0> for boot/uImage! GUM> ls /boot lrwxrwxrwx 13 Thu Jan 01 00:00:00 1970 uImage -> uImage-2.6.21 GUM> ls /boot/uImage GUM> ls /boot/uImage-2.6.21 find_inode failed for name=uImage-2.6.21 ls: Failed to scan jffs2 file structure GUM> fsload a2000000 boot/uImage ### JFFS2 loading 'boot/uImage' to 0xa2000000 find_inode failed for name=uImage-2.6.21 load: Failed to resolve inode structure ### JFFS2 LOAD ERROR<0> for boot/uImage! GUM> pri bootdelay=2 baudrate=115200 bootfile=boot/uImage verify=no ethact=SMC91C1111-0 serial#=66296072C4BDD977 ethaddr=62:72:C4:BD:D9:50 bootcmd=icache on; fsload a2000000 boot/uImage && bootm bootargs=console=ttyS0,115200n8 root=1f01 rootfstype=jffs2 stdin=serial stdout=serial stderr=serial Environment size: 286/4092 bytes GUM> |
From: Dave H. <dhy...@gm...> - 2008-06-25 05:23:30
|
Hi Alex, > GUM> pri > bootdelay=2 > baudrate=115200 > bootfile=boot/uImage > verify=no > ethact=SMC91C1111-0 > serial#=66296072C4BDD977 > ethaddr=62:72:C4:BD:D9:50 > bootcmd=icache on; fsload a2000000 boot/uImage && bootm > bootargs=console=ttyS0,115200n8 root=1f01 rootfstype=jffs2 > stdin=serial > stdout=serial > stderr=serial Try changing your bootcmd to be: setenv bootcmd "icache on; katload 100000 && bootm" -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Alex J. <al...@ba...> - 2008-06-25 13:29:29
|
Thanks, that got me a little bit further, but not home yet I am getting VFS: Cannot open root device "1f02" or unknown-block(31,2) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2) Now I have tried using bootargs using root=1f01 and root=1f02 and I get the similar results cannot open root device. Thanks -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dave Hylands Sent: Wednesday, June 25, 2008 1:24 AM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Newly Flashed Boot Problem - Connex - U-Boot 1.2.0 Hi Alex, > GUM> pri > bootdelay=2 > baudrate=115200 > bootfile=boot/uImage > verify=no > ethact=SMC91C1111-0 > serial#=66296072C4BDD977 > ethaddr=62:72:C4:BD:D9:50 > bootcmd=icache on; fsload a2000000 boot/uImage && bootm > bootargs=console=ttyS0,115200n8 root=1f01 rootfstype=jffs2 > stdin=serial > stdout=serial > stderr=serial Try changing your bootcmd to be: setenv bootcmd "icache on; katload 100000 && bootm" -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2008-06-25 13:53:36
|
Hi Alex, On Wed, Jun 25, 2008 at 6:29 AM, Alex Jeannopoulos <al...@ba...> wrote: > Thanks, that got me a little bit further, but not home yet I am getting > > VFS: Cannot open root device "1f02" or unknown-block(31,2) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(31,2) > > Now I have tried using bootargs using root=1f01 and root=1f02 and I get the > similar results > cannot open root device. For the newer kernels, you'll definitely want root=1f01 You may want to try re-downloading, now that the env is right. If you ever managed to get the kernel to partially bootup with the wrong stuff it could have corrupted stuff (jffs2 rewrites blocks that appear to be bad). If that still doesn't work, then send us the entire boot log, right from the beginning of u-boot to the error in the kernel. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Alex J. <al...@ba...> - 2008-06-26 04:31:46
|
I reflashed and I am still getting the error Unable to mount root fs on unknown-block(31,1), Below is the full boot process and flashing process. I had built the kernel after adding MACHINE_FEATURES in com.gumstix.collection/conf/machine/gumstix-custom-connex.conf rebuilt using bitbake -c rebuild task-base-gumstix bitbake -c rebuild gumstix-basic-image The full boot log showing the environment and flashing is below. Thanks Alex VFS: Cannot open root device "1f01" or unknown-block(31,1) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,1) U-Boot 1.2.0 (May 10 2008 - 13:33:03) - 400 MHz - 1604 *** Welcome to Gumstix *** DRAM: 64 MB Flash: 16 MB SMC91C1111-0 Can't overwrite "serial#" Can't overwrite "ethaddr" Net: SMC91C1111-0 Hit any key to stop autoboot: 2 þþþþÿþþ U-Boot 1.2.0 (May 10 2008 - 13:33:03) - 400 MHz - 1604 *** Welcome to Gumstix *** DRAM: 64 MB Flash: 16 MB SMC91C1111-0 Can't overwrite "serial#" Can't overwrite "ethaddr" Net: SMC91C1111-0 Hit any key to stop autoboot: 0 GUM> pri bootdelay=2 baudrate=115200 bootfile=boot/uImage verify=no ethact=SMC91C1111-0 serial#=66296072C4BDD977 ethaddr=62:72:C4:BD:D9:50 bootcmd=icache on; katload 100000 && bootm bootargs=console=ttyS0,115200n8 root=1f01 rootfstype=jffs2 reboot=cold,hard stdin=serial stdout=serial stderr=serial Environment size: 290/4092 bytes GUM> mmcinit Detected: 1983488 blocks of 1024 bytes (1937MB) MMC card. Vendor: Man 70 OEM 0000 "MMCM " Date 03/2007 Product: 595593857 Revision: N/A GUM> fatls mmc 1 9206892 gumstix-basic-image-gumstix-custom-connex.jffs2 913092 uimage-2.6.21-r1-gumstix-custom-connex.bin 2 file(s), 0 dir(s) GUM> fatload mmc 1 a2000000 gumstix-basic-image-gumstix-custom-connex.jffs2 reading gumstix-basic-image-gumstix-custom-connex.jffs2 9206892 bytes read GUM> protect on 1:0-1 Protect Flash Sectors 0-1 in Bank # 1 .. done GUM> erase all Erase Flash Bank # 1 - Warning: 2 protected sectors will not be erased! ............................................................................ .................................................. done GUM> cp.b a2000000 40000 ${filesize} Copy to Flash... done GUM> fatload mmc 1 a2000000 uimage-2.6.21-r1-gumstix-custom-connex.bin reading uimage-2.6.21-r1-gumstix-custom-connex.bin 913092 bytes read GUM> katinstall 100000 Copying kernel from 0xa2000000 to 0x00f00000 (length 0x00100000)...Erasing... ........ done Erased 8 sectors Writing...done GUM> katload 100000 Copying kernel to 0xa2000000 from 0x00f00000 (length 0x00100000)...done GUM> bootm ## Booting image at a2000000 ... Image Name: Angstrom/2.6.21/gumstix-custom-c Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 913028 Bytes = 891.6 kB Load Address: a0008000 Entry Point: a0008000 OK Starting kernel ... Linux version 2.6.21 (alexj@localhost.localdomain) (gcc version 4.1.2) #1 PREEMPT Tue Jun 24 21:10:47 EDT 2008 CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE), cr=0000397f Machine: The Gumstix Platform Memory policy: ECC disabled, Data cache writeback Memory clock: 99.53MHz (*27) Run Mode clock: 398.13MHz (*4) Turbo Mode clock: 398.13MHz (*1.0, inactive) CPU0: D VIVT undefined 5 cache CPU0: I cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets CPU0: D cache: 32768 bytes, associativity 32, 32 byte lines, 32 sets Built 1 zonelists. Total pages: 16256 Kernel command line: console=ttyS0,115200n8 root=1f01 rootfstype=jffs2 reboot=cold,hard PID hash table entries: 256 (order: 8, 1024 bytes) Console: colour dummy device 80x30 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: 62872KB available (1740K code, 181K data, 72K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 Time: pxa_timer clocksource has been installed. 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 io scheduler noop registered io scheduler cfq registered (default) pxa2xx-uart.0: ttyS0 at MMIO 0x40100000 (irq = 15) is a FFUART pxa2xx-uart.1: ttyS1 at MMIO 0x40200000 (irq = 14) is a BTUART pxa2xx-uart.2: ttyS2 at MMIO 0x40700000 (irq = 13) is a STUART pxa2xx-uart.3: ttyS3 at MMIO 0x41600000 (irq = 0) is a HWUART Probing Gumstix Flash ROM at physical address 0x00000000 (16-bit bankwidth) Gumstix Flash ROM: Found 1 x16 devices at 0x0 in 16-bit bank Intel/Sharp Extended Query Table at 0x0031 Using buffer write method cfi_cmdset_0001: Erase suspend on write enabled Using static partitions on Gumstix Flash ROM Creating 3 MTD partitions on "Gumstix Flash ROM": 0x00000000-0x00040000 : "Bootloader" 0x00040000-0x00f00000 : "RootFS" 0x00f00000-0x01000000 : "Kernel" TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 XScale DSP coprocessor detected. VFS: Cannot open root device "1f01" or unknown-block(31,1) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,1) -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dave Hylands Sent: Wednesday, June 25, 2008 9:54 AM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Newly Flashed Boot Problem - Connex - U-Boot 1.2.0 Hi Alex, On Wed, Jun 25, 2008 at 6:29 AM, Alex Jeannopoulos <al...@ba...> wrote: > Thanks, that got me a little bit further, but not home yet I am getting > > VFS: Cannot open root device "1f02" or unknown-block(31,2) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(31,2) > > Now I have tried using bootargs using root=1f01 and root=1f02 and I get the > similar results > cannot open root device. For the newer kernels, you'll definitely want root=1f01 You may want to try re-downloading, now that the env is right. If you ever managed to get the kernel to partially bootup with the wrong stuff it could have corrupted stuff (jffs2 rewrites blocks that appear to be bad). If that still doesn't work, then send us the entire boot log, right from the beginning of u-boot to the error in the kernel. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2008-06-26 04:49:27
|
Hi Alex, On Wed, Jun 25, 2008 at 9:31 PM, Alex Jeannopoulos <al...@ba...> wrote: > I reflashed and I am still getting the error Unable to mount root fs on > unknown-block(31,1), It would seem that the jffs2 image is somehow corrupt then. Try reloading the fileystem (.jffs2 file) and then don't load the kernel. Then from u-boot issue an ls command and see if it recognizes anything on the filesystem. You can also do ls /etc or use other directories to poke around and see what you can see in the filesystem. Repeat this with a known-good filesystem, just to confirm that it does in fact work. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Alex J. <al...@ba...> - 2008-06-26 13:00:34
|
A couple of weird things, I was able to execute >ls >ls /etc originally and then I tried just flashing the jffs2, I even recopied it to the mmc card, If I only flash the jffs2, I got a different error Bad Magic Number. Where can I find a prebuilt jffs2 that I can try (for connex board), Any other things I can try, I appreciate the quick responses so far. Thanks U-Boot 1.2.0 (May 10 2008 - 13:33:03) - 400 MHz - 1604 *** Welcome to Gumstix *** DRAM: 64 MB Flash: 16 MB SMC91C1111-0 Can't overwrite "serial#" Can't overwrite "ethaddr" Net: SMC91C1111-0 Hit any key to stop autoboot: 0 Instruction Cache is ON Copying kernel to 0xa2000000 from 0x00f00000 (length 0x00100000)...done ## Booting image at a2000000 ... Bad Magic Number U-Boot 1.2.0 (May 10 2008 - 13:33:03) - 400 MHz - 1604 *** Welcome to Gumstix *** DRAM: 64 MB Flash: 16 MB SMC91C1111-0 Can't overwrite "serial#" Can't overwrite "ethaddr" Net: SMC91C1111-0 Hit any key to stop autoboot: 0 GUM> ls Scanning JFFS2 FS: .....| Unknown node type: e002 len 2356 offset 0x27bec4 Unknown node type: e002 len 1912 offset 0x27cd78 / Unknown node type: e002 len 302 offset 0x281fdc ..\ Unknown node type: e002 len 2613 offset 0x420638 Unknown node type: e002 len 2722 offset 0x42158c Unknown node type: e002 len 2781 offset 0x436aac .............. done. drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 bin drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 boot drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 dev drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 etc drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 home drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 lib drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 media drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 mnt drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 proc drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 sbin drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 sys drwxrwxrwt 0 Thu Jan 01 00:00:00 1970 tmp drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 usr drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 var GUM> ls /etc -rw-rw-rw- 9 Thu Jan 01 00:00:00 1970 TZ drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 alternatives -rw-r--r-- 3650 Thu Jan 01 00:00:00 1970 asound.state -rw-r--r-- 119 Thu Jan 01 00:00:00 1970 asoundrc drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 bluetooth drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 boa -rw-r----- 139 Thu Jan 01 00:00:00 1970 bonjour.conf -rw-r--r-- 2059 Thu Jan 01 00:00:00 1970 busybox.links drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 dbus-1 drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 default -rwxr-xr-x 6666 Thu Jan 01 00:00:00 1970 device_table drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 dropbear -rw-r--r-- 27 Thu Jan 01 00:00:00 1970 filesystems -rw-r--r-- 1072 Thu Jan 01 00:00:00 1970 fstab -rw-r--r-- 461 Thu Jan 01 00:00:00 1970 group -rw-rw-r-- 139 Thu Jan 01 00:00:00 1970 gumstix-version -rw-r--r-- 26 Thu Jan 01 00:00:00 1970 host.conf -rw-rw-r-- 22 Thu Jan 01 00:00:00 1970 hostname -rw-r--r-- 44 Thu Jan 01 00:00:00 1970 hosts drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 init.d -rw-r--r-- 851 Thu Jan 01 00:00:00 1970 inittab -rw-r--r-- 1633 Thu Jan 01 00:00:00 1970 inputrc drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 ipkg -rw-r--r-- 739 Thu Jan 01 00:00:00 1970 ipkg.conf -rw-r--r-- 63 Thu Jan 01 00:00:00 1970 issue -rw-r--r-- 58 Thu Jan 01 00:00:00 1970 issue.net -rw-r--r-- 30 Thu Jan 01 00:00:00 1970 ld.so.conf -rw-r--r-- 449 Thu Jan 01 00:00:00 1970 mailcap.order -rw-r--r-- 17381 Thu Jan 01 00:00:00 1970 mime.types drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 modprobe.d drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 modutils -rw-r--r-- 119 Thu Jan 01 00:00:00 1970 motd lrwxrwxrwx 12 Thu Jan 01 00:00:00 1970 mtab -> /proc/mounts drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 network -rw-r--r-- 465 Thu Jan 01 00:00:00 1970 nsswitch.conf -rw-r--r-- 498 Thu Jan 01 00:00:00 1970 ntp.conf -rw-r--r-- 732 Thu Jan 01 00:00:00 1970 passwd drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 pcmcia -rw-r--r-- 864 Thu Jan 01 00:00:00 1970 profile -rw-r--r-- 2478 Thu Jan 01 00:00:00 1970 protocols -rw-r--r-- 23403 Thu Jan 01 00:00:00 1970 protocols.iana drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 rc.d drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 rc0.d drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 rc1.d drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 rc2.d drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 rc3.d drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 rc4.d drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 rc5.d drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 rc6.d drwxr-xr-x 0 Thu Jan 01 00:00:00 1970 rcS.d -rw-r--r-- 887 Thu Jan 01 00:00:00 1970 rpc -rw-r--r-- 666 Thu Jan 01 00:00:00 1970 scsi_id.config -rw-r--r-- 17571 Thu Jan 01 00:00:00 1970 services -rw-r--r-- 938722 Thu Jan 01 00:00:00 1970 services.iana drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 skel -rw-r--r-- 496 Thu Jan 01 00:00:00 1970 syslog.conf drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 terminfo drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 udev drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 udhcpc.d -rw-rw-r-- 13 Thu Jan 01 00:00:00 1970 version drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 wpa_supplicant drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 skel -rw-r--r-- 496 Thu Jan 01 00:00:00 1970 syslog.conf drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 terminfo drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 udev drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 udhcpc.d -rw-rw-r-- 13 Thu Jan 01 00:00:00 1970 version drwxrwxr-x 0 Thu Jan 01 00:00:00 1970 wpa_supplicant -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dave Hylands Sent: Thursday, June 26, 2008 12:50 AM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Newly Flashed Boot Problem - Connex - U-Boot 1.2.0 Hi Alex, On Wed, Jun 25, 2008 at 9:31 PM, Alex Jeannopoulos <al...@ba...> wrote: > I reflashed and I am still getting the error Unable to mount root fs on > unknown-block(31,1), It would seem that the jffs2 image is somehow corrupt then. Try reloading the fileystem (.jffs2 file) and then don't load the kernel. Then from u-boot issue an ls command and see if it recognizes anything on the filesystem. You can also do ls /etc or use other directories to poke around and see what you can see in the filesystem. Repeat this with a known-good filesystem, just to confirm that it does in fact work. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Dave H. <dhy...@gm...> - 2008-06-27 06:25:59
|
Hi Alex, On Thu, Jun 26, 2008 at 6:00 AM, Alex Jeannopoulos <al...@ba...> wrote: > A couple of weird things, I was able to execute >ls >ls /etc originally and > then I tried just flashing the jffs2, I even recopied it to the mmc card, If > I only flash the jffs2, I got a different error Bad Magic Number. yeah - that's because flashing the jffs2 erases the kernel. > Where can I find a prebuilt jffs2 that I can try (for connex board), Any > other things I can try, I appreciate the quick responses so far. Thanks I haven't used these, but starting here: <http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built-images/111.html> lead to <http://gumstix.net/feeds/current/glibc/images/gumstix-custom-connex/> -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Alex J. <al...@ba...> - 2008-06-27 12:53:46
|
Thanks, I was able to get back up and running flashing with a prebuilt using http://gumstix.net/feeds/current/glibc/images/gumstix-custom-connex/> Now I need to figure out how the images I built got corrupted. I used to be able to work the buildroot system and configure that, I need to do the same with the oe platform. Thanks again for your help Alex -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dave Hylands Sent: Friday, June 27, 2008 2:26 AM To: General mailing list for gumstix users. Subject: Re: [Gumstix-users] Newly Flashed Boot Problem - Connex - U-Boot 1.2.0 Hi Alex, On Thu, Jun 26, 2008 at 6:00 AM, Alex Jeannopoulos <al...@ba...> wrote: > A couple of weird things, I was able to execute >ls >ls /etc originally and > then I tried just flashing the jffs2, I even recopied it to the mmc card, If > I only flash the jffs2, I got a different error Bad Magic Number. yeah - that's because flashing the jffs2 erases the kernel. > Where can I find a prebuilt jffs2 that I can try (for connex board), Any > other things I can try, I appreciate the quick responses so far. Thanks I haven't used these, but starting here: <http://www.gumstix.net/Software/view/Getting-started/Working-with-pre-built -images/111.html> lead to <http://gumstix.net/feeds/current/glibc/images/gumstix-custom-connex/> -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |