mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: muntaqa <muntaqa@juno.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Using external toolchain with penguitronix BSP	distribution
Date: Tue, 15 Nov 2011 14:32:31 +0000 (UTC)	[thread overview]
Message-ID: <loom.20111115T152909-98@post.gmane.org> (raw)
In-Reply-To: <201111051554.43244.jbe@pengutronix.de>

Juergen Beisert <jbe@...> writes:

> 
> muntaqa wrote:
> > Juergen Beisert <jbe@...> writes:
> > > Out of curiosity: what advantage has your toolchain compared to our
> > > OSELAS ARMv4 toolchain?
> >
> > This is CodeSourcery open source toolchain.  I had chosen it a while ago
> > when building the project with buildroot.  I have been using it for a while
> > and have built and debugged all of my applications with it on mini2440.  At
> > this point, I did not want to discover or spend time on any other problems
> > since I have a working system except that I am trying to add QT
> > applications to my mini2440 platform.
> 
> Okay.
> 
> > Reason I switched to Pengutronix is that buildroot gave me some trouble
> > when building QT thru it plus it had always given me kernel panic errors
> > when installing the jffs2 root image (so I had been simply using tar balls
> > on top of the stock kernel/rootfs that mini2440 is shipped with).  I
> > thought switching to Pengutronix would finally let me burn a true image and
> > I can organize my project much better.
> >
> > Currently, I still have kernel panic messages when building the rootfs
> > using Pengutronix and CodeSourcery.  It seems perhaps that it is because of
> > gcc 4.5.1 that is being used in my version of CodeSourcery.  When I use
> > your toolchain, I can burn an image properly and do not receive kernel panic
> > messages.  Your toolchain uses gcc 4.5.2.
> 
> Do all supported kernels show the same panic? Sometimes one kernel has trouble 
> with a specific gcc version, and other kernels not. Did you try all kernels 
> from the BSP with your CodeSourcery toolchain?
> 
> > One issue that I see though with Pengutronix is that any time I change a
> > selection or add anything to QT configuration in Penguitronix ptxdist
> > menuconfig, it rebuilds the whole QT (ends up costing me couple of hours
> > plus I am not able to try anything quickly.)
> 
> On our new 24 core/96 GiB RAM machine Qt4 builds really quick in a few 
> minutes. 
> 
> Maybe you should start with a full blown Qt4, do your development with it, and 
> when it is finished, you can try to shrink the library by disabling some of 
> its options.
> 
> > I would like to start using pengutronix as long as it would be less
> > frustrating than buildroot.
> 
> I don't know buildroot. I work with PTXdist since years.
> 
> > BTW, my best wishes to you on this project, you guys have done alot of
> > good work and looking at your documentation the working environment, it
> > seems very promising.
> 
> Thanks.
> 
> Regards,
> Juergen
> 

Hello Juergen,

I am wondering if you would be able to help me with kernel panic issue?  I have
tried different gcc versions of CodeSourcery with about three kernel versions
and I always get kernel panics when booting mini2440.  I am following your quick
start guide for either botting from nfs or nand.  I follow the procedure for
nand updates etc.  Is there an inherent problem with burning JFFS2 format on
mini2440 or is it Code Sourcery that perhaps has a problem?  Any help
would be much appreciated.  Please let me know what information I need to
provide for you to be able to help me?  Below is the platformconfig settings:

#
# Automatically generated make config: don't edit
# PTXdist 2011.10.1
#
PTXCONF_PLATFORMCONFIG_VERSION="2011.10.1"
PTXCONF__platformconfig_MAGIC__=y

#
# ------------------------------------
#

#
# Target Platform Configuration 
#

#
# ------------------------------------
#
PTXCONF_PLATFORM="mini2440"
PTXCONF_PLATFORM_VERSION="-2011.10.0"

#
# architecture                  
#
# PTXCONF_ARCH_ALPHA is not set
# PTXCONF_ARCH_AVR32 is not set
# PTXCONF_ARCH_AVR is not set
PTXCONF_ARCH_ARM=y
# PTXCONF_ARCH_BLACKFIN is not set
# PTXCONF_ARCH_X86 is not set
# PTXCONF_ARCH_MINGW is not set
# PTXCONF_ARCH_PPC is not set
# PTXCONF_ARCH_M68K is not set
# PTXCONF_ARCH_SPARC is not set
# PTXCONF_ARCH_MICROBLAZE is not set
# PTXCONF_ARCH_MIPS is not set
# PTXCONF_ARCH_CRIS is not set
# PTXCONF_ARCH_PARISC is not set
# PTXCONF_ARCH_SH is not set
PTXCONF_ARCH_SUPPORTS_ENDIAN_BIG=y
PTXCONF_ARCH_SUPPORTS_ENDIAN_LITTLE=y
# PTXCONF_ENDIAN_BIG is not set
PTXCONF_ENDIAN_LITTLE=y
# PTXCONF_ARCH_ARM_V6 is not set
# PTXCONF_ARCH_ARM_IWMMXT is not set
# PTXCONF_ARCH_ARM_NEON is not set
# PTXCONF_HAS_HARDFLOAT is not set
PTXCONF_HAS_MMU=y
PTXCONF_SIZEOF_LONG_DOUBLE="8"
PTXCONF_ARCH_STRING="arm"

#
# paths & directories           
#
PTXCONF_SYSROOT_TARGET="${PTXDIST_PLATFORMDIR}/sysroot-target"
PTXCONF_SYSROOT_HOST="${PTXDIST_PLATFORMDIR}/sysroot-host"
PTXCONF_SYSROOT_CROSS="${PTXDIST_PLATFORMDIR}/sysroot-cross"

#
# toolchain                     
#
PTXCONF_CROSSCHAIN_VENDOR=""
PTXCONF_CROSSCHAIN_CHECK="4.5.2"
PTXCONF_LIBC_GLIBC=y
# PTXCONF_LIBC_UCLIBC is not set
PTXCONF_GLIBC_VERSION="2.13"
PTXCONF_GNU_TARGET="arm-none-linux-gnueabi"
PTXCONF_COMPILER_PREFIX="${PTXCONF_GNU_TARGET}-"
PTXCONF_COMPILER_PREFIX_KERNEL="${PTXCONF_COMPILER_PREFIX}"
PTXCONF_COMPILER_PREFIX_BOOTLOADER="${PTXCONF_COMPILER_PREFIX}"

#
# extra toolchain options       
#
PTXCONF_TARGET_EXTRA_CPPFLAGS="-march=armv4t -mtune=arm920t"
PTXCONF_TARGET_EXTRA_CFLAGS="-march=armv4t -mtune=arm920t"
PTXCONF_TARGET_EXTRA_CXXFLAGS="-march=armv4t -mtune=arm920t"
PTXCONF_TARGET_EXTRA_LDFLAGS="-march=armv4t -mtune=arm920t"
PTXCONF_KERNEL=y
# PTXCONF_KERNEL_INSTALL is not set
PTXCONF_KERNEL_MODULES=y
PTXCONF_KERNEL_MODULES_INSTALL=y
PTXCONF_KERNEL_MODULES_BUILD="modules"
#PTXCONF_KERNEL_VERSION="3.0"
#PTXCONF_KERNEL_MD5="398e95866794def22b12dfbc15ce89c0"
PTXCONF_KERNEL_VERSION="2.6.38"
PTXCONF_KERNEL_MD5="398e95866794def22b12dfbc15ce89c0"
PTXCONF_KERNEL_ARCH_STRING="arm"
# PTXCONF_KERNEL_IMAGE_BZ is not set
# PTXCONF_KERNEL_IMAGE_Z is not set
PTXCONF_KERNEL_IMAGE_U=y
# PTXCONF_KERNEL_IMAGE_VM is not set
# PTXCONF_KERNEL_IMAGE_VMLINUX is not set
# PTXCONF_KERNEL_IMAGE_RAW is not set
# PTXCONF_KERNEL_IMAGE_SIMPLE is not set
PTXCONF_KERNEL_IMAGE="uImage"
# PTXCONF_KERNEL_XZ is not set
# PTXCONF_KERNEL_LZOP is not set

#
# patching & configuration      
#
PTXCONF_KERNEL_SERIES="series"
PTXCONF_KERNEL_CONFIG="kernelconfig-${PTXCONF_KERNEL_VERSION}"

#
# Development features
#
PTXCONF_KERNEL_EXTRA_MAKEVARS="CONFIG_DEBUG_SECTION_MISMATCH=y"
# PTXCONF_HOST_DTC is not set
# PTXCONF_DTC is not set

#
# console options               
#
PTXCONF_CONSOLE_NAME="ttySAC0"
PTXCONF_CONSOLE_SPEED="115200"

#
# bootloaders                   
#
# PTXCONF_AT91BOOTSTRAP is not set
# PTXCONF_AT91BOOTSTRAP2 is not set
PTXCONF_BAREBOX=y
PTXCONF_BAREBOX_VERSION="2011.05.0"
PTXCONF_BAREBOX_MD5="d66774abcf9fa6c9530e13543cc707bc"
PTXCONF_BAREBOX_CONFIG="barebox-NAND-128M.config"
PTXCONF_BAREBOX_ARCH_STRING="arm"
PTXCONF_BAREBOX_EXTRA_ENV=y
PTXCONF_BAREBOX_EXTRA_ENV_PATH="${PTXDIST_PLATFORMCONFIGDIR}/barebox-128m-env"
PTXCONF_BOOTLOADER=y
# PTXCONF_GRUB is not set
# PTXCONF_HOST_MXS_UTILS is not set
# PTXCONF_U_BOOT_V2 is not set
# PTXCONF_U_BOOT is not set
# PTXCONF_X_LOAD is not set

#
# flash                         
#
PTXCONF_FLASH_BLOCKSIZE="128k"

#
# image creation options        
#
# PTXCONF_IMAGE_CPIO is not set
# PTXCONF_IMAGE_CPIO_GZ is not set
# PTXCONF_IMAGE_EXT2 is not set
# PTXCONF_IMAGE_HD is not set

#
# ipkg options                  
#
# PTXCONF_IMAGE_IPKG_PUSH_TO_REPOSITORY is not set
# PTXCONF_IMAGE_INSTALL_FROM_IPKG_REPOSITORY is not set
PTXCONF_IMAGE_IPKG_INDEX=y
PTXCONF_IMAGE_IPKG_EXTRA_ARGS=""
PTXCONF_IMAGE_JFFS2=y
PTXCONF_IMAGE_JFFS2_BLOCKSIZE=0x20000

#
# *** add '-n' here for NAND flash ***
#
PTXCONF_IMAGE_JFFS2_EXTRA_ARGS="-n"
# PTXCONF_IMAGE_JFFS2_SUM is not set
PTXCONF_IMAGE_KERNEL=y
# PTXCONF_IMAGE_KERNEL_INITRAMFS is not set
PTXCONF_IMAGE_KERNEL_INSTALL_EARLY=y
# PTXCONF_IMAGE_KERNEL_LZOP is not set
# PTXCONF_IMAGE_SQUASHFS is not set
PTXCONF_IMAGE_TGZ=y
# PTXCONF_IMAGE_UBI is not set
# PTXCONF_IMAGE_UBIFS is not set
# PTXCONF_IMAGE_UIMAGE is not set
PTXCONF_CROSS_MODULE_INIT_TOOLS=y
# PTXCONF_HOST_CDRKIT is not set
# PTXCONF_HOST_CMAKE is not set
# PTXCONF_HOST_CRAMFS is not set
# PTXCONF_HOST_DOSFSTOOLS is not set
# PTXCONF_HOST_E2FSPROGS is not set
# PTXCONF_HOST_GENEXT2FS is not set
# PTXCONF_HOST_GENPART is not set
# PTXCONF_HOST_GETTEXT is not set
# PTXCONF_HOST_LIBBLKID is not set
# PTXCONF_HOST_LIBBZ2 is not set
# PTXCONF_HOST_LIBCAP is not set
PTXCONF_HOST_LIBLZO=y
PTXCONF_HOST_LIBUUID=y
# PTXCONF_HOST_LZOP is not set
# PTXCONF_HOST_MKELFIMAGE is not set
PTXCONF_HOST_MTD_UTILS=y
# PTXCONF_HOST_MTOOLS is not set
# PTXCONF_HOST_OPENSSL is not set
# PTXCONF_HOST_SQUASHFS_TOOLS is not set
PTXCONF_HOST_UMKIMAGE=y
PTXCONF_HOST_UTIL_LINUX_NG=y
# PTXCONF_HOST_XL_TOOLS is not set
# PTXCONF_HOST_XZ is not set
PTXCONF_HOST_ZLIB=y





-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2011-11-15 14:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-30 23:57 muntaqa
2011-11-01 10:13 ` Michael Olbrich
2011-11-02  1:39   ` muntaqa
2011-11-02  8:35     ` Juergen Beisert
2011-11-05 13:31       ` muntaqa
2011-11-05 14:54         ` Juergen Beisert
2011-11-15 14:32           ` muntaqa [this message]
2011-11-15 14:57             ` Juergen Beisert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20111115T152909-98@post.gmane.org \
    --to=muntaqa@juno.com \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox