Hi Wulf Man,
I've added the related dtbo files in /lib/firmware/ and the links I've kept
in the /boot/uEnv.txt as follows:
###Overide capes with eeprom
#uboot_overlay_addr0=/lib/firmware/.dtbo
#uboot_overlay_addr1=/lib/firmware/.dtbo
But, it didn't help!! :(
On Tuesday, 27 February 2018
Thanks for responding!
It is indeed installed, but there is no overlay for the Blue i was able to
find in the list of overlays. the github you linked goes heavily into the
3.x kernels which don't apply to the device tree changes in the 4.9.x and
above kernels. i was hoping an overlay would
universal-io should be installed on that image by default.
you can configure all pins the way you want like this
echo 2 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio2/direction
read up on it on this github
https://github.com/cdsteinkuehler/beaglebone-universal-io
I dont
Having the hardest time with my beaglebone blue. first and foremost, i
followed the instructions after firing the unit up the first time, and
flashed the latest image. Since then, all i can attribute that to is lack
of knowledge on my part.I purchased this board because it had the built in
On Fri, Mar 9, 2018 at 4:03 PM, wrote:
> UART4 sorry for the typo, I am loading BB-UART4-00A0.dtbo not the UART2 one.
> The config-pin solution is working thanks a lot!!
> However, do you know why it is not working with the device tree? I would
> like to understand the
On Wednesday, January 25, 2017 at 9:48:46 AM UTC-8, amar ma'ruf wrote:
>
> Hi, Robert
>
> I'm trying to disable hdmi, and I got clue from this link :
> https://learn.adafruit.com/setting-up-wifi-with-beaglebone-black/hardware
>
> It says that I've to do : - mkdir /mnt/boot
>
UART4 sorry for the typo, I am loading BB-UART4-00A0.dtbo not the UART2
one.
The config-pin solution is working thanks a lot!!
However, do you know why it is not working with the device tree? I would
like to understand the problem
It seems that when I load a device tree it prevents somehow
On Fri, Mar 9, 2018 at 3:43 PM, wrote:
> Hello,
>
> I just wanted to tell you that I am encountering a similar issue, maybe the
> description of it can help.
> I wanted to use UART4 to send information to an Xbee radio, I am enabling it
> by loading the
Hello,
I just wanted to tell you that I am encountering a similar issue, maybe the
description of it can help.
I wanted to use UART4 to send information to an Xbee radio, I am enabling
it by loading the 3BB-UART2-00A0.dtbo3 in uEnv.txt :
###Master Enable
enable_uboot_overlays=1
###
Thanks Robert!.
I wasn't sure what that README statement meant either.
Maybe there's somewhere where a bug report can be issued against their
documentation to clarify...
Regards and see y'all in P.O.
On Thursday, March 8, 2018 at 2:05:00 PM UTC-6, RobertCNelson wrote:
>
> On Thu, Mar 8,
I'd recommend using this one instead
https://github.com/beagleboard/capes/blob/master/README.mediawiki
ESPECIALLY if you can find a better way of visualizing it than GitHub's own
preview.
On Friday, November 10, 2017 at 9:39:00 AM UTC, mike.ma...@gmail.com wrote:
>
> In case somebody is
Actually this is not correct, many pins (especially on P2) are just wrong.
Sorry :(
On Friday, November 10, 2017 at 9:39:00 AM UTC, mike.ma...@gmail.com wrote:
>
> In case somebody is interested in this: attached to my mail you can find a
> detailed pinout of the PocketBeagle expansion header.
Brilliant. Thanks
On Friday, November 10, 2017 at 9:39:00 AM UTC, mike.ma...@gmail.com wrote:
>
> In case somebody is interested in this: attached to my mail you can find a
> detailed pinout of the PocketBeagle expansion header.
>
> This is assembled out of the information of AM3358 TRM and the
In principle the answer is yes.
- first question would be to ask which board with WL18xxMOD on it you would
be planning to connect.
- you would need to use the SPI mode of the WL18xxMOD as there is no space
MMC interface on the pocket beagle. This is normally built with
CONFIG_WLCORE_SPI to
Hello everyone. Long time user, but first time poster here.
I'm currently a final year student at USW (www.southwales.ac.uk/lighting)
and, for one of our final year modules we have to create a product. In
addition to making the thing, for part of our University Project we have to
gather some
Instead of manually configuring the interface, have you considered using ConnMan? AFAIK,
the BeagleBone images ship with ConnMan enabled and the Wi-Fi in AP mode
("tethering" in ConnMan terms).
The command line tool is `connmanctl`. The Arch Linux wiki has a nice page on
how to use it.
On
On Fri, Mar 9, 2018 at 1:49 AM, 'Eric Schm.' via BeagleBoard
wrote:
> I tried to build my own MLO and uboot.img with this commands:
> - make CROSS_COMPILE=arm-linux-gnueabihf- distclean
> - make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf-
> am335x_boneblack_defconfig
On Fri, Mar 9, 2018 at 9:01 AM, Tony Giaccone wrote:
> it seems I spoke too soon.
>
> I now can turn on network sharing on my mac. To keep the pocketbeagle
> connected I have to switch from DHCP to manual on the mac side.
>
> I execute this on the pocketBeagle.
Once you
it seems I spoke too soon.
I now can turn on network sharing on my mac. To keep the pocketbeagle
connected I have to switch from DHCP to manual on the mac side.
I execute this on the pocketBeagle.
$ sudo /sbin/route add default gw 192.168.6.1
but then get this result:
$ ping 8.8.8.8
Is it Possible to interface WILINK 8 with pocket Beagle ?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an
20 matches
Mail list logo