From: <in...@ad...> - 2006-09-01 05:42:52
|
Hi. As I was unable to install colinux (hangs up) I installed vmware and Fedora 5. Everything works great except that I don't seem to download the right tool set. When I type: 'svn co http://svn.gumstix.com/gumstix-buildroot/trunk gumstix-buildroot' the cross compiler tool set is installed in the trunk directory but I don't have a gumstix directory anywhere. I am able to compile and build a rootfs.arm_nofpu.jffs2 and load it to the mmc card. However 'iminfo' on the Connex returns with Bad Magic Number so does 'bootm'. I did try different ways as explained on the wiki without success. I don't understand why I am not able to get the same directory tree as expected in the description in build root. The Connex+ netmmc+ audiostix is working without any problem with the original kernel, I can ping the internet and read the mmc card. What do I do wrong? Tnanks for any help. Rock. |
From: <in...@ad...> - 2006-09-01 22:24:18
|
Dave, I found the uImage and loaded it with no problem this time. But after 'bootm' when it starts the kernel, it stops with an error. See below. I did not modify the source it is build out of the box. As a test I did copy uImage from the Connex boot directory to the mmc card and power off /power on and that is working correctly. I admit that my knowledge of Linux is rusty. Thanks for the help. Rock. =============================================================================== GUM> fatload mmc 1 a2000000 uImage reading uImage 744832 bytes read GUM> iminfo a2000000 ## Checking Image at a2000000 ... Image Name: uImage Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 744768 Bytes = 727.3 kB Load Address: a0008000 Entry Point: a0008000 Verifying Checksum ... OK GUM> bootm a2000000 ## Booting image at a2000000 ... Image Name: uImage Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 744768 Bytes = 727.3 kB Load Address: a0008000 Entry Point: a0008000 OK Starting kernel ... Linux version 2.6.17gum (yvon@localhost.localdomain) (gcc version 3.4.5) #1 Thu Aug 31 21:14:01 MST 2006 CPU: XScale-PXA255 [69052d06] revision 6 (ARMv5TE) 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 Kernel command line: console=ttyS0,115200n8 root=1f02 rootfstype=jffs2 PID hash table entries: 512 (order: 9, 2048 bytes) 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: 63360KB available (1220K code, 247K data, 56K init) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 NET: Registered protocol family 2 IP route cache hash table entries: 512 (order: -1, 2048 bytes) TCP established hash table entries: 2048 (order: 1, 8192 bytes) TCP bind hash table entries: 1024 (order: 0, 4096 bytes) TCP: Hash tables configured (established 2048 bind 1024) TCP reno registered JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc. Initializing Cryptographic API io scheduler noop 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 2 MTD partitions on "Gumstix Flash ROM": 0x00000000-0x00040000 : "Bootloader" 0x00040000-0x01000000 : "RootFS" TCP bic registered No filesystem could mount root, tried: jffs2 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2) ================================================================================================== > ------------------------------ > > Message: 6 > Date: Fri, 1 Sep 2006 08:00:07 -0700 > From: "Dave Hylands" <dhy...@gm...> > Subject: Re: [Gumstix-users] [kernel build > To: "General mailing list for gumstix users." > <gum...@li...> > Message-ID: > <c32...@ma...> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Yvon, > > > My mistake was to assume that the directory tree were created automatically. Apart from that I did exactly > > the same as you just described except that I didn't find the uImage and thought I had to rename the > > jffs2 file to be able to load it. > > So once the kernel is built, it's placed in > > gumstix-buildroot/build_arm_nofpu/linux-2.6.17gum/arch/arm/boot/compressed/vmlinux > > This is then processed to produce: > > gumstix-buildroot/build_arm_nofpu/linux-2.6.17gum/arch/arm/boot/uImage > > and that then gets copied into > > gumstix-buildroot/build_arm_nofpu/root/boot/uImage > > So, if any of the above mentioned files are missing, then your make > wasn't successful. > > > > > Again, I searched in all the directories and couldn't find the uImage file. COuld this be because I didn't > > create the correct directory tree? > > The only portion of the directory tree that matters is what's below > gumstix-buildroot, and that's done for you by svn. The name/location > of gumstix-buildroot is arbitrary. > > I often create multiple directories with different names if I'm > working on multiple versions of buildroot. > > So I suspect that if your uImage isn't being created then its for some > other reason, and will involve carefully checking the make output, > especially near the end. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/ > > > |
From: Dave H. <dhy...@gm...> - 2006-09-01 23:25:11
|
Hi Rock, > I found the uImage and loaded it with no problem this time. But after 'bootm' when it starts the > kernel, it stops with an error. See below. > I did not modify the source it is build out of the box. > > As a test I did copy uImage from the Connex boot directory to the mmc card and power off /power on > and that is working correctly. > > I admit that my knowledge of Linux is rusty. > Thanks for the help. You're almost there. This particular problem is covered at the end of this page, in the section called "Troubleshooting": http://docswiki.gumstix.org/Replacing_the_filesystem_image -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: <in...@ad...> - 2006-09-02 03:22:40
|
Dave, I rejoiced too soon. Now it doesn't recognize the mmc card anymore. # df Filesystem 1k-blocks Used Available Use% Mounted on df: /proc/mounts: No such file or directory # uname -a Linux (none) 2.6.17gum #2 Fri Sep 1 19:37:42 MST 2006 armv5tel unknown # mount -t vfat /dev/mmcblk0 /mmc mount: Mounting /dev/mmcblk0 on /mmc failed: No such file or directory # mount /mnt/mmc mount: Mounting /dev/mmcblk0p1 on /mnt/mmc failed: No such file or directory # And is this message normal at the end of the boot: "/bin/sh: can't access tty; job control turned off" I don't remember seeing it before. Thanks, Rock. > ------------------------------ > > Message: 2 > Date: Fri, 01 Sep 2006 15:24:16 -0700 > From: in...@ad... > Subject: Re: [Gumstix-users] kernel build > To: gum...@li... > Message-ID: > <200...@em...> > > Content-Type: TEXT/plain; CHARSET=US-ASCII > > Dave, > > I found the uImage and loaded it with no problem this time. But after 'bootm' when it starts the > kernel, it stops with an error. See below. > I did not modify the source it is build out of the box. > > As a test I did copy uImage from the Connex boot directory to the mmc card and power off /power on > and that is working correctly. > > I admit that my knowledge of Linux is rusty. > Thanks for the help. > > Rock. > =============================================================================== |
From: Dave H. <dhy...@gm...> - 2006-09-02 04:15:11
|
Hi Rock, On 9/1/06, in...@ad... <in...@ad...> wrote: > Dave, > > I rejoiced too soon. Now it doesn't recognize the mmc card anymore. Ahem. When you login to the gumstix, the following message is printed: Welcome to Gumstix! By default, this gumstix is configured for CF support. Unfortunately, this means MMC support has to be disabled out of the box. To turn on MMC and turn off CF, edit the file /etc/modules and comment out or delete the pcmcia (CF) line, and uncomment the MMC lines. You then also need to comment out or remove the line "auto mwlan0" in /etc/network/interfaces if it exists, since it will otherwise cause the pcmcia driver to be loaded. So you need to edit a couple more files. You can do this on the gumstix using vi if you're familiar with it. Otherwise you can edit the files on your host machine using your favorite editor. You'll need to edit gumstix-buildroot/build_arm_nofpu/root/etc/modules and gumstix-buildroot/build_arm_nofpu/root/etc/netork/interfaces. Then remove the gumstix-buildroot/rootfs.arm_nofpu.jffs2 file and type make from within the gumstix-buildroot directory. Then reflash with the new jffs2 image. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Dave H. <dhy...@gm...> - 2006-09-01 06:09:58
|
Hi Rock, On 8/31/06, in...@ad... <in...@ad...> wrote: > Hi. > > As I was unable to install colinux (hangs up) I installed vmware and Fedora 5. Everything works great > except that I don't seem to download the right tool set. > > When I type: 'svn co http://svn.gumstix.com/gumstix-buildroot/trunk gumstix-buildroot' > the cross compiler tool set is installed in the trunk directory but I don't have a gumstix directory You create the gumstix directory yourself. On my machine, I would have done something like: cd ~ mkdir gumstix cd gumstix svn co http://svn.gumstix.com/gumstix-buildroot/trunk gumstix-buildroot cd gumstix-buildroot make defconfig make > anywhere. I am able to compile and build a rootfs.arm_nofpu.jffs2 and load it to the mmc card. > However 'iminfo' on the Connex returns with Bad Magic Number so does 'bootm'. You need to do an fsload before doing iminfo or bootm (or somehow get uImage into RAM). fsload loads uImage from the jffs2 filesystem. If you were to copy uImage onto yout mmc card you could do: The commands needs to copy your rootfs file from the MMC card into flash is this: mmcinit fatload mmc 1 a2000000 rootfs.arm_nofpu.jffs2 protect on 1:0-1 && erase all cp.b a2000000 40000 > I did try different ways as explained on the wiki without success. I don't understand why I am not able > to get the same directory tree as expected in the description in build root. This is described on this page in the Wiki: http://docwiki.gumstix.org/Flash_the_filesystem_image in the section "Flashing from MMC" -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |