Re: [beagleboard] BBBW wlan0 testing

2017-02-18 Thread Robert Nelson 
On Sat, Feb 18, 2017 at 9:06 PM, Kevin Gordon  wrote:
> I have been trying to resolve what causes a successful setup of connman to
> fail in Beaglebone Black Wireless. These are the steps:
> (1) Make a SDcard using bone-debian-8.7-lxqt-4gb-armhf-2017-02-12-4gb
> (successful)
> (2) Use connmamctl to setup wlan0 (successful)
> (3) #apt-get update #apt-get install leafpad #apt-get install gdbserver
> (successful)
> (4) #nano /boot/uEnv.txt (remove # from
> "dtb=am335x-boneblack-emmc-overlay.dtb")
> (5) reboot
> (5) #ifconfig -a (HEY wlan0 has disappeared and eth0 is now present with no
> internet)
> (6) #nano /boot/uEnv.txt (replace # in front of
> "dtb=am335x-boneblack-emmc-overlay.dtb")
> (7) #reboot
> (8) #ifconfig -a (HEY wlan0 has appeared and eth0 reappeared with internet
> working!)
> @RobertCNelson please help!

So, due to the shear number of *.dtb files, i haven't implemented a
direct "emmc-overlay" specific for the bbbw.

Instead, i've implemented something newer, utilizing U-Boot overlays.

First check what version of U-Boot you have installed via:

debian@test-bbb-1:~$ cd /opt/scripts/
debian@test-bbb-1:/opt/scripts$ git pull
remote: Counting objects: 24, done.
remote: Compressing objects: 100% (15/15), done.
remote: Total 24 (delta 17), reused 16 (delta 9), pack-reused 0
Unpacking objects: 100% (24/24), done.
>From https://github.com/RobertCNelson/boot-scripts
   59138cd..9427614  master -> origin/master
Updating 59138cd..9427614
Fast-forward
 tools/version.sh | 31 +--
 1 file changed, 25 insertions(+), 6 deletions(-)
debian@test-bbb-1:/opt/scripts$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[9427614dddb31f5187bab49e6eda73a2dd722d76]
eeprom:[A335BNLT0A5A1813BBBK3053]
dogtag:[rcn-ee.net console Debian Image 2015-08-17]
bootloader:[/dev/mmcblk0]:[U-Boot 2017.03-rc1-3-gad8008]
kernel:[4.10.0-rc8-omap2plus-r0]

Next take a look at this document:

http://elinux.org/Beagleboard:BeagleBone_Debian_Image_Migration#U-Boot_Overlays

to implement "dtb=am335x-boneblack-emmc-overlay.dtb" for the bbbw use
these options in /boot/uEnv.txt

enable_uboot_overlays=1
disable_uboot_overlay_video=1

(make sure you don't have a /uEnv.txt file as that isn't implemented
with this new method)

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhf22QUK4r_ZnDzKP8QC2FPeQxHa_2HCHW8Ko7a_K3ENg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBBW wlan0 testing

2017-02-18 Thread Kevin Gordon 
Extra item (9) #shutdown no longer is successful. BBBW immediately self 
reboots..

On Sunday, 19 February 2017 16:06:16 UTC+13, Kevin Gordon wrote:
>
> I have been trying to resolve what causes a successful setup of connman to 
> fail in Beaglebone Black Wireless. These are the steps:
> (1) Make a SDcard using bone-debian-8.7-lxqt-4gb-armhf-2017-02-12-4gb 
> (successful)
> (2) Use connmamctl to setup wlan0 (successful)
> (3) #apt-get update #apt-get install leafpad #apt-get install gdbserver 
> (successful)
> (4) #nano /boot/uEnv.txt (remove # from 
> "dtb=am335x-boneblack-emmc-overlay.dtb")
> (5) reboot
> (5) #ifconfig -a (HEY wlan0 has disappeared and eth0 is now present with 
> no internet)
> (6) #nano /boot/uEnv.txt (replace # in front of 
> "dtb=am335x-boneblack-emmc-overlay.dtb")
> (7) #reboot
> (8) #ifconfig -a (HEY wlan0 has appeared and eth0 reappeared with internet 
> working!)
> @RobertCNelson please 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/222abc15-3e93-4fa4-8a96-023e1c8200bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBBW wlan0 testing

2017-02-18 Thread Kevin Gordon 
I have been trying to resolve what causes a successful setup of connman to 
fail in Beaglebone Black Wireless. These are the steps:
(1) Make a SDcard using bone-debian-8.7-lxqt-4gb-armhf-2017-02-12-4gb 
(successful)
(2) Use connmamctl to setup wlan0 (successful)
(3) #apt-get update #apt-get install leafpad #apt-get install gdbserver 
(successful)
(4) #nano /boot/uEnv.txt (remove # from 
"dtb=am335x-boneblack-emmc-overlay.dtb")
(5) reboot
(5) #ifconfig -a (HEY wlan0 has disappeared and eth0 is now present with no 
internet)
(6) #nano /boot/uEnv.txt (replace # in front of 
"dtb=am335x-boneblack-emmc-overlay.dtb")
(7) #reboot
(8) #ifconfig -a (HEY wlan0 has appeared and eth0 reappeared with internet 
working!)
@RobertCNelson please 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/54b6fa56-82bb-4a45-8f74-7de377188451%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBBW connman problems

2017-02-18 Thread tdzamba 
Hello,

Apologies if this is a silly question. I am new to both the beagle bone and 
debian.

I have successfully booted my BBBW using a few different images from 
https://rcn-ee.com/rootfs/bb.org/testing. Everything goes well including 
the initial wifi setup using connman. However, after I configure my wifi 
using a method similar to that mentioned here: 
https://www.ccoderun.ca/programming/2016-12-18_BBBW/index.html#wifi, and I 
reboot, my connman doesn't seem to function the same.

Following a successful boot from a fresh image, and a successful initial 
wifi setup, and then a reboot, I get the following when running sudo 
connmanctl:

Error getting VPN connections: The name net.connman.vpn was not provided by 
any .service filesconnman
Error getting technologies: The name net.connman was not provided by any 
.service filesconnmanctl

I see the following if I then run sudo ifconfig -a

SoftAp0   Link encap:Ethernet  HWaddr 50:65:83:e0:ac:06  
  inet addr:192.168.8.1  Bcast:192.168.8.255  Mask:255.255.255.0
  inet6 addr: fe80::5265:83ff:fee0:ac06/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:28 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:6475 (6.3 KiB)

can0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
  NOARP  MTU:16  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:10 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:196 

can1  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
  NOARP  MTU:16  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:10 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:197 

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:404 errors:0 dropped:0 overruns:0 frame:0
  TX packets:404 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1 
  RX bytes:31907 (31.1 KiB)  TX bytes:31907 (31.1 KiB)

usb0  Link encap:Ethernet  HWaddr 50:65:83:e0:ac:05  
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  inet6 addr: fe80::5265:83ff:fee0:ac05/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:1239 errors:0 dropped:0 overruns:0 frame:0
  TX packets:227 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:190327 (185.8 KiB)  TX bytes:43688 (42.6 KiB)

wlan0 Link encap:Ethernet  HWaddr 50:65:83:e0:ac:03  
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Is this normal behavior, and am I just misunderstanding things?

I have tried flashing my BBBW (fresh from Digi Key) with a few different 
images from https://rcn-ee.com/rootfs/bb.org/testing. I have tried 
2017-02-05, and 2017-02-12, both bone-debian-8.6-lxqt-4gb-armhf versions. 
Both respond the same way in terms of connman behavior following initial 
setup and reboot.

Any advice would be greatly appreciated.

Thanks!

Tom

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/29aee854-b269-4885-aa28-b921a364c6c7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBone Green Board Cannot Connect to Internet

2017-02-18 Thread shunlee . ln 

Got the same problem here before note that Softap0 take the same ip than my 
modem use.
fixing that make the wifi connection stable and running fine.

But from that , no way to got BBG working as an Hotspot. wifidog seem 
blocking the access.
if you have any clues Robert , you're welcome

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/fd517441-cf0b-4dbf-bb4b-aa8c53ef1281%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] xrandr Can't open display

2017-02-18 Thread Przemek Klosowski 
On Fri, Feb 17, 2017 at 6:45 AM, sajeevan k  wrote:

> Now I am able to open a window as per a small qt progam in the LCD display.
>
> But still xrandr is not showing the outputs. It is showing no protocol 
> specified.

How are you running your qt program? Run xrandr in exactly the same
way; it should work.  If it doesn't, describe how you set up your
console, show exactly the commands you're typing and their output

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgGpKN8nSMDqo8vJGuTw5ckCeE3EcaoM-kz5Gh9d54X%2BDg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBBW Wireless Setup

2017-02-18 Thread Robert Nelson 
On Fri, Feb 17, 2017 at 2:14 PM,  wrote:
>
> Hi,
>
>
>   i don't detect the wifi componant WL1835MOD correctly
>
>  i see  eth0 not normal on this board, i should see wlan0
>
>   i watched a lot of tutorials, i didn't see this kind of problem.
>
> I tried 2 systems images :
>  - debian image 2016-11-06 Linux beaglebone 4_4_30_ti_r64
>  - debian image 2017-02-12 Linux beaglebone 4_4_48_ti_r88 (latest image)


Something is fishy with your board, please run:

debian@test-bbb-6:~$ cd /opt/scripts/
debian@test-bbb-6:/opt/scripts$ git pull
Already up-to-date.
debian@test-bbb-6:/opt/scripts$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[9427614dddb31f5187bab49e6eda73a2dd722d76]
eeprom:[A335BNLT0A5B2313BBBK3313]
dogtag:[rcn-ee.net console Debian Image 2015-08-17]
bootloader:[/dev/mmcblk0]:[U-Boot 2017.03-rc1-3-gad8008]
kernel:[4.9.10-bone4]

Regards,

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjUsPvGsALyDOuudYYDSBQCaTA25BNP_hpG_d0%2BuDeUcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Make BBG work as an Hotspot

2017-02-18 Thread Robert Nelson 
On Sat, Feb 18, 2017 at 2:26 PM,   wrote:
> hi all ,
>
> i actually trying to make this board working like an Hotspot ( AP with
> internet forwarding )
> SoftAP set me crazy ...
> Try all i can to have internet , but connected devices still answer :  '
> connected , no internet connection'
>
> clear all iptables , set iptables working for an other board ( pi)
> change dnsmasq parameters .. and still no internet.
>
> Is one of you get better results , I will be happy for any solution
> submited.
>
> Ps:it's a BBGW and i'm trying Wifi to wifi hotspot ( wifi extender )

As long as you have a usb-eth adapter to route everything upstream,
just install the iot image:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_iot

As long as it detects a eth0 device (from your usb-ethernet adapter)
it'll go into AP hotspot mode..

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYibCHkktVM0L2r%3DHotqotEvXc5mktYaxmW4dMvOwVLMpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Make BBG work as an Hotspot

2017-02-18 Thread shunlee . ln 
hi all ,

i actually trying to make this board working like an Hotspot ( AP with 
internet forwarding )
SoftAP set me crazy ... 
Try all i can to have internet , but connected devices still answer :  ' 
connected , no internet connection'

clear all iptables , set iptables working for an other board ( pi)
change dnsmasq parameters .. and still no internet.

Is one of you get better results , I will be happy for any solution 
submited.

Ps:it's a BBGW and i'm trying Wifi to wifi hotspot ( wifi extender )

thanks in advance..



-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5c852f55-d598-447d-acbc-a9e5a4a7dbb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: using desktop window for BBB console

2017-02-18 Thread woody.lois via BeagleBoard 


On Fri, 2/17/17, William Hermans  wrote:

 Subject: Re: [beagleboard] Re: using desktop window for BBB console
 To: beagleboard@googlegroups.com
 Date: Friday, February 17, 2017, 8:10 PM
 
 Just to be clear, I
 rarely recommend Ubuntu. But in the case of being used as a
 desktop. Ubuntu in my mind makes more sense than anything
 else. Debian can run on a desktop system, but that's not
 really where Debian shines. For the purpose of getting a
 Linux "newb" familiar with Linux. Ubuntu will
 probably be more hassle free for you. Debian tends to do
 what it does well, but sometimes it can be much higher
 maintenance. Such as you're finding out now. But if you
 install Ubuntu on that second partition / disk, I bet the
 serial adapter will "just work". Of course I can
 not guarantee that, but an FTDI serial device is something
 all Linuxes should have working, and most will. Debian is a
 bit different because stability is paramount. So if
 something is not 100% reliable, it wont make it into the
 stock kernel. Which is possibly what happened, but maybe
 not.
 
 On Fri, Feb 17, 2017
 at 10:58 AM, William Hermans 
 wrote:
 You can always retrograde to Wheezy, or use one of
 the Ubuntu 14.04 variants.  Personally I lean towards
 Lubuntu when I need a Linux desktop. But I do not use a
 Linux desktop all that often. I like Lubuntu because its
 LXDE that is highly configurable, and fast due to the
 desktop being accelerated. 
 
 On Fri, Feb 17, 2017
 at 10:03 AM, mzimmers 
 wrote:
 On Friday, February 17, 2017 at 9:50:16 AM
 UTC-7, RobertCNelson wrote:
 this looks to be either a kernel, cable or hub problem..
 
  Well, that's not
 good news. There is no hub, the cable works fine under
 Windows, so that leaves the kernel. And, this neophyte
 isn't ready to start mucking around in the
 kernel.
 So...what's a good fallback idea here? I
 don't want to make this a big project, but it would be
 nice if I could get the BBB console output while my desktop
 is booted to Debian. I tried the "screen" command
 that William suggested, and that failed as well (gave a
 "[screen is terminating]" error and
 stopped).
 Is this worthy of reporting as a bug to the
 keepers of Debian? 
 
 
 
 -- 
 
 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+unsubscribe@google
 groups.com.
 
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/beagleboard/7dc33938-ae20-
 4a9f-a9d3-1e853da91596%40googl egroups.com.
 
 For more options, visit https://groups.google.com/d/op
 tout.
 
 
 
 
 
 
 
 
 -- 
 
 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.
 
 To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORoFcr7hm9o0Zmw_n752kY%3D485jT6Jbi7ecEXqfeJzzFLg%40mail.gmail.com.
 
 For more options, visit https://groups.google.com/d/optout.
 n noiembrie 1947  regele  a fost invitat la Londra  la casatoria printesei 
Elisabeta  viitoarea regina Elisabeta a ll-a  cu printul Philip de Grecia'. La

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1268370.1503424.1487364107021%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBBW Wireless Setup

2017-02-18 Thread tvieil59 


Hi, 





  i don't detect the wifi componant WL1835MOD correctly


 i see  eth0 not normal on this board, i should see wlan0

  i watched a lot of tutorials, i didn't see this kind of problem. 

I tried 2 systems images :
 - debian image 2016-11-06 Linux beaglebone 4_4_30_ti_r64
 - debian image 2017-02-12 Linux beaglebone 4_4_48_ti_r88 (latest image)

Here is two screenshots of a terminal 







 


































































 If i use a wifi key on the USB host port, i can use wlan0 correctly.
What can i do to fix this?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d9a6a921-1b95-4f57-9527-eea5fdbb4089%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Help reading MLX90614 with Beaglebone Black

2017-02-18 Thread liam . p . savage 
I switched to a arduino Uno and problem persisted. Then discovered I had read 
the data sheet wrong. The schematic of the pins is looking from the bottom up 
while I had connected as if the schematic was looking at the top downwards. 
Once I connected it correctly, it worked on arduino, raspberry pi and 
beaglebone. I hope that makes sense and I'm not the only one to read it wrong 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/92854e47-36a3-458b-904d-4d727690e753%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBGW how is the initial WIFI setup with AP + client in parallel made?

2017-02-18 Thread sven . bohner 

Hi folks,

I would very appreciate if somebody could explain little quick how to setup 
a AP capable WIFI device like implemented on the BBGW to become an AP and 
at the same time is able to connect to an existing other WIFI network with 
an obviously different network address.

is this a hostapd feature?

What I am looking for is a starting point to learn about this setup. what 
packages are sw necessary for this? 

Thanks a lot for any answer.

I apologize if this topic already exists and I just didn't found it during 
my search. Links welcome.

Sven

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4ab4faab-0bd4-4fcb-b4dd-11bdc1618f87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: UAV Drone out of a BBBW

2017-02-18 Thread 'woody stanford' via BeagleBoard 
Check it.



Here's my drone now. The original design was a bit bulkey and the motors 
were smaller than I thought. Made out of bassword with 1/2" dowel so light 
as heck (its weight is mostly motor and battery, so I know it flies).This 
is what I call the "power section", in other words the drone itself. I have 
a "hardware section" that is the electronics (including my BBBW) and a 
"software section" (I keep driving the solution to softwaremy forte) 
where I'm going to use GCC to do the necessary I2C and UART reads/writes. 
Then I can finally do what I've been wanting to do: have the hardware for 
some deep programming about drone guidance and mathematical models, 
complete with full TCP-IP stack support and a PC's worth of power).


On Monday, January 30, 2017 at 6:19:30 PM UTC-7, woody stanford wrote:
>
> I posted the remote control for this in Software, but I put a bunch of 
> hardware in it so I thought I'd post it here.
>
>
> https://groups.google.com/forum/#!category-topic/beagleboard/software/evSIUcuWfUY
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/07672989-f1ea-4c76-aaaf-2987a19bfee4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working. Wrong device tree overlay?

2017-02-18 Thread robertsmaria934 via BeagleBoard 


On Sat, 2/18/17, robertsmaria934 via BeagleBoard  
wrote:

 Subject: Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working. 
Wrong device tree overlay?
 To: beagleboard@googlegroups.com
 Date: Saturday, February 18, 2017, 6:29 PM
 
 
 
 On Sat, 2/18/17, Mark K Cowan 
 wrote:
 
  Subject: Re: [beagleboard] Re: Microchip mcp2515, can over
 spi, not working. Wrong device tree overlay?
  To: "BeagleBoard" 
  Date: Saturday, February 18, 2017, 5:16 PM
  
  I solved it with my
  own devicetree overlay, loaded after the BB-SPIDEV0
 overlay.
   It's available
  at https://github.com/battlesnake/beaglebone-spi0-mcp2515
  
  On Saturday, 18 February 2017 14:22:19 UTC, Laurits Telle
  Riple  wrote:Hi!
  I got it to work, but not using the mainline
  driver. I bought a cape from towertech to be sure that my
  hardware was correct. They shipped the device with some
  modified version of the driver. Got some help in the
 beagle
  irc chat to try to find the origin of that driver. IIRC
 the
  driver was based on a driver from many years ago, but it
  works. I have not tested it over a long period, but it
 seems
  to work. I am currently trying to get it to work with the
  mainline driver, but its not my top priority right now.
  There has been several changes to the mainline driver
 since
  I tried to use it the last time, so i hope it will work
 next
  time I try it. With the towertech driver I managed to get
 it
  to work, both by using a overlay and just making my own
 DT.
  Should be instructions on how to compile if you download
  from these links. And I think there is a dto in the zip as
  well. If I get it to work with the mainline, I will update
  this thread.
  Btw. Some other guy on irc did not get this
  driver to work with his old rev of the can cape. I think I
  have rev5. Should work with that.
   TT3201 driver for Debian 7.x
  / Kernel 3.x
  
  
    *
  TT3201 driver for Debian 8.x / Kernel 4.x
  
  
  
  tirsdag 14. februar 2017 16.11.56 UTC+1 skrev Mark K Cowan
  følgende:Hi,
  Did you ever get the MCP2515 working over SPI?
   I'm attempting that now, but I'm not sure where to
  start.
  Thanks,  Mark
  
  
  On Tuesday, 20 September 2016 14:30:39 UTC+1, Laurits
 Telle
  Riple  wrote:After chatting in
  the IRC channel with Matthijs I was encouraged to not use
  overlays, and just make my own dtb.  I have tried that
 now,
  but it doesn't seem to work properly. I've enabled
  spi0 and spi1. And used the spi_loopback to see that my
 dtb
  was working, then i expanded it by adding a clock node and
  adding the mcp in the spi config. Also, the max14830 not
  working, maybe the same issue? Anyways, this is my
  dtb: 
  /* * 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/;
  #include
  "am33xx.dtsi"#include
  "am335x-bone-common.dtsi"#include
  "am33xx-overlay-edma-fix.dtsi"#include
  "irq.h"
  /
  {        model =
  "TI AM335x BeagleBone
  Black";     
    compatible = "ti,am335x-bone-black",
  "ti,am335x-bone",
  "ti,am33xx";
         
  clk16m:clk16m{   
              compatible =
  "fixed-clock";                clock-frequency =
  <1600>; 
                #clock-cells =
  <0>;     
    };
         
  clk4m:clk4m{     
            compatible =
  "fixed-clock";                clock-frequency =
  <400>; 
                #clock-cells =
  <0>;     
    };};
  _reg
  {       
  regulator-min-microvolt =
  <180>; 
        regulator-max-microvolt =
  <180>; 
        regulator-always-on;};
  
  {       
  vmmc-supply =
  <_fixed>;};
  
  {       
  vmmc-supply =
  <_fixed>;        pinctrl-names =
  "default";        pinctrl-0 =
  <_pins>;        bus-width =
  <8>;     
    status = "okay";};
  _opp_table
  {       
  /*         *
  All PG 2.0 silicon may not support 1GHz but some of the
  early         *
  BeagleBone Blacks have PG 2.0 silicon which is
  guaranteed     
     * to support 1GHz OPP so enable it for PG 2.0 on this
  board.       
   */       
  oppnitro@10
 {                opp-supported-hw =
  <0x06 0x0100>;        };};
  
  _pinmux{       
  spi1_pins:spi1_pins{               
  pinctrl-single,pins=<                       
 0x190
  0x33  /* mcasp0_aclkx.spi1_sclk,  OUTPUT_PULLUP | MODE 3
  */           
              0x194 0x33  /* mcasp0_fsx.spi1_d0,  
  
   INPUT_PULLUP | MODE3 */                     
   0x198
  0x13  /* mcasp0_axr0.spi1_d1,     OUTPUT_PULLUP | MODE
 3

Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working. Wrong device tree overlay?

2017-02-18 Thread robertsmaria934 via BeagleBoard 


On Sat, 2/18/17, Mark K Cowan  wrote:

 Subject: Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working. 
Wrong device tree overlay?
 To: "BeagleBoard" 
 Date: Saturday, February 18, 2017, 5:16 PM
 
 I solved it with my
 own devicetree overlay, loaded after the BB-SPIDEV0 overlay.
  It's available
 at https://github.com/battlesnake/beaglebone-spi0-mcp2515
 
 On Saturday, 18 February 2017 14:22:19 UTC, Laurits Telle
 Riple  wrote:Hi!
 I got it to work, but not using the mainline
 driver. I bought a cape from towertech to be sure that my
 hardware was correct. They shipped the device with some
 modified version of the driver. Got some help in the beagle
 irc chat to try to find the origin of that driver. IIRC the
 driver was based on a driver from many years ago, but it
 works. I have not tested it over a long period, but it seems
 to work. I am currently trying to get it to work with the
 mainline driver, but its not my top priority right now.
 There has been several changes to the mainline driver since
 I tried to use it the last time, so i hope it will work next
 time I try it. With the towertech driver I managed to get it
 to work, both by using a overlay and just making my own DT.
 Should be instructions on how to compile if you download
 from these links. And I think there is a dto in the zip as
 well. If I get it to work with the mainline, I will update
 this thread.
 Btw. Some other guy on irc did not get this
 driver to work with his old rev of the can cape. I think I
 have rev5. Should work with that.
  TT3201 driver for Debian 7.x
 / Kernel 3.x
 
 
   *
 TT3201 driver for Debian 8.x / Kernel 4.x
 
 
 
 tirsdag 14. februar 2017 16.11.56 UTC+1 skrev Mark K Cowan
 følgende:Hi,
 Did you ever get the MCP2515 working over SPI?
  I'm attempting that now, but I'm not sure where to
 start.
 Thanks,  Mark
 
 
 On Tuesday, 20 September 2016 14:30:39 UTC+1, Laurits Telle
 Riple  wrote:After chatting in
 the IRC channel with Matthijs I was encouraged to not use
 overlays, and just make my own dtb.  I have tried that now,
 but it doesn't seem to work properly. I've enabled
 spi0 and spi1. And used the spi_loopback to see that my dtb
 was working, then i expanded it by adding a clock node and
 adding the mcp in the spi config. Also, the max14830 not
 working, maybe the same issue? Anyways, this is my
 dtb: 
 /* * 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/;
 #include
 "am33xx.dtsi"#include
 "am335x-bone-common.dtsi"#include
 "am33xx-overlay-edma-fix.dtsi"#include
 "irq.h"
 /
 {        model =
 "TI AM335x BeagleBone
 Black";     
   compatible = "ti,am335x-bone-black",
 "ti,am335x-bone",
 "ti,am33xx";
        
 clk16m:clk16m{   
             compatible =
 "fixed-clock";                clock-frequency =
 <1600>; 
               #clock-cells =
 <0>;     
   };
        
 clk4m:clk4m{     
           compatible =
 "fixed-clock";                clock-frequency =
 <400>; 
               #clock-cells =
 <0>;     
   };};
 _reg
 {       
 regulator-min-microvolt =
 <180>; 
       regulator-max-microvolt =
 <180>; 
       regulator-always-on;};
 
 {       
 vmmc-supply =
 <_fixed>;};
 
 {       
 vmmc-supply =
 <_fixed>;        pinctrl-names =
 "default";        pinctrl-0 =
 <_pins>;        bus-width =
 <8>;     
   status = "okay";};
 _opp_table
 {       
 /*         *
 All PG 2.0 silicon may not support 1GHz but some of the
 early         *
 BeagleBone Blacks have PG 2.0 silicon which is
 guaranteed     
    * to support 1GHz OPP so enable it for PG 2.0 on this
 board.       
  */       
 oppnitro@10 {                opp-supported-hw =
 <0x06 0x0100>;        };};
 
 _pinmux{       
 spi1_pins:spi1_pins{               
 pinctrl-single,pins=<                        0x190
 0x33  /* mcasp0_aclkx.spi1_sclk,  OUTPUT_PULLUP | MODE 3
 */           
             0x194 0x33  /* mcasp0_fsx.spi1_d0,    
  INPUT_PULLUP | MODE3 */                        0x198
 0x13  /* mcasp0_axr0.spi1_d1,     OUTPUT_PULLUP | MODE 3
 */           
             0x19c 0x13  /* mcasp0_ahclkr.spi1_cs0,
  OUTPUT_PULLUP | MODE3 */               
 >;       
 };       
 spi0_pins:spi0_pins{               
 pinctrl-single,pins=<                        0x150
 0x30  /* spi0_sclk, INPUT_PULLUP | MODE0
 */           
             0x154 0x30  /* spi0_d0, INPUT_PULLUP |
 MODE0 */       
                 0x158 0x10  /* spi0_d1,
 OUTPUT_PULLUP | MODE0 */                        0x15c
 0x10  /* spi0_cs0, OUTPUT_PULLUP |

Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working. Wrong device tree overlay?

2017-02-18 Thread Mark K Cowan 
I solved it with my own devicetree overlay, loaded after the BB-SPIDEV0 
overlay.  It's available 
at https://github.com/battlesnake/beaglebone-spi0-mcp2515

On Saturday, 18 February 2017 14:22:19 UTC, Laurits Telle Riple wrote:
>
> Hi!
>
> I got it to work, but not using the mainline driver. I bought a cape from 
> towertech to be sure that my hardware was correct. They shipped the device 
> with some modified version of the driver. Got some help in the beagle irc 
> chat to try to find the origin of that driver. IIRC the driver was based on 
> a driver from many years ago, but it works. I have not tested it over a 
> long period, but it seems to work. I am currently trying to get it to work 
> with the mainline driver, but its not my top priority right now. There has 
> been several changes to the mainline driver since I tried to use it the 
> last time, so i hope it will work next time I try it. With the towertech 
> driver I managed to get it to work, both by using a overlay and just making 
> my own DT. Should be instructions on how to compile if you download from 
> these links. And I think there is a dto in the zip as well. If I get it to 
> work with the mainline, I will update this thread.
>
> Btw. Some other guy on irc did not get this driver to work with his old 
> rev of the can cape. I think I have rev5. Should work with that.
>
>  TT3201 driver for Debian 7.x / Kernel 3.x
> <
> https://dl.dropboxusercontent.com/u/2883083/TowerTech/towertech-tt3201-rev5.tar.gz
> >
>
>   * TT3201 driver for Debian 8.x / Kernel 4.x
> <
> https://dl.dropboxusercontent.com/u/2883083/TowerTech/towertech-tt3201-rev5-kernel-4.x.tar.gz
> >
>
>
> tirsdag 14. februar 2017 16.11.56 UTC+1 skrev Mark K Cowan følgende:
>>
>> Hi,
>>
>> Did you ever get the MCP2515 working over SPI?  I'm attempting that now, 
>> but I'm not sure where to start.
>>
>> Thanks,
>>   Mark
>>
>>
>>
>> On Tuesday, 20 September 2016 14:30:39 UTC+1, Laurits Telle Riple wrote:
>>>
>>> After chatting in the IRC channel with Matthijs I was encouraged to not 
>>> use overlays, and just make my own dtb.  I have tried that now, but it 
>>> doesn't seem to work properly. I've enabled spi0 and spi1. And used the 
>>> spi_loopback to see that my dtb was working, then i expanded it by adding a 
>>> clock node and adding the mcp in the spi config. Also, the max14830 not 
>>> working, maybe the same issue? Anyways, this is my dtb: 
>>>
>>> /*
>>>  * 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/;
>>>
>>> #include "am33xx.dtsi"
>>> #include "am335x-bone-common.dtsi"
>>> #include "am33xx-overlay-edma-fix.dtsi"
>>> #include "irq.h"
>>>
>>> / {
>>> model = "TI AM335x BeagleBone Black";
>>> compatible = "ti,am335x-bone-black", "ti,am335x-bone", 
>>> "ti,am33xx";
>>>
>>> clk16m:clk16m{
>>> compatible = "fixed-clock";
>>> clock-frequency = <1600>;
>>> #clock-cells = <0>;
>>> };
>>>
>>> clk4m:clk4m{
>>> compatible = "fixed-clock";
>>> clock-frequency = <400>;
>>> #clock-cells = <0>;
>>> };
>>> };
>>>
>>> _reg {
>>> regulator-min-microvolt = <180>;
>>> regulator-max-microvolt = <180>;
>>> regulator-always-on;
>>> };
>>>
>>>  {
>>> vmmc-supply = <_fixed>;
>>> };
>>>
>>>  {
>>> vmmc-supply = <_fixed>;
>>> pinctrl-names = "default";
>>> pinctrl-0 = <_pins>;
>>> bus-width = <8>;
>>> status = "okay";
>>> };
>>>
>>> _opp_table {
>>> /*
>>>  * All PG 2.0 silicon may not support 1GHz but some of the early
>>>  * BeagleBone Blacks have PG 2.0 silicon which is guaranteed
>>>  * to support 1GHz OPP so enable it for PG 2.0 on this board.
>>>  */
>>> oppnitro@10 {
>>> opp-supported-hw = <0x06 0x0100>;
>>> };
>>> };
>>>
>>>
>>> _pinmux{
>>> spi1_pins:spi1_pins{
>>> pinctrl-single,pins=<
>>> 0x190 0x33  /* mcasp0_aclkx.spi1_sclk, 
>>>  OUTPUT_PULLUP | MODE 3 */
>>> 0x194 0x33  /* mcasp0_fsx.spi1_d0, 
>>>  INPUT_PULLUP | MODE3 */
>>> 0x198 0x13  /* mcasp0_axr0.spi1_d1, 
>>> OUTPUT_PULLUP | MODE 3 */
>>> 0x19c 0x13  /* mcasp0_ahclkr.spi1_cs0, 
>>>  OUTPUT_PULLUP | MODE3 */
>>> >;
>>> };
>>> spi0_pins:spi0_pins{
>>> pinctrl-single,pins=<
>>> 0x150 0x30  /* spi0_sclk, INPUT_PULLUP | MODE0 */
>>> 0x154 0x30  /* spi0_d0, INPUT_PULLUP | MODE0 */
>>> 0x158 0x10  /* spi0_d1, OUTPUT_PULLUP

Re: [beagleboard] Re: Microchip mcp2515, can over spi, not working. Wrong device tree overlay?

2017-02-18 Thread Laurits Telle Riple 
Hi!

I got it to work, but not using the mainline driver. I bought a cape from 
towertech to be sure that my hardware was correct. They shipped the device 
with some modified version of the driver. Got some help in the beagle irc 
chat to try to find the origin of that driver. IIRC the driver was based on 
a driver from many years ago, but it works. I have not tested it over a 
long period, but it seems to work. I am currently trying to get it to work 
with the mainline driver, but its not my top priority right now. There has 
been several changes to the mainline driver since I tried to use it the 
last time, so i hope it will work next time I try it. With the towertech 
driver I managed to get it to work, both by using a overlay and just making 
my own DT. Should be instructions on how to compile if you download from 
these links. And I think there is a dto in the zip as well. If I get it to 
work with the mainline, I will update this thread.

Btw. Some other guy on irc did not get this driver to work with his old rev 
of the can cape. I think I have rev5. Should work with that.

 TT3201 driver for Debian 7.x / Kernel 3.x
<
https://dl.dropboxusercontent.com/u/2883083/TowerTech/towertech-tt3201-rev5.tar.gz
>

  * TT3201 driver for Debian 8.x / Kernel 4.x
<
https://dl.dropboxusercontent.com/u/2883083/TowerTech/towertech-tt3201-rev5-kernel-4.x.tar.gz
>


tirsdag 14. februar 2017 16.11.56 UTC+1 skrev Mark K Cowan følgende:
>
> Hi,
>
> Did you ever get the MCP2515 working over SPI?  I'm attempting that now, 
> but I'm not sure where to start.
>
> Thanks,
>   Mark
>
>
>
> On Tuesday, 20 September 2016 14:30:39 UTC+1, Laurits Telle Riple wrote:
>>
>> After chatting in the IRC channel with Matthijs I was encouraged to not 
>> use overlays, and just make my own dtb.  I have tried that now, but it 
>> doesn't seem to work properly. I've enabled spi0 and spi1. And used the 
>> spi_loopback to see that my dtb was working, then i expanded it by adding a 
>> clock node and adding the mcp in the spi config. Also, the max14830 not 
>> working, maybe the same issue? Anyways, this is my dtb: 
>>
>> /*
>>  * 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/;
>>
>> #include "am33xx.dtsi"
>> #include "am335x-bone-common.dtsi"
>> #include "am33xx-overlay-edma-fix.dtsi"
>> #include "irq.h"
>>
>> / {
>> model = "TI AM335x BeagleBone Black";
>> compatible = "ti,am335x-bone-black", "ti,am335x-bone", 
>> "ti,am33xx";
>>
>> clk16m:clk16m{
>> compatible = "fixed-clock";
>> clock-frequency = <1600>;
>> #clock-cells = <0>;
>> };
>>
>> clk4m:clk4m{
>> compatible = "fixed-clock";
>> clock-frequency = <400>;
>> #clock-cells = <0>;
>> };
>> };
>>
>> _reg {
>> regulator-min-microvolt = <180>;
>> regulator-max-microvolt = <180>;
>> regulator-always-on;
>> };
>>
>>  {
>> vmmc-supply = <_fixed>;
>> };
>>
>>  {
>> vmmc-supply = <_fixed>;
>> pinctrl-names = "default";
>> pinctrl-0 = <_pins>;
>> bus-width = <8>;
>> status = "okay";
>> };
>>
>> _opp_table {
>> /*
>>  * All PG 2.0 silicon may not support 1GHz but some of the early
>>  * BeagleBone Blacks have PG 2.0 silicon which is guaranteed
>>  * to support 1GHz OPP so enable it for PG 2.0 on this board.
>>  */
>> oppnitro@10 {
>> opp-supported-hw = <0x06 0x0100>;
>> };
>> };
>>
>>
>> _pinmux{
>> spi1_pins:spi1_pins{
>> pinctrl-single,pins=<
>> 0x190 0x33  /* mcasp0_aclkx.spi1_sclk, 
>>  OUTPUT_PULLUP | MODE 3 */
>> 0x194 0x33  /* mcasp0_fsx.spi1_d0, 
>>  INPUT_PULLUP | MODE3 */
>> 0x198 0x13  /* mcasp0_axr0.spi1_d1, 
>> OUTPUT_PULLUP | MODE 3 */
>> 0x19c 0x13  /* mcasp0_ahclkr.spi1_cs0, 
>>  OUTPUT_PULLUP | MODE3 */
>> >;
>> };
>> spi0_pins:spi0_pins{
>> pinctrl-single,pins=<
>> 0x150 0x30  /* spi0_sclk, INPUT_PULLUP | MODE0 */
>> 0x154 0x30  /* spi0_d0, INPUT_PULLUP | MODE0 */
>> 0x158 0x10  /* spi0_d1, OUTPUT_PULLUP | MODE0 */
>> 0x15c 0x10  /* spi0_cs0, OUTPUT_PULLUP | MODE0 */
>> >;
>> };
>> mcp2515_pins:mcp2515_pins{
>> pinctrl-single,pins=<
>> 0x1ac 0x37 /*mcasp0_ahclkx.gpio3_21,RX_ENABLED | 
>> PULLUP | MODE7 */
>> >;
>> };
>> max14830_pins:max14830_pins{
>>