System-Reference-Manual.wiki

[[images/PocketBeagle-size-compare-small.jpg|598x400px]]

'''PocketBeagle'''

'''System Reference Manual (SRM)'''

'''Revision A.x (on-line wiki edition)'''

'''December 6, 2017'''

'''Maintaining author: Jason Kridner ''jkridner@beagleboard.org'''''

'''Contributing Editor: Cathy Wicks  ''cathy@beagleboard.org'''''

'''THIS DOCUMENT '''

'''Terms'''
These design materials are *NOT SUPPORTED* and *DO NOT* constitute a reference design. Only “community” support is allowed via resources at [https://beagleboard.org/discuss BeagleBoard.org/discuss].

THERE IS NO WARRANTY FOR THE DESIGN MATERIALS, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE DESIGN MATERIALS “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE DESIGN MATERIALS IS WITH YOU. SHOULD THE DESIGN MATERIALS PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

In other words, you may use the design materials as you choose and there is no license with regards to usage in the manufacturing process. We mean it, these design materials may be totally unsuitable for any purposes. Don't blame us!

As a general rule, we don't encourage use of this or other off-the-shelf single board computers in commercial products without engaging with a manufacturer to create a supplier agreement and make sure that you can get material as your business demands. Further, we do update the design on occasions where we find it necessary and won't guarantee a supply of older revisions, though we do seek periodic manufacturing of all of our boards for a period of roughly 10 years and will make design changes to replace obsolete parts and that may impact your usage. If you do opt to use it in a product, you take full responsibility for that product.

Do not use the BeagleBoard.org logo or trademarks (such as BeagleBoard, BeagleBone and PocketBeagle) on your products without a [https://beagleboard.org/logo ''logo license''] from the BeagleBoard.org Foundation, but feel free to reference BeagleBoard.org.

See the [https://github.com/beagleboard/pocketbeagle/blob/master/LICENSE ''LICENSE''] file regarding the copyright of these materials.

= '''1.0 Introduction ''' =

This document is the '''System Reference Manual''' for PocketBeagle and covers its use and design. 
PocketBeagle is an ultra-tiny-yet-complete Linux-enabled, community-supported, open-source USB-key-fob-computer.  PocketBeagle features an incredible low cost, slick design and simple usage, making it the ideal development board for beginners and professionals alike.  Simply develop directly in a web browser providing you with a playground for programming and electronics.  Exploring is made easy with several available libraries and tutorials with many more coming.  
   :height: 400
PocketBeagle will boot directly from a microSD card.  Load a Linux distribution onto your card, plug your board into your computer and get started.  PocketBeagle runs GNU.Linux, so you can leverage many different high-level programming languages and a large body of drivers that prevent you from needing to write a lot of your own software.  

This design will keep improving as the product matures based on feedback and experience. Software updates will be frequent and will be independent of the hardware revisions and as such not result in a change in the revision number of the board.
A great place to find out the latest news and projects for PocketBeagle is on the home page
[https://beagleboard.org/pocket ''beagleboard.org/pocket'' ]

======  Figure 1. PocketBeagle Home Page  ======
[[images/1fig-PB-homepage.png]]

Make sure you check the support Wiki frequently for the most up to date information.
[https://github.com/beagleboard/pocketbeagle/wiki ''github.com/beagleboard/pocketbeagle/wiki'' ]

= '''2.0 Change History ''' =

This section describes the change history of this document and board. Document changes are not always a result of a board change. A board change will always result in a document change.

=== 2.1 Document Change History  ===

====== Table 1. Change History  ======

{|
!
'''Rev '''
!
'''Changes '''
!
'''Date '''
!
'''By '''
|-
|
A.x
|
Production Document
|
''December 7, 2017''
|
JK
|}

=== 2.2 Board Changes   ===

====== Table 2. Board History  ======
{|
!
'''Rev '''
!
'''Changes '''
!
'''Date '''
!
'''By '''
|-
|
A1
|
Preliminary
|
''February 14, 2017''
|
JK
|-
|
A2
|
Production. Fixed mikroBUS Click reset pins (made GPIO).
|
''September 22, 2017''
|
JK
|}

====  2.2.1 PocketBone   ====

Upon the creation of the first, 27mm-by-27mm, Octavo Systems OSD3358 SIP, Jason did a hack two-layer board in EAGLE called “PocketBone” to drop the Beagle name as this was a totally unofficial effort not geared at being a BeagleBoard.org Foundation project. The board never worked because the 32kHz and 24MHz crystals were backwards and Michael Welling decided to pick it up and redo the design in KiCad as a four-layer board. Jason paid for some prototypes and this resulted in the first successful “PocketBone”, a fully-open-source 1-GHz Linux computer in a fitting into a mini-mint tin.

====  2.2.2 Rev A1   ====

The Rev A1 of PocketBeagle was a prototype not released to production. A few lines were wrong to be able to control mikroBUS Click add-on board reset lines and they were adjusted.

====  2.2.3 Rev A2   ====

The Rev A2 of PocketBeagle was released to production and [https://www.prnewswire.com/news-releases/small-in-size--cost-meet-pocketbeagle-the-25-development-board-for-hobbyists-educators-and-professionals-300519950.html''launched at World MakerFaire 2017''].

Known issues in rev A2:
{|
! '''Issue '''
! '''Link '''
|-
| GPIO44 is incorrectly labelled as GPIO48
| [https://github.com/beagleboard/pocketbeagle/issues/4 ''github.com/beagleboard/pocketbeagle/issues/4'']
|}

=  '''3.0 Connecting Up PocketBeagle ''' =

This section provides instructions on how to hook up your board. The most common scenario is tethering PocketBeagle to your PC for local development.

===  3.1 What’s In the Package   ===

In the package you will find two items as shown in '''Figures 2 and 3'''.

* PocketBeagle
* Getting Started instruction card with link to the support URL.
======  Figure 2. PocketBeagle Package  ======
[[images/pocketbeagle_package_small_size.jpg]] 
======  Figure 3. PocketBeagle Package Insert  ======
[[images/PB-card-front-1.jpg]]
[[images/PB-card-back-1.jpg]]

=== 3.2 Connecting the board ===

This section will describe how to connect to the board. Information can also be found on the Quick Start Guide that came in the box. Detailed information is also available at
[https://beagleboard.org/getting-started ''beagleboard.org/getting-started'' ]

The board can be configured in several different ways, but we will discuss the most common scenario.  Future revisions of this document may include additional configurations.

=== 3.3 Tethered to a PC using Debian Images ===

In this configuration, you will need the following additional items: 
* microUSB to USB Type A Cable
* microSD card (>=4GB and <128GB)

The board is powered by the PC via the USB cable, no other cables are required. The board is accessed either as a USB storage drive or via a web browser on the PC. You need to use either Firefox or Chrome on the PC, IE will not work properly. '''Figure 4''' shows this configuration.
======  Figure 4. Tethered Configuration  ======
[[images/PB1-fullPC-3.jpg]]

In some instances, such as when additional add-on boards, or PocketCapes are connected, the PC may not be able to supply sufficient power for the full system. In that case, review the power requirements for the add-on board/cape; additional power may need to be supplied via the 5v input, but rarely is this the case.

==== 3.3.1 Getting Started  ====
The following steps will guide you to quickly download a PocketBeagle software image onto your microSD card and get started writing code.  

1.  Navigate to the Getting Started Page  [https://beagleboard.org/getting-started ''beagleboard.org/getting-started''] 
Follow along with the instructions and click on the link noted in Figure 5 below [https://beagleboard.org/latest-images ''beagleboard.org/latest-images'']. You can also get to this page directly by going to [https://bbb.io/latest ''bbb.io/latest'']
======  Figure 5. Getting Started Page  ======
[[images/5fig-PB-GetStarted.png]]

2.  Download the latest image onto your computer by following the link to the latest image and click on the Debian image for Stretch IoT (non-GUI) for BeagleBone and PocketBeagle via microSD card. See Figure 6 below. This will download a .img.xz file into the downloads folder of your computer.

======  Figure 6. Download Latest Software Image  ======
[[images/6fig-PB-DownloadSW.png]]

3. Transfer the image to a microSD card.  

Download and install an SD card programming utility if you do not already have one.  We like [https://etcher.io/ ''https://etcher.io/''] for new users and so we show that one in the steps below.  Go to your downloads folder and doubleclick on the .exe file and follow the on-screen prompts.  See figure 7.  

======  Figure 7. Download Etcher SD Card Utility  ======
[[images/7fig-PB-Etcherdownload.png]]
 
Insert a new microSD card into a card reader/writer and attach it via the USB connection to your computer.  Follow the instructions on the screen for selecting the .img file and burning the image from your computer to the microSD card.  Eject the SD card reader when prompted and remove the card.  See Figures 8 and 9.

======  Figure 8. Select the PocketBeagle Image  ======
[[images/8fig-PB-Etcherselectimage.png]]

======  Figure 9. Burn the Image to the SD Card  ======
[[images/9fig-PB-Etcherfinish.png]]

4. Insert the microSD card into the board - you'll hear a satisfying click when it seats properly into the slot.  It is important that your microSD card is fully inserted prior to powering the system.

======  Figure 10. Insert the microSD Card into PocketBeagle  ======
[[images/10fig-PB-SDcardinsert2.jpg]]

5. Connect the micro USB connector on your cable to the board as shown in Figure 11.  The microUSB connector is fairly robust, but we suggest that you not use the cable as a leash for your PocketBeagle.  Take proper care not to put too much stress on the connector or cable.

======  Figure 11. Insert the micro USB Connector into PocketBeagle  ======
[[images/11fig-PB-microUSBattach1.jpg]]

6. Connect the large connector of the USB cable to your Linux, Mac or Windows PC USB port as shown in Figure 12. The board will power on and the power LED will be on as shown in Figure 13 below.

======  Figure 12. Insert the USB connector into PC  ======
[[images/12fig-PB-USBtoPC1.jpg]]

======  Figure 13. Board Power LED  ======
[[images/13fig-PB-PowerLED1.png]]

7. As soon as you apply power, the board will begin the booting process and the userLEDs '''Figure 14 ''' will come on in sequence as shown below. It will take a few seconds for the status LEDs to come on, like teaching PocketBeagle to 'stay'. The LEDs will be flashing as it begins to boot the Linux kernel.  While the four user LEDS can be over written and used as desired, they do have specific meanings in the image that you've initially placed on your microSD card once the Linux kernel has booted. 

* '''USER0''' is the heartbeat indicator from the Linux kernel.
* '''USER1''' turns on when the microSD card is being accessed
* '''USER2''' is an activity indicator. It turns on when the kernel is not in the idle loop.
* '''USER3''' idle
======  Figure 14. User LEDs  ======
[[images/14fig-PB-UserLEDs1.png]]

==== 3.3.2 Accessing the Board and Getting Started with Coding  ====

The board will appear as a USB Storage drive on your PC after the kernel has booted, which will take approximately 10 seconds. The kernel on the board needs to boot before the port gets enumerated. Once the board appears as a storage drive, do the following:

1. Open the USB Drive folder to view the files on your PocketBeagle.

2. Launch Interactive Quick Start Guide.

Right Click on the file named '''START.HTM''' and open it in Chrome or Firefox.  This will use your browser to open a file running on PocketBeagle via the microSD card.  You will see '''file:///Volumes/BEAGLEBONE/START.htm''' in the url bar of the browser.  See Figure 15 below.  This action displays an interactive Quick Start Guide from PocketBeagle.

======  Figure 15. Interactive Quick Start Guide Launch  ======
[[images/15fig-PB-starthtmpage.png]]

3.  Enable a Network Connection.

Click on 'Step 2' of the Interactive Quick Start Guide page to follow instructions to "Enable a Network Connection" (pointing to the DHCP server that is running on PocketBeagle).  Copy the appropriate IP Address from the chart (according to your PC operating system type) and paste into your browser then add a ''':3000''' to the end of it.  See example in Figure 16 below. This will launch from PocketBeagle one of it's favorite Web Based Development Environments, Cloud9 IDE,  (Figure 17) so that you can teach your beagle new tricks!

======  Figure 16. Enable a Network Connection  ======
[[images/16fig-PB-enablenetwork.png]]

======  Figure 17. Launch Cloud9 IDE  ======
[[images/17fig-PB-cloud9.png]]

4.  Get Started Coding with Cloud9 IDE - blinking USR3 LED in JavaScript using the BoneScript library example
<ol>
<li>Create a new text file</li>
[[images/SRM1_cloud9blinkPB.png]]
<li>Copy and paste the below code into the editor<br />
<pre>
var b = require('bonescript');
var state = b.LOW;
b.pinMode("USR3", b.OUTPUT);
setInterval(toggle, 250);  // toggle 4 times a second, every 250ms
function toggle() {
    if(state == b.LOW) state = b.HIGH;
    else state = b.LOW;
    b.digitalWrite("USR3", state);
}
</pre>
</li>
[[images/SRM2_cloud9blinkPB.png]]
[[images/SRM3_cloud9blinkPB.png]]
<li>Save the new text file as ''blinkusr3.js'' within the default directory</li>
<li>Execute <pre>node blinkusr3.js</pre> within the default (/var/lib/cloud9) directory</li>
[[images/SRM4_cloud9blinkPB.png]]
<li>Type CTRL+C to stop the program running</li>
</ol>


==== 3.3.3  Powering Down ====

1. Standard Power Down
Press the power button momentarily with a tap. The system will power down automatically. This will shut down your software with grace.  Software routines will run to completion.<br><br>The Standard Power Down can also be invoked from the Linux command shell via "sudo shutdown -h now".<br>

2. Hard Power Down
Press the power button for 10 seconds.  This will force an immediate shut down of the software.  For example you may lose any items you have written to the memory.  Holding the button longer than 10 seconds will perform a power reset and the system will power back on.

3. Remove the USB cable
Remember to hold your board firmly at the USB connection while you remove the cable to prevent damage to the USB connector.

4. Powering up again.
If you'd like to power up again without removing the USB cable follow these instructions:
# If you used Step 1 above to power down, to power back up, hold the power button for 10 seconds, release then tap it once and the system will boot normally.
# If you used Step 2 above to power down, to power back up, simply tap the power button and the system will boot normally.

======  Figure 20. Power Button  ======
[[images/20fig-PB-powerbutton.png]]

=== 3.4 Other ways to Connect up to your PocketBeagle  ===

The board can be configured in several different ways. Future revisions of this document may include additional configurations.

As other examples become documented, we'll update them on the Wiki for PocketBeagle
[https://github.com/beagleboard/pocketbeagle/wiki ''github.com/beagleboard/pocketbeagle/wiki'' ]
See also the [https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/beagleboard/JtOGZb-FH2A/9GVu7I6kAQAJ ''on-line discussion.'']


= '''4.0 PocketBeagle Overview ''' =
PocketBeagle is built around Octavo Systems' OSD335x-SM System-In-Package that integrates a high-performance Texas Instruments AM3358 processor, 512MB of DDR3, power management, nonvolatile serial memory and over 100 passive components into a single package.  This integration saves board space by eliminating several packages that would otherwise need to be placed on the board, but more notably simplifies our board design so we can focus on the user experience.   

The compact PocketBeagle design also offers access through the expansion headers to many of the interfaces and allows for the use of add-on boards called PocketCapes and Click Boards from MikroElektronika, to add many different combinations of features. A user may also develop their own board or add their own circuitry.

=== 4.1 PocketBeagle Features and Specification  ===

This section covers the specifications and features of the board in a chart and provides a high level description of the major components and interfaces that make up the board.

====== Table 3. PocketBeagle Features  ======

{| class="wikitable"
! align="center" style="background:#f0f0f0;"|'''Feature'''
! align="center" style="background:#f0f0f0;"|''''''
|-
| System-In-Package||Octavo Systems OSD335x-SM in 256 Ball BGA (21mm x 21mm)
|-
| colspan="2" | SiP Incorporates : |
|-
| Processor||Texas Instruments 1GHz Sitara™ AM3358 ARM® Cortex®-A8 with NEON floating-point accelerator
|-
| Graphics Engine||Imagination Technologies PowerVR SGX530 Graphics Accelerator
|-
| Real-Time Units||2x programmable real-time unit (PRU) 32-bit 200MHz microcontrollers with single-cycle I/O latency
|-
| Coprocessor||ARM® Cortex®-M3 for power management functions
|-
| SDRAM Memory||512MB DDR3 800MHz RAM
|-
| Non-Volatile Memory||4KB I2C EEPROM for board configuration information
|-
| Power Management||TPS65217C PMIC along with TL5209 LDO to provide power to the system with integrated 1-cell LiPo battery support
|-
| colspan="2" | Connectivity : |
|-
| SD/MMC||Bootable microSD card slot
|-
| USB||High speed USB 2.0 OTG (host/client) micro-B connector
|-
| Debug Support||JTAG test points and gdb/other monitor-mode debug possible
|-
| Power Source||microUSB connector, also expansion header options (battery, VIN or USB-VIN)
|-
| User I/O||Power Button with press detection interrupt via TPS65217C PMIC
|-
| colspan="2" | Expansion Header : |
|-
| USB||High speed USB 2.0 OTG (host/client) control signals
|-
| Analog Inputs||8 analog inputs with 6 @ 1.8V and 2 @ 3.3V along with 1.8V references
|-
| Digital I/O||44 digital GPIOs accessible with 18 enabled by default including 2 shared with the 3.3V analog input pins
|-
| UART||3 UARTs accessible with 2 enabled by default
|-
| I2C||2 I2C busses enabled by default
|-
| SPI||2 SPI busses with single chip selects enabled by default
|-
| PWM||4 Pulse Width Modulation outputs accessible with 2 enabled by default
|-
| QEP||2 Quadrature encoder inputs accessible
|-
| CAN||2 CAN bus controllers accessible
|}

==== 4.1.1 OSD3358-512M-BSM System in Package ====

The Octavo Systems OSD3358-512M-BSM System-In-Package (SiP) is part of a family of products that are building blocks designed to allow easy and cost-effective implementation of systems based in Texas Instruments powerful Sitara AM335x line of processors.  The OSD335x-SM integrates the AM335x along with the TI TPS65217C PMIC, the TI TL5209 LDO, up to 1 GB of DDR3 Memory, a 4 KB EEPROM for non-volatile configuration storage and resistors, capacitors and inductors into a single 21mm x 21mm design-in-ready package.

With this level of integration, the OSD335x-SM family of SiPs allows designers to focus on the key aspects of their system without spending time on the complicated high-speed design of the processor/DDR3 interface or the PMIC power distribution.  It reduces size and complexity of design.  

Full Datasheet and more information is available at [https://octavosystems.com/octavo_products/osd335x-sm/ ''octavosystems.com/octavo_products/osd335x-sm/'']

=== 4.2 Board Component Locations  ===

This section describes the key components on the board, their location and function. 

Figure 21 below shows the locations of the devices, connectors, LEDs, and switches on the PCB layout of the board.

====== Figure 21. Key Board Component Locations  ======
[[images/21fig-PB-walkaround.png]]

'''Key Components'''

* '''The Octavo Systems OSD3358-512M-BSM System-In-Package''' is the processor system for the board
* '''P1 and P2 Headers''' come unpopulated so a user may choose their orientation
* '''User LEDs''' provides 4 programmable blue LEDs
* '''Power BUTTON''' can be used to power up or power down the board (see section 3.3.3 for details)
* '''USB 2.0 OTG''' is a microUSB connection to a PC that can also power the board
* '''Power LED''' provides communication regarding the power to the board
* '''microSD''' slot is where a microSD card can be installed.

= '''5.0 PocketBeagle High Level Specification ''' =

This section provides the high level specification of PocketBeagle.

=== 5.1 Block Diagram  ===

Figure 22 below is the high level block diagram of PocketBeagle.

======  Figure 22. PocketBeagle Key Components ======
[[images/22fig-PB-blockdiagram.png]]

=== 5.2 System in Package (SiP)  ===

The OSD335x-SM Block Diagram is detailed in Figure 23 below.  More information, including design resources are available on the [https://octavosystems.com/octavo_products/osd335x-sm 'Octavo Systems Website']

======  Figure 23. OSD335x SIP Block Diagram ======
[[images/OSD335x-color-block.jpg]]

Note: PocketBeagle utilizes the 512MB DDR3 memory size version of the OSD335x-SM
A few of the features of the OSD335x-SM SiP may not be available on PocketBeagle headers.  Please check Section 7 for the P1 and P2 header pin tables. 

=== 5.3 Connectivity  ===

==== 5.3.1 Expansion Headers  ====

PocketBeagle gives access to a large number of peripheral functions and GPIO via 2 dual rail expansion headers.  With 36 pins each, the headers have been left unpopulated to enable users to choose the header connector orientation or add-on board / cape connector style.  Pins are clearly marked on the bottom of the board with additional pin configurations available through software settings.  Detailed information is available in Section 7.

====== Figure 24. PocketBeagle Expansion Headers ======
[[images/24fig-PB-Headerphoto.png]]

==== 5.3.2 microSD Connector  ====

The board is equipped with a single microSD connector to act as the primary boot source for the board.  Just about any microSD card you have will work, we commonly find 4G to be suitable.

When plugging in the SD card, the writing on the card should be up. Align the card with the connector and push to insert. Then release. There should be a click and the card will start to eject slightly, but it then should latch into the connector. To eject the card, push the SD card in and then remove your finger. The SD card will be ejected from the connector. Do not pull the SD card out or you could damage the connector.

====== Figure 25. microSD Connector ======
[[images/25fig-PB-SDcard.png]]


==== 5.3.3 USB 2.0 Connector  ====

The board has a microUSB connector that is USB 2.0 HS compatible that connects the USB0 port to the SiP.  Generally this port is used as a client USB port connected to a power source, such as your PC, to power the board. If you would like to use this port in host mode you will need to supply power for peripherals via Header P1 pin 7 (USB1.VIN) or through a powered USB Hub. Additionally, in the USB host configuration, you will need to power the board through Header P1 pin 1 (VIN) or Header P1 pin 7 (USB1.VIN) or Header P2 pin 14 (BAT.VIN)

====== Figure 26. USB 2.0 Connector  ======
[[images/26fig-PB-USB.png]]

==== 5.3.4 Boot Modes  ====

There are three boot modes:  

* '''SD Boot''':  MicroSD connector acts as the primary boot source for the board.  This is described in Section 3.

* '''USB Boot''':  This mode supports booting over the USB port.  More information can be found in the project called "BeagleBoot"  This project ported the BeagleBone bootloader server BBBlfs(currently written in c) to JavaScript(node.js) and make a cross platform GUI (using electron framework) flashing tool utilizing the etcher.io project. This will allow a single code base for a cross platform tool.  For more information on BeagleBoot, see the [https://medium.com/@ravikp7/gsoc-2017-final-report-beagleboot-a20d28c8d632 ''BeagleBoot Project Page''].

* '''Serial Boot''':  This mode will use the serial port to allow downloading of the software. A separate USB to TTL level  [http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_RPi.pdf ''serial UART converter cable''] is required or you can connect one of the Mikroelektronika [https://shop.mikroe.com/ftdi-click ''FTDI Click Boards''] to use this method.  The UART pins on PocketBeagle's expansion headers support the interface.  For more information regarding the pins on the expansion headers and various modes, see Section 7.  

====== Table 4. UART Pins on Expansion Headers for Serial Boot  ======
{| class="wikitable" style="white-space:nowrap;"
| '''Header.Pin'''
| '''Silkscreen'''
| '''Proc Ball'''
| '''SiP Ball'''
| '''Pin Name (Mode 0)'''
|-
| P1.22
| GND
| 
| 
| GND
|-
| P1.30
| U0_TX
| E16
| B12
| uart0_txd
|-
| P1.32
| U0_RX
| E15
| A12
| uart0_rxd
|-
|}

If the Serial Boot is not in use, the UART0 pins can be used for Serial Debug.  See Section 5.6 for more information.

'''''Software to support USB and serial boot modes is not provided by beagleboard.org.'' ''Please contact TI for support of this feature.''

=== 5.4 Power  ===

The board can be powered from three different sources:

* A USB port on a PC.
* A power supply with a USB connector.
* Expansion Header pins.

'''Note:''' VIN-USB is directly shorted between the USB connector on PocketBeagle and USB1_VI on the expansion headers. You should only source power to the board over one of these and may optionally use the other as a power sink.

The tables below show the power related pins available on PocketBeagle's Expansion Headers.

====== Table 5. Power Inputs Available on Expansion Headers  ======
{| class="wikitable" style="white-space:nowrap;"
| '''Header.Pin'''
| '''Silkscreen'''
| '''Proc Ball'''
| '''SiP Ball'''
| '''Pin Name (Mode 0)'''
|-
| P1.01
| VIN
| 
| P10, R10, T10
| VIN
|-
| P1.07
| USB1_VI
| 
| P9, R9, T9
| VIN-USB
|-
| P2.14
| BAT_+
| 
| P8, R8, T8
| VIN-BAT
|}

====== Table 6. Power Outputs Available on Expansion Headers  ======

{| class="wikitable" style="white-space:nowrap;"
| '''Header.Pin'''
| '''Silkscreen'''
| '''Proc Ball'''
| '''SiP Ball'''
| '''Pin Name (Mode 0)'''
|-
| P1.14
| +3.3V
| 
| F6, F7, G6, G7
| VOUT-3.3V
|-
| P1.24
| VOUT
| 
| K6, K7, L6, L7
| VOUT-5V
|-
| P2.13
| VOUT
| 
| K6, K7, L6, L7
| VOUT-5V
|-
| P2.23
| +3.3V
| 
| F6, F7, G6, G7
| VOUT-3.3V
|}

====== Table 5. Ground Pins Available on Expansion Headers  ======
{| class="wikitable" style="white-space:nowrap;"
| '''Header.Pin'''
| '''Silkscreen'''
| '''Proc Ball'''
| '''SiP Ball'''
| '''Pin Name (Mode 0)'''
|-
| P1.15
| USB1_GND
| 
| 
| GND
|-
| P1.16
| GND
| 
| 
| GND
|-
| P1.22
| GND
| 
| 
| GND
|-
| P2.15
| GND
| 
| 
| GND
|-
| P2.21
| GND
| 
| 
| GND
|}

'''Note''':  A comprehensive tutorial for Power Inputs and Outputs for the OSD335x System in Package is available in the [https://octavosystems.com/app_notes/osd335x-design-tutorial/bare-minimum-boot/power-input-ouput/ 'Tutorial Series'] on the Octavo Systems website.

=== 5.5 JTAG Pads  ===

Pads for an optional connection to a JTAG emulator has been provided on the back of PocketBeagle. 
More information about JTAG emulation can be found on the TI website - [https://www.ti.com/tools-software/debug.html 'Entry-level debug through full-capability development']

====== Figure 27. JTAG Pad Connections  ======
[[images/27fig-PB-JTAGpads.png]]

=== 5.6 Serial Debug Port  ===

Serial debug is provided via UART0 on the processor.  See Section 5.3.4 for the Header Pin table.  Signals supported are TX and RX. None of the handshake signals (CTS/RTS) are supported.  A separate USB to TTL level  [http://www.ftdichip.com/Support/Documents/DataSheets/Cables/DS_TTL-232R_RPi.pdf ''serial UART converter cable''] is required or you can connect one of the Mikroelektronika [https://shop.mikroe.com/ftdi-click ''FTDI Click Boards'']to use this method.  

====== Figure 28. Serial Debug Connections  ======
[[images/28fig-PB-serialdebug.png]]

If serial boot is not used, the UART0 can be used to view boot messages during startup and can provide access to a console using a terminal access program like [http://www.putty.org/ ''Putty''].  To view the boot messages or use the console the UART should be set to a baud rate of 115200 and use 8 bits for data, no parity bit and 1 stop bit (8N1).

= '''6.0 Detailed Hardware Design ''' =

The following sections contain schematic references for PocketBeagle.  Full schematics in both PDF and Eagle are available on the [https://github.com/beagleboard/pocketbeagle 'PocketBeagle Wiki']

=== 6.1  OSD3358-SM SiP Design ===
Schematics for the OSD3358-SM SiP are divided into several diagrams.

==== 6.1.1 SiP A OSD3358 SiP System and Power Signals ====

====== Figure 29. SiP A OSD3358 SiP System and Power Signals  ======
[[images/SiP-A-sch.png]]

==== 6.1.2 SiP B OSD3358 SiP JTAG, USB & Analog Signals ====

====== Figure 30. SiP B OSD3358 SiP JTAG, USB & Analog Signals  ======
[[images/SiP-B-sch.png]]


==== 6.1.3 SiP C OSD3358 SiP Peripheral Signals ====

====== Figure 31. SiP C OSD3358 SiP Peripheral Signals  ======
[[images/SiP-C-sch.png]]

==== 6.1.4 SiP D OSD3358 SiP System Boot Configuration  ====

====== Figure 32. SiP D OSD3358 SiP System Boot Configuration  ======
[[images/SiP-D-sch.png]]


==== 6.1.5 SiP E OSD3358 SiP Power Signals  ====

====== Figure 33. SiP E OSD3358 SiP Power Signals  ======
[[images/SiP-E-sch.png]]


==== 6.1.6 SiP F OSD3358 SiP Power Signals ====

====== Figure 34. SiP F OSD3358 SiP Power Signals  ======
[[images/SiP-F-sch.png]]


=== 6.2  MicroSD Connection ===

The Micro Secure Digital (microSD) connector design is highlighted in Figure 35.

====== Figure 35. microSD Connections  ======
[[images/usdconnector-sch.png]]


=== 6.3 USB Connector ===

The USB connector design is highlighted in Figure 36.

Note that there is an ID pin for dual-role (host/client) functionality. The hardware fully supports it, but care should be taken to ensure the kernel in use is either statically or dynamically configured to recognize and utilize the proper mode.

====== Figure 36. USB Connection  ======
[[images/USB-sch.png]]

=== 6.4 Power Button Design ===

The power button design is highlighted in Figure 37.

====== Figure 37. Power Button  ======
[[images/Power-button-sch.png]]

=== 6.5 User LEDs ===
There are four user programmable LEDs on PocketBeagle.  The design is highlighted in Figure 38. 
Table 6 Provides the LED control signals and pins.  A logic level of "1" will cause the LEDs to turn on. 

====== Figure 38. User LEDs  ======
[[images/User-LEDs-sch.png]]

====== Table 6. User LED Control Signals/Pins  ======
{| class="wikitable" style="white-space:nowrap;"
| '''LED'''
| '''Signal Name'''
| '''Proc Ball'''
| '''SiP Ball'''
|-
| USR0
| GPIO1_21
| V15
| P13
|-
| USR1
| GPIO1_22
| U15
| T14
|-
| USR2
| GPIO1_23
| T15
| R14
|-
| USR3
| GPIO1_24
| V16
| P14
|}

=== 6.6 JTAG Pads ===
There are 7 pads on the bottom of PocketBeagle to connect JTAG for debugging.  The design is highlighted in Figure 39. 
More information regarding JTAG debugging can be found at [https://www.ti.com/jtag 'www.ti.com/jtag']

====== Figure 39. JTAG Pads Design  ======

[[images/JTAG-pads-sch.png]]

=== 6.7 PRU-ICSS  ===

The Programmable Real-Time Unit Subsystem and Industrial Communication SubSystem (PRU-ICSS) module is located inside the AM3358 processor, which is inside the Octavo Systems SiP. Commonly referred to as just the "PRU", this little subsystem will unleash a lot of performance for you to use in your application.  Consisting of dual 32-bit RISC cores (Programmable Real-Time Units, or PRUs), data and instruction memories, internal peripheral modules, and an interrupt controller (INTC). The programmable nature of the PRU-ICSS, along with their access to pins, events and all SoC resources, provides flexibility in implementing fast real-time responses, specialized data handling operations, custom peripheral interfaces, and in offloading tasks from the other processor cores of the system-on-chip (SoC). Access to these pins is provided by PocketBeagle's expansion headers and is multiplexed with other functions on the board. Access is not provided to all of the available pins.

Some getting started information can be found on https://beagleboard.org/pru.

Additional documentation is located on the Texas Instruments website at [http://processors.wiki.ti.com/index.php/PRU-ICSS ''processors.wiki.ti.com/index.php/PRU-ICSS''] and also located at [http://github.com/beagleboard/am335x_pru_package ''http://github.com/beagleboard/am335x_pru_package''.] 

Example projects using the PRU-ICSS can be found at [http://processors.wiki.ti.com/index.php/PRU_Projects ''processors.wiki.ti.com/index.php/PRU_Projects''].

==== 6.7.1 PRU-ICSS Features  ====

The features of the PRU-ICSS include:

Two independent programmable real-time (PRU) cores:

* 32-Bit Load/Store RISC architecture
* 8K Byte instruction RAM (2K instructions) per core
* 8K Bytes data RAM per core
* 12K Bytes shared RAM
* Operating frequency of 200 MHz
* PRU operation is little endian similar to ARM processor
* All memories within PRU-ICSS support parity
* Includes Interrupt Controller for system event handling
* Fast I/O interface

– 16 input pins and 16 output pins per PRU core. (Not all of these are accessible on the PocketBeagle.  Please check the Pin Table below for PRU-ICSS features available through the P1 and P2 headers.)

==== 6.7.2 PRU-ICSS Block Diagram  ====

Figure 40 is a high level block diagram of the PRU-ICSS.

[[images/40fig-PB-PRU-block.png]]

====== Figure 40. PRU-ICSS Block Diagram  ======

==== 6.7.3 PRU-ICSS Pin Access  ====

Both PRU 0 and PRU1 are accessible from the expansion headers.  Listed below are the ports that can be accessed on each PRU.

Table 6. below shows which PRU-ICSS signals can be accessed on PocketBeagle and on which connector and pins on which they are accessible.  Some signals are accessible on the same pins.

======  Table 6. PRU0 and PRU1 Access  ======
Use scroll bar at bottom of chart to see additional features in columns to the right.
When printing this document, you will need to print this chart separately.

{| class="wikitable" style="white-space:nowrap;"
| Header.Pin
| Silkscreen
| Processor Ball
| SiP Ball
| Mode3
| Mode4
| Mode5
| Mode6
| Note
|-
| P1.02
| A6/87
| R5
| F2
| 
| 
| pr1_pru1_pru_r30_9 (Output)
| pr1_pru1_pru_r31_9 (Input)
| 
|-
| P1.04
| 89
| R6
| E1
| 
| 
| pr1_pru1_pru_r30_11 (Output)
| pr1_pru1_pru_r31_11 (Input)
| 
|-
| P1.06
| SPI0_CS
| A16
| A14
| 
| pr1_uart0_txd (Output)
| 
| 
| UART Transmit Data
|-
| P1.08
| SPI0_CLK
| A17
| A13
| 
| pr1_uart0_cts_n (Input)
| 
| 
| UART Clear to Send
|-
| P1.10
| SPI0_MISO
| B17
| B13
| 
| pr1_uart0_rts_n (Output)
| 
| 
| UART Request to Send
|-
| P1.12
| SPI0_MOSI
| B16
| B14
| 
| pr1_uart0_rxd (Input)
| 
| 
| UART Receive Data
|-
| P1.20
| 20
| D14
| B4
| 
| 
| pr1_pru0_pru_r31_16 (Input)
| 
|
|-
| P1.26
| I2C2_SDA
| D18
| B10
| 
| 
| pr1_uart0_cts_n (Input)
| 
| UART Clear to Send
|-
| P1.28
| I2C2_SCL
| D17
| A10
| 
| 
| pr1_uart0_rts_n (Output)
| 
| UART Request to Send
|-
| P1.29
| PRU0_7
| A14
| C4
| 
| 
| pr1_pru0_pru_r30_7 (Output)
| pr1_pru0_pru_r31_7 (Input)
| 
|-
| P1.30
| U0_TX
| E16
| B12
| 
| 
| pr1_pru1_pru_r30_15 (Output)
| pr1_pru1_pru_r31_15 (Input)
| 
|-
| P1.31
| PRU0_4
| B12
| A3
| 
| 
| pr1_pru0_pru_r30_4 (Output)
| pr1_pru0_pru_r31_4 (Input)
|
|- 
| P1.32
| U0_RX
| E15
| A12
| 
| 
| pr1_pru1_pru_r30_14 (Output)
| pr1_pru1_pru_r31_14 (Input)
| 
|-
| P1.33
| PRU0_1
| B13
| A2
| 
| 
| pr1_pru0_pru_r30_1 (Output)
| pr1_pru0_pru_r31_1 (Input)
| 
|-
| P1.35
| P1.10
| V5
| F1
| 
| 
| pr1_pru1_pru_r30_10 (Output)
| pr1_pru1_pru_r31_10 (Input)
| 
|-
| P1.36
| PWM0A
| A13
| A1
| 
| 
| pr1_pru0_pru_r30_0 (Output)
| pr1_pru0_pru_r31_0 (Input)
| 
|-
| P2.09
| I2C1_SCL
| D15
| B11
| 
| 
| pr1_uart0_txd (Output)
| pr1_pru0_pru_r31_16 (Input)
| UART Transmit Data
|-
| P2.11
| I2C1_SDA
| D16
| A11
| 
| 
| pr1_uart0_rxd (Input)
| pr1_pru1_pru_r31_16 (Input)
| UART Receive Data
|-
| P2.17
| 65
| V12
| T7
| 
| 
| pr1_mdio_mdclk
| 
| MDIO Clk
|-
| P2.18
| 47
| U13
| P7
| 
| 
| pr1_ecap0_ecap_capin_apwm_o
| pr1_pru0_pru_r31_15 (Input)
| Enhanced capture input or Auxiliary PWM out
|-
| P2.20
| 64
| T13
| R7
| 
| 
| pr1_mdio_data
| 
| MDIO Data
|-
| P2.22
| 46
| V13
| T6
| 
| 
| 
| pr1_pru0_pru_r31_14 (Input)
| 
|-
| P2.24
| 48
| T12
| P6
| 
| 
| 
| pr1_pru0_pru_r30_14 (Output)