COM 1 Not Working??

crmann
I have been unable to communicate to my GPS module using a terminal
application using COM-1. I can open the other COM ports (2 and 3) but COM-1
 behaves as if it is being used (cannot open COM port). I realize COM-1 is
initialized by the bootloader but I do not think that it would stay
initialized and in use even after CE boots. Maybe I am wrong? I do not have
the TTL converter for my other COM ports but I know for certain my GPS
module works perfectly with my PC using Putty. Any insight is appreciated!

crmann
Also note I have my CE image built as a "Ship Build" meaning ALL debug
strings and functions are disabled.

andromeda
try com2 and test

Shanty
Hi,
COM1 is working for me in WinCE
I am using it to communicate with
a program in the PC as the network 
driver seems to have issues.
Unless some other program in WinCE
has already opened it up you should
not be getting the problem.

COM2 and COM3 ofcourse are working too as
I am using COM2 to communicate with another
3.3V serial device.

Errol
crmann, did you enable KITL on COM0 in the Options.H?

Shanty, the network drivers have been fixed in the BPS on the wiki(as far
as i know), see:
http://code.google.com/p/friendlyarm/wiki/EnglishBSP

Thanks,
Errol

crmann
Thanks for the feedback - I'll examine the state of KITL in options.h!

crmann
I checked options.h and KITL was disabled. I would think this would be the
correct configuration? KITL is used for debug so I would think it would
interfere with a device on COM1. I didn't have a whole lot of time to work
on it this weekend (build + download is almost an hour!) and didn't try
building an image with it enabled. After I re-read what KITL was for I
assumed it was best to leave it disabled.

Parsha
if you don't use main serial cable of mini2440,I should say to you that in
COM1's Port of board Rx and Tx Pin is displaced(that means Tx is Rx and Rx
is Tx)...