how to build a win ce5 serial port program

[nicolas]

Yes I saw.
What error are you seing when you try to open the com port ?

[IDrenth]

I get a error like COM0 can not be opened and COM1 can not be opened.If I select COM2 or COM3 no error .

If use putty and found out that he is sending on baud rate 115200 this message.
"+SL_GetStatus 0x38BF0"


maybe windows ce is ussing the port

[nicolas]

I dont think COM0 is even valid. I may be wrong, need to check the PB, but I thought only COM1, 2, 3 were available.

If COM1 cannot be opened it may be because windows has used it for debugging. IE. KITL.
I have had very strange results with different WinCE images and KITL.
In some, even thought COM1 is being used for debugging I can open the port and use it - at the same time, which under normal circumstances is illogical. In other images, I cannot open the COM1 because debugging is enabled.

Load up putty or whichever terminal client you have, and boot up the image.
If you get alot of data (text) when winCE is booting, then its most likely that the debugging is on, and has taken over COM1, in which you would need to use a new image (or make your own).

[IDrenth]

I see this on my screen of putty.

+---------------------------------------------+
| S3C2440A USB Downloader ver R0.03 2004 Jan |
+---------------------------------------------+
USB: IN_ENDPOINT:1 OUT_ENDPOINT:3
FORMAT: <ADDR(DATA):4>+<SIZE(n+10):4>+<DATA:n>+<CS:2>
NOTE: Power off/on or press the reset button for 1 sec
in order to get a valid USB device address.

NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
Could not found stored vivi parameters. Use default vivi parameters.
Press Return to start the LINUX/Wince now, any other key for vivi
Clear the free memory .............................................................

Read wince image from flash:
Sector addr on NAND: 0x520
TotalSector: 0xd276
LoadAddress: 0x30200000
JumpAddr: 0x30201000


and more

[nicolas]

Further down...whats the last few lines you see ?

[IDrenth]

VIVI version 0.1.4 (root@capcross) (gcc version 2.95.3 20010315 (release)) #0.1. 4 Wed Oct 29 06:24:02 CST 2008
MMU table base address = 0x33DFC000
Succeed memory mapping.
DIVN_UPLL0
MPLLVal [M:7fh,P:2h,S:1h]
CLKDIVN:5h


+---------------------------------------------+
| S3C2440A USB Downloader ver R0.03 2004 Jan |
+---------------------------------------------+
USB: IN_ENDPOINT:1 OUT_ENDPOINT:3
FORMAT: <ADDR(DATA):4>+<SIZE(n+10):4>+<DATA:n>+<CS:2>
NOTE: Power off/on or press the reset button for 1 sec
in order to get a valid USB device address.

NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
Could not found stored vivi parameters. Use default vivi parameters.
Press Return to start the LINUX/Wince now, any other key for vivi
Clear the free memory .......................................................... ...

Read wince image from flash:
Sector addr on NAND: 0x520
TotalSector: 0xd276
LoadAddress: 0x30200000
JumpAddr: 0x30201000
..........................
Run wince, JumpAddr = 0x30201000
Clear the memory unused ..
áWindows CE Kernel for ARM (Thumb Enabled) Built on Feb 8 2007 at 23:36:51
ProcessorType=0920 Revision=0
sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 8c2013bc

Windows CE Firmware Init
INFO: Initializing system interrupts...
INFO: Initializing system clock(s)...
INFO: Initializing driver globals area...
SDMMC config set rGPGCON: fd96fdba
OEMInit Done...
Sp=ffffc7cc
NandFlash FMD_Init
NandFlash FMD_Init Done
PWR: Process Attach
>PWR_Init(602ED68)
HW_Init : GetProcAddress
HW_Init : ERROR_INVALID_PARAMETER
HW_Init : InitializeCriticalSection
HW_Init : VirtualAlloc
HW_Init : pPWR->State
HW_Init : HW_InitRegisters
HW_Init : CreateEvent
HW_Init : InterruptInitialize
HW_Init : CreateThread
HW_Init : CeSetThreadPriority
HW_Init OOCS: 0x00
HW_Init INT1: 0x00
HW_Init INT2: 0x00
HW_Init INT3: 0x00
HW_Init : Donw
<PWR_Init:0x37a70
>PWR_Open(0x37a70, 0x0, 0x3)
<PWR_Open:1
>PWR_IOControl(0x321000, 0x0, 0, 0x60377b8)
<PWR_IOControl:1
>PWR_Open(0x37a70, 0x0, 0x3)
<PWR_Open:2
PWR_Close(0x37a70)
384 clock
SetBaudRate -> 960031780 (0 opens)
Data Abort: Thread=8fa60b48 Proc=8e026160 'device.exe'
AKY=00000025 PC=029928bc(ser2440.dll+0x000028bc) RA=029928a8(ser2440.dll+0x000028a8) BVA=06000000 FSR=00000007
OEMSetAlarmTime: Year: 2010, Month: 3, Day: 14, Hour: 2, Minute: 0, second: 0 rcnr=0h
RasEntry '`USB Socket Default' Created
SL_Close


this is the total

[nicolas]

Yeah as I suspected. the CE image has taken over the serial port for bugging of the kernel. KITL.
You will need to find an image with it disabled, or make your own.

Unless someone can figure out a way to 'share' the serial port with the debugger.

[IDrenth]

Do you know how to make a image ?

and were did you see it in the terminal that it is in use ??

[nicolas]

I know it is in use because of the output.
That output is the debugger output.

To create your own image, check the manual pdf.
You will need to download Platform Builder Trial and the WinCE BSP for the board., from the ftp.
Follow the manual instructions to install and build an image.
I cant provide an image as I have the Mini24404 and not the qq2440.

Alternatively, as i noted before, there may another way to open the port such that it is shared with the debugger.
I dont know how (or if its even possible)

[IDrenth]

how can I switch off the debug mode so I can use it for communication in PB5