Sponsored Content
Operating Systems Linux Help Cross compiling a kernel for an HP Jornada 728 Post 302360863 by semash! on Sunday 11th of October 2009 01:15:58 AM
Old 10-11-2009
Help Cross compiling a kernel for an HP Jornada 728

Hello,
I just bought an old Jornada 728 and, as you may know, it comes with Windows CE 3.0. I do not use Windows, so i wanted to create my own linux system for the Jornada.

I know there are projects like Jlime, Familiar Linux, 720 Degrees, etc. But i want something based on the distribution i use, Slackware and made by myself.

My problem is weird, i have a gcc compiler for ARM platform (arm-linux-gcc) and i'm using linux kernel version 2.6.30.5. Here are the steps i follow:
(on /home/linux-2.6.30.5/)

1. make mrproper
2. cp arch/arm/configs/jornada720_defconfig .config
So i use a default configuration kernel for that computer, it should work as is, but doesn't.

3. make ARCH=arm CROSS_COMPILE=/path/to/arm-linux- menuconfig
I configure the kernel to fit my needs...
4. make

Now i have a zImage created on arch/arm/boot/, so i copy it to the Jornada CompactFlash memory. This Kernel image is supposed to be loaded from WinCE by a program called linexec.exe, it uses a params.txt file, which i have configured as follows:

\Storage Card\zImage
\Storage Card\initrd.gz

Three days ago, i successfully created a bootable kernel on the Jornada, it hanged at loading the initial ramdisk, but IT WORKED, there appeared tux on the display, loaded the TCP/IP stack, etc. The thing is that now i am not able to make a working kernel!, i compile it, and when loading from the device, the WinCE hangs and does nothing, or the linexec.exe shows a black screen as if it was going to boot, but nothing shows up or happens.

The processor is a StronARM SA-1110, and yes, i configure the kernel with support for SA-1111 and SA-1100 based processors.

My questions are:

-Is there a reason for a kernel to not be "bootable" on that device?
-Which steps am i passing by to make the kernel work, if any?
-Can you please guide me on successfully compile a kernel for this computer?

Please excuse my poor english, it's not my mother language.
Thanks in advance.
 

4 More Discussions You Might Find Interesting

1. Programming

Cross compiling under Windows for Linux

I have two headless servers I am writing code for, and a Windows box networked with them. I want to compile my code within an IDE on the Windows box (eclipse most likely) and run the compiled binarys on the Linux boxes. Will this work? Using Cygwin (or MinGW)? Thoughts? Cheers, Ian (8 Replies)
Discussion started by: IanVaughan
8 Replies

2. Linux

kernel compiling

Hello, I have several questions to get awnsered about the newer linux kernels (2.6.25) and above. 1st question: Ive read that the newer kernels you can compile the marvell sd8686 driver from the source. can anyone confrim this? only binaries i see for that driver are for 2.6.24 and im already... (0 Replies)
Discussion started by: old noob
0 Replies

3. UNIX for Dummies Questions & Answers

Cross-compiling libiconv for uclinux

Hi everyone, I want to cross-compile libiconv for uclinux to create a static library. I use the following command : ./configure --enable-static --disable-shared --build=i686-pc-linux-gnu --host=nios2-unknown-linux-gnu --prefix=/home/captain/Programs/nios2-linux/uClinux-dist/staging/usr... (2 Replies)
Discussion started by: moganesh
2 Replies

4. UNIX and Linux Applications

Cross Compiling Issue of udev-151 for MIPS Little Endain Architecture

Hi All, I am trying to cross compile udev-151 for MIPS little endian architecture. I am configuring like this: ./configure --prefix=$PWD/sree --host=mips-linux-gnu configure: WARNING: If you wanted to set the --build type, don't use --host. If a cross compiler is detected then... (3 Replies)
Discussion started by: bsreeram
3 Replies
sb2-init(1)							 sb2-init man page						       sb2-init(1)

NAME
sb2-init - initialize a target for scratchbox2 SYNOPSIS
sb2-init [OPTION]... [TARGETNAME] [COMPILER[:SPECS]] [SECONDARY_COMPILER...] DESCRIPTION
sb2-init initializes a target for scratchbox2. If no options or other parameters are given, already initialized targets are listed. A scratchbox2 target is simply a light-weight, symbolic name for a configuration set. A target does not contain anything that is active, like running processes; hence a user never "works inside a target". Instead, sessions are used for all active operations. Sessions are created by the sb2 command. sb2-init is expected to be run in the directory you want to use as the target root filesystem. TARGETNAME is the name of the target to initialize. If it refers to an existing target, then the target is re-initialized. Otherwise a new one is created. COMPILER is full path to a cross-compiler (gcc), of the form $HOME/arm-2006q3/bin/arm-linux-gcc. An optional SPECS parameter is path to the compiler specs file. If more than one compiler is specified, additional compilers are available by version number (e.g. if the primary is known as "gcc" and "gcc-4.1", the secondary may be "gcc-3.4", etc) Note that the compiler is usually used during the target creation process to determine CPU architecture of the target system. OPTIONS
-c "command" specify cpu transparency command, for example: "qemu-arm", "sbrsh" or "qemu-arm -R 256M". CPU transparency method is the program which is used to execute foreign binaries, that the host computer can not execute directly. -p "command" specify cpu transparency command for staticly linked native binaries. -r [hostname] generate sbrsh config using remote device address -l [hostname] NFS server/localhost address seen by remote device -d set target as default scratchbox2 target (default target can also be set later with the sb2-config command) -m [mapping_mode] use mapping_mode as default. Default for this is "simple" -h Print help. -n don't build libtool for the target -N don't generate localization files for the target -s skip checks for target root's /usr/include etc. -t [tools_dir] set directory containing the build tools distribution -C "options" add extra options for the compiler, for example: -C "-fgnu89-inline" -A arch manually override target architecture -M arch manually override machine name (see uname(2)). This defaults to the target architecture (see option -A) -v display version EXAMPLES
mkdir $HOME/buildroot cd $HOME/buildroot [fetch a rootfs from somewhere and extract it here] sb2-init -c qemu-arm TARGET /path/to/cross-compiler/bin/arm-linux-gcc FILES
$HOME/.scratchbox2/* SEE ALSO
sb2(1), sb2-config(1), qemu(1) BUGS
No known bugs at this time. AUTHORS
Lauri T. Aarnio 2.2 17 December 2010 sb2-init(1)
All times are GMT -4. The time now is 07:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy