From: ken s. <ken...@gm...> - 2006-12-05 18:36:35
|
you should be able to use binutils 2.16.1, but you'll need to rebuild everything if you've already done a make. i.e. rm -rf build_arm_nofpu _and_ rm -rf toolchain_build_arm_nofpu i'd recommend starting by building a simple (use the defaults) initramfs. buildroot should just work. it is important to understand that the latest revision in subversion isn't the latest released version. i'm currently using revision 1092, which was the last version using the 2.6.17 kernel. rev 1092 used binutils 2.17 and gcc 3.4.5 none of the commits since then add features i need or fix bugs that matter to me. you can also start with an /init that just prints a message or starts /bin/sh before doing anything more complicated. --- ken On 12/5/06, Gordon Dobie <gor...@ee...> wrote: > Hi Ken, > > Thanks for the help. BTW is it ok to use Binutils 2.16.1 as the newer > experimental versions cause the buildroot to stop working for me? > > The Gumstix crashes even earlier now! I will try again from scratch > tomorrow. The current output is: > > U-Boot 1.1.4 (May 23 2006 - 12:47:17) > > *** Welcome to Gumstix *** > > U-Boot code: A3F00000 -> A3F2369C BSS: -> A3F58748 > RAM Configuration: > Bank #0: a0000000 64 MB > Flash: 4 MB > SMC91C1111-0 > Can't overwrite "serial#" > Net: SMC91C1111-0 > Hit any key to stop autoboot: 0 > Instruction Cache is ON > Found gumstix-factory script... > ## Executing script at a2000000 > MMC found. Card desciption is: > Manufacturer ID = 410000 > HW/FW Revision = a 1 > Product Name = BMH FA > Serial Number = d7bf70 > Month = 7 > Year = 2006 > reading uImage-2.6.17-initrd > > 1181804 bytes read > reading ramdisk.img > > 2678014 bytes read > ## Booting image at a1000000 ... > Image Name: uImage > Image Type: ARM Linux Kernel Image (uncompressed) > Data Size: 1181740 Bytes = 1.1 MB > Load Address: a0008000 > Entry Point: a0008000 > OK > ## Loading Ramdisk Image at a2000000 ... > Image Name: rootfs > Image Type: ARM Linux RAMDisk Image (gzip compressed) > Data Size: 2677950 Bytes = 2.6 MB > Load Address: 00000000 > Entry Point: 00000000 > > Starting kernel ... > > data abort > pc : [<a000823c>] lr : [<a0008270>] > sp : a0131c64 ip : a00080bc fp : 00000003 > r10: 10000000 r9 : 00000000 r8 : a0000100 > r7 : 00000175 r6 : 69052d06 r5 : a0008000 r4 : 00008000 > r3 : 00004000 r2 : 00008000 r1 : 00000c1e r0 : 00004004 > Flags: Nzcv IRQs off FIQs off Mode SVC_32 > Resetting CPU ... > > resetting ... > > Thanks, > > Gordon > > > -----Original Message----- > From: gum...@li... > [mailto:gum...@li...] On Behalf Of ken > staton > Sent: 05 December 2006 15:28 > To: General mailing list for gumstix users. > Subject: Re: [Gumstix-users] initramfs again! > > On 12/5/06, Gordon Dobie <gor...@ee...> wrote: > > I am trying to get the tutorial on the Wiki to work, but am having > some > > issues - http://docwiki.gumstix.org/Root_filesystems (Sorry > > I am fairly new to Linux and the Gumstix!) > > > > > > > > The plan is to boot a 4mB flash basix from the MMC, but I am having > trouble > > getting it to work. > > > > > > > > 1. Firstly I gather you need to recompile the kernel after "Enable > drivers > > required in the kernel". I tried just entering these lines into a > shell, > > then doing: > > > > cd <gumstix-buildroot> > > cd build_arm_nofpu > > cd linux-<the version of linux you're using> > > make ARCH=arm CROSS_COMPILE=`pwd`/../staging_dir/bin/arm-linux- > > cd <gumstix-builtroot> > > make > > > > > > I left out - make ARCH=arm > > CROSS_COMPILE=`pwd`/../staging_dir/bin/arm-linux- > > menuconfig, is this correct? > > > > this is correct. you must build the entire toolchain and buildroot > first: > make defconfig > make > > then the steps above. > > > > > > 2. To change Busybox, I used "make menuconfig" and "make" in the > busybox > > folder. Then "make" in the buildroot folder. > > > > you should specify the architecture here, then let buildroot's make > handle it: > in busybox dir - > make ARCH=arm menuconfig > then in <gumstix-buildroot> dir > make > > > > > 3. For "Prepare the initramfs image" > > > > I take it I need to run "chmod +x init", to make the file executable, > is > > this correct? > > yes, it does need to be executable > > > > > My current version, loads the image, and the ramdisk.img, but is > unable to > > mount the mmc to /mnt/mmc, then can't mount the rootfs. It hangs at a > > kernal panic warning. > > > > posting the boot messages will give a better idea of where it is going > off track. > > --- > ken |