Hello,
I was working with PicoCOM4 with Linux but now I must to switch to Windows CE again. I didn't do the first change from Windows to Linux so I don't know how to switch again. I downloaded the last version of NBoot and Eboot (Windows CE) but I don't know how to transmitte the files to PicoCOM or if first I must to erase the Linux from the PicoCOM and how tot do it.
Could you help me, please?
Hello,
for install the kernel use NetDCUUSBLoader from http://www.fs-net.de/download/bin/->Tools (refer readme/howto in installdir).
To change to Windows CE you need to boot into nboot. To do this you need to press 's' in DCUTermi serial connection and power the board.
Then press 'E' to erase the NAND Flash.
Press 'd' to download EBoot. ('Transmit Binary File ...' in DCUTermi).
Then save it with 'f' and reboot.
Now you must enter the MAC address (the serial number of the PicoCOM, starts with 000551). It is on a sticker on the PicoCOM.
If only 6 digits are on the sticker (instead of 12) start with 000551 and add the other digits.
Press 'du' to start the USB download. Load the kernel file with NetDCUUsbloader and transmit it to the PicoCOM.
After the flash is formatted and the kernel is written to the flash you have a PicoCOM with WindowsCE.
I've followed your steps fs-supportDB, I've installed the Eboot successfully and and defined the MAC address, but when I transmit the kernel image (I tried XIPNK_CORE_CF35_121029.bin and XIPNK_CORE_CF2_121029.bin, because I'm not sure about the diference betwen the diferent the kernels avaliable on the webside) it appears this error on DCUTermi:
##1 files tranfered
INFO: Write image at 0x80139000 size 0x018a6c64 to NAND Flash
Create partition for boot section ...
Success
Create partition for kernel section ...
Success
Create partition for FFSDISK section ...
Success
WriteRegionsToNandFlash
INFO: [0] Found chain information (pChainInfo=0x8014FD04 Extensions=0x3).
[Dump XIP Chain Summary]
- pvAddr: 0x80739000
- dwMaxLength : 16384
- usOrder : 0x0
- usFlags : 0x0
- reserved : 0x0
Writing single region/multi-region update, dwBINFSPartLength: 25848932
INFO: BP_OpenPartition: dwBINFSPartLength =0x18A6C64).
INFO: Part_StartSector=0x140, Part_TotalSectors=0x0000A001
ERROR: WriteRegionsToNandFlash: BINFS partition is to small.
AUTO-BOOT enabled
ERROR: Flash write failed
HALT Reason=0xFFFFFFF4
ERROR: FlashWrite failed
ERROR !!!!
Disable AUTO BOOT
Reboot system and correct bootloader settings
SpinForever...
Could you help me again, please?
Thank you for your help!
The partition for the kernel is too small, you have to change it.
Press 'P' in EBoot, then set size for OS-Image larger than kernel size (e.g. for XIPNKPC4_CORE_CF2_121029.bin set it to at least 20).
I would set it to 25 or 32 if you don't need the space in the FFSDISK, so you can install lager images without repartitioning the flash.
Just press Enter to set the other values to default.
Wait until the flash is partitioned and start the download again.
Hello,
with the partition done and kernel installed, PicoCOM initiates Windows CE and appears the Windows enviroment on the touchscreen, but in DCUTermi appears the error: "CreateFile() failed -> ERROR COM1:" and the serial comunication is blocked. I habilitate the NDCUCFG utility but it's not ready (I'm following First Steps Documentation, page 24), I supose because of this error. I also uploaded Nboot to a newer version but the problem it's still there.
DCUTermi messages booting de PicoCOM4 are this:
Microsoft Windows CE Ethernet Bootloader Common Library Version 1.1 Built Feb 16 2012 15:13:12
Microsoft Windows CE Bootloader for PicoCOM4 Built Feb 16 2012
Portions copyright (c) 2009 F&S Elektronik Systeme GmbH
Boot Loader, Version 1.6
NBoot, Version C425
HW-Watchdog: ON
System ready!
Preparing for download...
Press >S< to step into monitor...
AUTO BOOT enabled
Kernel (2547kB) read from flash disk started finished in 1 milliseconds
INFO: OEMLaunch: Jumping to Physical Address 0x301422CCh (Virtual Address 0x0h)...
Windows CE Kernel for ARM (Thumb Enabled) Built on Sep 14 2011 at 17:32:03
PicoCOM4 V1.11 - Firmware Init
Copyright (c) 2010 F&S Elektronik Systeme GmbH
Build: Oct 29 2012/12:44:30
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: 2006, Month: 1, Day: 1, Hour: 12, Minute: 38, second: 37
Drivers\Builtin\Serial1 - OFF
RestartReason: Reset
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).
FSPART: FS partition driver loaded
OEM: Not cleaning system hive
OEM: Not cleaning user profiles
OEM: Not cleaning system hive
DIO-Layout: >=V1.20
PM-NETDCU: STARTED
+OALIoCtlHalGetHWEntropy
OHCI: Version 1.2, ActiveKey = Drivers\BuiltIn\OHCI
I2C: Version 2.5, ActiveKey = Drivers\Active\10
PSS: Version 1.1, ActiveKey = Drivers\Active\11
VDE: Version 1.0, ActiveKey = Drivers\Active\12
NDIS:Version 1.0
CID: Version 2.8, ActiveKey = Drivers\Active\17
WAV: Version 1.0, ActiveKey = Drivers\Active\18
HSMMC: Initializing the HSMMC Host ControllerHSMMC: Version 1.2, ActiveKey = Drivers\Active\19
UART: Version 1.2, Key = Drivers\Active\32
DEBUG: UART0 SYSINTR : 64
BCS: Version 1.2, ActiveKey = Drivers\Active\33
NI2C: Version 3.0, ActiveKey = Drivers\Active\34
DIO: Version 2.4, ActiveKey = Drivers\Active\35
USBFN: Version 1.0, ActiveKey = Drivers\Active\37
USBFN: USB Serial Function Class Enabled : Serial_Class
USBFN: HW_USBClocks::D0
LCD: Version 1.7, 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
CheckAutoStart: Version 1.5, LaunchNum = 100
NDCUCFG V 54 started. Platform: PicoCOM4
NDCUCFG Open COM1: at 38400 Baud
CreateFile() failed -> ERROR COM1:
Thanks.
Hello,
Quote"CreateFile() failed -> ERROR COM1:"
This is not a real error. "Ndcucfg" and serial debug line using the same port. So if debug output is enabled "ndcucfg" can't start.
Resolution:
1. Disable serial debug output (bototloader command "O")
OR
2. Redirect "ndcucfg" (Registry: HKLM\system\ndcucfg)
NDCUCFG and debug output are on the same COM port.
You can enable/disable the debug output in EBoot with 'O'
in NDCUCFG you can do iot with 'serial debug on' and 'serial debug off'
