Re: Configuring WinCE 5.0 for the TME PC104-P3 embedded computer
- From: Avi Shmidman <AviShmidman@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 28 Jul 2005 07:01:11 -0700
Dear Dean,
Thank you for your response.
I am wondering how I can verify whether my system is configured to use the
FLAT display driver. In the OSDesignView tab of my workspace, under "device
drivers/display", the only item which is included is the "VGA Linear (Flat)
framebuffer" driver. Is this sufficient, or is there something else I must
configure in order to ensure that the FLAT driver takes effect at load time?
- Avi
"Dean Ramsier" wrote:
> You've implemented the hive registry, and it's apparently not been done
> correctly for this device. First remove the hive registry component (make
> sure you do a CLEAN sysgen after removing it) and get your device running.
> After it's up to your satisfaction you can then try to get the hive
> implemented. It's difficult enough to do anyway, and shouldn't be attempted
> on the first pass at board bringup.
>
> Note that you can probably just use the flat display driver, it will
> probably work fine.
>
> --
> Dean Ramsier - eMVP
>
>
> "Avi Shmidman" <AviShmidman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:6177BE6C-878C-428F-8FC4-3363B562B6F5@xxxxxxxxxxxxxxxx
> > Hello All,
> > Our target system is the TME PC104-P3 embedded computer. We have built a
> > debug nk.bin which runs successfully on our standard PC. However, when we
> > download it to the TME PC104-P3, something goes wrong. The bootloader
> > succeeds in making the connection, the nk.bin is downloaded, and the
> debugger
> > connects. At that point, though, nothing more is displayed, and the kernel
> > debugger indicates some errors (copied below). Now, in truth, I have not
> yet
> > found video drivers for the board (it uses the C&T 69030; TME does not
> supply
> > the drivers, and Asiliant does not have them on their website either -
> anyone
> > have any ideas?), but it seems to me that something more is going wrong.
> > The output from the kernel debugger is as follows:
> >
> > The Kernel Debugger connection has been established (Target CPU is X86).
> > Target name: CE Device
> > Probe name: KdStub
> > Binary Image should be loaded at 0x80220000 / Data relocated at 0x82277000
> > Loaded symbols for
> > 'C:\WINCE500\PBWORKSPACES\TEST2\RELDIR\CEPC_X86_DEBUG\NK.EXE'
> > Loaded symbols for
> > 'C:\WINCE500\PBWORKSPACES\TEST2\RELDIR\CEPC_X86_DEBUG\KD.DLL'
> > Loaded symbols for
> > 'C:\WINCE500\PBWORKSPACES\TEST2\RELDIR\CEPC_X86_DEBUG\OSAXST1.DLL'
> > Loaded symbols for
> > 'C:\WINCE500\PBWORKSPACES\TEST2\RELDIR\CEPC_X86_DEBUG\OSAXST0.DLL'
> > Loaded symbols for
> > 'C:\WINCE500\PBWORKSPACES\TEST2\RELDIR\CEPC_X86_DEBUG\HD.DLL'
> > 4294767356 PID:3fdf002 TID:3fdf1de 0x83fdf030: first = 01590000, last =
> > 02000000, SharedDllBase = 02160000
> > 4294767358 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module
> > coredll.dll at address 0x03F40000-0x03FF4000 (RW data at
> > 0x01FFE000-0x01FFF765)
> > Loaded symbols for
> > 'C:\WINCE500\PBWORKSPACES\TEST2\RELDIR\CEPC_X86_DEBUG\COREDLL.DLL'
> > 4294767372 PID:3fdf002 TID:3fdf1de 0x83fdf030: Did not find emulation code
> > for x86... using floating point hardware.
> > 4294767473 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: >>> Loading module
> > coredll.dll at address 0x03F40000-0x03FF4000 (RW data at
> > 0x01FFE000-0x01FFF765)
> > 4294767487 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: >>> Loading module
> > filesys.exe at address 0x04010000-0x04083000
> > Loaded symbols for
> > 'C:\WINCE500\PBWORKSPACES\TEST2\RELDIR\CEPC_X86_DEBUG\FILESYS.EXE'
> > 4294767500 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: CertMod.dll not found,
> > using old OEM Trust Model
> > 4294767501 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FileSystem Starting -
> > starting with clean file system
> > 4294767503 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FS: initializing ROM/RAM
> > file system
> > 4294767503 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: SC_CreateAPIHandle:
> pvData
> > == NULL
> > 4294767504 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FS: Registering file
> system
> > ROM, index 2, flags 0x00000031
> > 4294767504 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FS: Mount complete (ROM,
> > index 2, flags 0x00000031)
> > 4294767506 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: >>> Loading module
> > eventlog.dll at address 0x02FD0000-0x02FEB000 (RW data at
> > 0x01E61000-0x01E618B4)
> > Loaded symbols for
> > 'C:\WINCE500\PBWORKSPACES\TEST2\RELDIR\CEPC_X86_DEBUG\EVENTLOG.DLL'
> > 4294767519 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: EventLog:: EventLogInit()
> > called
> > 4294767520 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: OEMIoControl: Unsupported
> > Code 0x101008c - device 0x0101 func 35
> > 4294767521 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FSVOL: Opening existing
> > volume
> > 4294767522 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FSVOL: Volume heap
> already
> > initialized
> > 4294767522 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FSREG: Mounted ROM
> portion
> > of boot registry
> > 4294767523 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FSVOL: Creating clean
> > virtual volume
> > 4294767523 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FSVOL: Initializing
> volume
> > heap
> > 4294767525 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FSREG: Mounted RAM
> portion
> > of boot registry
> > 4294767526 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: PCIReg(key: , device:
> 0/0/0)
> > 4294767527 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FS: Creating signal event
> > SYSTEM/DevMgrApiSetReady
> > 4294767528 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FS: Creating signal event
> > SYSTEM/PowerManagerReady
> > 4294767528 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FS: Creating signal event
> > SYSTEM/GweApiSetReady
> > 4294767529 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FS: Creating signal event
> > ReleaseFSD
> > 4294767529 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FSREG: Unable to read
> value
> > "Start DevMgr" under HKEY_LOCAL_MACHINE\init\BootVars
> > 4294767530 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: FILESYS: NOT starting
> > device manager to reach system hive.
> > 4294767530 PID:e3fc8c1a TID:e3fc8bea 0x83fc8a3c: OEMIoControl: Unsupported
> > Code 0x10100d4 - device 0x0101 func 53
> >
> >
> >
> >
>
>
>
.
- References:
- Configuring WinCE 5.0 for the TME PC104-P3 embedded computer
- From: Avi Shmidman
- Re: Configuring WinCE 5.0 for the TME PC104-P3 embedded computer
- From: Dean Ramsier
- Configuring WinCE 5.0 for the TME PC104-P3 embedded computer
- Prev by Date: Re: right click menu ( no context menu for stylus ) problem? help !
- Next by Date: ARM compiler bug?
- Previous by thread: Re: Configuring WinCE 5.0 for the TME PC104-P3 embedded computer
- Next by thread: FSSCTL_FLUSH_BUFFERS bug
- Index(es):
Relevant Pages
|
|
