RPI-CONSOLE

Raspberry PI Console Card - Features

• Console port lets you talk to your Raspberry Pi over USB without a keyboard/mouse/monitor or Ethernet connection.
  • 115200 baud
  • Real FTDI chip (FT230XS)
• USB Mini-B connector
  • Mounted on the bottom of the card (See also our Micro USB version)
• Jumper selectable - power the Pi from your computer's USB port
  • Newer Pi cards may take too much power
• Transmit/receive LEDs
• (3) Pi Connector options - extender allows daughtercards to be added on top
  • 26-pin extender connector works with Model A and Model B Pis
  • 40-pin extender connector works with Model A+, Model B+ Pis and the new Pi 2
  • 26-pin non-extender connector works with all Model Pis

Driver

• Finding your COM port can be a hassle in Windows. Here's how we find the port in Window 8.1
  • Run Device Manager
  • Expand the Ports (COM & LPT)
  • USB Serial Port is the RPI-Console card (COM5 in this instance, your mileage may vary)

Right click on the COM line at Properties to show that the part is an FTDI part and the driver is working properly

Set the baud rate to 115,200 baud, 8 data bits, 1 stop bit

Here are the driver details

Prototype Qualification Tests Tested on a Raspberry Pi Model A+ Able to power the Raspberry Pi Model A+ Able to monitor the boot sequence of a Raspberry Pi Model A+

Factory Acceptance Tests

Arduino Uno with Sensor Shield

Set 2 communications jumpers to COM (not the I2C position below)

Custom wired RASPI-PLUS-GVS-CFG bare board

• Card is connected to act as a Raspberry Pi emulator
  • Install 20x2 male header going up on board to board connector at top of the board
  • Install the TXS0108EWPR 3.3V<>5V Voltage Translator at U2
  • Install F1 (5V fuse)
  • Install 3.3V regulator at C2 position

• Wire the Vreg
  • VReg pin 1 goes to ground side of C2
  • VReg pin 2 goes to +3.3V side of C2
  • Jumper tab to VReg pin 2
  • Wire VReg pin 3 to V5-8 pin 2 (+5V)
• Add 47 uF cap from IO16-2 (+5V) and IO16-1 (GND)
• Install 330 Ohm resistor at R4
• Install 3mm LED at W jumper (J22-1 to J22-2) position (Cathode of LED to pin 1 of J22)
• Add wire from UART connector pin 3 to V3-1 pin (TXD on CFG card) (Serial out from Pi)
• Add wire from UART connector pin 4 to V3-2 pin (RXD on CFG card) (Serial in to Pi)
• Install 2x3 header at V5-1/V5-2 position
  • V5-1 (pin 1 = GND, pin 2 = +5V, pin 3 = TxD - Serial out from the Arduino)
  • V5-2 (pin 1 = GND, pin 2 = +5V, pin 3 = RxD - Serial in to the Arduino)

Wire Arduino UNO to custom board

• Wire V5-1 header pin S (pin 3) to Arduino Shield communications connector pin 3 (TX)
• Wire V5-2 header pin S (pin 3) to Arduino Shield communications connector pin 4 (RX)
• Wire V5-1 header pin GND (pin 1) to Arduino GND pin
• Wire V5-1 header pin +5V (pin 2) to Arduino +5V power

Alternate - Wire GVSDuino to custom board

• Wire V5-1 header pin S (pin 3) to GVSDuino pin 3 (TX)
• Wire V5-2 header pin S (pin 3) to GVSDuino pin 4 (RX)
• Wire V5-1 header pin GND (pin 1) to Arduino GND pin
• Wire V5-1 header pin +5V (pin 2) to Arduino +5V power

Test Software

• Poll for receive character
• When character is received, echo back character
• Loop forever
• Code on GitHub

Test Procedure

• Test setup as above
• Test setup powered down
• Install UUT (RPI-Console card being tested)
• Disconnect USB cable to Arduino (not used for power)
• Install P1 jumper on UUT (power the test station from the RPI-CONSOLE)
• Connect USB cable from Test Computer (laptop) to UUT
• Boards should power up
• Look in Device manager to make sure COM port was added
• Run putty on Test Computer (laptop)
  • Select COM port in putty
  • 9600, n, 8, 1
  • No handshake
• Hit reset on Arduino Shield or attached to GVSDuino
• Verify the message comes back

The quick brown fox jumped over the lazy dog
0123456789
asdfghjkl
Hit keys to test

• Type and verify that the character comes back
• Disconnect USB to RPI-Console

Delete Extra Ports on a Windows machine

• Windows assigns new ports and keeps old ports.
• We tested over a hundred cards and ended up with a lot of unused serial ports.
• If you have a lot of serial ports that you no longer use, you can return them to the pool for future use.

From this webpage.

• Open the Command Prompt as administrator and start the Device Manager from the same command prompt.

1. Right-click “Command Prompt” in Accessories and choose “Run as Administrator”
2. Enter “set devmgr_show_nonpresent_devices=1″ – without the quotes obviously
3. Enter “start devmgmt.msc”
4. In the box that opens, select “Show hidden devices” in the ‘view’ menu.

Now if you expand the section on COM ports, all the COM ports that have ever been created will be displayed, the non present ones being in grey. You can uninstall away anything that you don’t want (right click, select uninstall).

Specs

• 26-pin stacking connector
• 40-pin stacking connector

External links

• [https://learn.adafruit.com/adafruits-raspberry-pi-lesson-5-using-a-console-cable/test-and-configure Adafruit tutorial
• NOOBS without a display
• How COM Ports Are Allocated On Driver Installation

Troubleshooting

Raspberry Pi 3 problem described below (with solution):

With the release of the Raspberry Pi 3 the original hardware UART from the Broadcom processor 
has been reassigned to the Bluetooth chipset and the UART output on the GPIO pins now uses a mini-uart port. 
The mini-uart doesn't have a separate clock divisor and uses the core clock frequency.

Assembly Sheet

• RPI-CONSOLE Assembly Sheet