[beagleboard] how to send bitstream file to FPGA from beaglebone web server

[jaziri ibtihel]

Hi 
I want to know is this possible to configure FPGA from beaglebone webserver 
by sending bitstream file.
Thanks

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beagle bone not network/serial accessible over USB in Mac OS X El Capitan

[joshua . a . beam]

Thanks for posting. Hopefully this gets resolved.

On Saturday, October 24, 2015 at 12:34:18 PM UTC-7, Heath Raftery wrote:
>
> To save others the angst, I just wanted to report that on the latest Mac 
> OS X (El Capitan 10.11) the Beaglebone Black is currently not usable via 
> the USB connection, except as a storage device. The alternative is to power 
> it somehow and connect via Ethernet.
>
> Normally there are two methods of console connection via USB: as a virtual 
> network device using HoRNDIS or as a virtual serial device using FTDI USB 
> Serial drivers. Both are thwarted by El Capitan because it enforces kext 
> signing, but for slightly different reasons:
>
>- HoRNDIS simply hasn't been signed for the latest OS, so refuses to 
>load. A preview version that is signed has become available (discussed 
>here: 
>
> http://beagleboard.org/Community/Forums?place=topic%2Fbeagleboard%2Fsp3_x1k5WP8%2Fdiscussion
>  
>and over at the source: https://github.com/jwise/HoRNDIS/issues/42 ) 
>but it does not appear to work with the Beaglebone.
>- FTDI's drivers contain a long list of recognised chips, but the 
>Beaglebone isn't one. Adding support is a simple matter of adding the 
>vendor and product ID to the kext, but unfortunately doing so invalidates 
>the signature and the kext will no longer load!
>
> If anyone discovers improvements on this state of affairs then please let 
> us know. I'll do the same.
>
> Regards,
> Heath
>
>

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Debian 4.1.15-ti-r40 on BBB with LCD touch cursor jumping to right.

[scottellis . developer]

You can connect your button signals to onPressed() instead of onClicked() 
so it just uses the down event.

That's working for me with Qt5/framebuffer/4.1 or 4.4 kernels and a 4DCape 
touchscreen, but the GUI for this app is pretty simple and only has buttons 
for user input.

NewHaven capacitive touchscreens I'm using on other projects behave much 
better.

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Latest image (bone-debian-8.2-tester-2gb-armhf-2015-11-12-2gb.img.xz) not booting on BBW (OK on BBB)

[Stéphane Massot]

Le vendredi 15 janvier 2016 16:16:26 UTC+1, RobertCNelson a écrit :
>
>
>
> On Fri, Jan 15, 2016 at 8:53 AM, Stéphane Massot  > wrote:
>
>> Hello,
>>
>> I have been working on a BBB from the 2015-11-12 image (debian 8.1).
>>
>
> use weekly snapshots from:
>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots
>
> That 8.1 image has known issues..
>

Alright, I moved to the bone-debian-8.2-console-armhf-2016-01-10-2gb image.

But so far I get exactly the same results.

You can find my boot log there : http://pastebin.com/WXuv6Xzm

>  
>
>>
>> It works well, so I tried to use the image in our older beaglebone (BBW) 
>> products, since it is supposed to be compatible.
>>
>
> Works fine here..
>  
>
>>
>> However it doesn't boot ! I've tried again with the vanilla image (the 
>> same image but without my custom modifications), and it doesn't boot either.
>> In fact, it starts the boot operation, and after 1min30, prints some 
>> errors related to the cape manager, and then all the board's lights go off 
>> (even the ethternet LEDs), and it goes radio-silent.
>>
>> You will find attached my complete boot log from the console output on 
>> USB. At first glance, what strikes me is :
>>
>
>
> debug: [/boot/dtbs/4.1.12-ti-r29/am335x-boneblack-emmc-overlay.dtb] ...
>
> Why did you do that?
>
> The White is not the Black...
>
> The White doesn't need the special "overlay.dtb"...
>
> My bad, I had removed the corresponding line from uEnv.txt; but I forgot 
to uncomment "dtb=", so it was still set.

I corrected that, but it didn't solve my problem so far.

Thanks for your help.

Regards,

-- 
Stéphane Massot

>

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to set up multiple w1-gpio for a capeless BeagleBoneBlack?

[Maurice H.]

I've come to the point where I can load the device tree and see that it is 
loaded.
There is however no ID in /sys/devices/w1_bus_master1

Connections I have: GND = P9.1 DATA = P8.11 and VDD = P9.4 (3V3)

For your info I also have a TMP36, DHT22 and BMP183 connected. They all 
seem to work fine.

Do I need to load a kernelmodule I wonder (w1-gpio or something?)
Any suggestions?

Maurice

On Sunday, May 19, 2013 at 7:58:50 AM UTC+2, Russell Senior wrote:
>
> > "Russell" == Russell Senior  
> writes: 
>
> Here's what I did to get a one-wire bus working on BeagleBone Black. 
> I created (modified from the weather cape's) a DTS file: 
>
>   /* 
>   * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/ 
>   * 
>   * This program is free software; you can redistribute it and/or modify 
>   * it under the terms of the GNU General Public License version 2 as 
>   * published by the Free Software Foundation. 
>   */ 
>   /dts-v1/; 
>   /plugin/; 
>
>   / { 
>  compatible = "ti,beaglebone"; 
>  part-number = "BB-BONE-W1"; 
>  version = "00A0"; 
>
>  fragment@0 { 
>  target = <_pinmux>; 
>  __overlay__ { 
>   nocape_w1_pins: pinmux_nocape_w1_pins { 
>   pinctrl-single,pins = < 
>   0x34 0x37   /* 
> gpmc_ad13.gpio1_13, OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */ 
>   >; 
>   }; 
>  }; 
>  }; 
>
>  fragment@1 { 
>  target = <>; 
>  __overlay__ { 
>  onewire@0 { 
>  compatible  = "w1-gpio"; 
>  pinctrl-names   = "default"; 
>  pinctrl-0   = <_w1_pins>; 
>  status  = "okay"; 
>
>  gpios = < 13 0>; 
>  }; 
>  }; 
>  }; 
>   }; 
>
> [...]

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] wi-fi with beaglebone black

[Chibueze Elisha]

*root@beaglebone:~# iwconfig*
wlan0 IEEE 802.11bgn  ESSID:off/any
  Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm
  Retry short limit:7   RTS thr:off   Fragment thr:off
  Encryption key:off
  Power Management:off

lono wireless extensions.

eth0  no wireless extensions.

usb0  no wireless extensions.

can0  no wireless extensions.

can1  no wireless extensions.

I have modified* /etc/network/interfaces* with my network's *ssid *and 
*password*, it looks like this:

  GNU nano 2.2.6File: /etc/network/interfaces   

#hwaddress ether DE:AD:BE:EF:CA:FE

# The secondary network interface
#auto eth1
#iface eth1 inet dhcp

*# WiFi Example*
*auto wlan0*
*iface wlan0 inet dhcp*
*wpa-ssid "homeNet"*
*wpa-psk  "h0mes1stem5"*

# Ethernet/RNDIS gadget (g_ether)
# Used by: /opt/scripts/boot/autoconfigure_usb0.sh
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1

 but after running *"ifup wlan0"*, I get this:

*root@beaglebone:~# ifup wlan0*
Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/00:0c:43:01:0a:7d
Sending on   LPF/wlan0/00:0c:43:01:0a:7d
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


Any ideas on how to fix this?

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

[Mike]

On 01/18/2016 08:00 PM, Dean wrote:

*My BBB setup is as follows ...*
Linux beaglebone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 
2015 armv7l GNU/Linux

BeagleBoard.org Debian Image 2015-11-12

*For whatever reason I cannot access a library (i.e. libEBBLibrary.so) 
and I am not sure what I am missing. Might someone offer a suggestion 
on where I am going wrong or what I can do to rectify it?? Thanks in 
advance who those that reply.*
root@beaglebone:~/exploringBB/chp09/LCDcharacter# sudo sh -c "echo 
BB-SPIDEV1 > $SLOTS"


root@beaglebone:~/exploringBB/chp09/LCDcharacter# cat $SLOTS|grep SPI

4: P-O-L- 0 Override Board Name,00A0,Override Manuf,BB-SPIDEV1



root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./build

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp

./LCDApp: error while loading shared libraries: libEBBLibrary.so: 
cannot open shared object file: No such file or directory



root@beaglebone:~/exploringBB/chp09/LCDcharacter# g++ LCDApp.cpp 
../../library/libEBBLibrary.so -o LCDApp -I "../../library"


root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp

./LCDApp: error while loading shared libraries: libEBBLibrary.so: 
cannot open shared object file: No such file or directory



root@beaglebone:~/exploringBB/chp09/LCDcharacter# echo $PATH

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

root@beaglebone:~/exploringBB/chp09/LCDcharacter# export 
LD_LIBRARY_PATH="../../library/libEBBLibrary.so:$LD_LIBRARY_PATH"

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp
./LCDApp: error while loading shared libraries: libEBBLibrary.so: 
cannot open shared object file: No such file or directory




I don't believe that LD_LIBRARY_PATH is searched in the manner you're 
thinking in the last lines.  If memory serves you need to specify the 
full path from / i.e. absolute not relative.


Mike

--
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

[Robert Nelson]

On Mon, Jan 18, 2016 at 7:00 PM, Dean  wrote:
> My BBB setup is as follows ...
> Linux beaglebone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015
> armv7l GNU/Linux
> BeagleBoard.org Debian Image 2015-11-12
>
> For whatever reason I cannot access a library (i.e. libEBBLibrary.so) and I
> am not sure what I am missing. Might someone offer a suggestion on where I
> am going wrong or what I can do to rectify it?? Thanks in advance who those
> that reply.
> root@beaglebone:~/exploringBB/chp09/LCDcharacter# sudo sh -c "echo
> BB-SPIDEV1 > $SLOTS"
>
> root@beaglebone:~/exploringBB/chp09/LCDcharacter# cat $SLOTS|grep SPI
>
> 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,BB-SPIDEV1
>
>
>
> root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./build
>
> root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp
>
> ./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot
> open shared object file: No such file or directory
>
>
> root@beaglebone:~/exploringBB/chp09/LCDcharacter# g++ LCDApp.cpp
> ../../library/libEBBLibrary.so -o LCDApp -I "../../library"
>
> root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp
>
> ./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot
> open shared object file: No such file or directory
>
>
> root@beaglebone:~/exploringBB/chp09/LCDcharacter# echo $PATH
>
> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
>
> root@beaglebone:~/exploringBB/chp09/LCDcharacter# export
> LD_LIBRARY_PATH="../../library/libEBBLibrary.so:$LD_LIBRARY_PATH"
> root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp
> ./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot
> open shared object file: No such file or directory

Well "No such file or directory"..

and it's not available:

https://packages.debian.org/search?searchon=contents=libEBBLibrary.so=exactfilename=stable=any

So, you better check where you built "LCDApp", and fix your error..

Regards,


-- 
Robert Nelson
https://rcn-ee.com/

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

[Dean]

*My BBB setup is as follows ...* 
Linux beaglebone 4.1.12-ti-r29 #1 SMP PREEMPT Mon Nov 9 22:46:19 UTC 2015 
armv7l GNU/Linux
BeagleBoard.org Debian Image 2015-11-12

*For whatever reason I cannot access a library (i.e. libEBBLibrary.so) and 
I am not sure what I am missing. Might someone offer a suggestion on where 
I am going wrong or what I can do to rectify it?? Thanks in advance who 
those that reply.*
root@beaglebone:~/exploringBB/chp09/LCDcharacter# sudo sh -c "echo 
BB-SPIDEV1 > $SLOTS" 

root@beaglebone:~/exploringBB/chp09/LCDcharacter# cat $SLOTS|grep SPI

4: P-O-L- 0 Override Board Name,00A0,Override Manuf,BB-SPIDEV1



root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./build 

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp

./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot 
open shared object file: No such file or directory


root@beaglebone:~/exploringBB/chp09/LCDcharacter# g++ LCDApp.cpp 
../../library/libEBBLibrary.so -o LCDApp -I "../../library"

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp

./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot 
open shared object file: No such file or directory


root@beaglebone:~/exploringBB/chp09/LCDcharacter# echo $PATH

/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

root@beaglebone:~/exploringBB/chp09/LCDcharacter# export 
LD_LIBRARY_PATH="../../library/libEBBLibrary.so:$LD_LIBRARY_PATH"
root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp 
./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot 
open shared object file: No such file or directory


-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

[Mike]

On 01/18/2016 09:57 PM, William Hermans wrote:
Also, using LD_LIBRARY_PATH in this manner is just flat out wrong. If 
you have a shared library file, put it in the correct directory to 
begin with.


On Mon, Jan 18, 2016 at 6:24 PM, Mike > wrote:




root@beaglebone:~/exploringBB/chp09/LCDcharacter# export 
LD_LIBRARY_PATH="../../library/libEBBLibrary.so:$LD_LIBRARY_PATH"

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp
./LCDApp: error while loading shared libraries: libEBBLibrary.so: 
cannot open shared object file: No such file or directory



I don't believe that LD_LIBRARY_PATH is searched in the manner
you're thinking in the last lines.  If memory serves you need to
specify the full path from / i.e. absolute not relative.

Mike

Exactly my thoughts William.  As a sys admin I've seen way to much LD_* 
abuse not just LD_LIBRARY_PATH...  It's really not that hard on Linux, 
but if following other bad examples, well what can one say? Somewhere 
out there is a great reference on GCC, G++ and using libraries.  The 
title or link eludes me now.  Was from the UK somewhere I believe.


Mike

--
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

[Dean]

All said something else is going on here. libEBBLibrary.so is definitely 
there yet it does not take. I should mention that namespace std is being 
used to make updates on code easier. See code listed below. 


root@beaglebone:~/exploringBB/chp09/LCDcharacter# export 
LD_LIBRARY_PATH="~/exploringBB/library/libEBBLibrary.so:$LD_LIBRARY_PATH"

root@beaglebone:~/exploringBB/chp09/LCDcharacter# ./LCDApp

./LCDApp: error while loading shared libraries: libEBBLibrary.so: cannot 
open shared object file: No such file or directory

root@beaglebone:~/exploringBB/chp09/LCDcharacter# cd ../../library

root@beaglebone:~/exploringBB/library# ls

CMakeLists.txt README build bus display docs example gpio libEBBLibrary.a 
libEBBLibrary.so motor network sensor

root@beaglebone:~/exploringBB/library# 


Here is the code ...


#include 
#include 
#include 
#include "display/LCDCharacterDisplay.h"
using namespace std;
using namespace exploringBB;

int main(){
   cout << "Starting EBB LCD Character Display Example" << endl;
   SPIDevice *busDevice = new SPIDevice(2,0); //Using second SPI bus (both 
loaded)
   busDevice->setSpeed(100);  // Have access to SPI Device object
   ostringstream s;   // Using this to combine text and int 
data
   LCDCharacterDisplay display(busDevice, 16, 2); // Construct 16x2 LCD 
Display
   display.clear();   // Clear the character LCD module
   display.home();// Move the cursor to the (0,0) 
position
   display.print("EBB by D. Molloy"); // String to display on the first row
   for(int x=0; x<=1; x++){   // Do this 10,000 times
  s.str("");  // clear the ostringstream object s
  display.setCursorPosition(1,3); // move the cursor to second row
  s << "X=" << x; // construct a string that has an int 
value
  display.print(s.str()); // print the string X=*** on the LCD 
module
   }
   cout << "End of EBB LCD Character Display Example" << endl;
}


-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] error while loading shared libraries BBB 4.1.12-ti-r29

[Mike]

On 01/18/2016 10:14 PM, Przemek Klosowski wrote:

On Mon, Jan 18, 2016 at 9:57 PM, William Hermans  wrote:

Also, using LD_LIBRARY_PATH in this manner is just flat out wrong. If you
have a shared library file, put it in the correct directory to begin with.

On Mon, Jan 18, 2016 at 6:24 PM, Mike  wrote:

  export LD_LIBRARY_PATH="../../library/libEBBLibrary.so:$LD_LIBRARY_PATH"

Why do you think it's wrong? The point of LD_LIBRARY_PATH is to
collect all the places you might have shared libs, whether system or
application or private.
There's even another trick, using LD_PRELOAD to force certain library
into the image to override symbols from e.g. system libraries; this
works great for debugging.

BTW, if you need to add a library file or directory to a single
application, I'd recommend just setting the environment for this
single command rather than exporting it for general use:

LD_PRELOAD=/home/user/proj/lib/libdebug.so  LCDApp

I'm not going debate the use of LD_LIBRARY_PATH, as an admin all I'll 
say is it's terribly abused and a security nightmare if not used properly.


Your example may well solve his issue and is a workable solution. Noting 
the the path is absolute and not relative...


Mike

--
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Device tree overlay does not affect GPIO pin's state

[Davide Picchi]

1) Reboot the board
2) check whether the cape has been rightly loaded
3) if yes, check the pinmux again.

Your device tree seems ok to me

2016-01-09 9:29 GMT+01:00 :

> Hi all,
>
> I started using Beaglebone Black with Debian 7.9 for my project and I'm
> trying to load my own device-tree overlay in order to get more GPIO pins
> available. I need to use P8.46 pin as GPIO (Mode7) pin. I've disabled HDMI
> cape and then built custom dts to configure P8.46 pin as GPIO pin (mode7,
> output, pull-down):
>
> /dts-v1/;
> /plugin/;
>
>
> /{
> compatible = "ti,beaglebone", "ti,beaglebone-black";
> part_number = "BS_PINMODE_P8_46_0x7";
>
>
> exclusive-use =
> "P8.46",
> "gpio2_7";
>
>
> fragment@0 {
> target = <_pinmux>;
> __overlay__ {
> bs_pinmode_P8_46_0x7: pinmux_bs_pinmode_P8_46_0x7 {
> pinctrl-single,pins = <0x0a4 0x7>;
> };
> };
> };
>
>
> fragment@1 {
> target = <>;
> __overlay__ {
> bs_pinmode_P8_46_0x7_pinmux {
> compatible = "bone-pinmux-helper";
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <_pinmode_P8_46_0x7>;
> };
> };
> };
> };
>
> Then I've compiled dts and put dtbo in /lib/firmware. I can load the
> overlay manually:
>
> root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,bspm_P8_46_7
>
> But when I tried to check pin config I got the next output:
> root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins |
> grep "pin 71"
> pin 71 (44e1091c)  pinctrl-single
>
> What's wrong with my dts why I can't change muxing for the pin? What am I
> missing?
>
> --
> 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
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] OSX el Capitan breaks HoRNDIS?

[joshua . a . beam]

Hey Heath, I am running 10.11.1 on one laptop, and 10.11.2 on another 
laptop. I connected my BBB via USB, installed the drivers, attempted to SSH 
and was unable to connect. I also tried connecting via ethernet and using 
an external power supply, but for some reason I was not able to connect 
that way either.

>From your message it looks like you were able to get it to work on 10.11.1? 
Are you able to SSH via network over USB now?

If all else fails, I have a WiFi dongle coming in the mail today that I am 
going to try...

On Saturday, October 24, 2015 at 2:55:06 PM UTC-7, Heath Raftery wrote:
>
> On Sunday, October 25, 2015 at 6:34:18 AM UTC+11, Heath Raftery wrote:
>>
>> On Wednesday, October 21, 2015 at 2:17:44 AM UTC+11, RobertCNelson wrote:
>>>
>>>
>>> http://nyus.joshuawise.com/HoRNDIS-rel8pre1.pkg 
>>>
>>>
>> Anyone get this version to work? There's certainly progress since the 
>> kext now happily loads. But nothing happens when I plug the Beaglebone in. 
>> In particular, nothing appears in System Preferences -> Network, and 
>> there's no response from 192.168.7.2. Is there another step to turn 
>> "tethering" on in the Beaglebone?
>>
>> Answering my own question: there's nothing more to do, except upgrade to 
> 10.11.1. Then it all just works! 
>

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] OSX el Capitan breaks HoRNDIS?

[Heath Raftery]

Joshua,

Yes, it definitely worked for me on 10.11.1, but I later realised it probably 
had more to do with the restart than the system upgrade. I think even 
restarting the BBB was enough to stop it working, until the next reboot of 
10.11.1. If you have a power supply and an ethernet port handy, then using that 
ought to be a much easier and more reliable method. If I were you, I’d focus on 
getting that working so you’re not thwarted by funky USB tethering shenanigans.

Heath

> On 19 Jan 2016, at 6:53 AM, joshua.a.b...@gmail.com wrote:
> 
> Hey Heath, I am running 10.11.1 on one laptop, and 10.11.2 on another laptop. 
> I connected my BBB via USB, installed the drivers, attempted to SSH and was 
> unable to connect. I also tried connecting via ethernet and using an external 
> power supply, but for some reason I was not able to connect that way either.
> 
> From your message it looks like you were able to get it to work on 10.11.1? 
> Are you able to SSH via network over USB now?
> 
> If all else fails, I have a WiFi dongle coming in the mail today that I am 
> going to try...
> 
> On Saturday, October 24, 2015 at 2:55:06 PM UTC-7, Heath Raftery wrote:
> On Sunday, October 25, 2015 at 6:34:18 AM UTC+11, Heath Raftery wrote:
> On Wednesday, October 21, 2015 at 2:17:44 AM UTC+11, RobertCNelson wrote:
> 
> http://nyus.joshuawise.com/HoRNDIS-rel8pre1.pkg 
>  
> 
> 
> Anyone get this version to work? There's certainly progress since the kext 
> now happily loads. But nothing happens when I plug the Beaglebone in. In 
> particular, nothing appears in System Preferences -> Network, and there's no 
> response from 192.168.7.2. Is there another step to turn "tethering" on in 
> the Beaglebone?
> 
> Answering my own question: there's nothing more to do, except upgrade to 
> 10.11.1. Then it all just works! 
> 
> -- 
> For more options, visit http://beagleboard.org/discuss 
> 
> --- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/beagleboard/sp3_x1k5WP8/unsubscribe 
> .
> To unsubscribe from this group and all its topics, send an email to 
> beagleboard+unsubscr...@googlegroups.com 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] No output voltage on GPIO headers

[Sam Daleo]

I've messed around with device tree overlays a bit, and I'm wondering if I 
could have screwed something up to cause the 3.3 and 5v headers to not 
output voltage? Is there a way to fix this in /sys/ ?

Thanks!

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] No output voltage on GPIO headers

[evilwulfie]

Does the board still boot ?


On 1/18/2016 2:32 PM, Sam Daleo wrote:
>
> I've messed around with device tree overlays a bit, and I'm wondering
> if I could have screwed something up to cause the 3.3 and 5v headers
> to not output voltage? Is there a way to fix this in /sys/ ?
>
> Thanks!
> -- 
> 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 email to beagleboard+unsubscr...@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: bbb startup fails with cape

[Davide Picchi]

Read BBB-SRM paragraph: 6.7 and 8.3
I drive some pins needed for the boot process

Am Freitag, 12. Juni 2015 03:06:10 UTC+2 schrieb luc.d...@gmail.com:
>
> hello all,
> I design a cape for BBB.
> this cape use a lot of of bbb gpio (28 as input - opto isolated, 24 as 
> output - relay).
> I launch some bonescript to work with.
> all works when I plug the cape after bbb has started.
> but if I plug the cape before the bbb start, it does not boot : only the 
> power led swith on. other leds keep off. the bbb won't start.
> I think it is a problem with the bonescript GPIO device tree not loaded at 
> boot time.
> can someone confirm that ?
> do I need an eeprom on my cape to configure device tree on start up ?
> or I will have a chance to do that only programmatically ?
> thank's
>

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] ubuntu doesnt go to desktop

[Davide Picchi]

Did you typed:

$startx

???


But I think you should install a VNC-Server anyway

2016-01-09 16:22 GMT+01:00 :

> hi guys
>
> I want to get ubuntu on my beaglebone black. I write image on micro sd and
> after plugging beaglebone black to power its start booting.
>
> Afterwards i had to type in login and password. Yeah i was logged in.
>
> The problem is i am not getting to desktop
>
> always coming
>
> ubuntu@arm:
>
> So which command i have to type in to start ubuntu?
>
> Pls help
>
> --
> 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
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Device tree overlay does not affect GPIO pin's state

[Davide Picchi]

Sorry I forgot:

you should check with the following command:

root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins |
grep "8a4"

because you have 0x0a4 that is the offset. Ok, now you should add 44e10800
=> 44e108a4
Looking for "8a4" is enough and you ll find the right pin.

Pin 71 is not the right one.

2016-01-18 21:04 GMT+01:00 Davide Picchi :

> 1) Reboot the board
> 2) check whether the cape has been rightly loaded
> 3) if yes, check the pinmux again.
>
> Your device tree seems ok to me
>
> 2016-01-09 9:29 GMT+01:00 :
>
>> Hi all,
>>
>> I started using Beaglebone Black with Debian 7.9 for my project and I'm
>> trying to load my own device-tree overlay in order to get more GPIO pins
>> available. I need to use P8.46 pin as GPIO (Mode7) pin. I've disabled HDMI
>> cape and then built custom dts to configure P8.46 pin as GPIO pin (mode7,
>> output, pull-down):
>>
>> /dts-v1/;
>> /plugin/;
>>
>>
>> /{
>> compatible = "ti,beaglebone", "ti,beaglebone-black";
>> part_number = "BS_PINMODE_P8_46_0x7";
>>
>>
>> exclusive-use =
>> "P8.46",
>> "gpio2_7";
>>
>>
>> fragment@0 {
>> target = <_pinmux>;
>> __overlay__ {
>> bs_pinmode_P8_46_0x7: pinmux_bs_pinmode_P8_46_0x7 {
>> pinctrl-single,pins = <0x0a4 0x7>;
>> };
>> };
>> };
>>
>>
>> fragment@1 {
>> target = <>;
>> __overlay__ {
>> bs_pinmode_P8_46_0x7_pinmux {
>> compatible = "bone-pinmux-helper";
>> status = "okay";
>> pinctrl-names = "default";
>> pinctrl-0 = <_pinmode_P8_46_0x7>;
>> };
>> };
>> };
>> };
>>
>> Then I've compiled dts and put dtbo in /lib/firmware. I can load the
>> overlay manually:
>>
>> root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots
>>  0: 54:PF---
>>  1: 55:PF---
>>  2: 56:PF---
>>  3: 57:PF---
>>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G
>>  5: ff:P-O-- Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI
>>  6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN
>>  7: ff:P-O-L Override Board Name,00A0,Override Manuf,bspm_P8_46_7
>>
>> But when I tried to check pin config I got the next output:
>> root@beaglebone:~# cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pins |
>> grep "pin 71"
>> pin 71 (44e1091c)  pinctrl-single
>>
>> What's wrong with my dts why I can't change muxing for the pin? What am I
>> missing?
>>
>> --
>> 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
>> email to beagleboard+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] OSX el Capitan breaks HoRNDIS?

[William Nickell]

I connected using Ethernet after the USB failed. It worked after a couple of 
tries. Haven’t tried the USB again since recent OS upgrades.

With the Ethernet, I had to use a separate USB supply, but no big deal.

Hopefully, the issue is gone now.



> On Jan 18, 2016, at 2:53 PM, joshua.a.b...@gmail.com wrote:
> 
> Hey Heath, I am running 10.11.1 on one laptop, and 10.11.2 on another laptop. 
> I connected my BBB via USB, installed the drivers, attempted to SSH and was 
> unable to connect. I also tried connecting via ethernet and using an external 
> power supply, but for some reason I was not able to connect that way either.
> 
> From your message it looks like you were able to get it to work on 10.11.1? 
> Are you able to SSH via network over USB now?
> 
> If all else fails, I have a WiFi dongle coming in the mail today that I am 
> going to try...
> 
> On Saturday, October 24, 2015 at 2:55:06 PM UTC-7, Heath Raftery wrote:
> On Sunday, October 25, 2015 at 6:34:18 AM UTC+11, Heath Raftery wrote:
> On Wednesday, October 21, 2015 at 2:17:44 AM UTC+11, RobertCNelson wrote:
> 
> http://nyus.joshuawise.com/HoRNDIS-rel8pre1.pkg 
>  
> 
> 
> Anyone get this version to work? There's certainly progress since the kext 
> now happily loads. But nothing happens when I plug the Beaglebone in. In 
> particular, nothing appears in System Preferences -> Network, and there's no 
> response from 192.168.7.2. Is there another step to turn "tethering" on in 
> the Beaglebone?
> 
> Answering my own question: there's nothing more to do, except upgrade to 
> 10.11.1. Then it all just works! 

Tom Nickell
wnick...@cinci.rr.com



-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Can't connect to Beaglebone after doing a "reboot"

[Davide Picchi]

Yes.
It does it something (more oft than wanted). The reason is that your BBB
gets rebooted but in the process doesn't initialize the eth0. Check in your
router and you'll see the BBB that is not able to get connected with the
internet.

I fixed in the following way:
create a crontab with the following line:

@reboot /etc/init.d/networking restart

There is an old post about this problem. If I find it, I post it here.

Regards

2016-01-16 2:54 GMT+01:00 Markus Huber :

> I am using a Beaglebone for 4 months now and never had this problem. I
> flushed it and installed the new OS (the latest one debian 7.9), then I
> connect to it with
>
> ssh root@192.168.7.2
>
> that works the first time, when I do
>
> shutdown -h now unplug it and replug it again it works.
>
> But when I do
>
> reboot
>
> it reboots but I can't connect or ping it anymore. Once I unplug and
> replug it in, it works again.
>
> Any ideas?
>
> --
> 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
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Enable SPI interface with LCD 7 CAPE

[Marco Laranjeira]

Hi robert.
Many thanks to you. I'll try it tomorrow.
Best regards,
Marco
Em 17/01/2016 23:48, "Robert Nelson"  escreveu:

> On Sun, Jan 17, 2016 at 2:56 PM,   wrote:
> >> Hello there.
> >
> > I'm getting the same problem. did you find any solution for this?
>
> SPI0 share a line with one of the lcd enable pins, while SPI1 shares a
> pin with a key button (which is safe to disable)..
>
> I did a write up here:
>
>
> https://eewiki.net/display/linuxonarm/FLIR+Lepton+on+BeagleBone+Black+and+Green#FLIRLeptononBeagleBoneBlackandGreen-LCD7Setup
>
> Using 4.1.x + bb.org-overlays
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/jmHb8Qh4QOg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.