Serial Terminal For Windows Ce
Hi, I am running a Vortex 6350rde with an ICOP (thats the manufacturer of the board) BSP. I have created a windows CE headless image (NO VIDEO, KEYBOARD or MOUSE) that has all of the functions I need. Communication to the device is through Serial Ports and Network. The problem is that I want to disable the DEBUG serial port. I use COM1 in my target application and the DEBUG output is interfering. The OS is directing debug info and printf statements out COM1 which I am presently monitoring using a terminal.
You can use any terminal emulation application to view messages sent from the serial port of a standard development board (SDB) or hardware platform. Use the messages. Serial port windows ce free download. ScriptCommunicator / serial terminal ScriptCommunicator is a scriptable cross-platform data terminal which supports serial port.
I saw that in the registry there was a setting HKLM DRIVERS CONSOLE OutPutto set to -1. So I can set that to 0 and the printf statements will no longer be directed to COM1. That still leaves the debug statements. By following the 'sources.' Understanding the build system is very important when working with CE. In this specific case you would start in OALEXE, this sources. File will link to OALLIB.
Check the sources file of OALLIB and see which libraries it links to. One of them will be debugserial or something similar. Do a search on your platform tree first to see which sources file produces debugserial.lib. If nothing, check your PLATFORM COMMON SOC folders and finally PLATFORM COMMON.
Serial Terminal For Windows 10 Free
Follow the breadcrumbs. You can find more information about understanding the build system on my blog (link below). Good luck, Michel Verhagen, eMVP Check out my blog: GuruCE Microsoft Embedded Partner Consultancy, training and development services. Paul, Thanks for responding.
Yes it is basically something the Vendor should be able to help with. Unfortunately, they arent always that much help. It is a RETAIL build. The only setting I have checked in the Platform Builder settings is Enable Full Kernel Mode. My understanding about the DEBUG SERIAL PORT is that some file implements OEMInitDebugSerial, OEMWriteDebugString, OEMWriteDebugByte, OEMReadDebugByte. Since these functions are called before the OS really starts they use direct PORTREAD/PORTWRITE to send rcv data to the COM Port.
There is no way to disable these functions except to recode them??? The question is which file are the real functions in?? I already tried 4 debug.c files to no avail. I have just found another one in WINCE PLATFORM COMMON SRC X86 COMMON OTHER debug.c I just disabled the functions in that file and am rebuilding the OS. Will post the results Thanks Ken. By following the 'sources.'
Understanding the build system is very important when working with CE. In this specific case you would start in OALEXE, this sources.
File will link to OALLIB. Check the sources file of OALLIB and see which libraries it links to.
Cygwin
One of them will be debugserial or something similar. Do a search on your platform tree first to see which sources file produces debugserial.lib.
Terminal For Windows Download
If nothing, check your PLATFORM COMMON SOC folders and finally PLATFORM COMMON. Follow the breadcrumbs. You can find more information about understanding the build system on my blog (link below). Good luck, Michel Verhagen, eMVP Check out my blog: GuruCE Microsoft Embedded Partner Consultancy, training and development services.