Posts by al12559

al12559 · Mar 2nd 2011

Hello everybody,
I would be grateful if anybody could assist me in overcoming this problem:
After I start to communicate with an I2C device, the ActiveSync connection will be closed after a reproducible duration.
I use a PicoCOM2 with a custom-made mainboard, connected to WindowsXP using ActiveSync 4.5.
The I2C driver is activated (with Debug=1 setting), one device (MCP23017 PortExpander) is connected to the bus and works normally.
Serial debug shows:

Code

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Nov 23 2010 11:16:01
Microsoft Windows CE Bootloader for PICOCOM2 Built Dec 22 2010
Portions copyright (c) 2007 F&S Elektronik Systeme GmbH
Boot Loader, Version 1.7
NBoot, Version C215
32 MB Ram
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
Board Revision: 1.10
System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
+ReadKernelRegionFromNandFlash
Image Signature in Flash Memory found (dwSig=0x43454345)
TOC pointer=0x810385B0
ROMHDR (cTOC = 0x00f265b0) ---------------------
DLL First : 0x4001c001
DLL Last : 0x40a8c0a0
Physical First : 0x80112000
Physical Last : 0x8103a494
Num Modules : 185
RAM Start : 0x81040000
RAM Free : 0x81058000
RAM End : 0x82012000
Num Copy Entries : 2
Copy Entries Offset : 0x808f8e88
Prof Symbol Length : 0x00000000
Prof Symbol Offset : 0x00000000
Num Files : 68
Kernel Flags : 0x00000000
FileSys RAM Percent : 0x20202020
Driver Glob Start : 0x00000000
Driver Glob Length : 0x00000000
CPU : 0x01c2
MiscFlags : 0x0002
Extensions : 0x80113140
Tracking Mem Start : 0x00000000
Tracking Mem Length : 0x00000000
Kernel (15521kB) read from flash disk started finished in 5881 milliseconds
Kernel read from NAND
INFO: OEMLaunch: Jumping to Physical Address 0x20113000h (Virtual Address 0x0h)...
Windows CE Kernel for ARM (Thumb Enabled) Built on Aug 4 2010 at 14:23:58
PicoCOM2 V1.16 - Firmware Init
Copyright (c) 2008 F&S Elektronik Systeme GmbH
Build: Jan 18 2011/09:27:33
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x400b
OEMInit: SDRAM = 32 MB
DCache: 128 sets, 4 ways, 32 line size, 16384 size
ICache: 128 sets, 4 ways, 32 line size, 16384 size
OEM: Force clean boot.
OALTimerInit
OALKitlStart
Firmware Init Done.
OEM: Watchdog ENABLED
Handle Event:0xa00003, sysintr=0x10OEM: Not clearing storage
OEM: Not cleaning system hive
OEM: Not cleaning user profiles
OEM: Not cleaning system hive
PM-NETDCU: STARTED
NET: Version V1.5, ActiveKey = Comm\ETHNETA
USBFN: Version 1.2, ActiveKey = Drivers\Active\07
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
BCS: Version 1.0, ActiveKey = Drivers\Active\22
NI2C: Version 1.13, ActiveKey = Drivers\Active\23
NI2C: Installed ISR handler, Dll = 'pc2_twiisr.dll', Handler = 'ISRHandler', Irq = 13, SysIntr = 0x15
NI2C: Interrupt service thread ID: 0x03aa0002
NI2C: TWI_CWGR = 0x00029494
DIO: Version 3.3, ActiveKey = Drivers\Active\24
SDHC:Version 1.2, ActiveKey = Drivers\Active\25
SDHC:Card state change detected!
DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 150, Name Glyn G-ET035009DH6
DDGPE:Width: 320 Height: 240 Bpp: 16
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED
NDCUCFG V: 042 started. Platform: PicoCOM2
CheckAutoStart: Version 1.4, LaunchNum = 100
CreateFile() failed -> ERROR COM1:
NET: cable attached
USBFN:C_USB_DEVICE::ThreadRun: : Attach Detected

Display More

ActiveSync is connected (taskbar icon turns into green), these are the ActiveSync log files

Code

-----------------------------------------------------------------------
11:32:35 ActiveSync verbunden (Icon in PC-Taskleiste wird grün)
-----------------------------------------------------------------------
WCESCOMM.LOG:
-----------------------------------------------------------------------
03/02/2011 11:32:34.941 - Windows CE Services (4.5.0) Communication Logging.
03/02/2011 11:32:34.941 - Logging file auto-purge after a successful device connection.
03/02/2011 11:32:34.941 -
03/02/2011 11:32:35.066 - CesProxy: Accept on port 990, IsWinsock 1, hResult 0
03/02/2011 11:32:35.066 - TCP: ....S., 192.168.55.100(1033) => 192.168.55.101(990) Seq=9385890-9385890 Ack=0 Win=8192 Len=44
03/02/2011 11:32:35.082 - TCP: .A..S., 192.168.55.101(990) => 192.168.55.100(1033) Seq=2690367-2690367 Ack=9385891 Win=33580 Len=44
03/02/2011 11:32:36.019 - CesProxy: Accept on port 990, IsWinsock 1, hResult 0
03/02/2011 11:32:36.019 - TCP: ....S., 192.168.55.100(1034) => 192.168.55.101(990) Seq=9386843-9386843 Ack=0 Win=8192 Len=44
03/02/2011 11:32:36.019 - TCP: .A..S., 192.168.55.101(990) => 192.168.55.100(1034) Seq=2954334-2954334 Ack=9386844 Win=33580 Len=44
03/02/2011 11:32:36.050 - CesProxy: recv failed on Win socket 990, err = 10054
03/02/2011 11:32:36.066 - CesProxy: Close Win socket 990
03/02/2011 11:32:36.066 - CesProxy: Close PPP socket 990
03/02/2011 11:32:36.066 - TCP: ...R.., 192.168.55.100(1033) => 192.168.55.101(990) Seq=9386081-9386081 Ack=2954355 Win=0 Len=40
03/02/2011 11:32:36.082 - CesProxy: recv failed on PPP socket 990, err = 10004
03/02/2011 11:32:36.097 - TCP: .A.R.., 192.168.55.101(990) => 192.168.55.100(1034) Seq=2954371-2954371 Ack=9387364 Win=0 Len=40
03/02/2011 11:32:36.097 - CesProxy: recv failed on PPP socket 990, err = 10054
03/02/2011 11:32:36.097 - CesProxy: Close Win socket 990
03/02/2011 11:32:36.113 - CesProxy: recv failed on Win socket 990, err = 10053
03/02/2011 11:32:36.113 - CesProxy: Close PPP socket 990
-----------------------------------------------------------------------
WCESMgr.log:
-----------------------------------------------------------------------
03/02/2011 11:32:35.457 Creating new partnership for device 0x0 (PicoCOM2, PicoCOM2).
03/02/2011 11:32:35.457 Creating a guest connection for device of type 'PicoCOM2'
03/02/2011 11:32:35.597 **************** Logging Started ****************
03/02/2011 11:32:35.597 Process G:\Programme\Microsoft ActiveSync\WCESMgr.exe p(2616)
03/02/2011 11:32:35.597 ActiveSync second instance started, Cmd line: '/onconnect'
03/02/2011 11:32:35.597 ActiveSync second instance exiting
03/02/2011 11:32:35.597 **************** Logging Stopped ****************
03/02/2011 11:32:35.457 p(3300) t(1912) TraceToFile -> ERROR in CPartnerReg::Initialize : hr = 0x8000ffff - syncmgr.cpp(5726)
03/02/2011 11:32:35.457 p(3300) t(1912) TraceToFile -> ERROR in CPartnerReg::CreatePartnerReg : hr = 0x8000ffff - syncmgr.cpp(5642)
03/02/2011 11:32:35.457 p(3300) t(1912) TraceToFile -> ERROR in CProfiles::SetDeviceDataFolder : hr = 0x80070057 - syncmgr.cpp(5280)
03/02/2011 11:32:35.457 p(3300) t(1912) TraceToFile -> ERROR in CDevInfo::CreateGuestProfile : hr = 0x80070057 - partner.cpp(1579)
03/02/2011 11:32:35.457 p(3300) t(1696) TraceToFile -> ERROR in AllowMultiHomingIfCapable : hr = 0x80072746 - partner.cpp(1906)

Display More

Now I start an application that communicates with the port expander using CreateFile/WriteFile/ReadFile on the I2C driver. Serial debug:

Code

NI2C: TWI_CWGR = 0x00029494
USBFN:C_USB_DEVICE::ThreadRun: : Detach Detected

(The "USBFN:C_USB_DEVICE" is a USB flash drive.) Exactly 106 seconds later the ActiveSync connection is closed down, the taskbar icon turns grey.ActiveSync log files show:

Code

-----------------------------------------------------------------------
WCESCOMM.LOG:
-----------------------------------------------------------------------
03/02/2011 11:34:44.948 - Device timed out, timeout 100, iret 0, Connected 1, RLSD 1. Error 0
03/02/2011 11:34:44.948 - CesProxy: recv failed on Win socket 5679, err = 10054
03/02/2011 11:34:44.948 - Connection: Prep for a new socket connection.
03/02/2011 11:34:44.948 - CesProxy: Close PPP socket 5679
03/02/2011 11:34:45.058 - CesProxy: Close Win socket 5679
-----------------------------------------------------------------------
WCESMgr.log:
-----------------------------------------------------------------------
03/02/2011 11:34:45.105 p(3300) t(1912) TraceToFile -> ERROR in CPartnerReg::Initialize : hr = 0x8000ffff - syncmgr.cpp(5726)
03/02/2011 11:34:45.105 p(3300) t(1912) TraceToFile -> ERROR in CPartnerReg::CreatePartnerReg : hr = 0x8000ffff - syncmgr.cpp(5642)
03/02/2011 11:34:45.105 p(3300) t(1912) TraceToFile -> ERROR in CProfiles::GetDeviceDataFolder : hr = 0x80070057 - syncmgr.cpp(4982)
03/02/2011 11:34:45.105 p(3300) t(1912) TraceToFile -> ERROR in CSyncMgrApp::DeleteProfileData2 : hr = 0x80070057 - syncmgr.cpp(3925)

Display More

Neither unplugging and replugging the USB cable nor NDCUCFG:Reboot will restore the connection, a cold reboot is required.
--
I tried the same setup with a PicoCOM starter kit and the same PicoCOM module. The only difference is that in this case there is no device connected over I2C.
When I start my application that tries to connect the I2C device, serial debug output is

Code

NI2C: TWI_CWGR = 0x00029494
NI2C: TWI_CWGR = 0x00029494
NI2C: TWI_CWGR = 0x00029494
NI2C: TWI_CWGR = 0x00029494
NI2C: TWI_CWGR = 0x00029494
NI2C: TWI_CWGR = 0x00029494
NI2C: TWI_CWGR = 0x00029494
NI2C: TWI_CWGR = 0x00029494
NI2C: TWI_CWGR = 0x00029494
NI2C: TWI_CWGR = 0x00029494

I observe that the line

Code

USBFN:C_USB_DEVICE::ThreadRun: : Detach Detected

is missing, instead

Code

NI2C: TWI_CWGR = 0x00029494

is issued multiple times, probably due to the missing I2C device. (Both setups can't be compared I'm afraid.)
Can you explain this behaviour? The constant time interval of 106 s before ActiveSync is disconnected (tried many times) leads to the assumption a timeout might be expired. But which? of what device or component?
The line containing

Quote

Device timed out, timeout 100, iret 0, Connected 1, RLSD 1. Error 0

in WCESCOMM.LOG might give a hint. There is no ethernet connection.
Any help I will appreciate as the short ActiveSync life time is very annoying. Debugging an application from VisualStudio is impossible.

al12559 · Feb 11th 2011

As I could not find any information about the undocumented "boot display" command (not in this forum as well), using it was an effort to finally get the module running.
Now I did what you proposed (EBoot: E and download the kernel) - at no avail. Behaviour is exactly as before.
I suppose I should send the module to you to have it checked? How long would that take?
Can you identify any differences between my four modules according to their serial numbers?

al12559 · Feb 11th 2011

Both serial debug outputs reflect the situation after configuring and activating Mode150.
In case (3) it is the output of one of the 3 PicoCOM modules that behave normally.
In case (4) it is the output of the PicoCOM module that remains blank (or dark).
In that case I reset the mode by

Code

!>display mode set 2

to the default value and received some display but not matching my display properties, just teh same as after downloading the kernel.
After I activated Mode150 again, the result was a blank screen. Not any error messages.
I cannot find any difference in the debug output that might indicate a deviation.

al12559 · Feb 11th 2011

Quote

Is there any error message during second boot?

Not that I'm aware of. What do you mean by second boot? I quoted the serial debug outputs of the both cases and see no difference.

Quote

Is your mode100 configuration in registry still available or has the registry been reset?

Registry had been reset after downloading the kernel. Next I sent the text file with the display seetings via DCUTerm to PicoCOM and rebooted. Registry contents for Mode150 is

Code

[HKEY_LOCAL_MACHINE\Drivers\Display\LCD\Mode150]
"Verbose"=dword:00000001
"EnableCursor"=dword:00000000
"PPL"=dword:00000140
"columns"=dword:00000140
"ELW"=dword:00000044
"BLW"=dword:00000014
"HSW"=dword:0000000a
"LPP"=dword:000000f0
"rows"=dword:000000f0
"EFW"=dword:00000004
"BFW"=dword:00000010
"VSW"=dword:00000002
"bpp"=dword:00000010
"lcdclk"=dword:0000000a
"config"=dword:08000000
"EarlyLCDVoltage"=dword:00000001
"type"=dword:00000006
"contrastvalue"=dword:00000000
"contrastenable"=dword:00000000
"height"=dword:00000035
"width"=dword:00000046
"msignal"=dword:00000002
"name"="Glyn G-ET035009DH6"

Display More

I had set the "verbose" value to 1 but did not mention any additional output on serial debug.

al12559 · Feb 11th 2011

I still cannot get the display ET0350G0DM6 to work with one PicoCOM2 module.
History:
(1) Install Kernel V-1.16 with standard Hitachi display settings
=> Desktop is shown but settings do not match the ones of my display
(2) Set up and activate Mode150 with

Code

reg open \drivers\display\lcd
reg create key Mode150
reg set value name string "Glyn G-ET035009DH6"
reg set value msignal dword 2
reg set value width dword 70
reg set value height dword 53
reg set value contrastenable dword 0
reg set value contrastvalue dword 0
reg set value type dword 6
reg set value EarlyLCDVoltage dword 1
reg set value config dword 0x08000000
reg set value lcdclk dword 10
reg set value bpp dword 16
reg set value EnableCursor dword 0
REM **********Vertical*************+
reg set value VSW dword 2
reg set value BFW dword 16
reg set value EFW dword 4
reg set value rows dword 240
reg set value LPP dword 240
REM **********Horizontal*************+
reg set value HSW dword 10
reg set value BLW dword 20
reg set value ELW dword 68
reg set value columns dword 320
reg set value PPL dword 320
display mode set 150
boot display on
REM **
ECHO reg save
REM **
reg save

Display More

(3) Using the same custom-made mainboard and the same display, these settings lead to a normal desktop display when applied to PicoCOM2
S/N 0005 5102 3F2D
S/N 0005 5102 3DF5
S/N 0005 5102 116A.
Serial debug output is

Code

Windows CE Kernel for ARM (Thumb Enabled) Built on Aug 4 2010 at 14:23:58
PicoCOM2 V1.16 - Firmware Init
Copyright (c) 2008 F&S Elektronik Systeme GmbH
Build: Jan 18 2011/09:27:33
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x400b
OEMInit: SDRAM = 32 MB
DCache: 128 sets, 4 ways, 32 line size, 16384 size
ICache: 128 sets, 4 ways, 32 line size, 16384 size
OEM: Force clean boot.
OALTimerInit
OALKitlStart
Firmware Init Done.
OEM: Watchdog ENABLED
Handle Event:0xa00003, sysintr=0x10OEM: Not clearing storage
OEM: Not cleaning system hive
OEM: Not cleaning user profiles
OEM: Not cleaning system hive
PM-NETDCU: STARTED
NET: Version V1.5, ActiveKey = Comm\ETHNETA
USBFN: Version 1.2, ActiveKey = Drivers\Active\10
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
USBFN:C_USB_DEVICE::ThreadRun: : Attach Detected
COM: Version 1.11, ActiveKey = Drivers\Active\12
CID: Version 2.4, ActiveKey = Drivers\Active\15
BCS: Version 1.0, ActiveKey = Drivers\Active\27
NI2C: Version 1.13, ActiveKey = Drivers\Active\28
DIO: Version 3.3, ActiveKey = Drivers\Active\29
WAV: Version 2.3, ActiveKey = Drivers\Active\30
SDHC:Version 1.2, ActiveKey = Drivers\Active\31
DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 150, Name Glyn G-ET035009DH6
DDGPE:Width: 320 Height: 240 Bpp: 16
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED
CheckAutoStart: Version 1.4, LaunchNum = 100
NDCUCFG V: 042 started. Platform: PicoCOM2
CreateFile() failed -> ERROR COM1:

Display More

(4) But when the same settings are applied to PicoCOM2
S/N 0005 5102 3F3C
the display remains dark!
Serial debug output is

Code

Windows CE Kernel for ARM (Thumb Enabled) Built on Aug 4 2010 at 14:23:58
PicoCOM2 V1.16 - Firmware Init
Copyright (c) 2008 F&S Elektronik Systeme GmbH
Build: Jan 18 2011/09:27:33
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x400b
OEMInit: SDRAM = 32 MB
DCache: 128 sets, 4 ways, 32 line size, 16384 size
ICache: 128 sets, 4 ways, 32 line size, 16384 size
OEM: Force clean boot.
OALTimerInit
OALKitlStart
Firmware Init Done.
OEM: Watchdog ENABLED
Handle Event:0xa00003, sysintr=0x10OEM: Not clearing storage
OEM: Not cleaning system hive
OEM: Not cleaning user profiles
OEM: Not cleaning system hive
PM-NETDCU: STARTED
NET: Version V1.5, ActiveKey = Comm\ETHNETA
USBFN: Version 1.2, ActiveKey = Drivers\Active\10
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
USBFN:C_USB_DEVICE::ThreadRun: : Attach Detected
COM: Version 1.11, ActiveKey = Drivers\Active\12
CID: Version 2.4, ActiveKey = Drivers\Active\15
BCS: Version 1.0, ActiveKey = Drivers\Active\27
NI2C: Version 1.13, ActiveKey = Drivers\Active\28
DIO: Version 3.3, ActiveKey = Drivers\Active\29
WAV: Version 2.3, ActiveKey = Drivers\Active\30
SDHC:Version 1.2, ActiveKey = Drivers\Active\31
DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 150, Name Glyn G-ET035009DH6
DDGPE:Width: 320 Height: 240 Bpp: 16
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED
CheckAutoStart: Version 1.4, LaunchNum = 100
NDCUCFG V: 042 started. Platform: PicoCOM2
CreateFile() failed -> ERROR COM1:
NET: cable attached

Display More

(5)After I reset the display type to Mode2, situation is the same as in (1)

How can I overcome this??

al12559 · Feb 10th 2011

Quote

Does this mean that even the exceptions mentioned above only appear after installing this driver?

Yes, it does. Installing this driver was part of a configuration file for various settings. After splitting it into parts for display, driver, desktop settings it became clear that the exceptions are introduced by this driver. Apart from these exceptions, the module controlled by this driver works normally. I just wanted to remove this uncertainty in the boot process.

Quote

The driver you are trying to use on PicoCOM2, is it build for Windows CE 6.0?

As far as I know. I don't have the source code but may contact the developers.

Quote

Maybe you could check the dependecies for this dll (with depends.exe).

This USB device driver is shown to be dependent only on COREDLL.DLL. This seems to be reasonable as it is the same with other DLLs that I use on the PicoCOM.

al12559 · Feb 9th 2011

This is the Debug output after resetting registry (EBoot: R) - no exceptions:

Code

Windows CE Kernel for ARM (Thumb Enabled) Built on Aug 4 2010 at 14:23:58
PicoCOM2 V1.16 - Firmware Init
Copyright (c) 2008 F&S Elektronik Systeme GmbH
Build: Jan 18 2011/09:27:33
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x400b
OEMInit: SDRAM = 32 MB
DCache: 128 sets, 4 ways, 32 line size, 16384 size
ICache: 128 sets, 4 ways, 32 line size, 16384 size
OEM: Force clean boot.
OALTimerInit
OALKitlStart
Firmware Init Done.
OEM: Watchdog ENABLED
Handle Event:0xa00003, sysintr=0x10OEM: Not clearing storage
OEM: Cleaning system hive
OEM: Cleaning user profiles
OEM: Cleaning system hive
PM-NETDCU: STARTED
NET: Version V1.5, ActiveKey = Comm\ETHNETA
USBFN: Version 1.2, ActiveKey = Drivers\Active\10
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
COM: Version 1.11, ActiveKey = Drivers\Active\12
CID: Version 2.4, ActiveKey = Drivers\Active\15
BCS: Version 1.0, ActiveKey = Drivers\Active\27
NI2C: Version 1.13, ActiveKey = Drivers\Active\28
DIO: Version 3.3, ActiveKey = Drivers\Active\29
WAV: Version 2.3, ActiveKey = Drivers\Active\30
SDHC:Version 1.2, ActiveKey = Drivers\Active\31
DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 2, Name Hitachi TX09
DDGPE:Width: 240 Height: 320 Bpp: 16
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED
CheckAutoStart: Version 1.4, LaunchNum = 100
NDCUCFG V: 042 started. Platform: PicoCOM2
CreateFile() failed -> ERROR COM1:
NET: cable attached
USBFN:C_USB_DEVICE::ThreadRun: : Attach Detected

Display More

After I install a driver for a USB device by sending the text file

Code

reg open \Drivers\BuiltIn
reg create key BWTDriver
reg set value Prefix String "BWT"
reg set value Dll String "\FFSDISK\BWTCEDRV.dll"
reg set value Order dword 9
reg set value Index dword 1
reg open \Drivers\USB\LoadClients
reg create key 5795_11970
reg create key Default
reg create key Default
reg create key BWT
reg set value DLL String "\FFSDISK\BWTCEDRV.dll"
reg open \Drivers\USB\LoadClients
reg create key 5795_11972
reg create key Default
reg create key Default
reg create key BWT
reg set value DLL String "\FFSDISK\BWTCEDRV.dll"

Display More

to PicoCOM, the Debug Output changes to (mention the two exceptions)

Code

Windows CE Kernel for ARM (Thumb Enabled) Built on Aug 4 2010 at 14:23:58
PicoCOM2 V1.16 - Firmware Init
Copyright (c) 2008 F&S Elektronik Systeme GmbH
Build: Jan 18 2011/09:27:33
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x400b
OEMInit: SDRAM = 32 MB
DCache: 128 sets, 4 ways, 32 line size, 16384 size
ICache: 128 sets, 4 ways, 32 line size, 16384 size
OEM: Force clean boot.
OALTimerInit
OALKitlStart
Firmware Init Done.
OEM: Watchdog ENABLED
Handle Event:0xa00003, sysintr=0x10OEM: Not clearing storage
OEM: Not cleaning system hive
OEM: Not cleaning user profiles
OEM: Not cleaning system hive
PM-NETDCU: STARTED
NET: Version V1.5, ActiveKey = Comm\ETHNETA
USBFN: Version 1.2, ActiveKey = Drivers\Active\10
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
USBFN:C_USB_DEVICE::ThreadRun: : Attach Detected
COM: Version 1.11, ActiveKey = Drivers\Active\12
Exception 'Raised Exception' (-1): Thread-Id=01210002(pth=81ec9b00), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=02330002(pprc=812f6490) 'udevice.exe'
PC=c004fd34(k.coredll.dll+0x0002fd34) RA=80130520(kernel.dll+0x00006520) SP=d05ae924, BVA=00000000
Exception 'Raised Exception' (-1): Thread-Id=01210002(pth=81ec9b00), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=02330002(pprc=812f6490) 'udevice.exe'
PC=c003bb54(k.coredll.dll+0x0001bb54) RA=80130520(kernel.dll+0x00006520) SP=d05ae1d0, BVA=ffffffff
CID: Version 2.4, ActiveKey = Drivers\Active\16
BCS: Version 1.0, ActiveKey = Drivers\Active\28
NI2C: Version 1.13, ActiveKey = Drivers\Active\29
DIO: Version 3.3, ActiveKey = Drivers\Active\30
WAV: Version 2.3, ActiveKey = Drivers\Active\31
SDHC:Version 1.2, ActiveKey = Drivers\Active\32
SDHC:Card state change detected!
DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 2, Name Hitachi TX09
DDGPE:Width: 240 Height: 320 Bpp: 16
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED
NDCUCFG V: 042 started. Platform: PicoCOM2
CheckAutoStart: Version 1.4, LaunchNum = 100
CreateFile() failed -> ERROR COM1:
NET: cable attached

Display More

Can you give any explanation why installing this driver causes exceptions? The device controlled by this driver works normally.

al12559 · Feb 9th 2011

Am I correct to conclude that the registry settings I changed are not part of the stated hash value? Their modification does not lead to a registry reset on installing a kernel.
How can I force a registry reset to default values upon installing a kernel?

al12559 · Feb 9th 2011

[admin comment]
Thread splittet from: Debug output while booting shows exceptions

Quote

this issue has been solved already?!

Yes, it has. I decided to open another thread because it seems hard to get answered more than one single question at once. On the other hand, searching for questions regarding NDCUCFG is rather frustrating because this item will be ignored due to too many hits, even if ANDed with more words.

(repeated questions:)

Quote

How do I set an identical clean initial state on a PicoCOM module?
Is it sufficient to use "NetDCU USB Loader" for writing NBoot, EBoot and kernel?
How do I secure an identical initial registry contents?

I observed, that only writing a different kernel version than the one currently existing on the PicoCOM module seems to create standard registry settings: If e.g. display or built-in driver registry settings had been modified after installing the kernel (Glyn display type, audio and ananlog input drivers deactivated), I will find the same modified settings after writing the same kernel version again. On the other hand, if I write another kernel version to the module, I find standard settings (Hitachi display type, audio and ananlog input drivers activated)

How can that be explained?

al12559 · Feb 8th 2011

Setting

Code

config = 0x00A00000

does not help.

My current registry settings are

Code

[HKEY_LOCAL_MACHINE\Drivers\Display\LCD]
"Mode"=dword:00000096
"UseBootInit"=dword:00000000
"MemBase"=dword:00000000
"MemLen"=dword:00000000
[HKEY_LOCAL_MACHINE\Drivers\Display\LCD\Mode110]
"EnableCursor"=dword:00000001
"Rotate"=dword:0000010e
"ELW"=dword:00000010
"BLW"=dword:0000001e
"VSW"=dword:00000002
"lcdclk"=dword:00000006
"bpp"=dword:00000010
"HSW"=dword:00000020
"PPL"=dword:000000f0
"columns"=dword:000000f0
"config"=dword:00400000
"type"=dword:00000006
"contrastvalue"=dword:000005ff
"contrastenable"=dword:00000001
"height"=dword:00000056
"width"=dword:00000073
"LPP"=dword:00000140
"rows"=dword:00000140
"msignal"=dword:00000002
"BFW"=dword:00000004
"EFW"=dword:00000008
"name"="Hitachi TX09"
[HKEY_LOCAL_MACHINE\Drivers\Display\LCD\Mode150]
"EnableCursor"=dword:00000000
"PPL"=dword:00000140
"columns"=dword:00000140
"ELW"=dword:00000044
"BLW"=dword:00000014
"HSW"=dword:0000000a
"LPP"=dword:000000f0
"rows"=dword:000000f0
"EFW"=dword:00000004
"BFW"=dword:00000010
"VSW"=dword:00000002
"bpp"=dword:00000010
"lcdclk"=dword:0000000a
"config"=dword:00A00000
"EarlyLCDVoltage"=dword:00000001
"type"=dword:00000006
"contrastvalue"=dword:00000000
"contrastenable"=dword:00000000
"height"=dword:00000035
"width"=dword:00000046
"msignal"=dword:00000002
"name"="Glyn G-ET035009DH6"

Display More

After changing "config" to 0x08000000 I was not surprised to have the correct display again as this setting was valid for all previous installations.
What about the NDCUCFG command

Code

boot display on

?
Is it required? What parameters are valid?

al12559 · Feb 8th 2011

Code

REM
REM ********** Display settings *************+
REM
reg open \drivers\display\lcd
reg create key Mode150
reg set value name string "Glyn G-ET035009DH6"
reg set value msignal dword 2
reg set value width dword 70
reg set value height dword 53
reg set value contrastenable dword 0
reg set value contrastvalue dword 0
reg set value type dword 6
reg set value EarlyLCDVoltage dword 1
reg set value config dword 0x08000000
reg set value lcdclk dword 10
reg set value bpp dword 16
REM **********Vertical*************+
reg set value VSW dword 2
reg set value BFW dword 16
reg set value EFW dword 4
reg set value rows dword 240
reg set value LPP dword 240
REM **********Horizontal*************+
reg set value HSW dword 10
reg set value BLW dword 20
reg set value ELW dword 68
reg set value columns dword 320
reg set value PPL dword 320
reg set value EnableCursor dword 0
display mode set 150
REM Command required for new PicoCOM modules:
boot display on
REM

Display More

These settings proved to be valid using other PicoCOM2 modules on the same custom-made mainboard with the same display.

al12559 · Feb 8th 2011

After I wrote the Kernel V-1.16 to a PicoCOM2 module the display settings are set for a Hitachi display. Debug Output:

Quote

DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 150, Name Glyn G-ET035009DH6
DDGPE:Width: 320 Height: 240 Bpp: 16
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED

Actually I use a Glyn display. I apply the required settings using
ndcucfg -B"\FFSDISK\setiings.txt", issue a "reg save" and a "reboot" from ndcucfg.
After that Debug Output reports:

Quote

DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 120, Name Glyn G-ET035009DH6
DDGPE:Width: 320 Height: 240 Bpp: 16
DDGPE:GetLCDcontrast: read contrast value: 0x5f
DDGPE:GetLCDcontrast: dwDefaultContrast=0x0, contrast=0x5f
Backlight mode can't be read from registry. Defaulting it to enabled state
DDGPE:DispDrvrBacklightControl ON
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED

Display More

Display remains dark. Using "Windows CE Remote Zoom-In" (Visual Studio 2008 tools) I read out a normal display contents (Windows CE desktop), probably from the display buffer.
In another topic

Quote

http://www.forum.fs-net.de/viewtopic.php?f=26&t=2666

I read

Quote

Calling the command "boot display on" in NetDCU Config Utility makes the different. It was not necessary with the old modules but is required for the new ones.

(1) Would that be the solution for my case?
(2) What are "new", what are "old" modules? Can they be distinguished by their serial numbers on the top badge?

I cannot find this command in NDCUCFG Version:042
Is it documented anywhere?

Regards

AndrÃƒÂ© Lehmann

al12559 · Feb 8th 2011

How do I issue NDCUCFG commands from the DCUTermi window? From the debug output I see from
"NDCUCFG V: 041 started. Platform: PicoCOM2"
that NDCUCFG should be running on the remote system. But neither issuing a command nor transmitting a text file with NDCUCFG commands works.
If I connect to the serial debug output using DCUTermi and press "S" while starting PicoCOM, I have a ":>" cursor, but not a "!>" cursor.
The terminal program accepts EBoot commands such as "?" or "T".
In the "First steps" document it is stated

Quote

!>
If this command prompt appears in the terminal program you are
ready to pass commands to NDCUCFG utility. Otherwise something
went wrong. Please check various parameters described in chapter
1.2.

How do I change to this cursor? What may have gone wrong?

Regards

AndrÃƒÂ© Lehmann

Addendum:
I found out myself. I had to disable the serial debug output by calling "O" in the EBoot prompt. After reboot I now have the NDCUCFG prompt.

al12559 · Feb 4th 2011

Quote

Do the PicoCOMs also show these exceptions if running on our Starerkit?

Yes. The same two modules show exceptions while the same last one does not. Thus I would rule out my base board as being responsible for the failure state.
How do I set an identical clean initial state on a PicoCOM module?
Is it sufficient to use "NetDCU USB Loader" for writing NBoot, EBoot and kernel?
How do I secure an identical initial registry contents?

Can you provide me with a new adapter board to attach the Hitachi display (PicoCOM2_FirstSteps_eng.pdf, page 3, figure 2) to the starter kit? Due to frequent changing I broke the black lock at the connector.

How do I issue NDCUCFG commands from the DCUTermi window? From the debug output I see from
"NDCUCFG V: 041 started. Platform: PicoCOM2"
that NDCUCFG should be running on the remote system. But neither issueing a command nor transmitting a text file with NDCUCFG commands works.

al12559 · Feb 4th 2011

Quote

Does the exception still occure if removing USB cable?

This is the debug output when there is no USB connection:

Code

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Nov 23 2010 11:16:01
Microsoft Windows CE Bootloader for PICOCOM2 Built Dec 22 2010
Boot Loader, Version 1.7
NBoot, Version C220
32 MB Ram
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
Board Revision: 1.10
System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
+ReadKernelRegionFromNandFlash
Image Signature in Flash Memory found (dwSig=0x43454345)
TOC pointer=0x810373A0
ROMHDR (cTOC = 0x00f253a0) ---------------------
DLL First : 0x4001c001
DLL Last : 0x40a8c0a0
Physical First : 0x80112000
Physical Last : 0x81039284
Num Modules : 185
RAM Start : 0x81040000
RAM Free : 0x81058000
RAM End : 0x82012000
Num Copy Entries : 2
Copy Entries Offset : 0x80c22e64
Prof Symbol Length : 0x00000000
Prof Symbol Offset : 0x00000000
Num Files : 68
Kernel Flags : 0x00000000
FileSys RAM Percent : 0x20202020
Driver Glob Start : 0x00000000
Driver Glob Length : 0x00000000
CPU : 0x01c2
MiscFlags : 0x0002
Extensions : 0x80113140
Tracking Mem Start : 0x00000000
Tracking Mem Length : 0x00000000
Kernel (15516kB) read from flash disk started finished in 5090 milliseconds
Kernel read from NAND
INFO: OEMLaunch: Jumping to Physical Address 0x20113000h (Virtual Address 0x0h)...
Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 31 2010 at 15:28:51
PicoCOM2 V1.14 - Firmware Init
Build: Aug 6 2010/16:05:39
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x400b
OEMInit: SDRAM = 32 MB
DCache: 128 sets, 4 ways, 32 line size, 16384 size
ICache: 128 sets, 4 ways, 32 line size, 16384 size
OEM: Force clean boot.
OALTimerInit
OALKitlStart
Firmware Init Done.
OEM: Watchdog ENABLED
Handle Event:0xa00003, sysintr=0x10OEM: Not clearing storage
OEM: Not cleaning system hive
OEM: Not cleaning user profiles
OEM: Not cleaning system hive
PM-NETDCU: STARTED
NET: Version V1.5, ActiveKey = Comm\ETHNETA
USBFN: Version 1.2, ActiveKey = Drivers\Active\07
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
Exception 'Raised Exception' (-1): Thread-Id=01210002(pth=81ec5adc), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=021d0002(pprc=812e5a80) 'udevice.exe'
PC=c004fccc(k.coredll.dll+0x0002fccc) RA=801304c8(kernel.dll+0x000064c8) SP=d05ae924, BVA=00000000
Exception 'Raised Exception' (-1): Thread-Id=01210002(pth=81ec5adc), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=021d0002(pprc=812e5a80) 'udevice.exe'
PC=c003baec(k.coredll.dll+0x0001baec) RA=801304c8(kernel.dll+0x000064c8) SP=d05ae1d0, BVA=ffffffff
BCS: Version 1.0, ActiveKey = Drivers\Active\22
NI2C: Version 1.13, ActiveKey = Drivers\Active\23
SDHC:Version 1.2, ActiveKey = Drivers\Active\24
SDHC:Card state change detected!
DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 150, Name Glyn G-ET035009DH6
DDGPE:Width: 320 Height: 240 Bpp: 16
DDGPE:GetLCDcontrast: read contrast value: 0x5f
DDGPE:GetLCDcontrast: dwDefaultContrast=0x0, contrast=0x5f
Backlight mode can't be read from registry. Defaulting it to enabled state
DDGPE:DispDrvrBacklightControl ON
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED
NDCUCFG V: 041 started. Platform: PicoCOM2
CheckAutoStart: Version 1.4, LaunchNum = 100
CreateFile() failed -> ERROR COM1:

Display More

There is still nothing displayed.

Quote

Are you running the PicoCOM2 on the starterkit or on a custom baseboard?

On a custom baseboard. I have used the same type for months successfully. The other day one baseboard was damaged, so I had to use another one of the same type.

Quote

Have you tried to stablilze your power supply?

Not so easy because the custom baseboard is delivered 12V 2.5A from a mains adapter, and the PicoCOM supply voltage is converted on the custom baseboard.

How do I reset the contents of FFSDISK without repartitioning? I observe that settings such as the display mode remain unchanged after writing a new kernel to the module. Before that I always had to apply NDCUCFG commands to set the corrrect display parameters after updating the kernel.

Quote

I might not wonder if the display stays blank after the exceptions.

I compared three PicoCOMs on the same base board.
Two (PC1, PC2) show the stated exceptions, one (PC3) does not. The display remains dark in case of PC1, not for PC2 and PC3. In all modules the same display type is set.

How can I issue NDCUCFG commands from the DCUTermi window?

al12559 · Feb 4th 2011

I updated NBoot and EBoot. The exceptions remain:

Code

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Nov 23 2010 11:16:01
Microsoft Windows CE Bootloader for PICOCOM2 Built Dec 22 2010
Boot Loader, Version 1.7
NBoot, Version C220
32 MB Ram
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
Board Revision: 1.10
System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
+ReadKernelRegionFromNandFlash
Image Signature in Flash Memory found (dwSig=0x43454345)
TOC pointer=0x810373A0
ROMHDR (cTOC = 0x00f253a0) ---------------------
DLL First : 0x4001c001
DLL Last : 0x40a8c0a0
Physical First : 0x80112000
Physical Last : 0x81039284
Num Modules : 185
RAM Start : 0x81040000
RAM Free : 0x81058000
RAM End : 0x82012000
Num Copy Entries : 2
Copy Entries Offset : 0x80c22e64
Prof Symbol Length : 0x00000000
Prof Symbol Offset : 0x00000000
Num Files : 68
Kernel Flags : 0x00000000
FileSys RAM Percent : 0x20202020
Driver Glob Start : 0x00000000
Driver Glob Length : 0x00000000
CPU : 0x01c2
MiscFlags : 0x0002
Extensions : 0x80113140
Tracking Mem Start : 0x00000000
Tracking Mem Length : 0x00000000
Kernel (15516kB) read from flash disk started finished in 5137 milliseconds
Kernel read from NAND
INFO: OEMLaunch: Jumping to Physical Address 0x20113000h (Virtual Address 0x0h)...
Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 31 2010 at 15:28:51
PicoCOM2 V1.14 - Firmware Init
Build: Aug 6 2010/16:05:39
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x400b
OEMInit: SDRAM = 32 MB
DCache: 128 sets, 4 ways, 32 line size, 16384 size
ICache: 128 sets, 4 ways, 32 line size, 16384 size
OEM: Force clean boot.
OALTimerInit
OALKitlStart
Firmware Init Done.
OEM: Watchdog ENABLED
Handle Event:0xa00003, sysintr=0x10OEM: Not clearing storage
OEM: Not cleaning system hive
OEM: Not cleaning user profiles
OEM: Not cleaning system hive
PM-NETDCU: STARTED
NET: Version V1.5, ActiveKey = Comm\ETHNETA
USBFN: Version 1.2, ActiveKey = Drivers\Active\07
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
USBFN:C_USB_DEVICE::ThreadRun: : Attach Detected
Exception 'Raised Exception' (-1): Thread-Id=01210002(pth=81ec5adc), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=021d0002(pprc=812e5a80) 'udevice.exe'
PC=c004fccc(k.coredll.dll+0x0002fccc) RA=801304c8(kernel.dll+0x000064c8) SP=d05ae924, BVA=00000000
Exception 'Raised Exception' (-1): Thread-Id=01210002(pth=81ec5adc), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=021d0002(pprc=812e5a80) 'udevice.exe'
PC=c003baec(k.coredll.dll+0x0001baec) RA=801304c8(kernel.dll+0x000064c8) SP=d05ae1d0, BVA=ffffffff
BCS: Version 1.0, ActiveKey = Drivers\Active\22
NI2C: Version 1.13, ActiveKey = Drivers\Active\23
SDHC:Version 1.2, ActiveKey = Drivers\Active\24
SDHC:Card state change detected!
DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 150, Name Glyn G-ET035009DH6
DDGPE:Width: 320 Height: 240 Bpp: 16
DDGPE:GetLCDcontrast: read contrast value: 0x5f
DDGPE:GetLCDcontrast: dwDefaultContrast=0x0, contrast=0x5f
Backlight mode can't be read from registry. Defaulting it to enabled state
DDGPE:DispDrvrBacklightControl ON
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED
NDCUCFG V: 041 started. Platform: PicoCOM2
CheckAutoStart: Version 1.4, LaunchNum = 100
CreateFile() failed -> ERROR COM1:

Display More

If I use another PicoCOM2 module on the same mainboard (i.e. the same power supply), I receive the following debug output without exceptions:

Code

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built May 4 2010 19:05:37
Microsoft Windows CE Bootloader for PICOCOM2 Built May 18 2010
Boot Loader, Version 1.5
NBoot, Version C215
32 MB Ram
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
Board Revision: 1.10
System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
+ReadKernelRegionFromNandFlash
Image Signature in Flash Memory found (dwSig=0x43454345)
TOC pointer=0x810373A0
ROMHDR (cTOC = 0x00f253a0) ---------------------
DLL First : 0x4001c001
DLL Last : 0x40a8c0a0
Physical First : 0x80112000
Physical Last : 0x81039284
Num Modules : 185
RAM Start : 0x81040000
RAM Free : 0x81058000
RAM End : 0x82012000
Num Copy Entries : 2
Copy Entries Offset : 0x80c22e64
Prof Symbol Length : 0x00000000
Prof Symbol Offset : 0x00000000
Num Files : 68
Kernel Flags : 0x00000000
FileSys RAM Percent : 0x20202020
Driver Glob Start : 0x00000000
Driver Glob Length : 0x00000000
CPU : 0x01c2
MiscFlags : 0x0002
Extensions : 0x80113140
Tracking Mem Start : 0x00000000
Tracking Mem Length : 0x00000000
Kernel (15516kB) read from flash disk started finished in 5843 milliseconds
Kernel read from NAND
INFO: OEMLaunch: Jumping to Physical Address 0x20113000h (Virtual Address 0x0h)...
Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 31 2010 at 15:28:51
PicoCOM2 V1.14 - Firmware Init
Build: Aug 6 2010/16:05:39
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x400b
OEMInit: SDRAM = 32 MB
DCache: 128 sets, 4 ways, 32 line size, 16384 size
ICache: 128 sets, 4 ways, 32 line size, 16384 size
OEM: Force clean boot.
OALTimerInit
OALKitlStart
Firmware Init Done.
OEM: Watchdog ENABLED
WARNING: Can't use RTC - Using default system time
Handle Event:0xa00003, sysintr=0x10OEM: Not clearing storage
OEM: Not cleaning system hive
OEM: Not cleaning user profiles
OEM: Not cleaning system hive
PM-NETDCU: STARTED
NET: Version V1.5, ActiveKey = Comm\ETHNETA
USBFN: Version 1.2, ActiveKey = Drivers\Active\10
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
COM: Version 1.8, ActiveKey = Drivers\Active\12
CID: Version 2.1, ActiveKey = Drivers\Active\16
BCS: Version 1.0, ActiveKey = Drivers\Active\28
NI2C: Version 1.13, ActiveKey = Drivers\Active\29
WAV: Version 2.3, ActiveKey = Drivers\Active\30
SDHC:Version 1.2, ActiveKey = Drivers\Active\31
SDHC:Card state change detected!
DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 150, Name Glyn G-ET035009DH6
DDGPE:Width: 320 Height: 240 Bpp: 16
DDGPE:GetLCDcontrast: read contrast value: 0x5f
DDGPE:GetLCDcontrast: dwDefaultContrast=0x0, contrast=0x5f
Backlight mode can't be read from registry. Defaulting it to enabled state
DDGPE:DispDrvrBacklightControl ON
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED
NDCUCFG V: 041 started. Platform: PicoCOM2
CheckAutoStart: Version 1.4, LaunchNum = 100
CreateFile() failed -> ERROR COM1:
NET: cable attached
USBFN:C_USB_DEVICE::ThreadRun: : Attach Detected

Display More

By the way, the attached display does not show anything though "Windows CE Remote Zoom-in" (a tool from Visual Studio 2008) reads a correct screen shot from the display buffer. What could be the reason for this?
(The display module is OK as seen with another PicoCOM2 module on the same mainboard.)

al12559 · Feb 3rd 2011

Hello,

after setting up a new system I receive the following debug output while booting.
As my application does not run properly I want to ask for explanation of the "exception" messages:

Code

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Dec 12 2008 16:31:35
Microsoft Windows CE Bootloader for PICOCOM2 Built Dec 15 2008
Boot Loader, Version 1.0
NBoot, Version C215
32 MB Ram
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
Board Revision: 1.10
System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
+ReadKernelRegionFromNandFlash
Image Signature in Flash Memory found (dwSig=0x43454345)
TOC pointer=0x810385B0
ROMHDR (cTOC = 0x00f265b0) ---------------------
DLL First : 0x4001c001
DLL Last : 0x40a8c0a0
Physical First : 0x80112000
Physical Last : 0x8103a494
Num Modules : 185
RAM Start : 0x81040000
RAM Free : 0x81058000
RAM End : 0x82012000
Num Copy Entries : 2
Copy Entries Offset : 0x808f8e88
Prof Symbol Length : 0x00000000
Prof Symbol Offset : 0x00000000
Num Files : 68
Kernel Flags : 0x00000000
FileSys RAM Percent : 0x20202020
Driver Glob Start : 0x00000000
Driver Glob Length : 0x00000000
CPU : 0x01c2
MiscFlags : 0x0002
Extensions : 0x80113140
Tracking Mem Start : 0x00000000
Tracking Mem Length : 0x00000000
Kernel read from flash disk started finished in 4876 milliseconds
Kernel read from NAND
INFO: OEMLaunch: Jumping to Physical Address 0x20113000h (Virtual Address 0x0h)...
Windows CE Kernel for ARM (Thumb Enabled) Built on Aug 4 2010 at 14:23:58
PicoCOM2 V1.16 - Firmware Init
Build: Jan 18 2011/09:27:33
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0x400b
OEMInit: SDRAM = 32 MB
DCache: 128 sets, 4 ways, 32 line size, 16384 size
ICache: 128 sets, 4 ways, 32 line size, 16384 size
OEM: Force clean boot.
OALTimerInit
OALKitlStart
Firmware Init Done.
OEM: Watchdog ENABLED
Handle Event:0xa00003, sysintr=0x10OEM: Not clearing storage
OEM: Not cleaning system hive
OEM: Not cleaning user profiles
OEM: Not cleaning system hive
PM-NETDCU: STARTED
NET: Version V1.5, ActiveKey = Comm\ETHNETA
USBFN: Version 1.2, ActiveKey = Drivers\Active\07
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETUUID
Exception 'Raised Exception' (-1): Thread-Id=01210002(pth=81ec7adc), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=021d0002(pprc=812e6a80) 'udevice.exe'
PC=c004fd34(k.coredll.dll+0x0002fd34) RA=80130520(kernel.dll+0x00006520) SP=d05ae924, BVA=00000000
Exception 'Raised Exception' (-1): Thread-Id=01210002(pth=81ec7adc), Proc-Id=00400002(pprc=81052308) 'NK.EXE', VM-active=021d0002(pprc=812e6a80) 'udevice.exe'
PC=c003bb54(k.coredll.dll+0x0001bb54) RA=80130520(kernel.dll+0x00006520) SP=d05ae1d0, BVA=ffffffff
BCS: Version 1.0, ActiveKey = Drivers\Active\22
NI2C: Version 1.13, ActiveKey = Drivers\Active\23
SDHC:Version 1.2, ActiveKey = Drivers\Active\24
SDHC:Card state change detected!
DDGPE:Read registry settings from Drivers\Display\LCD
Display-Mode: 150, Name Glyn G-ET035009DH6
DDGPE:Width: 320 Height: 240 Bpp: 16
DDGPE:InitializeDisplayHardware Complete
EnableTouchscreen PASSED
NDCUCFG V: 042 started. Platform: PicoCOM2
CheckAutoStart: Version 1.4, LaunchNum = 100
CreateFile() failed -> ERROR COM1:
USBFN:C_USB_DEVICE::ThreadRun: : Attach Detected

Display More

al12559 · Jan 25th 2011

Which driver do you mean: USBFN (pc2_usbfn.dll) ?
Disabling this driver results in losing the ActiveSync connection capability which I must retain.

al12559 · Jan 25th 2011

Can you comment on the following:
Issuing the call

Code

b_success = DeviceIoControl(hDIO, IOCTL_DIO_REQUEST_IRQ, &dw_IRQ, sizeof(DWORD), NULL, 0, NULL, NULL);

results in the debug output

Code

+OALIntrRequestSysIntr IRQ (254) already used by SYSINTR (18)

Issuing the call

Code

b_success = DeviceIoControl(hDIO, IOCTL_DIO_RELEASE_IRQ, &dw_IRQ, sizeof(DWORD), NULL, 0, NULL, NULL ) ;

results in the debug output

Code

+OEMInterruptDisable(24), irq: 254
-OEMInterruptDisable

Situation remains that

Code

b_success = DeviceIoControl(hDIO, IOCTL_DIO_WAIT_IRQ, &s_IRQStat, sizeof(s_IRQStat), &dw_WaitState, sizeof(dw_WaitState), NULL, NULL) ;

always returns

Code

dw_WaitState != WAIT_OBJECT_0

which means TimeOut though the line monitored for interrupts receives suitable state changes as seen by alternatively polling.

All calls to DeviceIoControl() return non-zero.

Thank you in advance for any hints

al12559 · Jan 24th 2011

Hello everybody,

may I kindly ask to receive an answer?
I suppose, at least the last two little questions can be answered with little effort.

As this is the only means of communication (no phone service) I need your assistance.
I cannot go on with my application before interrupt functionality is working.

Thank you in advance

Posts by al12559

ActiveSync disconnects when I2C is active

Changing display type => no display?

Changing display type => no display?

Changing display type => no display?

Changing display type => no display?

Debug output while booting shows exceptions

Debug output while booting shows exceptions

Registry reset after updating

Registry reset after updating

Changing display type => no display?

Changing display type => no display?

Changing display type => no display?

Remote NDCUCFG - how to execute commands on PicoCOM from PC?

Debug output while booting shows exceptions

Debug output while booting shows exceptions

Debug output while booting shows exceptions

Debug output while booting shows exceptions

Digital IO using Interrupts

Digital IO using Interrupts

Digital IO using Interrupts