Hello all,

I've been experimenting with PB 4.2 with a fair amount of success. I built
the CEPC, and ran through the tutorials just fine. I've used both eboot.bin
to transfer the image via Ethernet, and copied the nk.bin to the drive and
loaded it locally. I'm now trying to venture into new waters. I want to try
and get a Fujitsu Stylus 1000 Pen tablet (486 DX 100, 340 Type III drive, 24
Meg RAM) running on CE. I've run into problems (surprise, surprise), and am
looking for some insight. I've copied the CEPC nk.bin to the hard drive of
the tablet, and select the load it locally option. I've been able to get
Win95 and Win98 running on the tablet with the pen working.

Question #1
The VESA test utility comes back with "Number of valid FLAT driver modes:
0". Does that mean that I cannot use this device at all, or I need to
get/develop a custom driver for the adapter (Chips Technologies

Question #2
When the image unpacks, it gets to the 100% mark, displays "Jumping to
0x0023AF88" and then reboots. I've looked at the debug info in
Hyperterminal, but a good portion of it doesn't make sense to me. Can
someone assist in decyphering it for me. I built 3 different CEPC platforms,
Mobile Handheld, Mobile Handheld with lots of stuff removed, and the Tiny
Kernel. I'm including the debug infor for each.

Mobile Handheld:
Debug Serial Init

SysInit: GDTBase=814580f8 IDTBase=81486160 KData=81499800
Windows CE Kernel for i486 Built on Mar 13 2003 at 22:43:26
g_PageDir = 814a1000
No PCI bus
+OEMKitlInit
Unable to initialize KITL Transports!
-OEMKitlInit
KITL Initialization Failed, No debugging support available
CEPC Firmware Init
RTC - Status Reg B - 0x02
PCIBIOS:: BIOS Address static map to addr=a00e0000
GetPicRoutingIrqTable: Start
search_pci_bios start
search_pci_bios end fails
GetPicRoutingIrqTable: FAILS!!!
Firmware Init Done.
Looking for rom chain
Rom chain NOT found
Booting Windows CE version 4.20 for
(x86
)
&pTOC = 80225408, pTOC = 814562d8, pTOC->ulRamFree = 814a1000, MemForPT =
000240
00

Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 1849, Secondary pages: 0, Filesystem pages = 924

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 814c6000, extension: 00001000, length: 00739000
X86Init done, OEMAddressTable = 8023afa8.
Windows CE KernelInit

Tiny Kernel:

Debug Serial Init

SysInit: GDTBase=802be0f8 IDTBase=802c2c40 KData=802cd8000t: 1089,
SrcAddr.wPort: 2048
Windows CE Kernel for i486 Built on Mar 13 2003 at 22:43:26FTP link[1]:
State:3, DestAddr.wPort: 1103, SrcAddr.wPort:
g_PageDir = 802d5000
CEPC Firmware Init
RTC - Status Reg B - 0x02
PCIBIOS:: BIOS Address static map to addr=a00e0000
GetPicRoutingIrqTable: Start
search_pci_bios start
search_pci_bios end fails
GetPicRoutingIrqTable: FAILS!!!
Firmware Init Done.
Looking for rom chain
Rom chain NOT found
Booting Windows CE version 4.20 for
(x86
)
&pTOC = 80225410, pTOC = 80281c40, pTOC->ulRamFree = 802d5000, MemForPT =
000240
00

Old or invalid version stamp in kernel structures - starting clean!
Configuring: Primary pages: 6404, Secondary pages: 0, Filesystem pages =
3202

Booting kernel with clean memory configuration:
Memory Sections:
[0] : start: 802fa000, extension: 00002000, length: 01904000
X86Init done, OEMAddressTable = 802327f8.
Windows CE KernelInit



Thanks in advance,


-Jorden

--
There are 10 different types of people in the world... those who understand
Binary, and those who don't.

Remove "nospam." to reply via email.

RE: Newbie help requested by jeffgla

jeffgla
Tue Feb 17 00:46:59 CST 2004


Question #1: It just means that your display controller doesn't support a
VESA BIOS. It also means you can't use the FLAT display driver shipped
with PB - you'll need to find/develop a custom display driver for your
hardware or find a display controller which supports a VESA BIOS version
2.0 or greater. There are some C&T display drivers floating around.

Question #2: Reboots during the early boot stage are usually memory errors
that trigger an unhandled exception. You probably want to review the
config.bib file (platform\cepc\files) and make sure the memory
configuration being selected for the build matches what's physically
available on your device.

Jeff