tutorials:common:customization:wireless_serial_port
Differences
This shows you the differences between two versions of the page.
|
tutorials:common:customization:wireless_serial_port [2013/11/09 08:01] soloforce [Prerequisite] |
tutorials:common:customization:wireless_serial_port [2013/12/23 14:50] (current) |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| </WRAP></WRAP> | </WRAP></WRAP> | ||
| ===== Abstract ===== | ===== Abstract ===== | ||
| - | Sometimes, the serial port cable between Cubieboard and PC is annoying, because it may mess up your desktop. In this tutorial, two similar approaches are presented to guide you to get rid of the annoying cable. Serial-bluetooth module is quite common and cheap these days, and it is really a good choise to make a wirless serial port connection to PC. | + | Sometimes, the serial port cable between Cubieboard and PC is annoying, because it may mess up your desktop. In this tutorial, two similar approaches are presented to guide you to get rid of the annoying cable, and create a wireless interactive console. In fact, wireless console is quite usefull especially there is no network connection between Cubieboard and PC, or there is no SSH server installed on the Cubieboard. Serial-bluetooth module is quite common and cheap these days, and it is really a good choise to make a wirless serial port connection to PC. |
| - | ===== Method one: ttyS0 directed to serial-bluetooth module ===== | + | ===== Method one: UART0(ttyS0) directed to serial-bluetooth module ===== |
| ==== Prerequisite ==== | ==== Prerequisite ==== | ||
| === Hardware === | === Hardware === | ||
| + | * This method is only available for Cubieboard1 & Cubieboard2, While Cubieboard3(Cubietruck) does not expand out the UART-VCC pin so that unable to power the serial-bluetooth module. | ||
| * Cubieboard side: A serial-bluetooth module, to be attached to Cubieboard's TTL serial port. Notice that, this module should be **3.3v powered**, because Cubieboard's TTL VCC is 3.3v. | * Cubieboard side: A serial-bluetooth module, to be attached to Cubieboard's TTL serial port. Notice that, this module should be **3.3v powered**, because Cubieboard's TTL VCC is 3.3v. | ||
| {{ :tutorials:common:customization:p31108-130501.jpg?400 |}} | {{ :tutorials:common:customization:p31108-130501.jpg?400 |}} | ||
| - | * PC side: Another serial-bluetooth module, combined with a TTL-to-USB serial module, **5.0v** powered, to be plugged into PC's USB port. If your PC has a built-in bluetooth, these two modules could be omitted, but you have to create the bluetooth serial port(rfcomm port) for communicating on your own, will be discussed later of this tutorial. | + | * PC side: Another serial-bluetooth module combined with a TTL-to-USB serial module(**5.0v** VCC), to be plugged into PC's USB port. If your PC has a built-in bluetooth, these two modules could be omitted, but you have to create the bluetooth serial port(rfcomm port) for communicating on your own, will be discussed later of this tutorial. |
| {{ :tutorials:common:customization:p31108-130420.jpg?400 |}} | {{ :tutorials:common:customization:p31108-130420.jpg?400 |}} | ||
| * Some connecting wires and 2.54mm connectors | * Some connecting wires and 2.54mm connectors | ||
| === Software === | === Software === | ||
| - | * Cubieboard side: ttyS0 should be configured as an interactive console, which means the following configurations should be done | + | Cubieboard side: ttyS0 should be configured as an interactive console, which means the following configurations should be done |
| - | - //**/boot/uEnv.txt**// should add extra boot arguments like **//bootargs=console=ttyS0,115200//** | + | * //**/boot/uEnv.txt**// should add extra boot arguments like |
| - | - //**/etc/inittab**// should add a line like **//T0:2345:respawn:/sbin/getty -L ttyS0 115200 vt100//** | + | <file>bootargs=console=ttyS0,115200 console=tty0</file> |
| - | * PC side: Serial console clients like minicom or gtkterm(recommended) | + | * //**/etc/inittab**// should add a line like |
| + | <file>T0:2345:respawn:/sbin/getty -L ttyS0 115200 vt100</file> | ||
| + | |||
| + | PC side: Serial console clients like minicom or gtkterm(recommended) | ||
| ==== Configuration & Connection ==== | ==== Configuration & Connection ==== | ||
| * Both serial-bluetooth modules should be configured to baud rate at **115200**, and pre-paired. | * Both serial-bluetooth modules should be configured to baud rate at **115200**, and pre-paired. | ||
| - | * Cubieboard's TTL serial port(ttyS0) should be connected to the **3.3v serial-bluetooth** | + | * The **3.3v serial-bluetooth** should be conected to Cubieboard's TTL serial port(aka. ttyS0 in Linux) |
| - | * The **5.5v serial-bluetooth** module should be attached to the TTL-to-USB module, then plug into the PC USB port | + | * The **5.5v serial-bluetooth** module combined with the TTL-to-USB module, should be plugged into the PC's USB port |
| * Open gtkterm(or minicom) port **/dev/ttyUSB0** with parameters **115200-8-n-1** | * Open gtkterm(or minicom) port **/dev/ttyUSB0** with parameters **115200-8-n-1** | ||
| Line 37: | Line 41: | ||
| | | ||
| ===== Method two: usb serial console to serial-bluetooth module ===== | ===== Method two: usb serial console to serial-bluetooth module ===== | ||
| - | When installed in a case, like [[http://docs.cubieboard.org/_detail/addons/y.png?id=addons|this]], Cubieboard's TTL interface would be blocked and can no longer be plugged in the TTL to USB cable. In this case, we could exploit the USB port to make wireless serial port possible. This method is a bit different from method one previously mentioned, especially on the Cubieboard's side. | + | When installed in a case, like [[http://docs.cubieboard.org/_detail/addons/y.png?id=addons|this]], Cubieboard's TTL interface would be blocked and can no longer be plugged in the TTL to USB cable. In this case, we could exploit the USB port to make wireless serial port possible. This method is a bit different from method one previously mentioned, especially on the Cubieboard's side. What's more, this method remains the chance of choosing either TTL serial port or USB serial port for wireless console. In a word, this is a safe and flexible method. |
| ==== Prerequisite ==== | ==== Prerequisite ==== | ||
| ===hardware=== | ===hardware=== | ||
| - | * Cubieboard side: A serial-bluetooth module, combined with a TTL-to-USB serial module, **5.0v** powered, to be plugged into Cubieboard's USB port. | + | * Cubieboard side: A serial-bluetooth module, combined with a TTL-to-USB serial module (**5.0v** VCC), to be plugged into Cubieboard's USB port. |
| * PC side: The same as method one. | * PC side: The same as method one. | ||
| ===software=== | ===software=== | ||
| - | Cubieboard's kernel configuration should be done, enable below configs (press 'Y' to select) | + | Cubieboard's kernel configuration should be done, enable below fetures(press 'Y' to select) |
| - //**Device Drivers->USB support**// | - //**Device Drivers->USB support**// | ||
| - //**USB Serial Converter support**// | - //**USB Serial Converter support**// | ||
| Line 56: | Line 60: | ||
| Like configurations mentioned in method one, the follwing alteration should be done. | Like configurations mentioned in method one, the follwing alteration should be done. | ||
| - | * /boot/uEnv.txt should add extra boot arguments like **//bootargs=console=ttyUSB0,115200//** | + | * //**/boot/uEnv.txt**// should add extra boot arguments like |
| - | * /etc/inittab should add a line like **//T0:2345:respawn:/sbin/getty -L ttyUSB0 115200 vt100//** | + | <file> |
| + | bootargs=console=ttyS0,115200 console=ttyUSB0,115200 console=tty0 | ||
| + | </file> | ||
| + | * //**/etc/inittab**// should add lines like | ||
| + | <file> | ||
| + | T0:2345:respawn:/sbin/getty -L ttyS0 115200 vt100 | ||
| + | T1:2345:respawn:/sbin/getty -L ttyUSB0 115200 vt100 | ||
| + | </file> | ||
| + | :!: That above bootargs & two lines will make both TTL serial port(ttyS0) and USB serial port(ttyUSB0) interactive consoles. | ||
| ==== Connection ==== | ==== Connection ==== | ||
| Both Cubieboard and PC 's USB port will be used for connection. | Both Cubieboard and PC 's USB port will be used for connection. | ||
| Line 101: | Line 113: | ||
| | | ||
| ===== Conclusion ===== | ===== Conclusion ===== | ||
| - | * method one is simpler, but the TTL port is the only choice for connection. | + | * method one is simpler, but the UART TTL port is the only choice for connection. |
| * method two needs more hardware, and the boot message such as U-Boot message could never show up, because the USB serial console won't work until the kernel boots up. The advantage is USB connection is much easier and could be expanded by USB hubs. | * method two needs more hardware, and the boot message such as U-Boot message could never show up, because the USB serial console won't work until the kernel boots up. The advantage is USB connection is much easier and could be expanded by USB hubs. | ||
tutorials/common/customization/wireless_serial_port.1383955281.txt.gz · Last modified: 2013/12/23 14:50 (external edit)
Page Tools
