Subject: Stop in cross-compilation of JORNADA720 on x86
To: None <port-hpcarm@netbsd.org>
From: Enry <hpcarm@enry.net>
List: port-hpcarm
Date: 05/26/2001 22:05:48
Hello, NetBSD/hpcarm

I dropped 1.5 (x86) on an Intel Pentium III for the purpose of
cross-compiling a hpcarm kernel for my SA1110 based Jornada 720 (*pet*pet*).
But the compilation failed, and I not yet knowledgeable enough with the port
to fix the problem.  Suggestions would be much appreciated.
Here's what I did:

- pkg_add cross/arm-netbsd and binutils to set up the crosscompiling
environment
- cvs checkout of full syssrc tree
- borrowed hpcmips-make script from NetBSD/hpcmips site and altered for
hpcarm and arm-netbsd compiler (script renamed to hpcarm-make)
- in sys/arch/hpcarm/conf, ran 'configure JORNADA720', since the options in
'JORNADA720' are OK for me.
- cd ../compile/JORNADA720; hpcarm-make depend
- hpcarm-make
- prayed to bsd god

Unfortunately, arm-netbsd-gcc returned an error "Error: Bad arguments to
instruction" when compiling arch/hpcarm/hpcarm/softintr.c.  Please see
below:

---SNIP---

/usr/pkg/cross/bin/arm-netbsd-gcc  -O2 -Werror -Wall -Wcomment -Wpointer-ari
th -Wno-uninitialized -Wno-main -I. -I../../../../arch -I../../../.. -nostdi
nc -DHPCARM -DSAIP -DLKM -DDIAGNOSTIC -DCONSPEED="0x4b00" -DBOOTINFO_FB_LINE
_BYTES="0x500" -DBOOTINFO_FB_WIDTH="0x280" -DBOOTINFO_FB_HEIGHT="0xf0" -DBOO
TINFO_FB_TYPE="5" -DFRAMEBUF_HW_BASE="0x48200000" -DMAXUSERS=32 -D_KERNEL -D
hpcarm -Darm32  -c ../../../../arch/hpcarm/hpcarm/softintr.c
/tmp/ccU5WnSl.s: Assembler messages:
/tmp/ccU5WnSl.s:149: Error: Bad arguments to instruction
/tmp/ccU5WnSl.s:179: Error: Bad arguments to instruction
/tmp/ccU5WnSl.s:187: Error: Bad arguments to instruction
*** Error code 1

---SNIP---

I don't have much arm32 assembler experience :/

On the other hand, I was able to get
/arch/hpcarm/snapshot/kernel/netbsd-20010224 working on my 720.
Unfortunately, I was unable to mount any root filesystem (my flash card is
formatted MSDOS).  Furthermore, I really don't know how a miniroot.fs
filesystem image is created.  Does someone have any suggestions for that
solution?

Regards,

Enry