Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

COM1, COM2 - which is which (USB/TTL, RS232)


  • Please log in to reply
2 replies to this topic

#1 SteveS

SteveS

    Member

  • Members
  • PipPip
  • 21 posts

Posted 22 August 2012 - 08:48 AM

Hi. I'm pretty sure this isn't a new question, but I couldn't see a suitable answer, so I'm asking anew. I have a number of different Netduino models (vanilla, Plus, Mini). Since there are both TTL level and RS232 level Tx/Rx pairs, I assume these map TX0/RX0 = COM1, DTx/DRx = COM2. Firstly, do I have these the right way around or not? Secondly, does the transport selection change the port assignments? Thirdly, am I right in thinking that when debugging, the transport selected means the relevant port is not available? Finally, can the transport be identified from within the CLR in some way (in other words, can an app determine which the debugging port is)? I'm wanting to interface to some serial hardware which, like the Netduino, has both 232 and TTL levels (although there's only one UART, there's a MAX232, solder-pad selectable). Since I have spare digital I/O, it occurred to me to hack the solder pads so I can software switch the mode. Power-cycling the device isn't an issue, since I'm using another pin to do just that :) SteveS

#2 Nevyn

Nevyn

    Advanced Member

  • Members
  • PipPipPip
  • 1072 posts
  • LocationNorth Yorkshire, UK

Posted 22 August 2012 - 12:07 PM

Since there are both TTL level and RS232 level Tx/Rx pairs, I assume these map TX0/RX0 = COM1, DTx/DRx = COM2.
Firstly, do I have these the right way around or not?

The pinout cards can be found in the Wiki, if it's not listed as RS232 then it's a TTL level. The pinout for the Plus and the Classic are the same.

Secondly, does the transport selection change the port assignments?

No, the pin assignments remain the same.

Thirdly, am I right in thinking that when debugging, the transport selected means the relevant port is not available?

Correct.

Finally, can the transport be identified from within the CLR in some way (in other words, can an app determine which the debugging port is)?

To be honest I do not know the answer to this one.

Regards,
Mark

To be or not to be = 0xFF

 

Blogging about Netduino, .NET, STM8S and STM32 and generally waffling on about life

Follow @nevynuk on Twitter


#3 SteveS

SteveS

    Member

  • Members
  • PipPip
  • 21 posts

Posted 22 August 2012 - 01:10 PM

Doh! I have the pinout PDFs printed out and on a cork-board! Shame I didn't look more closely. (I do have an excuse - my advanced years mean I wear varifocals, and unless I squint and sit very close, I can't read them... Only the Mini has direct connection support for RS232 levels, so that just leaves my last query, every thing else is sorted. Thanks. SteveS




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.