It sounds like you have a UART exposed to pin header that doesn't have the RS232 transceiver. I suggest that you try the MinComm sample in the IoT Core Samples: https://github.com/ms-iot/samples to get a list of ports and test the ports.
Direct connect the IoT Device via RS-232C
I have an IoT device with only Tx/Rx 2 pins and hope to get a connection via notebook PC PCH uart2 Tx/Rx 2 pins. I enabled the serial port 2 on BIOS, and I found the address 0x2f8 device here. Without any DCD and DSR pins connected. I can not get regular operation on Windows 10.
- I tried to Add legacy hardware on Device Manager.
- Select the Communication Port.
- Change the Resources (I/O Range 02F8 - 02FF) and IRQ 0x000003.
Unfortunately, I got an abnormal device after steps 1~3 rebooted my netbook PC. Device status "This device cannot start. (Code10). A device which does not exist was specified.
I don't know about DCD and DSR issues or others? Have any chance to communicate with this device via Tx/Rx RS232C?
Or do I need to create a new serial driver for this device?
Hi @Carson Wu ,
We have not received a response from you. Did the reply could help you? If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. By doing so, it will benefit all community members who are having this similar issue. Your contribution is highly appreciated.
Sign in to comment
Sort by: Most helpful
Thanks for your suggestion. That's right. I forgot the RS232 transceiver. I may need to connect a TTL for RS232. will check your suggestion MinComm code first or connect an external transceiver.
There are a couple of ways to access the COM ports. There is the SerialPort Class and the Windows.Devices.SerialCommunication namesspace. For .NET 6 and UWP, RHPROXY has to be in the firmware. All though this is an older article it still applies to IoT Enterprise: https://www.annabooks.com/Articles/Articles_IoT10Core/Windows-10-IoT-microIO-Requirements-on-IA-Rev1.6.pdf. I don't know if you are trying to access the COM port with .NET Framework or .NET6.
Sign in to comment