From: Craig H. <cr...@hu...> - 2005-01-01 19:09:45
|
Oh, and one more thing -- might be safest to re-poke the MDREFR=20 register on the PXA before trying to flash stuff... You'll need to change the low-order byte and a half of the MDREFR to=20 018, which means: md.l 0x48000004 <will print some value> mw.l 0x48000004 0xNNNNN018 <where those N's are from the value printed above> This will increase the RAM refresh rate to the correct value for that=20 reboot cycle. If you reset the gumstix before installing the new=20 u-boot, then you'll need to do that again. C On Jan 1, 2005, at 10:00 AM, Peter Darling wrote: > craig, > > Thanks a lot for taking a look. maybe an error occured when i > transfered the image with zmodem(for reminiscence), i'll look at the > checksum from uboot (32 vs.zm's 8 bit).. i should just buy an mmc > card. > > -peter > > On Thu, 30 Dec 2004 18:06:02 -0800, Craig Hughes > <cr...@hu...> wrote: >> Peter, >> >> not sure how to read the 2nd half of your message there -- looks like >> some weird copy/pastisms plus some line-wrapping ugliness which makes >> it hard to tell what's going on. Looks though like your root_fs is >> corrupt and the linux JFFS2 driver is complaining about it. U-boot >> seems to have dealt with JFFS2 at least well enough to read uImage=20 >> from >> it (assuming you didn't change the boot procedure and get uImage from >> elsewhere). If you didn't unprotect off the u-boot sectors, then=20 >> erase >> all should have been fine -- u-boot is write-protected. Could well = be >> that you have a bad root_fs image or there was an error in writing it >> to flash. After copying the root_fs from RAM to flash, try CRCing it >> in flash in u-boot, to verify that it did in fact write correctly. >> >> For future reference, to erase just the root_fs bits of flash: >> >> erase 1:2-31 >> >> C >> >> On Dec 30, 2004, at 11:05 AM, Peter Darling wrote: >> >>> Hello all. I am having a few problems with my gumstix unit; I = believe >>> that I may have messed up my flash partitions while trying to = upgrade >>> the kernel. instead of erasing only the sectors for the kernel (i >>> couldn't nail the syntax) , I did an 'erase all' , counting on the = RO >>> properties of other sectors. can anyone tell if that is my problem = by >>> looking at uboot's flinfo? >>> >>> GUM> flinfo >>> >>> Bank # 1: CFI conformant FLASH (16 x 16) Size: 4 MB in 32 Sectors >>> Erase timeout 16384 ms, write timeout 1 ms, buffer write timeout=20 >>> 1024 >>> ms, buffe >>> r size 32 >>> Sector Start Addresses: >>> 00000000 (RO) 00020000 00040000 00060000 >>> 00080000 >>> >>> 000A0000 000C0000 000E0000 00100000 >>> 00120000 >>> >>> 00140000 00160000 00180000 001A0000 >>> 001C0000 >>> >>> 001E0000 00200000 00220000 00240000 >>> 00260000 >>> >>> 00280000 002A0000 002C0000 002E0000 >>> 00300000 >>> >>> 00320000 00340000 00360000 00380000 >>> 003A0000 >>> >>> 003C0000 003E0000 >>> GUM> >>> >>> -Peter >>> >>> >>> >>> more: >>> >>> Restarting system. at MMIO 0x4160000 >>> >>> >>> U-Boot 1.1.1 (Oct 3 2004 - 18:38:12) /usr/sbin/dropbear >>> Using n >>> >>> *** Welcome to Gumstix *** 162 www-da >>> physmap flash >>> >>> U-Boot code: A3F00000 -> A3F1B01C BSS: -> = A3F4CB54phys_mapped_flash: >>> Found 1 x16 devices at 0x0 in 16 >>> RAM Configuration:nf -b -d >>> Bank #0: a0000000 64 MB >>> Intel/Sharp E >>> erase_region_count =3D 32 erase_region_size =3D 131072h >>> cfi_cmdset_0001: Erase suspe >>> Flash: 4 MBnabledd -n - >>> Hit any key to stop autoboot: 0 >>> Using buffer write meth >>> ### JFFS2 loading 'boot/uImage' to 0xa2000000ion parsing not >>> available8 root 336 R >>> Scanning JFFS2 FS: ..... done. partition parsing not availab >>> ### JFFS2 load complete: 610140 bytes loaded to 0xa2000000lash ROM = at >>> physical address 0x000000 1 root 344 S >>> 2 >>> Usin >>> Load Address: a0008000 >>> Usin >>> Entry Point: a0008000stix Flash ROMflush] >>> Verifying Checksum ... OK >>> >>> Creating 2 MTD partitio >>> Uncompressing Kernel Image ... OK >>> 24 root SW [kswap >>> >>> Starting kernel ...000 : "Bootloader" >>> >>> Uncompressing Linux.......................................... done, >>> booting the SW [mtd >>> NET: Registered protocol family 2 >>> 52 root >>> kernel.IP: rou >>> Linux version 2.6.9-rc1-gum (root@enterprise) (gcc version 3.4.2) #1 >>> Fri Nov 12 /usr/sbin/dropbe >>> TCP: Hash tables configured (established 4096 bind 8192)data >>> 23:29:24 MST 2004in/boa >>> CPU: XScale-PXA255 [69052d06] revisions2 files >>> usb0: Ethernet Gadget, v >>> Memory clock: 99.53MHz (*27) >>> 1 >>> Run Mode clock: 199.07MHz (*2) using pxa2xx_udc, OUT ep2out- >>> Turbo Mode clock: 199.07MHz (*1.0, inactive) >>> 3 root >>> Built 1 zonelists >>> usb0: MAC 0e:00: >>> Kernel command line: console=3DttyS0,115200n8 root=3D1f02=20 >>> rootfstype=3Djffs2 >>> reboot=3Dco >>> 12 root >>> usb0: RNDIS readyblockd/0] >>> NET: Registered protoc >>> ld,hardy 17 ro >>> PID hash table entries: 512 (order 9: 4096 bytes)) started >>> 23 root S >>> >>> JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.nit.d/rcS: 26: >>> /etc/init.d/S50rendezvous: Perm >>> SA1100/PXA2xx Watchdog Timer: timer margin 60 sec >>> HCID_E >>> The system is going >>> ttyS0 at MMIO 0x40100000 (irq =3D 15) is a FFUARTng SIGTERM to all >>> processes.D2HCI_ENABLE=3Dfalse >>> ttyS1 at MMIO 0x40200000 (irq =3D 14) is a BTUARTncated] >>> mc=82Sc5=01=01=3D=01=0E=BE?=E5=02<=0Fudhcp 0.9.9-pre7=06=01=03=06AN >>> ttyS2 at MMIO 0x40700000 (irq =3D 13) is a STUARTv/ttyS1 >>> >>> >>> ttyS3 at MMIO 0x41600000 (irq =3D 0) is a HWUART >>> >>> >>> >>> Can't initialize device: Invalid argument >>> Starting network... >>> pxa2xx_udc: version 14-Dec-2003 >>> usb0: Ethernet Gadget, version: St Patrick's Day 2004 >>> usb0: using pxa2xx_udc, OUT ep2out-bulk IN ep1in-bulk STATUS=20 >>> ep6in-bulk >>> usb0: MAC 0e:00:be:3f:e5:02 >>> usb0: HOST MAC 0e:00:be:3f:e5:02 >>> usb0: RNDIS ready >>> NET: Registered protocol family 17 >>> udhcpc (v0.9.9-pre) started >>> Dec 31 16:00:13 udhcpc[129]: udhcpc (v0.9.9-pre) started >>> Backgrounding >>> Dec 31 16:00:14 udhcpc[129]: Backgrounding >>> Dec 31 16:00:14 udhcpc[142]: Sending discover... >>> Starting dropbear sshd: OK >>> /etc/init.d/rcS: 26: /etc/init.d/S50httpd: Permission denied >>> /etc/init.d/rcS: 26: /etc/init.d/S50rendezvous: Permission denied >>> NET: Registered protocol family 1 >>> >>> >>> >>> Welcome to the Gumstix Linux Distribution! >>> >>> gumstix login: >>> >>> >>> ------------------------------------------------------- >>> The SF.Net email is sponsored by: Beat the post-holiday blues >>> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >>> It's fun and FREE -- well, = almost....http://www.thinkgeek.com/sfshirt >>> _______________________________________________ >>> gumstix-users mailing list >>> gum...@li... >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> ------------------------------------------------------- >> The SF.Net email is sponsored by: Beat the post-holiday blues >> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |