beagleboard / pocketbeagle Goto Github PK

View Code? Open in Web Editor NEW

276.0 52.0 73.0 16.03 MB

BeagleBoard.org PocketBeagle - ultra small, ultra flexible, ultra affordable

Home Page: https://beagleboard.org/pocket

License: Creative Commons Attribution 4.0 International

Makefile 10.06% Python 89.94%

pocketbeagle's Introduction

BeagleBoard.org PocketBeagle

An even more bare-bones-BeagleBone made super-tiny, affordable and cloneable

PocketBeagle is an ultra-tiny-yet-complete open-source USB-key-fob computer. PocketBeagle features an incredible low cost, slick design and simple usage, making PocketBeagle the ideal development board for beginners and professionals alike.

See documentation for usage details and the forum for support.

Terms

These design materials are NOT SUPPORTED and DO NOT constitute a reference design. Only “community” support is allowed via resources at 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 logo license from the BeagleBoard.org Foundation, but feel free to reference BeagleBoard.org.

See the LICENSE file regarding the copyright of these materials.

pocketbeagle's People

Contributors

Stargazers

Watchers

pocketbeagle's Issues

Documentation Link to Upverter Project is Broken

The link to the upverter project here: https://github.com/beagleboard/pocketbeagle/wiki/FAQ#Is_this_open_hardware_and_what_is_the_design_in

is dead.

AUDIO Output

Hi,

Dont we have audio output with OSD3358?

Thanks

GPIO 44 labelled as 48 in silkscreen

Thanks for an amazing board!

In my testing the pin labelled as 48 in the silkscreen is actually accessed as pin 44.

I haven't found an official pinout illustration for PocketBeagle but I did find this one: http://files.linuxgizmos.com/bboard_pocketbeagle_pinout.jpg I'm unsure of the original source of this image but the image also describes that pin as 44.

Pocketbeagle not booting from SD card (but is visible on USB without the SDCARD)

Hello everybody.
Yesterday I receiver PockedBeagle from Farnell and try to boot from SD card. Only Power LED is on, the rest is dead. I have tried 5 different cards with different size and 3 diffrent USB cables.
System is dead. Whe system has card included, on attached linux system there is no USB device (no messages in dmesg also). I've tried two diffrent official Debian images from - current and last previous.
When I remove the card and again attach board, I see new device named Texas Instruments and dmesg also presents messages about new device.

Pocketbeagle not booting from SD card

I'm trying to evaluate a PocketBeagle (rev A2) for use in an instrumentation class I'm teaching this Spring, however, the one I have refuses to boot. I just purchased it from Arrow, and the microSD card that I'm using to boot it has never had anything else written to it (save by the manufacturer).

Using the Etcher program suggested by the quick start guide, I've burned a 16GB microSD card once with the image for Debian Linux v9.5 and, after that failed, with Debian Linux v9.1. Both times, the only change I've done is to edit /boot/uEnv.txt as directed to make sure that cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh is uncommented.

Booting with Debian v9.1
Upon plugging in the PB to USB, all 4 LEDs light up momentarily. They all go off, and USR0 starts its heartbeat pattern. USR1 starts to blink intermittantly and the Octavo chip starts to heat up. After about 5 seconds, all four LEDs light up simultaneously. I let it stay that way for 5-10 more seconds before the Octavo chip gets too warm and unplug the USB.

Booting with Debian v9.5
1 - Upon plugging in the PB to USB, all 4 LEDs light up momentarily.
2 - They all go off, and USR0 starts its heartbeat pattern and USR2 is on. USR1 starts to blink intermittantly.
3 - After about 20 seconds, USR2 blinks quickly and intermittently while being dim, USR1 stays off, and USR0 continues its heartbeat pattern.
4 - The Octavo chip is starting to get warm. I let it stay that way for 30 more seconds and unplug the USB.

In neither case does the board get recognized from a computer running Ubuntu 16.10. Attempts to browse to the board by going to 192.168.6.2 (while booting with Debian v9.5) failed, but resulted in all 4 LEDs lighting up simultaneously after step 2 of the aforementioned boot process.

I'm at quite a loss as to how to proceed. Any help would be appreciated.

Can't compile .DTS to .DTBO on pocketbeagle

How can I do that ?

4.14 bus error

Previously I was using kernel 4.4 where I was pulling data from an mcp3004 ADC. It worked fine with uio_pruss and setting the pins, but when I upgraded to kernel 4.14 I started getting bus errors. It isn't my wiring or any of my scripts because they are all exactly the same between both kernels. I recompiled everything to see if it might be that, but that didn't work either. Is there something that changed between kernels that I should be looking at?

where's the PocketBeagle's linux kernel?

As you see,I had downloaded the PocketBeagle's image for my SD/TF card,and it runs also.
But I can't do more kernel platform development with the source code of PocketBeagle.
so , where's the source code of PocketBeagle's linux kernel, please?

GPIO44 is incorrectly labelled as GPIO48

Can't boot from SD card

I think my board is booting from the wrong mmc

I've downloaded the latest image from http://beagleboard.org/latest-images for pocketbeagle named Debian 9.3 2018-03-05 4GB SD IoT, then flashed the image to an 8gb sd card using etcher. The board refuses to boot after inserting the card and powering it.

Only the blue PWR led is on, and the octavo chip gets hot.

When I connected a serial monitor to UART0, I found that it is trying to boot from MMC1 not MMC0 (the SD card)

System Reference Manual pin 48 or 44?

Fig. 41 shows the P2 header +3.3V as pin 48 but the next image Fig. 42 shows it as 44 (pin 24 of the P2)
which is it? thanks.

Question on Beaglebone pocket project

We tried to duplicate your pocket Hardware.
Our produced board:
When power is connected, only one LED comes up
Original Pocket Beagle:
When power is connected, only one LED comes up and then other 4 LEDs are up sequencially.

Should we fuse ROM? or EEPROM? to boot it up?
and how to?
Can you share the link if there is any guide for it?

Boot debugging

I'm attempting to boot an existing BeagleBone image I have on an SD card (and then debug to see if there are any require changes for the new board), however I'm not getting any signs of life from the board other than a steady blue LED.

Are there any hardware pins I can use to get serial UART output from the bootloader to debug the boot sequence? Is there any official flow I can follow to get the board to boot from a well-known image?

PinOut Names not working correctly

first of all: really nice board! thank you!

i have a problem with bonescript and the pin names. i try to use the gpio pins from p2.
after a frustrating time where nothing worked with the board. i figured out that i have to update the bonescript module with the latest release from github. (it was not integrated in the lastest debian image)

now i am able to use the "P1_xx" "P2_xx" declaration for the pins without getting just an error.
sadly it does not work properly for all pins, from my testing.

the pin P2_2 and P2_8 working correctly with a pushbutton.
but the pins P2_4 + 6 + 10 do not get any input with the same code.

i try to find the answer with the getPinMode methode but i cannot get a clue out of it.

not working:

{ pin: 'P2_6',
  name: 'GPIO1_25',
  options:
   [ 'gpmc_wpn',
     'gmii2_rxer',
     'gpmc_csn5',
     'rmii2_rxer',
     'mmc2_sdcd',
     'pr1_mii1_txen',
     'uart4_txd',
     'gpio1_25' ],
  gpio: { active: true, direction: 'in', allocated: false } }
mux = undefined
pullup = undefined
slew = undefined
gpio = [object Object]
options = gpmc_wpn,gmii2_rxer,gpmc_csn5,rmii2_rxer,mmc2_sdcd,pr1_mii1_txen,uart4_txd,gpio1_25
pin = P2_6
name = GPIO1_25
err = undefined

working:

{ pin: 'P2_8',
  name: 'GPIO1_28',
  options:
   [ 'gpmc_ben1',
     'mii2_col',
     'NA',
     'mmc2_dat3',
     'NA',
     'NA',
     'mcasp0_aclkr',
     'gpio1_28' ],
  gpio: { active: true, direction: 'in', allocated: false } }
mux = undefined
pullup = undefined
slew = undefined
gpio = [object Object]
options = gpmc_ben1,mii2_col,NA,mmc2_dat3,NA,NA,mcasp0_aclkr,gpio1_28
pin = P2_8
name = GPIO1_28
err = undefined

do you have any idea what i can do, to use this pins?

Graphics out

Hello!
I need to add an HDMI output to the pocketbeagle. (even if it requires a chip like the NXP TDA)

How can I go about that and how could I make it work with linux?
Thank you so much!

Low battery monitoring?

Is there a way to query for the battery status, either a low battery message or voltage output?

Contribution to wiki?

I've managed to work out how to "train" :) the PocketBeagle to share an internet/wifi connection with my Ubuntu 20.04 LTS. Would you be interested in having me add that "how-to" procedure to the Wiki via pull request?

Incorrect pinout diagram label for P2_28 gpio

The pinout image for the pocket beagle has the wrong GPIO pin number for P2_28. It is labelled as 124 but the pocket beagle schematic links it to MCASP0_AXR1. This pin is described on P36 of the data sheet as being gpio3_20. The math (3x32+20) would indicate that this is really pin 116.

The device tree has the correct mapping for P2_28.

gpio = <0x160 0x14 0x0>;

The 0x14 is an offset of 20. This mapping works fine with config-pin to toggle the P2_28 gpio.

Installing gspread error

I am currently running my pocketbeagle with Debian 9.5 2018-10-07 4GB SD IoT,
I have tried a couple of tatorials on how to install gspread with no luck.
I get this error when I run "sudo install pip3 gspread" in the Lenix terminal window using putty.exe

debian@beaglebone:~$ sudo pip3 install gspread
[sudo] password for debian:
Collecting gspread
Exception:
Traceback (most recent call last):
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connection.py", line 138, in _new_conn
(self.host, self.port), self.timeout, **extra_kw)
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/util/connection.py", line 75, in create_connection
for res in socket.getaddrinfo(host, port, family, socket.SOCK_STREAM):
File "/usr/lib/python3.5/socket.py", line 733, in getaddrinfo
for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", line 594, in urlopen
chunked=chunked)
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", line 350, in _make_request
self._validate_conn(conn)
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", line 837, in _validate_conn
conn.connect()
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connection.py", line 281, in connect
conn = self._new_conn()
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connection.py", line 147, in _new_conn
self, "Failed to establish a new connection: %s" % e)
requests.packages.urllib3.exceptions.NewConnectionError: <requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0xb5e20a70>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pip/basecommand.py", line 215, in main
status = self.run(options, args)
File "/usr/lib/python3/dist-packages/pip/commands/install.py", line 353, in run
wb.build(autobuilding=True)
File "/usr/lib/python3/dist-packages/pip/wheel.py", line 749, in build
self.requirement_set.prepare_files(self.finder)
File "/usr/lib/python3/dist-packages/pip/req/req_set.py", line 380, in prepare_files
ignore_dependencies=self.ignore_dependencies))
File "/usr/lib/python3/dist-packages/pip/req/req_set.py", line 554, in _prepare_file
require_hashes
File "/usr/lib/python3/dist-packages/pip/req/req_install.py", line 278, in populate_link
self.link = finder.find_requirement(self, upgrade)
File "/usr/lib/python3/dist-packages/pip/index.py", line 465, in find_requirement
all_candidates = self.find_all_candidates(req.name)
File "/usr/lib/python3/dist-packages/pip/index.py", line 423, in find_all_candidates
for page in self._get_pages(url_locations, project_name):
File "/usr/lib/python3/dist-packages/pip/index.py", line 568, in _get_pages
page = self._get_page(location)
File "/usr/lib/python3/dist-packages/pip/index.py", line 683, in _get_page
return HTMLPage.get_page(link, session=self.session)
File "/usr/lib/python3/dist-packages/pip/index.py", line 792, in get_page
"Cache-Control": "max-age=600",
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py", line 501, in get
return self.request('GET', url, **kwargs)
File "/usr/lib/python3/dist-packages/pip/download.py", line 386, in request
return super(PipSession, self).request(method, url, *args, **kwargs)
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py", line 488, in request
resp = self.send(prep, **send_kwargs)
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/sessions.py", line 609, in send
r = adapter.send(request, **kwargs)
File "/usr/share/python-wheels/CacheControl-0.11.7-py2.py3-none-any.whl/cachecontrol/adapter.py", line 47, in send
resp = super(CacheControlAdapter, self).send(request, **kw)
File "/usr/share/python-wheels/requests-2.12.4-py2.py3-none-any.whl/requests/adapters.py", line 423, in send
timeout=timeout
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/connectionpool.py", line 643, in urlopen
_stacktrace=sys.exc_info()[2])
File "/usr/share/python-wheels/urllib3-1.19.1-py2.py3-none-any.whl/urllib3/util/retry.py", line 315, in increment
total -= 1
TypeError: unsupported operand type(s) for -=: 'Retry' and 'int'

No drive

Hello,

i have a pocketbeagle rev. 18355 i installed the image: https://debian.beagleboard.org/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz. The beagle is booting, but no drive is connected to my windows 10 system. I tried on two systems, but it doesnt work.

I dont know what's the problem? someone can help?

thanks

issue about the CAN Bus of Pocketbeagle

Please can anybody help me? I try to use the can bus with SN65HVD230 can module. I enable the can pins by:
config-pin P2_09 can
config-pin P2_11 can
And then I test loopback, it works. But if I try to communicate with other CAN module, there are no data transmitted or received when I check with ifconfig can0. ( I also try with other CAN pins, but it still cannot work). Do I need other configuration or what' wrong with my operation?

Wrong defaults in pinout diagram?

In the pinout diagram (PocketBeagle_pinout.png), do the dotted lines indicate the default mode? If so, the PRU defaults are wrong (P1_29/31/33/35 and P2_28/30/32/34).

I checked the latest Stretch IoT build (Linux beaglebone 4.4.91-ti-r133 #1 SMP Tue Oct 10 05:18:08 UTC 2017 armv7l GNU/Linux) and these pins come up in GPIO mode, not PRU.