(Some info on beaglebone) |
No edit summary |
||
Line 21: | Line 21: | ||
Avoid injecting current into IOs when the beaglebone is powered off. In particular, the digital I/Os are '''NOT''' 3.3V-tolerant when the 3.3V supply is off. | Avoid injecting current into IOs when the beaglebone is powered off. In particular, the digital I/Os are '''NOT''' 3.3V-tolerant when the 3.3V supply is off. | ||
== Playing with it == | |||
URL of web interface, cloud9 IDE, and SSH login and password are currently on a piece of paper on the BBB. Quite a bit of javascript on the web interface is broken, but the cloud9 IDE seems to work... mostly. | |||
I've installed/written a bunch of utility scripts: | |||
* <code>gpio-parse</code> can convert between various ways of identifying GPIOs | |||
* <code>sudo gpio-export</code> exports a GPIO via sysfs (accepts any format that <code>gpio-parse</code>, prints the sysfs paths) | |||
* <code>sudo gpio-unexport</code> removes such exports | |||
* <code>sudo show-pins</code> detailed overview of pin config and usage | |||
* <code>~/charger-info.pl</code> shows (some) status info of the charger state | |||
* <code>~/charger-config.sh</code> configures the PMIC with more liberal charger settings and resets the charger. May be necessary to get it to charge it all via USB depending on the usb port and cable length/quality. |
Revision as of 06:54, 4 April 2016
BeagleBone Black | |
---|---|
Owner | User:zmatt |
Status | |
Hostname | bbb |
Tool | |
Tool category |
BeagleBone Black Property "Tool Image" (as page type) with input value "File:{{{Picture}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Picture}}} {{{InventoryOwner}}}Property "Tool Owner" (as page type) with input value "{{{InventoryOwner}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process. {{{Location}}}Property "Tool Location" (as page type) with input value "{{{Location}}}" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
Description
BeagleBone Black (rev C), donated by my employer Dutch & Dutch. It has one minor defect: one I/O pin (P9.26 / GPIO 0.14) has been damaged, probably by overvoltage, and has become unusable. I've stuffed it with polycaprolactone to clearly mark it and avoid accidental use.
Like most of our BBBs it also has a small patch: the separate regulator for "VDD_3V3B" has been removed and the voltage rail has been tied to the "VDD_3V3A" instead, which means it has a single unified 3.3V rail. This patch was done to avoid the problem where the 3V3B remains enabled too long during poweroff and indefinitely if the BBB is supplied via battery power. With this patch the BBB can be safely powered via its battery terminals (single Li-ion cell, BBB has integrated charger). An obvious side-effect is that less power can be drawn from the BBB's 3.3V supply by external hardware. See [elinux.org/BeagleBone_Power_Management here] for more info on BBB power supply infrastructure.
Information on pin functions can be found in this spreadsheet. Laminated printouts of the P9 and P8 tabs are also somewhere in the space.
Hardware safety notes
The expansion header pins connect to the processor without any real protection, and being careless can destroy an IO or the entire processor.
The digital I/Os are 3.3V and are NOT 5V-tolerant.
The ADC inputs are max 1.8V. Due to a hardware erratum they may be briefly shorted together and/or to vdd or ground during power-up, hence it is recommended to avoid connecting them to low-impedance outputs (e.g. opamps) without a series resistor.
Avoid injecting current into IOs when the beaglebone is powered off. In particular, the digital I/Os are NOT 3.3V-tolerant when the 3.3V supply is off.
Playing with it
URL of web interface, cloud9 IDE, and SSH login and password are currently on a piece of paper on the BBB. Quite a bit of javascript on the web interface is broken, but the cloud9 IDE seems to work... mostly.
I've installed/written a bunch of utility scripts:
gpio-parse
can convert between various ways of identifying GPIOssudo gpio-export
exports a GPIO via sysfs (accepts any format thatgpio-parse
, prints the sysfs paths)sudo gpio-unexport
removes such exportssudo show-pins
detailed overview of pin config and usage~/charger-info.pl
shows (some) status info of the charger state~/charger-config.sh
configures the PMIC with more liberal charger settings and resets the charger. May be necessary to get it to charge it all via USB depending on the usb port and cable length/quality.