Hello ....

Alright, given a Jornada 720 with a 128MB CF card.

I prepared the CF card with two partitions.  The first is a MS-DOS
partition [id 6, 4MB long] that holds a copy of -current hpcboot.exe and a
gzipped -current netbsd ARM kernel.

The second partition [id 169, 118MB long] is a big endian ffs file system.
It contains most of a recent hpcarm build from releng.netbsd.org, about
83MB worth.

The CF card was prepared on a NetBSD/i386 system, the ffs file system was
created with 'newfs -B be ...'.  The NetBSD/i386 machine was using FFS_EI
to mount the file system.  I used 'fdisk' and 'disklabel -I ...' against
the CF on the i386 machine, and used a MS-WINDOWS 98 box to format the
MS-DOS partition.

Something isn't right, however..  When I click on hpcarm.exe, I get the
'Push OK to boot.' popup, which I presume means hit the 'Yes' button.
After that, however, everything appears to hang and resets are required to
get control of the computer again.  The screen never clears and all key
responses are ignored, including the on/off button.  The console log
contains the following:

BOOT START
ARM architecture.
MemoryManager: LockPages
FileManager: FAT
[0] 0xc0000000 size 0x08000000
[1] 0xc8000000 size 0x08000000
[2] 0xd0000000 size 0x08000000
[3] 0xd8000000 size 0x08000000
GetVersionEx
Windows CE 3.0
GetSystemInfo:
wProcessorArchitecture      0x5
dwPageSize                  0x1000
dwAllocationGranularity     0x00010000
dwProcessorType             0xa11
wProcessorLevel             0x4
wProcessorRevision          0x8
Display: 640x240 16bpp
Reg0 :6901b118
Reg1 :c002327f
Reg2 :c002327f
Reg3 :00000001
Reg5 :c0023007
Reg6 :01f90008
Reg13:0a000000
Reg14:00000000
CPSR :2000001f
open file "\Storage Card\netbsd.gz"(1074002 byte).
Loader: ELF
file size: +0x1e6cf4+0x49e94+[(symbol block: header 472 string 102910 symbol 134352 byte) = 0x3a0a8] = 0x26b0a8 byte
address translation table 640 pages.(5120 byte)
allocated 640 page. mapped 640 page.
2nd bootloader vaddr=0x0036f000 paddr=0xc1d38000
2nd bootloader copy done.
[0] vaddr 0xc0040000 file size 0x1e6cf4 mem size 0x1e6cf4
        ->load 0xc0040000+0x001e6cf4=0xc0226cf4 ofs=0x00008000+0x1e6cf4
[1] vaddr 0xc022ecf4 file size 0x49e94 mem size 0x8c974
        ->load 0xc022ecf4+0x0008c974=0xc02bb668 ofs=0x001eecf4+0x49e94
[zero clear] ->0xc0278b88+0x00042ae0=0xc02bb668
        ->load 0xc02bb668+0x000001d8=0xc02bb840
        ->load 0xc02bb840+0x000191fe=0xc02d4a3e ofs=0x0025f430+0x191fe
        ->load 0xc02d4a40+0x00020cd0=0xc02f5710 ofs=0x0023e760+0x20cd0
load link 624 zero clear link 1.
kernel entry address: 0xc0040000
framebuffer: 640x240 type=5 linebytes=0 addr=0x00000000
console = 1


The bootloader noted that there was a console attached, so I would presume
that it would feel the need to use it, rather then a serial console.  I
specified that 'wd' be used as the source of the root filesystem, and I
presume that this will be the second partition on the disk.

I suspect that I am missing something obvious, but I am at a lose to
understand what.  Any help would be appreciated.  Thanks...






-- 
Brad Spencer - brad@anduin.eldar.org
http://anduin.eldar.org  - & -  http://anduin.ipv6.eldar.org [IPv6 only]
[finger brad@anduin.eldar.org for PGP public key]