PineNote Development/UART - Revision history

Mweigand: Restructure the PineNote UART-dongle page: show stock uart picture and usage first and move the custom dongle section down

2024-12-31T08:56:37Z

Restructure the PineNote UART-dongle page: show stock uart picture and usage first and move the custom dongle section down

@@ Line 1: / Line 1: @@
-[[File:Pinenote-uart-dongle.jpeg|thumb|Basic non-stock PineNote UART dongle]]
+[[File:Pn_uart_connection.jpg|thumb|Batch 1+2 UART dongle in use]]
 This page contains information on creating and using a [https://en.wikipedia.org/wiki/Universal_asynchronous_receiver-transmitter UART] dongle for the [[PineNote]].
@@ Line 31: / Line 31: @@
 </gallery>
-== Creating a dongle ==
+== Using the dongle ==
 A typical self-built PineNote UART dongle design has the following components:
@@ Line 116: / Line 157: @@
 Experience shows that RX/TX-TX/RX connections will have the PineNote face down while connected, while RX/RX-TX/TX connections will put the PineNote face up.
-== Using the dongle ==
+=== Troubleshooting Custom UART dongles ===
 If you don't see any text in your terminal as the PineNote boots, or the text is garbled, try the following:
 * Ensure your GND, RX/TX, and CC jump wires are connected to the correct pins on both the USB-UART adapter and the USB-C breakout board
 If you can see text but are having trouble sending <code>ctrl+c</code> to the PineNote during boot:
 * Double-check your Y-shaped pull-up resistor cable; if this isn't working properly you'll probably be able to read text but not send text
-== USB passthrough ==
+== USB passthrough (only custom-built dongles) ==
 If your USB-C breakout board has a passthrough/intercept design, you can connect to your PineNote over USB and UART at the same time.
@@ Line 159: / Line 172: @@
 It's important to connect directly from USB-A, without any intermediate USB-C components.
 Note that connecting a live USB cable to your USB-C breakout board in this way dramatically increases the danger of frying your PineNote with a short, so you should only do this if all connectors are safely wrapped in electrical tape.
 [[Category:PineNote]]

Dsimic: /* Stock dongle */ Ditto

2024-11-15T20:23:29Z

Stock dongle: Ditto

← Older revision		Revision as of 20:23, 15 November 2024
Line 24:		Line 24:
	{{Warning\|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}		{{Warning\|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}

	The stock UART dongle included with the PineNote is a simple device ~~plugging~~ directly into the PineNote's USB-C port. The dongle exposes a female USB-C port, which the user ~~uses~~ to get access to the serial console UART. This design unfortunately ruled out passthrough USB connections, where the user connects to the PineNote via UART and USB simultaneously. The dongle is not currently available separately for purchase.		The stock UART dongle included with the PineNote is a simple device that plugs directly into the PineNote's USB-C port. The dongle exposes a female USB-C port, which the user connects to their host computer to get access to the serial console UART. This design unfortunately ruled out passthrough USB connections, where the user connects to the PineNote via UART and USB simultaneously. The dongle is not currently available separately for purchase.

	<gallery>		<gallery>

Dsimic: /* Stock dongle */ Wording improvements

2024-11-15T20:22:40Z

Stock dongle: Wording improvements

← Older revision		Revision as of 20:22, 15 November 2024
Line 24:		Line 24:
	{{Warning\|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}		{{Warning\|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}

	The stock UART dongle included with the PineNote ~~was~~ a simple device plugging directly into the PineNote's USB-C port.		The stock UART dongle included with the PineNote is a simple device plugging directly into the PineNote's USB-C port. The dongle exposes a female USB-C port, which the user uses to get access to the serial console UART. This design unfortunately ruled out passthrough USB connections, where the user connects to the PineNote via UART and USB simultaneously. The dongle is not currently available separately for purchase.
	The dongle ~~exposed~~ a female USB-C port, which the user ~~plugged into~~ to get UART ~~access~~.
	This design unfortunately ruled out passthrough USB connections, where the user connects to the PineNote via UART and USB simultaneously.
	The dongle is not currently available for purchase.

	<gallery>		<gallery>

Dsimic: /* Stock dongle */ Describe the presence of the USB UART adapter

2024-11-15T20:21:01Z

Stock dongle: Describe the presence of the USB UART adapter

← Older revision		Revision as of 20:21, 15 November 2024
Line 22:		Line 22:

	== Stock dongle ==		== Stock dongle ==
			{{Warning\|The second PineNote batch, which started shipping during the first half of November 2024, is the last batch that has the USB UART dongle included in the box.}}

	The stock UART dongle included with the PineNote was a simple device plugging directly into the PineNote's USB-C port.		The stock UART dongle included with the PineNote was a simple device plugging directly into the PineNote's USB-C port.

Ahelwer: /* Using the dongle */ fixed link

2023-10-14T21:17:02Z

Using the dongle: fixed link

← Older revision		Revision as of 21:17, 14 October 2023
Line 128:		Line 128:
	# Identify the USB-UART adapter in your <code>/dev</code> directory by running <code>ls /dev</code> with it plugged in, unplugging it, then again running <code>ls /dev</code> and seeing what changed; it is likely to be called <code>/dev/ttyUSB0</code>		# Identify the USB-UART adapter in your <code>/dev</code> directory by running <code>ls /dev</code> with it plugged in, unplugging it, then again running <code>ls /dev</code> and seeing what changed; it is likely to be called <code>/dev/ttyUSB0</code>
	# Check your permissions; run <code>ls -l /dev/ttyUSB0</code> to see which groups have access to the dongle (probably <code>dialout</code> or <code>uucp</code>), and add your user to that group; remember you need to log out before group changes take effect		# Check your permissions; run <code>ls -l /dev/ttyUSB0</code> to see which groups have access to the dongle (probably <code>dialout</code> or <code>uucp</code>), and add your user to that group; remember you need to log out before group changes take effect
	# Install [https://~~www~~.~~gnu~~.org/~~software/screen~~/ minicom] (or [https://askubuntu.com/q/40959 some other option], but the instructions below are written for <code>minicom</code>)		# Install [https://salsa.debian.org/minicom-team/minicom minicom] (or [https://askubuntu.com/q/40959 some other option], but the instructions below are written for <code>minicom</code>)
	# In a terminal window, run <code>minicom -D /dev/ttyUSB0 -b 1500000</code> or run <code>minicom --setup</code> to specify these settings by default		# In a terminal window, run <code>minicom -D /dev/ttyUSB0 -b 1500000</code> or run <code>minicom --setup</code> to specify these settings by default

Ahelwer: /* Creating a dongle */ added note about debug accessory mode

2023-10-14T19:48:24Z

Creating a dongle: added note about debug accessory mode

← Older revision		Revision as of 19:48, 14 October 2023
Line 56:		Line 56:
	The first (TX) is used for transmitting data and the second (RX) is used for receiving data, from the perspective of the PineNote.		The first (TX) is used for transmitting data and the second (RX) is used for receiving data, from the perspective of the PineNote.
	Also note the configuration channel pins labeled <code>TYPEC_CC1</code> for A5 and <code>TYPEC_CC2</code> for B5.		Also note the configuration channel pins labeled <code>TYPEC_CC1</code> for A5 and <code>TYPEC_CC2</code> for B5.
	~~These pins are used to signal to the PineNote that a UART dongle is present.~~
	The diagram shows they must be connected to a 3.3V source in parallel, mediated by resistors.		The diagram shows they must be connected to a 3.3V source in parallel, mediated by resistors.
			Per the USB-C standard, when these pins are pulled high this indicates the device should enter [https://en.wikipedia.org/wiki/USB-C#Debug_Accessory_Mode Debug Accessory Mode]; connecting them to a voltage source & limiting the current with [https://www.electronics-tutorials.ws/logic/pull-up-resistor.html pull-up resistors] accomplishes this.
	The schematic indicates 10,000 Ohm resistors, but community member Visti Andresen (talpadk) experimented and found 1,000 Ohm resistors work better.		The schematic indicates 10,000 Ohm resistors, but community member Visti Andresen (talpadk) experimented and found 1,000 Ohm resistors work better.
	Our mission is to wire up pins from a USB-UART adapter to a USB-C breakout board following these requirements.		Our mission is to wire up pins from a USB-UART adapter to a USB-C breakout board following these requirements.
Line 84:		Line 84:
	The solitary leg will connect to a 3.3V source on your USB-UART adapter.		The solitary leg will connect to a 3.3V source on your USB-UART adapter.
	The twin arms will connect to the configuration channel pins on your USB-C breakout board.		The twin arms will connect to the configuration channel pins on your USB-C breakout board.
	~~This setup is called using pull~~-~~up resistors~~, ~~and you can read~~ a ~~nice introduction to their purpose~~ [https://www.electronics-tutorials.ws/logic/pull-up-resistor.html ~~here~~].		Per the USB-C standard, when these pins are pulled high this indicates the device should enter [https://en.wikipedia.org/wiki/USB-C#Debug_Accessory_Mode Debug Accessory Mode]; connecting them to a voltage source & limiting the current with [https://www.electronics-tutorials.ws/logic/pull-up-resistor.html pull-up resistors] accomplishes this.

	For this project you'll need:		For this project you'll need:

Ahelwer: /* Using the dongle */

2023-10-14T19:30:31Z

Using the dongle

← Older revision		Revision as of 19:30, 14 October 2023
Line 124:		Line 124:
	# Plug the USB-C breakout board into the USB-C port on the bottom of your PineNote; the orientation matters, so try both and remember which one works		# Plug the USB-C breakout board into the USB-C port on the bottom of your PineNote; the orientation matters, so try both and remember which one works

	Once the hardware is connected, we need ~~to get~~ some program on your computer to communicate over that connection with 1500000 (1.5 million) bps, 8 data bits, 1 stop bit, no parity and no flow control.		Once the hardware is connected, we need some program on your computer to communicate over that connection with 1500000 (1.5 million) bps, 8 data bits, 1 stop bit, no parity and no flow control.
	Here's how you do that:		Here's how you do that:
	# Identify the USB-UART adapter in your <code>/dev</code> directory by running <code>ls /dev</code> with it plugged in, unplugging it, then again running <code>ls /dev</code> and seeing what changed; it is likely to be called <code>/dev/ttyUSB0</code>		# Identify the USB-UART adapter in your <code>/dev</code> directory by running <code>ls /dev</code> with it plugged in, unplugging it, then again running <code>ls /dev</code> and seeing what changed; it is likely to be called <code>/dev/ttyUSB0</code>

Ahelwer: /* Using the dongle */

2023-10-14T19:29:38Z

Using the dongle

← Older revision		Revision as of 19:29, 14 October 2023
Line 124:		Line 124:
	# Plug the USB-C breakout board into the USB-C port on the bottom of your PineNote; the orientation matters, so try both and remember which one works		# Plug the USB-C breakout board into the USB-C port on the bottom of your PineNote; the orientation matters, so try both and remember which one works

	Once the hardware is connected, we need to get some program to communicate over ~~UART~~ with 1500000 (1.5 million) bps, 8 data bits, 1 stop bit, no parity and no flow control.		Once the hardware is connected, we need to get some program on your computer to communicate over that connection with 1500000 (1.5 million) bps, 8 data bits, 1 stop bit, no parity and no flow control.
	Here's how you do that:		Here's how you do that:
	# Identify the USB-UART adapter in your <code>/dev</code> directory by running <code>ls /dev</code> with it plugged in, unplugging it, then again running <code>ls /dev</code> and seeing what changed; it is likely to be called <code>/dev/ttyUSB0</code>		# Identify the USB-UART adapter in your <code>/dev</code> directory by running <code>ls /dev</code> with it plugged in, unplugging it, then again running <code>ls /dev</code> and seeing what changed; it is likely to be called <code>/dev/ttyUSB0</code>

Ahelwer: /* Using the dongle */

2023-10-14T19:29:07Z

Using the dongle

← Older revision		Revision as of 19:29, 14 October 2023
Line 124:		Line 124:
	# Plug the USB-C breakout board into the USB-C port on the bottom of your PineNote; the orientation matters, so try both and remember which one works		# Plug the USB-C breakout board into the USB-C port on the bottom of your PineNote; the orientation matters, so try both and remember which one works

	Once the hardware is connected, ~~set up your computer~~'s ~~software as follows~~:		Once the hardware is connected, we need to get some program to communicate over UART with 1500000 (1.5 million) bps, 8 data bits, 1 stop bit, no parity and no flow control.
			Here's how you do that:
	# Identify the USB-UART adapter in your <code>/dev</code> directory by running <code>ls /dev</code> with it plugged in, unplugging it, then again running <code>ls /dev</code> and seeing what changed; it is likely to be called <code>/dev/ttyUSB0</code>		# Identify the USB-UART adapter in your <code>/dev</code> directory by running <code>ls /dev</code> with it plugged in, unplugging it, then again running <code>ls /dev</code> and seeing what changed; it is likely to be called <code>/dev/ttyUSB0</code>
	# Check your permissions; run <code>ls -l /dev/ttyUSB0</code> to see which groups have access to the dongle (probably <code>dialout</code> or <code>uucp</code>), and add your user to that group; remember you need to log out before group changes take effect		# Check your permissions; run <code>ls -l /dev/ttyUSB0</code> to see which groups have access to the dongle (probably <code>dialout</code> or <code>uucp</code>), and add your user to that group; remember you need to log out before group changes take effect

Ahelwer: /* Troubleshooting */ added note about data settings in UART

2023-10-14T14:07:53Z

Troubleshooting: added note about data settings in UART

← Older revision		Revision as of 14:07, 14 October 2023
Line 146:		Line 146:
	* Connect your USB-C breakout board to your PineNote in the opposite orientation		* Connect your USB-C breakout board to your PineNote in the opposite orientation
	* Run <code>minicom</code> as sudo in case your user doesn't have appropriate permissions		* Run <code>minicom</code> as sudo in case your user doesn't have appropriate permissions
	* Ensure you are setting the baud rate ~~in the <code>screen</code> command~~ to 1500000 (1.5 million)		* Ensure you are setting the baud rate to 1500000 (1.5 million), and (less importantly because these are probably used by default) 8 data bits, 1 stop bit, no parity and no flow control

	If you can see text but are having trouble sending <code>ctrl+c</code> to the PineNote during boot:		If you can see text but are having trouble sending <code>ctrl+c</code> to the PineNote during boot: