Re: [gentoo-embedded] cirrus ep93xx chips / maverick crunch

[wireless]

Christopher Friedt wrote:

>> I'm not sure what I missed?

> http://perpetual-notion.blogspot.com/2008/02/maverick-crunch-eabi-support-for.html
>
>
> mkdir -p /usr/local/portage/maverick_overlay &&
> SRV="http://vaiprime.visibleassets.com" \
> LOC="~cfriedt/overlays/maverick.tar.bz2" \
> wget -O - ${SRV}/${LOC} | \
> tar xpjf - -C /usr/local/portage/maverick_overlay &&
> PORTDIR_OVERLAY="/usr/local/portage/crossdev_overlay \
> /usr/local/portage/maverick_overlay" \
> ECONF_EXTRA="--disable-nls --enable-shared \
> --with-system-zlib --without-included-gettext \
> --enable-threads=posix --enable-clocale=gnu \
> --with-fpu=maverick --with-float-abi=softfp \
> --with-cpu=ep9312 --enable-languages=c,c++" \
> USE="-gcj -gtk -fortran -mudflap" \
> crossdev -S \
> --l 2.5-r4 --g 4.1.2 --b 2.17-r1 \
> armv4t-maverick-linux-gnueabi


SUCCESS!


* Host Portage ARCH:     amd64
 * Target Portage ARCH:   arm
 * Target System:         armv4t-maverick-linux-gnueabi
 * Stage:                 4 (C/C++ compiler)

 * binutils:              binutils-2.17-r1
 * gcc:                   gcc-4.1.2
 * headers:               linux-headers-[stable]
 * libc:                  glibc-2.5-r4

 * PORTDIR_OVERLAY:       /usr/local/portage/maverick_overlay
 * PORT_LOGDIR:           /var/log/elog/
 * PKGDIR:
/usr/portage/packages/cross/armv4t-maverick-linux-gnueabi
 * PORTAGE_TMPDIR:        /var/tmp/cross/armv4t-maverick-linux-gnueabi
  --------------------------------------------------------------------
 * Using sys-devel/binutils from /usr/local/portage/maverick_overlay
instead of /usr/portage
 * Using sys-devel/gcc from /usr/local/portage/maverick_overlay
instead of /usr/portage
 * Forcing the latest versions of {binutils,gcc}-config/gnuconfig ...
        [ ok ]
 * Log: /var/log/elog//cross-armv4t-maverick-linux-gnueabi-binutils.log
 * Emerging cross-binutils ...
        [ ok ]
 * Log: /var/log/elog//cross-armv4t-maverick-linux-gnueabi-gcc-stage1.log
 * Emerging cross-gcc-stage1 ...
        [ ok ]
 * Log:
/var/log/elog//cross-armv4t-maverick-linux-gnueabi-linux-headers.log
 * Emerging cross-linux-headers ...
        [ ok ]
 * Log: /var/log/elog//cross-armv4t-maverick-linux-gnueabi-glibc.log
 * Emerging cross-glibc ...
        [ ok ]
 * Log: /var/log/elog//cross-armv4t-maverick-linux-gnueabi-gcc-stage2.log
 * Emerging cross-gcc-stage2 ...
        [ ok ]



I then manually downloaded your bz file : maverick.tar.bz2

uppacked it with: tar xpjf  ./maverick.tar.bz2
into this dir: /usr/local/portage/maverick_overlay

and this used this command string:
PORTDIR_OVERLAY="/usr/local/portage/crossdev_overlay
/usr/local/portage/maverick_overlay" ECONF_EXTRA="--disable-nls
--enable-shared --with-system-zlib --without-included-gettext
--enable-threads=posix --enable-clocale=gnu --with-fpu=maverick
--with-float-abi=softfp --with-cpu=ep9312 --enable-languages=c,c++"
USE="-gcj -gtk -fortran -mudflap" crossdev -S --l 2.5-r4 --g 4.1.2 --b
2.17-r1 armv4t-maverick-linux-gnueabi


Now I'm going to build a kernel, locate it per the EMAC support
suggestion and see if I can reboot off of the SD card. From EMAC :

" The only thing I would add is that you can boot filesystems from the
SD card. This will allow you to have your 2 bootable images.
The kernel must be stored in the flash but this takes up much less
room and you could easily store more than one.

Example redboot command for booting from an SD card:

load -v -r -b 0x80000 zImage-IPAC-9302-e1.2
exec -c "console=ttyAM0,57600 root=/dev/mmca1 rootfstype=ext3"

This will load a kernel from flash into memory (SDRAM), and execute it
with the boot args in quotes. The boot args here will tell it which
tty port to use for console  input/output, and specify the location of
the root filesystem as being in the  mmca device on partition 1 with
and ext3 filesystem."


Thanks for all of the help!

James

-- 
gentoo-embedded@l.g.o mailing list