Contents • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Hardware & Peripherals: - detailed information about the Raspberry Pi boards. - guide to the Raspberry Pi models.

- using the GPIO and other connectors. - GPIO plug-in boards providing additional functionality.

The Synaptics Pointing Device Driver will allow you to add some advanced features to your laptops pad. Holux gps usb device. Uninstall the USB driver that you have installed in the Win 7 Driver for M-1000C~ GPS receiver to match its device. HOLUX GPS USB DEVICE (COM3)HOLUX driver DOWNLOAD NOW Driver. I bought this GPS receiver to replace a Microsoft branded receiver I had that got destroyed some time back. The first thing that went smoothly was the installation of the drivers onto my Windows 7 laptop. Once I used their diagnostic software to verify that it was working correctly, I tried it with my moving map software.

- attaching a screen to the Raspberry Pi. - lots of nice cases to protect the Raspberry Pi. Other Peripherals - all sorts of peripherals used with the Raspberry Pi. A note about this page: For USB devices, please specify if they required a powered hub Notes 19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the unless stated otherwise.

A suggested suffix markup scheme is as follows: • (A) - Relates to model A production board • (B) - Relates to model B production board • (!) - Information from alpha and beta board days -- beta board verified peripherals should still apply to production boards for the most part, but the alpha board is fairly different • No markup - relates to all production boards Discuss: If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order. Power Usage Notes Warning: Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the Raspberry Pi. If the Raspberry Pi's supply voltage falls below a certain value (anecdotally stated as around 4.75 V), or it begins to fluctuate, your setup may become unstable. There is a which is worth a read. Model B Hardware Revisions and USB Power limits Hardware Revision 1.0 The original Model B board had current limiting polyfuses which limited the power output of each USB port to approximately 100 mA.

USB devices using more than 100 mA had to be connected via a powered hub. The Raspberry Pi's PSU was chosen with a power budget of 700 mA of which 200 mA were assigned to the USB ports, so the Raspberry Pi's (poly)fuses were designed only for devices up to 100 mA, and typical 140 mA polyfuses will have as much as 0.6 volt across them when drawing currents near the 100 mA limit. As a consequence the USB ports are only directly suitable for 'single current unit' USB devices which, according to USB specifications, are designed to work with just 4.4 Volt. Not only do non single current unit devices draw more current (causing greater Voltage drops, and greater stress on the fuses), they also might require 4.75 Volt to work. Model B Hardware Revision 2.0 and Revision 1.0 with ECN0001 change This had the polyfuses removed, removing the 100 mA current limitation for each USB port (but leaving the main fuse F3 intact). Users should still ensure their power supply can power the Raspberry Pi and the USB peripherals. Revision 2.0 was released in August 2012.

Warning: Because the polyfuses have been removed, back feeding of the PI, by applying power via its normal USB output, can damage D 17 if triggered by an over-voltage, and so lead to consequential over-heating. This can be discovered by melts, scorching, smoke or worse. Linux Driver Issues Shortly after the Raspberry Pi was released it was confirmed that there were a number of issues with the Linux USB driver for the SMSC95xx chip. These included problems with USB 1.x peripherals that use split transactions, a fixed number of channels (causing problems with Kinect) and the way the ARM processor handles the SMSC95xx interrupts. A large number of fixes were included in the 2012-08-19-Wheezy-raspbian Linux image. Powered USB Hubs This section has been moved to a separate page. See USB Remotes • The USB dongle allows the use of any remote control with your Raspberry Pi.

Configure the device on your desktop PC, then simply plug into your Pi for a perfect media center companion. Available from and • ASUS TV FM Remote IR - ID 3353:3713 - works. Receiver connected to an USB Hub. Tested with archlinux in X. It works also as pointer (pressing 'Toggle' button) • ATI Remote Wonder (X10 Wireless Technology, Inc. X10 Receiver) — ID 0bc7:0004 — appears as a joystick-like 2 button mouse and a 0-9 keypad without drivers on console and X.

• - keyboard and touchpad work. Have not verified multi-touch features. • mini 2.4 GHz wireless keyboard and touchpad. • Pan.Code D1000 - 2.4GHz Wireless keyboard and touchpad. • Wireless Smart Pad ad Mini Keyboard.

The pad works as a mouse, but not multi touch features. The keyboard works. • Rii Wireless 2.4 GHz Keyboard-mouse Combo, also known as, and. Working perfectly, just plug & play.

• USB RF Keyboard and air mouse (B) • Bluetooth Adapter, Touchpad, Laser Pointer, Presentation & Multimedia Controls work perfectly, but it needs a little love and config for make it work. USB Keyboards This section has been moved to a separate page. See USB Mouse devices This section has been moved to a separate page. See USB Real Time Clocks • Cymbet • Cymbet CBC-EVAL-06 USB Real Time Clock (FT2232 to SPI to RV-2123) Device information at Code to access the RTC from Linux: Does not require a powered hub. Internet USB Wi-Fi Adapters This section has been moved to a separate page. See USB Bluetooth adapters This section has been moved to a separate page.

See USB Ethernet adapters This section has been moved to a separate page. See USB 3G Dongles Huawei • E1750 • E173 • E1820 Works on Raspbian with Sakis3G • E220 • E353 HiLink Works on Raspbian • E160 (AT commands only) • E169, E620, E800, (12d1:1001) - works on Raspbian Wheezy, • E303 - works with Raspbian Wheezy 2015-02-16 out of the box, will be recognized as network-adapter [ethX]. Usb_modeswitch may be used to configure it as a serial modem, so that tools like sakis3g (mobile connection) and gammu (SMS) have a better control over it (note: be sure to download a version of Gammu newer than 1.37.0 so that it is fully supported) Sierra Wireless • AirCard 250u works with wvdial/network manager • AirCard 320u (0f3d:68aa) works in WWAN mode, driver provided by the kernel. Tested on Arch. • Kernel version 3.10 has a bug that causes the WWAN interface to never be in RUNNING state (no carrier). Use 3.6 kernel instead.

• AT command guide can be found • for GPS to work you have to enable it. Reimage Repair License Key Keygen here. First, setup the modem (guide ) and after that enable NMEA output by passing nmea=1 parameter to the sierra kernel module. Enabling NMEA output may cause the modem to drop connections / restart itself. This is probably related to higher power drain. This may not be the issue when a powered hub is used. • 307 Works fine with Sakis3G script. The connection LED does not change its state after establishing a connection but the same behaviour on a normal linux system.

• AirCard 340u (Netgear/ATT Beam) works with latest GobiNet/GobiSerial code on Raspbian and 3.10.25+ kernel. Requires firmware update from Netgear to disable Windows 8 support and make it autoconnect.. ZTE • ZTE MF190S • ZTE MF626 Works fine with Sakis3G script. You can use force it to ALWAYS be in modem mode (See here: ), or use usb-modeswitch ( as described here ) • ZTE MF628 Tested with Sakis3g using --noprobegsm, use usb_modeswitch to get ID 19d2:0031. • ZTE MF70 (Telstra 3G USB + Wi-FI) Tested.

Automatically appears as ethernet device. No usb_modeswitch required.

Use DHCP to acquire IP address/DNS/Gateway etc. To configure modem, use web browser and visit • ZTE Rocket MF591 - Tested with T-mobile network and Model B+ running Raspbian with usb-modeswitch and Sakis3G script. (Followed guide to work: ) Others • Franklin U600 from Sprint / VirginMobile • Use usb_modeswitch and vendor 0x1fac and product 0x0150/0x0151 • Digicom Internet Key 7.2 HSUPA MU372-L01 Tested on Raspbian and Archlinux. Detected as 230d:0001.

Works with cdc_acm driver. Install usb_modeswitch. There are 2 'com ports'( /dev/ttyACM0 and /dev/ttyACM1 ). Tested with Network Manager.Works also perfectly with SAKYS3G tools (!! Led is always off!!) and wvdial. A working wvdial.conf:.

(for example for Vodafone IT, replace Init3 with this: Init3 = AT+CGDCONT=1,'IP','web.omnitel.it' and replace line Modem = /dev/ttyUSB0 with Modem = /dev/ttyACM1 ) and run with wvdial voda. • Vodafone MD950 (1dbc:0005) - is working on RPi (Raspbian Wheezy) but not out of the box,.

USB 4G Dongles Huawei • Huawei E398 LTE USB Rotator Mobile Broadband • Huawei E3372 LTE USB stick USB Sound Cards You will usually want the alsa package for sound. In the Debian image for Raspberry Pi (and possibly other distributions) USB sound cards are prevented from loading as the first sound card, which can be an annoyance if it's the only device you have. To disable this behaviour edit /etc/modprobe.d/alsa-base.conf and comment out the last line; options snd-usb-audio index=-2.

If you are not user pi you may need to add your username to the audio group thus: sudo adduser yourusername audio (user pi usually belongs to this group anyway). • Creative • • Daffodil •. Tested with low-cost headphone/microphone set via audacity (See notes at ). • Edirol • • GWCtech • (aka ) - playback works fine, Recording stutters unless dwc_otg.speed=1 is set • Hercules • • Hewlett Packard • Hewlett Packard (HP) Premium Digital Headset, Model No: HUD-02. It supports both audio out and audio in.

Works in Audacity. Recprding volume is quiet even with recording mixer level turned way up. Additional post-mixer amplification of audio-in is recommended, if possible. • Kingwin • (Both audio out/in work, lsusb lists as 'C-Media USB Headphone Set') • Logilink • • Logitech • (stereo works with ALSA, have not tried 7.1 Surround Sound) • NuForce uDAC-2 • • Plantronics • (works with ALSA) (shows up in lsusb as 0d8c:000c C-Media Electronics, Inc. Audio Adapter) • SpeedLink • - Device ID: 0d8c:000e ('C-Media Electronics, Inc.

Audio Adapter'). Working, but on Raspbian 3.6.11 it fills up kern.log with 'cm109_urb_irq_callback: urb status -71' messages. To prevent this, you can insert `:msg, contains, 'cm109_urb_irq_callback' ~´ as first rule into /etc/rsyslog.conf. • Terratec • (not with USB high speed; add dwc_otg.speed=1 to /boot/cmdline.txt, but that will slow down all USB transfers) • Texas Instruments PCM2704 • Databases of supported sound cards • • Class compliant USB sound cards Any USB1.1 audio interface that is class compliant should work with Linux, same goes for USB2.0 interfaces that adhere to the current USB audio standards. There are some interfaces that are supported in Linux while they do not comply to the standards because specific quirks have been added to the USB Linux drivers. To verify if your interface is supported search for a manual of your interface and check if it needs drivers to run under Windows/Mac. If the manual explicitely mentions no drivers are needed the interface is almost surely a class compliant device.

When in doubt check the aforementioned databases. Troubleshooting If you encounter problems setting up your USB soundcard check the RPi Wiki article in the linuxaudio.org Wiki: • Bulleted list item USB IR Receivers • The USB dongle allows the use of any remote control with your Raspberry Pi. Configure the device on your desktop PC, then simply plug into your Pi for a perfect media center companion.

Available from, and • SMK Manufacturing, Inc. EHome Infrared Receiver (Works out of the box with OpenELEC) USB Radio devices • FM Radio • ADS InstantFM Music - FM radio tuner works fine under Debian. USB TV Tuners and DVB devices • August • DVB-T205, based on rtl2832u chipset, worked with on older 3.2 kernel.

Couldn't get same device working reliably on current kernel. (On the older 3.2 kernel it worked with Saorview (Irish DTT service), both HD & SD.) • Derek? • TV28T v2 USB DVB-T & RTL-SDR Receiver, RTL2832U & R820T Tuner, MCX Input. DVB-T works with OpenElec 4.2.1 connected to the PiHub, tvheadend backend + frontend, finds all expected, non-encrypted channels in the south of Germany. I did not try to use the remote. • DVBSky •: Scanning/watching SD and HD works via vdr and streamdev plugin, watching on the Raspberry Pi directly is laggy as hell.

DVB-USB and I2C support must be enabled in the kernel. Needs drivers/firmware from.

• Sundtek • Sundtek MediaTV Digital Home • Sundtek MediaTV Pro • Sundtek SkyTV Ultimate •: digital TV works, streaming to Windows / Linux is no problem. Easy installation • Hauppauge • Hauppauge NOVA-T Stick (Revision 70xxx) DiBcom DiB0700 chipset, requires powered hub. • Hauppauge NOVA-TD Stick (Revision 52xxx) DiBcom DiB0700 chipset, requires powered hub. • Hauppauge WinTV-HVR-1950 (tested analog tuner with omxplayer, tested Digital OTA with MythTV) • Hauppauge WinTV-HVR-950Q (tested Digital OTA with TVHeadend in Raspbian) • K-World • K-World UB499-2T Dual DVB-T USB Tuner. IT9137 chipset. With no other USB devices connected Raspberry Pi can just about power this stick.

IR and supplied remote work with XBMC. • Technisat • Technisat_SkyStar_USB_HD. Instructions: Used the Raspberry Pi to receive and redirect it via network to another host. Didn't try to play back the stream on the Raspberry Pi itself. Tested with Astra 19. Acer Aspire 5742 Network Adapter Driver. 2E radio and SD-TV channels • TECHNOTREND • TT-TVStick CT2-4400 USB Fernbedienung rev2. DVB-T works with OpenElec 4.9.4 BETA connected to the PiHub, tvheadend backend + frontend, finds all expected, non-encrypted channels in the south of Germany.

DVB-C also works, finds around >30 TVs and >100 radio stations. I did not try to use the remote, nor did I listen to any radio station. TV works, SD channels are ok, HD channels jitter. Tvheadend backend crashes often within OpenElec 4.9.4 BETA, but restarts, so still buggy but looks good(BETA!).

It did not work out of the box with the stable OpenElec 4.2.1. • Terratec • Terratec H7.

Tested DVB-C with, under and latest (April, 14 2013). • Generic •, based on AF9015 chipset. •, based on RTL2832 FC12 (HD/SD), IR was detected, but it is not tested. • dongle, based on IT9135.

This tuner comes in two revisions. Revision is printed on PCB. 1.0; should work with 3.2+ kernel, need confirmation. 2.0; works with kernel 3.6.11, without a powered hub. This tuner also requires a firmware (dvb-usb-it9135-02.fw) which can be downloaded from.

It's in Hungarian, so google translate or equivalent is recommended. The remote also works. According to, there may be issues on some software configurations when using omxplayer. USB Video / Frame grabbers • EasyCAP DC60 (STK1160 chip) - works out of the box for older versions of Raspbian. If you're getting grey stripes see this • EasyCAP (UTV007 Fushicai chip) - works after driver compilation - see instructions. Remember to use older Raspbian version. • Hauppage HVR 1900 USB Webcams This section has been moved to a separate page.

See USB GPS devices • Columbus • Columbus V-800 (MediaTek (MTKII) 3329 GPS chipset) - does not require powered USB hub. Works on Wheezy (using gpsd & gpsd-clients) • Royaltek • Royaltek RGM 2000 SiRF2 using the included serial (TTL) to USB - converter (Prolific pl2303-chip) • Garmin • Garmin eTrex Vista HCx: It works, but it may draw too much power. To get it working (software part): • GlobalSat • GlobalSat BU-353 Does not require a powered hub, works fine when directly plugged into the Raspberry Pi. On Raspian, requires the gpsd and gpsd-client packages.

For some reason, the gpsd daemon does not always start correctly on boot. You may need to do something like the following to manually restart it: sudo killall gpsd; sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock • GlobalSat BU-353-S4 supports two protocols: NMEA, and SiRF v4. NMEA works fine, but SiRF v4 isn't compatible with 'gpsd's SiRF v3 interpreter, resulting in a greatly reduced data rate (as low as four location fixes per hour). To keep 'gpsd's autoconfiguration from putting the receiver in SiRF mode, you'll need to pass the '-b' flag when starting 'gpsd'. • Wintec • WBT-200: No problem on Debian • Holux • Holux M-215: Works fine on Arch, uses Silicon Labs CP210x RS232 serial adaptor driver • Bluenext • Bluenext BN903S: No problem on Debian image (). • U blox NEO 6 - works well, connects via GPIO (serial console).

USB UART and USB to Serial (RS-232) adapters A USB UART adapter is used to access the serial console of the Raspberry Pi from a development host such as a laptop or desktop PC. The USB end connects to the PC and the UART header end connects to the USB. While it is possible to connect the USB end to another Raspberry Pi, this configuration has not been tested unless explicitly mentioned against an individual entry below. Working USB to Serial Adapters • FTDI (Future Technology Devices International Limited) • FT232 chip based adapters works for some people, but others find it hangs Linux when the port is opened. The module is ftdi_sio. • FT232R USB UART works out of the box between Raspbian Wheezy and OS X Mavericks (Product-ID: 0x6001, Manufacturer-ID: 0x0403, Maximal Speed: 12 MBit/s, Maximal Power Consumption: 90 mA).

• FT2232D dual RS232/FIFO works (used in various JTAG devices) • Belkin • F5U409 Works OOTB; does not support speeds above 115,200, so you can't use it for DMX or other high-speed protocols. • Prolific • PL2303 chip based adaptors works fine on latest Debian tested with minicom, gtkterm and screen. A USB to Serial (RS-232) adapter is used the other way around, ie. The USB end connects to the Raspberry Pi and the RS-232 end (DSUB-9 or DSUB-25 pin) to the other device which may be another computer, (old) modem or printer, or some electronic test equipment. • 'Best Connectivity' (Possibly also sold under the 'Newlink HQ' or 'Kenable HQ' labels) • FG-U1232-PL2 Based upon the Prolific PL2303X chipset and listed by lsusb as ID 067b:2303 Prolific Technology, Inc.

PL2303 Serial Port. Appears as /dev/ttyUSB0, and requires the user to be a member of the dialout group (which pi is for Raspbian Wheezy). Initially tested using an old RS Datalinker setup in 'loopback' mode via microcom upto 9600 baud, and gtkterm after installing that from source code.

All handshake lines toggled as expected and no characters were lost. Subsequently gtkterm was used to check bi-directional communication with an ancient brother EP44 electronic typewriter (as a printer/dumb terminal) at 1200 baud. Signal lines were again monitored with the Datalinker.

• 'PL2303HX USB to RS232 TTL Converter Adapter Module' on dx.com: • Based on the Prolific PL-2303HX chipset. Listed by lsusb as ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port. Appears as /dev/ttyUSBX with GUID dialout so your user has to be in that group. If not, sudo usermod -a -G dialout yourusername will add your user to the dialout group.

Works great with screen /dev/ttyUSBX 115200 to connect from your workstation to your RPi. Problem USB to Serial Adapters HL-340 • CH340 Chipset - Currently not supported by RPi but there is a patch of kernel code, but it is for a 2.X kernel. If you find you have bought one of these, then it may work under Windows, but as of writing there is no support for RPi. Otherwise you can have a go at getting the patch to work. USB Multi-Card Readers Working USB Multi-Card Readers • US Robotics USB 3.0 All-In-One Multi-Format Card Reader (Product # USR8420) Accepts 5 cards simultaneously • SD/MMC + MS/MS PRO or DUO/DUO PRO + CF/MD + SM + SD/MMC or MS/MS PRO. Useful for backing up cards containing other OS Distros • Generic (Nintendo branded) • identified as '14cd:8123 Super Top SD MMC Reader' (B) Problem USB Multi-Card Readers • Generic • Card reader based on NEODIO ND3260-LD chip, identified as '0aec:3260 Neodio Technologies Corp.

7-in-1 Card Reader', fails after a few seconds with all access lights blinking. (B) USB Smart-Card Readers Working USB Smart-Card Readers •. Works out of the box without any extra drivers. Does not require powered USB hub.

Other, exotic USB devices Joysticks / Joypads • Microsoft • Xbox360 Controller (045e:028e): works. Tested with archlinux, connected to an USB Hub, used as 'mouse' in X, package xf86-input-joystick • Logitech • Dual Action: works, connected directly to the Pi. • Ion • Go Pad: works. Tested on Raspbian Wheezy (release 2014-01-07), connected to on-board USB port (Model B rev. • VZTEC • USB Double Shock Controller Game Pad Joystick VZ-GA6002: works. Tested on RetroPie V2.3, connected to on-board USB port (Model B+).

Numpads • Conceptronic / Holtek • USB numpad (04d9:a02a): works. Tested with archlinux, connected to an USB Hub • Speedlink SL-7430-SGY • USB numpad (04d9:1603, HT82M99E Holtek chip inside): works. Tested with Raspbian “wheezy” • GreenAsia Inc.

() • USB numpad (0e8f:0022): works. Tested with Raspbian “wheezy” USB to Parallel Port/Printer Adapters • Prolific • PL2305 Chipset with Centronics 36w connector. Originally purchased for use with a netbook and connected to an old Canon BJC-250 printer.

Worked fine under with its in-built BJC-250 driver. Could not install the CUPS drivers etc.

For Wheezy-Raspbian initially, but was able to do so for Wheezy-armel. Once I'd updated/upgraded Wheezy all was fine.(See notes at for more info. And also a ) USB to IDE/SATA • JMicron Technology • JM20337 USB to SATA/PATA Combo Bridge (152d:2338) - works on Raspbian and Arch. The hard drive requires an external power supply. • Nippon Labs • 2.5' SATA HDD USB Adapter with silicone HDD sleeve. Model: USB-ADT-25SATA. Works on powered Hub, not directly to Raspberry Pi.

Built-in 'Y' power adapter. Does work direct on some ver2.0 boards if used with 5.25 power supply, or Y adapter CAN Bus • PEAK-System (www.peak-system.com) • PCAN-USB using the driver (kernel module) from Home automation • Tellstick (www.telldus.com), installation • Depends on libftdi1 Weather station • Oregon Scientific WMRS-200: Work out of the box (tested with Raspbian & wview) One-Wire • PCsensor • USB9097 (1a86:7523): works out of the box but issue with LAN after a few hours, no problem after a firmware update. Identify's as 'QinHeng Electronics HL-340 USB-Serial adapter' Tested with raspbian/wheezy + domotiga & digitemp directly to USB port & 4 sensors connected via a '1-wire hub'. Claims to be 'fully replace DS9097, DS9490 of MAXIM'. Simple and cheap solution to measure temperature.

Touch Screen • ACER T230H touch screen This link is Broken • USB TS identifies as 'Quanta Computer, Inc. Optical dual-touch panel', module hid_quanta • Seems to draw over 200 mA from USB! • SainSmart 3.2 touch screen • 320*240 • 3.2 inch • SSD1289:240 RGB x 320 TFT Drive • Video: Raspberry Pi with a 3.2' TFT with Touch control • Tutorial: Raspberry Pi with a 3.2″ TFT with Touch control Floppy Disk Drive • Samsung USB Floppy Drive SFD-321U/HP • I suppose a floppy drive might be considered exotic nowadays! • LSUSB lists it as Samsung Electro-Mechanics Co.

Floppy Disk Drive • Only tried connected to a powered USB hub, as the drive is labelled 5 V at 0.5 A on a Raspberry Pi running Debian Wheezy. • tail -f /var/log/syslog looking for mount device when plugged in, came up as SDA in testing. • sudo mkdir /media/floppy • sudo mount /dev/sda /media/floppy • Contents of floppy now available in /media/floppy • To remove drive, ensure no sessions have the floppy directory as the current working directory.

• sudo umount /media/floppy • Y-E Data model HU-35EF • Requires a powered hub and manual mounting/unmounting like the Samsung drive above. USB Missile Launcher • USB Missile Launcher / Rocket Launcher sold in UK by Marks and Spencer, but it is also sold under a range of other names. • USB ID 1130:0202 Tenx Technology, Inc. Use apt-get install pymissile (python code) and there is C code at USB Docking Stations • StarTech USB 3.0 to Dual 2.5'/3.5' SATA HDD Dock (SATDOCK2U3GB) • This is an externally powered dual sata HDD docking station, which has USB2.0 compatibility with the Raspberry Pi. • Tested with latest Raspbmc and Debian Wheezy Raspbian, 3.1.9+ #168 • Icy Box USB 3.0 to Dual 2.5'/3.5' SATA HDD Dock (IB-120StU3) • Externally powered dual HDD dock, USB 2 compatible. • Tested with Slackware ARM 14.0 and drives in both slots, just show up as separate SCSI disks.

USB RFID Reader • Unbranded 125 kHz EM4100 RFID reader from eBay sellers ( miniUSB adapter/cable, works perfectly (bought from ) • Youse • Dual USB Wall Plate. Has a 2.1A 'Tablet' port, a 1A 'Phone' port and a US electrical outlet. Powers a Raspberry Pi 2 from the 2.1A 'Tablet' port. Available from Five Below. • ZTE • ZTE Blade charger STC-A22O501700USBA-A 5 V 700 mA Problem power Adapters • Nokia • 5 V 1.2 A AC-10A & AC-10E Chargers only provide 4.8V at TP1 & TP2 • Provides only 4.7V across TP1 & TP2 when at idle • Masterplug • Masterplug Surge Protected USB Adaptor 2 x 1 A USB Polished Black - USB ports and Ethernet don't work with this adapter and some screen artifacts using HDMI. • Monoprice • 5 V, 2 A 3 Outlet Power Surge Protector Wall Tap with 2 Built-In USB Charger - some display artifacts, sometimes unable to find mouse, some failures to boot.

Measured to less than 4.75 V between TP1 and TP2 when used with a Monoprice cable. • Sony Ericsson • 5 V, 850 mA EP800. Some failures to boot, Ethernet loops at boot.