After more than three weeks - are there any updates? I need to find a reliable way to do this.
Posts by al12559
-
-
Hello,
QuoteCan you adjust keyboard layout using taskbar, save registry and then reboot. Are the settings persit?
No.
(1) If I change using the taskbar icon from DE to EN, save the registry, reboot, I still find DE as current setting.
(2) If I use Settings => Control panel => Regional and language settings => Input Language to switch from DE to EN, the setting is persistent.
(3) The method to changeinto
, save registry and reboot still does not work.
-
Hello,
Quoteare you able to save any entry under HKCU?
Yes, I am, in HKCU as well as in HKLM..
QuoteDo you use latest kernel?
I use kernel V-1.03. I had tried kernel V-1.04 and V-1.05 which led to serious malfunctions so that I returned to the last known good version. I will give V-1.07 a try.
BTW: What does the prefix "XIP" in "XIPNKPC4_CORE_CF35_120416" mean? Can it be used on PicoCOM4 just as the previous versions?Regards
André Lehmann
-
May I hope to get an answer before we switch back from Daylight Saving Time on Oct 28?
-
Hello all,
I want to switch between the keyboard layouts for German (0x407) and English (0x409) from my application.
Which registry setting has to be modified?
I tried the NetDCU approach given in http://www.forum.fs-net.de/vie…111&hilit=keyboard+layout but it does not seem to work with PicoCOM4:
To switch from English to German, I replaced HKCU\Keyboard Layout\Preload\Default="00000409" by "00000407" and saved registry. After reboot I found the value to be "00000409" again, and the current layout was still English.Thank you in advance for a timely response.
André Lehmann
-
Quote
Did you try InternetExplorer or Command Shell for example, same behavior?
I tried the Windows Explorer and did not observe the FTP server disconnecting. So it works for now.
On the other hand, FileZilla is a tool well-known for stability and adherence to standards. it remains unclear why it receives the disconnection message (it never actively disconnects except on user request). -
I successfully installed the FTP server
Quoteon PicoCOM4.
Now I wonder what the FTPD related registry parameters mean.
Especially I want to prevent the FTP server from disconnecting automatically which it obviously does shortly after a file transfer.
Is there a setting to do this?
On the PC side I use the FTP client FileZilla. -
When I inspect settings at Start=>Settings=>Control Panel=>Date/Time on my PicoCOM4,
time zone is set to "(GMT+01:00)",
The option "Automatically adjust clock for daylight saving" is checked (both settings are permanent and survive a reboot).
Date and time are set correctly as well, a RTC battery is inserted..But there was no change after Mar 25.
What could have prevented it? -
Quote
We will release a new Pro image in short term.
As four months have passed since this statement:
Any news on this item? -
As the card is mounted deep inside an instrument I hesitated to first check the card .
I was fooled by the startup statementwhich I took for an indication that the driver recognised an inserted card.
Can you comment on this message? It appears in both cases: card inserted or not inserted.
The SD card turned out to have become defective (during normal operation without any unload/load operation). -
I use the kernel 1.03 (Nov 8, 2011). A SD card is attached to my device controlled by PicoCOM4.
Until last week the SD card was working fine. Now - without any modification - it cannot be accessed as "SDCard" anymore.
On the contrary, the startup output states as it used to do beforeDo you have any idea?
Thank you in advance -
How can I install both PicoCOM2 and PicoCOM4 SDKs on one computer using VisualStudio 2008?
Depending on the project I need one or the other.If I try to install PicoCOM2 after PicoCOM4 SDK, I only have the option to modify, repair or remove PicoCOM4 SDK.
After I installed PicoCOM4 SDK I cannot open VS2008 projects that use the PicoCOM2 SDK anymore.
Consequently I cannot replace the PicoCOM2 SDK dependency with one on PicoCOM4 SDK.What steps do you propose?
-
Quote
We will release a new Pro image in short term.
As more than 2 months have passed since the release of NKPC4_PRO_CF35_111123.zip:
Can you give an estimate when a kernel showing the mouse cursor will be available? -
Thank you.
I would recommend to include this information in a <readme.txt> file accompanying the <picocom4_sdk_v101.msi> file as it appears to be a systematic error.How can I install both PicoCOM2 and PicoCOM4 SDKs on one computer?
Depending on the project I need one or the other.If I try to install PicoCOM2 after PicoCOM4 SDK, I only have the option to modify, repair or remove PicoCOM4 SDK.
After I installed PicoCOM4 SDK I cannot open VS2008 projects that use the PicoCOM2 SDK. Consequently I cannot replace the PicoCOM2 SDK dependency with one on PicoCOM4 SDK. -
Hello,
after I downloaded <picocom4_sdk_v101.msi> I tried to install it in VS2008 on Windows7(32).
Installation failed with two messages:and
After that installation is rolled back.
How can I overcome this?Greetings
-
Even after setting the recommended value PenUpDebounce to 0 I observe the same behaviour:
- Precision of touch panel coordinate recognition is much too low.
- The corresponding mouse cursor [I use one of the PicoCOM4 kernels that DOES support a mouse cursor] jumps to positions far away from the recently pressed touch panel coordinates.
I set the touchpanel driver parameter Debug to 4 and go a list of the available settings.
What do the following undocumented settings mean, and what are valid values?
My current settings areCode- TCHMDD: Debug = 0x4.
- TCHPDD: MinCalibrationPointCount = 0x4 (Default)
- TCHPDD: SamplePeriodLowHns = 0x30d40 (Default)
- TCHPDD: SamplePeriodHighHns = 0x186a0 (Default)
- TCHPDD: DeltaXCoordTolerance = 0xa
- TCHPDD: DeltaYCoordTolerance = 0xa
- TCHPDD: AdcReadHoldoffHns = 0x7d0 (Default)
- TCHPDD: PenDownHoldoffHns = 0xc350 (Default)
- TCHPDD: TouchSamples = 0x7 (Default)
- TCHPDD: Debounce = 0x0 (Default)
- TCHPDD: DebounceJitter = 0x3 (Default)
- TCHPDD: AutoCalib = 0x0 (Default)
- TCHPDD: MinMove = 0xa (Default)
- TCHPDD: MaxMove = 0x32 (Default)
- TCHPDD: ADCConvFreq = 0xf4240 (Default)
- TCHPDD: PenUpDebounce = 0x0
- TCHPDD: ToggleLED = 0x0 (Default)
A touch panel "double-click" is never intended or evaluated in my application.
-
With the current kernel version V1.03, 111108 the mouse cursor is still missing.
What could be the reason for it?
Under which conditions did you observe the problem had been solved?
Can you see anything wrong in my serial debug output on booting?Code- Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Oct 4 2011 17:14:18
- Microsoft Windows CE Bootloader for PicoCOM4 Built Oct 4 2011
- Portions copyright (c) 2009 F&S Elektronik Systeme GmbH
- Boot Loader, Version 1.2
- NBoot, Version C423
- HW-Watchdog: ON
- System ready!
- Preparing for download...
- Press >S< to step into monitor...
- AUTO BOOT enabled
- Kernel (30329kB) read from flash disk started finished in 1 milliseconds
- INFO: OEMLaunch: Jumping to Physical Address 0x3014239Ch (Virtual Address 0x0h)...
- Windows CE Kernel for ARM (Thumb Enabled) Built on Dec 17 2010 at 07:41:08
- PicoCOM4 V1.03 - Firmware Init
- Copyright (c) 2010 F&S Elektronik Systeme GmbH
- Build: Nov 8 2011/14:25:38
- INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
- HW-WATCHDOG: ENABLED
- FMD: NAND ID:0xec76 --> Samsung: 512MBit (64MB)
- FMD: IsBlockBad - Page #: 0x0
- FMD: IsBlockBad - Page #: 0x20
- FMD: Block 0 to 20 are locked for boot loader
- -OEMInit
- OALIoCtlHalInitRTC: Year: 2006, Month: 1, Day: 1, Hour: 12, Minute: 0, second: 0
- Time returned from OEMGetRealTime: Year: 2011, Month: 11, Day: 15, Hour: 7, Minute: 32, second: 30
- Drivers\Builtin\Serial1 - OFF
- RestartReason: Software
- FMD: NAND ID:0xec76 --> Samsung: 512MBit (64MB)
- FMD: IsBlockBad - Page #: 0x0
- FMD: IsBlockBad - Page #: 0x20
- FMD: Block 0 to 20 are locked for boot loader
- FMD: FMD_OEMIoControl: unrecognized IOCTL (0x71c24).
- OEM: Not cleaning system hive
- OEM: Not cleaning user profiles
- OEM: Not cleaning system hive
- DIO-Layout: <V1.20
- PM-NETDCU: STARTED
- OHCI: Version 1.2, ActiveKey = Drivers\BuiltIn\OHCI
- I2C: Version 2.5, ActiveKey = Drivers\Active\09
- PSS: Version 1.0, ActiveKey = Drivers\Active\10
- VDE: Version 1.0, ActiveKey = Drivers\Active\11
- +OALIoCtlHalGetHWEntropy
- NDIS:Version 1.0
- WAV: Version 1.0, ActiveKey = Drivers\Active\15
- CID: Version 2.6, ActiveKey = Drivers\Active\16
- HSMMC: Version 1.0, ActiveKey = Drivers\Active\17
- FSKBDHID: Version 1.0, ActiveKey = Drivers\Active\21
- UART: Version 1.2, Key = Drivers\Active\33
- DEBUG: UART0 SYSINTR : 64
- BCS: Version 1.1, ActiveKey = Drivers\Active\34
- NI2C: Version 3.0, ActiveKey = Drivers\Active\36
- DIO: Version 2.2, ActiveKey = Drivers\Active\37
- USBFN: Version 1.0, ActiveKey = Drivers\Active\39
- USBFN: USB Serial Function Class Enabled : Serial_Class
- USBFN: HW_USBClocks::D0
- LCD: Version 1.3, ActiveKey =
- LCD: Read registry settings from Drivers\Display\LCD
- Display-Mode: 2, Name Hitachi TX09
- Width: 240 Height: 320 Bpp: 16
- TCHPDD: Version 1.3, Key = HARDWARE\DEVICEMAP\TOUCH
- TCHKEY: Version 1.0, Key = HARDWARE\DEVICEMAP\TOUCH\VirtualKeys
- USBFN: HIGH Speed
- NDCUCFG V: 045 started. Platform: PicoCOM4
- USBFN: HIGH Speed
- CheckAutoStart: Version 1.5, LaunchNum = 100
- NDCUCFG Open COM1: at 38400 Baud
- CreateFile() failed -> ERROR COM1:
-
Quote
Cursor now also is working in PRO kernel image.
Unfortunately I cannot confirm.
I installed the new kernel image on PicoCOM4 (Starter Kit mainboard), verified the EnableCursor=1 value. But situation is the same as before:
No mouse cursor, but left-click or right-click at the invisible cursor position yields the desired action. -
(As I do not know whether I will finally get an answer in an older thread "How to enable mouse cursor on PicoCOM4?" I feel forced to open a new thread.)
When I use the kernel image NKPC4_PRO_CF35_111006, a mouse cursor will never be displayed, regardless of the setting inThis behavior is shown on both the starter kit and my custom mainboard. On the other hand, this setting has the correct effect on both the mainboards, when I use another current PicoCOM4 kernel image.
As I have to use a HTML browser it is important for me to get the said kernel version up and running. And at least as long as you develop it is no fun to lack a mouse cursor - not speaking of system setting dialog windows that do not fit into small screens and cannot be operated without a mouse.
Did you look into this issue already?
-
Can you confirm that the kernel NKPC4_PRO_CF35_111006.bin does not display a mouse cursor at all while the other versions permit to show/hide the cursor? I observed these differences using two display types (Hitachi and Glyn) quite reproducibly.