Re: [beagleboard] UART1 using BB-UART1 vs cape-universal

[Brian Anderson]

OK, thanks Robert. I'll try an updated kernel and see what happens. 


Issue fixed on 4.1.17-ti-rt-r46.  Thanks!
 

> Curious, what was the issue and why didn't it manifest itself with the 
> different settings in cape-universal?
>
> Still interested in why the pull-up/pull-down values are different in 
> cape-universal vs BB-UART.
>
> ba
>
>

-- 
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: Beaglebone Cloud9 Default User

[Wally Bkg]

I'm not very experienced with Cloud9 or BoneScript, but as I understand it, 
at present BoneScript is only usable for code running as root because of 
device driver permissions.  Also BoneScript PWM is not working in the 
"latest" versions.

While this is not optimal, adding user permissions into the mix would 
likely overwhelm people coming from Arduino.  Raspberry Pi currently has 
basically the same setup where only root users can use on board hardware, 
unless its changed with a new Raspbian release recently.
 
Are you accessing Cloud9 via the USB "gadget" or Ethernet (Wired or WiFi)?  
I might make a difference.


On Thursday, January 7, 2016 at 3:42:01 PM UTC-6, Paul Wolfson wrote:
>
> I've been using my BBB for some time with Ubuntu 3.8.13-bone30 but 
> upgraded to Debian 4.1.12-ti-r29 because of OS stability problems.  The 
> Cloud9 IDE is back.  I opened it and saw a command shell prompt running as 
> root@beaglebone.
>
> Does anyone know off the top of their head where the default user is set?
>
> I saw this, 
> http://stackoverflow.com/questions/28822695/change-the-username-and-add-a-password-for-cloud9-in-the-beaglebone-black
>  but 
> after changing 
> .describe("auth", "Basic Auth username:password")
> to
> .describe("auth", "debian:temppwd")
>
> and rebooting, the Cloud9 bash prompt is still "root@beaglebone:~# ."
>
> [if this is a double post, I apologize]
>
>

-- 
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: DHT11 Grove on Beaglebone and general impression on Beaglebone

[Jean-Bernard Boichat]

The BeagleBone community forum is not too active, sure. It's a pity for 
such a good board and concept.
I found today one or two good articles like "Is BoneScript more trouble 
than its worth?"
I have myself problem every 4-5 days with a Bonescript Web server 
distributing my sensor data, where I have to add soon a watchdog (a for 
loop does not help). 

With IRC channel, your probably means I2C. Voltage and resistors, it's 
clear.
Then, it's a question of hardware and conditions, like a DS18B20 on my BBB 
with 5V over a 5 meters cable ... and works as a charm.

Anyway, that was not my question here, dealing with the software only.

*I believe I found it an hour 
ago: https://github.com/adafruit/Adafruit_Python_DHT 
*

For the humidity I do not need precision, and for the temperature I will 
probably add an LM35 or DS18B20.
On my BBB I implemented in Python a function to read many times the two 
LM35 (2m cables!!), to remove the highest and lowest values, and to compute 
the average: great result with precision of about .5 degrees are far 
sufficient.

Thanks Robert: I just consulted now a number of your documents. Very good 
work!
Regards Robert ... and the others  

Le jeudi 4 février 2016 18:58:11 UTC+1, RobertCNelson a écrit :
>
> On Thu, Feb 4, 2016 at 11:49 AM, Jean-Bernard Boichat 
>  wrote: 
> > 
> > Just see now that this blog is not too active!!!???!!! 
>
> Expecting a response in under 2 minutes? 
>
> Use the irc channel for that.. 
>
> -- 
> 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.

Re: [beagleboard] Re: Beaglebone Cloud9 Default User

[Paul Wolfson]

I very much appreciate the reply.  I was accessing Cloud9 through eth0 not
usb0 so root access from the network was possible.  Were I only accessing
the BeagleBone over the usb network I wouldn't have been concerned.
However I remotely connected over port 3000 and saw a command line running
with root.

I tried chasing down the problem but found the Cloud9 IDE just too
convoluted to figure out.  I tried but failed to change the default user
and password in the configuration file referred to in my earlier post.  At
that point I simply killed Cloud9, and just used Byobu (tmux) terminals to
work with node.js.

In the latest build Debian r43 build Cloud9 is not installed by default so
it's all good.  Robert's little connmanctl tutorial post yesterday made
networking much easier than messing with /etc/network/interfaces.

-
Paul Wolfson, Ph.D., TX LPI, #A17473
Editor, TALI "The Texas Investigator"
Dallas Legal Technology
3402 Oak Grove Avenue, Suite 300-A
Dallas, Texas 75204-2353


*214-257-0984 (Tel)214-838-7220 (Fax)Send me an email. *
-
The contents of this email are confidential to the sender and the ordinary
user of the email address to which it was addressed, and may also be
privileged.  If you are not the addressee of the email, you may not copy,
forward, disclose or otherwise use it or any part of it in any form
whatsoever.  If you have received this email in error, please advise the
sender at  214-257-0984.  Thank you.
-

On Fri, Feb 5, 2016 at 11:21 AM, Wally Bkg  wrote:

> I'm not very experienced with Cloud9 or BoneScript, but as I understand
> it, at present BoneScript is only usable for code running as root because
> of device driver permissions.  Also BoneScript PWM is not working in the
> "latest" versions.
>
> While this is not optimal, adding user permissions into the mix would
> likely overwhelm people coming from Arduino.  Raspberry Pi currently has
> basically the same setup where only root users can use on board hardware,
> unless its changed with a new Raspbian release recently.
>
> Are you accessing Cloud9 via the USB "gadget" or Ethernet (Wired or
> WiFi)?  I might make a difference.
>
>
>
> On Thursday, January 7, 2016 at 3:42:01 PM UTC-6, Paul Wolfson wrote:
>>
>> I've been using my BBB for some time with Ubuntu 3.8.13-bone30 but
>> upgraded to Debian 4.1.12-ti-r29 because of OS stability problems.  The
>> Cloud9 IDE is back.  I opened it and saw a command shell prompt running as
>> root@beaglebone.
>>
>> Does anyone know off the top of their head where the default user is set?
>>
>> I saw this,
>> http://stackoverflow.com/questions/28822695/change-the-username-and-add-a-password-for-cloud9-in-the-beaglebone-black
>>  but
>> after changing
>> .describe("auth", "Basic Auth username:password")
>> to
>> .describe("auth", "debian:temppwd")
>>
>> and rebooting, the Cloud9 bash prompt is still "root@beaglebone:~# ."
>>
>> [if this is a double post, I apologize]
>>
>> --
> 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: DHT11 Grove on Beaglebone and general impression on Beaglebone

[Robert Nelson]

On Fri, Feb 5, 2016 at 10:51 AM, Przemek Klosowski
 wrote:
> On Fri, Feb 5, 2016 at 10:34 AM, Jean-Bernard Boichat
>  wrote:
>> The BeagleBone community forum is not too active, sure. It's a pity for such
>> a good board and concept.
>
> Are you participating in this discussion by sending email to
> beagleboard@googlegroups.com, or via some other way? I see it as an
> email stream of a dozen or so messages a day. I'd call it pretty
> active.
>
>> I found today one or two good articles like "Is BoneScript more trouble than 
>> its worth?"
>> I have myself problem every 4-5 days with a Bonescript Web server
>> distributing my sensor data, where I have to add soon a watchdog
>
> Do you require constant running, or do you sleep and run? If the
> latter, you probably should respawn a fresh interpreter each time, do
> the work and quit---otherwise you are at the mercy of memory leaks
> that are hard to avoid in an interpreter.
>
>
>> With IRC channel, your probably means I2C. Voltage and resistors, it's clear.
>
> No, IRC is the Internet Relay Chat software, a distributed chat
> application that developers tend to use. When people log in into IRC,
> they tend to watch it in real time, so potentially It provides more
> immediate communication. This list is email-based so everyone has to
> actively go and check the new emails.
>
>> Then, it's a question of hardware and conditions, like a DS18B20 on my BBB 
>> with 5V over a 5 meters cable ... and works as a charm.
>
> If you place an analog voltage greater than 1.8 Volts on the analog
> input pin of the BBB, you will destroy that input. This is different
> from DS18B20, which has a digital one-wire interface using I think
> standard 3.3V digital signaling. Note that 5V is too much: you need to
> drop the voltage to 3.3V even for digital signals.

and it looks like mis-read the data sheet... the dh11 actually is a
simple bus, i first thought it was analog out..

It can be powered by 3.3v and there is kernel driver for this:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/iio/humidity/dht11.c?id=refs/tags/v4.5-rc2

and the dt bindings:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/iio/humidity/dht11.txt

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.

Re: [beagleboard] Re: DHT11 Grove on Beaglebone and general impression on Beaglebone

[Jean-Bernard Boichat]

Thanks a lot Robert

Le vendredi 5 février 2016 18:10:34 UTC+1, RobertCNelson a écrit :
>
> On Fri, Feb 5, 2016 at 10:51 AM, Przemek Klosowski 
>  wrote: 
> > On Fri, Feb 5, 2016 at 10:34 AM, Jean-Bernard Boichat 
> >  wrote: 
> >> The BeagleBone community forum is not too active, sure. It's a pity for 
> such 
> >> a good board and concept. 
> > 
> > Are you participating in this discussion by sending email to 
> > beagl...@googlegroups.com , or via some other way? I see 
> it as an 
> > email stream of a dozen or so messages a day. I'd call it pretty 
> > active. 
> > 
> >> I found today one or two good articles like "Is BoneScript more trouble 
> than its worth?" 
> >> I have myself problem every 4-5 days with a Bonescript Web server 
> >> distributing my sensor data, where I have to add soon a watchdog 
> > 
> > Do you require constant running, or do you sleep and run? If the 
> > latter, you probably should respawn a fresh interpreter each time, do 
> > the work and quit---otherwise you are at the mercy of memory leaks 
> > that are hard to avoid in an interpreter. 
> > 
> > 
> >> With IRC channel, your probably means I2C. Voltage and resistors, it's 
> clear. 
> > 
> > No, IRC is the Internet Relay Chat software, a distributed chat 
> > application that developers tend to use. When people log in into IRC, 
> > they tend to watch it in real time, so potentially It provides more 
> > immediate communication. This list is email-based so everyone has to 
> > actively go and check the new emails. 
> > 
> >> Then, it's a question of hardware and conditions, like a DS18B20 on my 
> BBB with 5V over a 5 meters cable ... and works as a charm. 
> > 
> > If you place an analog voltage greater than 1.8 Volts on the analog 
> > input pin of the BBB, you will destroy that input. This is different 
> > from DS18B20, which has a digital one-wire interface using I think 
> > standard 3.3V digital signaling. Note that 5V is too much: you need to 
> > drop the voltage to 3.3V even for digital signals. 
>
> and it looks like mis-read the data sheet... the dh11 actually is a 
> simple bus, i first thought it was analog out.. 
>
> It can be powered by 3.3v and there is kernel driver for this: 
>
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/drivers/iio/humidity/dht11.c?id=refs/tags/v4.5-rc2
>  
>
> and the dt bindings: 
>
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/iio/humidity/dht11.txt
>  
>
> 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.

Re: [beagleboard] Re: Beaglebone Cloud9 Default User

[William Hermans]

>
>
>
> * I very much appreciate the reply.  I was accessing Cloud9 through eth0
> not usb0 so root access from the network was possible.  Were I only
> accessing the BeagleBone over the usb network I wouldn't have been
> concerned.  However I remotely connected over port 3000 and saw a command
> line running with root.I tried chasing down the problem but found the
> Cloud9 IDE just too convoluted to figure out.  I tried but failed to change
> the default user and password in the configuration file referred to in my
> earlier post.  At that point I simply killed Cloud9, and just used Byobu
> (tmux) terminals to work with node.js.*


You're not alone with finding cloud9 too convoluted to even bother messing
with. Personally, I have years experience with Debian( think over 20 ), and
am a very experienced programmer in a few different languages. So I'm not
exactly computer illiterate, and can usually solve most problems rather
quickly. Not so with the current default base Debian image with cloud9 etc.

I actually found it much easier to build my own Debian images from scratch,
based on Roberts kernel build guide, compiling Nodejs personally, and
installing it via a package, than using the cloud9 images with bonescript,
and all that fluff.

I just use a very basic custom image that is less than 200M in size, with
Nodejs + Express + NPM installed, and then ssh in to write code on a NFS
share <--- This is so I can edit code for the BBB on a local system running
Windows, in my editor of choice. VIM, and all that is kind of neat, but is
not exactly my sort of "thing" . . .


On Fri, Feb 5, 2016 at 9:44 AM, Paul Wolfson  wrote:

> I very much appreciate the reply.  I was accessing Cloud9 through eth0 not
> usb0 so root access from the network was possible.  Were I only accessing
> the BeagleBone over the usb network I wouldn't have been concerned.
> However I remotely connected over port 3000 and saw a command line running
> with root.
>
> I tried chasing down the problem but found the Cloud9 IDE just too
> convoluted to figure out.  I tried but failed to change the default user
> and password in the configuration file referred to in my earlier post.  At
> that point I simply killed Cloud9, and just used Byobu (tmux) terminals to
> work with node.js.
>
> In the latest build Debian r43 build Cloud9 is not installed by default so
> it's all good.  Robert's little connmanctl tutorial post yesterday made
> networking much easier than messing with /etc/network/interfaces.
>
> -
> Paul Wolfson, Ph.D., TX LPI, #A17473
> Editor, TALI "The Texas Investigator"
> Dallas Legal Technology
> 3402 Oak Grove Avenue, Suite 300-A
> Dallas, Texas 75204-2353
>
>
> *214-257-0984 <214-257-0984> (Tel)214-838-7220 <214-838-7220> (Fax)Send me
> an email. *
> -
> The contents of this email are confidential to the sender and the ordinary
> user of the email address to which it was addressed, and may also be
> privileged.  If you are not the addressee of the email, you may not copy,
> forward, disclose or otherwise use it or any part of it in any form
> whatsoever.  If you have received this email in error, please advise the
> sender at  214-257-0984.  Thank you.
> -
>
> On Fri, Feb 5, 2016 at 11:21 AM, Wally Bkg  wrote:
>
>> I'm not very experienced with Cloud9 or BoneScript, but as I understand
>> it, at present BoneScript is only usable for code running as root because
>> of device driver permissions.  Also BoneScript PWM is not working in the
>> "latest" versions.
>>
>> While this is not optimal, adding user permissions into the mix would
>> likely overwhelm people coming from Arduino.  Raspberry Pi currently has
>> basically the same setup where only root users can use on board hardware,
>> unless its changed with a new Raspbian release recently.
>>
>> Are you accessing Cloud9 via the USB "gadget" or Ethernet (Wired or
>> WiFi)?  I might make a difference.
>>
>>
>>
>> On Thursday, January 7, 2016 at 3:42:01 PM UTC-6, Paul Wolfson wrote:
>>>
>>> I've been using my BBB for some time with Ubuntu 3.8.13-bone30 but
>>> upgraded to Debian 4.1.12-ti-r29 because of OS stability problems.  The
>>> Cloud9 IDE is back.  I opened it and saw a command shell prompt running as
>>> root@beaglebone.
>>>
>>> Does anyone know off the top of their head where the default user is set?
>>>
>>> I saw this,
>>> http://stackoverflow.com/questions/28822695/change-the-username-and-add-a-password-for-cloud9-in-the-beaglebone-black
>>>  but
>>> after changing
>>> .describe("auth", "Basic Auth username:password")
>>> to
>>> .describe("auth", "debian:temppwd")
>>>
>>> and rebooting, the Cloud9 bash prompt is still "root@beaglebone:~# ."
>>>
>>> [if this is a double post, I apologize]
>>>
>>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You 

Re: [beagleboard] Re: DHT11 Grove on Beaglebone and general impression on Beaglebone

[Jean-Bernard Boichat]

See my answers below:

Le vendredi 5 février 2016 17:52:01 UTC+1, Przemek Klosowski a écrit :
>
> On Fri, Feb 5, 2016 at 10:34 AM, Jean-Bernard Boichat 
>  wrote: 
> > The BeagleBone community forum is not too active, sure. It's a pity for 
> such 
> > a good board and concept. 
>
> Are you participating in this discussion by sending email to 
> beagl...@googlegroups.com , or via some other way? I see it 
> as an 
> email stream of a dozen or so messages a day. I'd call it pretty 
> active. 
>
>
I just use http://beagleboard.org/Community/Forums
Something better?
 

> > I found today one or two good articles like "Is BoneScript more trouble 
> than its worth?" 
> > I have myself problem every 4-5 days with a Bonescript Web server 
> > distributing my sensor data, where I have to add soon a watchdog 
>
> Do you require constant running, or do you sleep and run? If the 
> latter, you probably should respawn a fresh interpreter each time, do 
> the work and quit---otherwise you are at the mercy of memory leaks 
> that are hard to avoid in an interpreter. 
>

Just this:

#!/bin/bash
> cd /root/nodejs
> while :
> do
> exec sudo node bbbserver.js >/dev/null
> sleep 1
> done
>

Loop in case bbbserver.js crashes 
and:

var http = require("http");
> var url  = require('url');
> var fs   = require('fs');
> var io   = require('/usr/local/lib/node_modules/socket.io'); 
> var b= require('/usr/local/lib/node_modules/bonescript');
> //Lets define a port on 192.168.1.61 where we want to listen to
> const PORT=8001; 
> //console.log("Server listening on port %s", PORT);
> var server = http.createServer(function(request, response) {
> var path = url.parse(request.url).pathname;
>   switch(path){
> case '/':
>   ..
>   break;
> case '/lightsync':
>   response.writeHead(200, {'Content-Type': 'text/plain'});
>   var reading = b.analogRead('P9_40');   //Synchronous light value 
> (< 1.0 Volt))
>   value = (1 - ((1.0 - (reading*reading*reading)) * 1)) | 0
>   response.write('' + value);  //string conversion  
>   response.end();
>   break;
> case '/fixed.html':
> 
> break;
> default:
> response.writeHead(404);
> response.write("opps this doesn't exist - 404");
> response.end();
> break;
> }
>   });
> server.listen(PORT);
> var value = 
> var listener = io.listen(server);
> listener.sockets.on('connection', function(socket) {
> b.analogRead('P9_40', computeValue);
> 
> socket.emit('message', {'message': value});
> });
> function computeValue(x) {
> reading = x.value
> value = (1 - ((1.0 - (reading*reading*reading)) * 1)) | 0 
> }


The value calculation allows to react more at middle range of light (sensor 
outside).

My Raspberry calls this BBB Webserver during 2 periods erlay in the morning 
and the evening up to a predefined time like 23:30 in a config file (not in 
the night for instance).
My Raspberry computes the sunrise and sunset depending of the seasons, and 
of some predefined time, will switch on or off the lights connected on my 
Raspberry relays. Everthing in Java and stable.

By checking the light outside (BBB) I can switch on or off the light 
depending on the darkness before the sunset period and after the sunrise 
period. 
That system simulates presence too and has a movement sensor too (pratical 
in the night)

I should probably check the memory leak on the BBB before ps-greping the 
node bbbserver.js process in a watchdog rebot loop.  


>
> > With IRC channel, your probably means I2C. Voltage and resistors, it's 
> clear. 
>
> No, IRC is the Internet Relay Chat software, a distributed chat 
> application that developers tend to use. When people log in into IRC, 
> they tend to watch it in real time, so potentially It provides more 
> immediate communication. This list is email-based so everyone has to 
> actively go and check the new emails. 
>

I understand now, sorry. No need of IRC I think. I think it's a good way 
too to search for learning (as well as finding crazy comments)! Although!
 

>
> > Then, it's a question of hardware and conditions, like a DS18B20 on my 
> BBB with 5V over a 5 meters cable ... and works as a charm. 
>
> If you place an analog voltage greater than 1.8 Volts on the analog 
> input pin of the BBB, you will destroy that input. This is different 
> from DS18B20, which has a digital one-wire interface using I think 
> standard 3.3V digital signaling. Note that 5V is too much: you need to 
> drop the voltage to 3.3V even for digital signals. 
>

Thanks for the 1.8V input. I did not care too much!

The way I did: I built my 3 temperature cables (2 with LM35 and one longer 
going outside) and check them on the Arduino by identifying the right 
voltage/resistance. Then I installed them, one by one, on the BBB with 
individual python scripts,

At the end everything goes 

Re: [beagleboard] Can't see USB hard drive

[William Hermans]

If the drive does not show up from the output of lsusb, then the hardware
isn't connecting to the OS. So, I would suggest bypassing the USB HUB for a
temporary test, and see if the drive shows up like that.

3.8.13-bone47 might be old, but I know it works with external self powered
USB hard drives. As I've booted from USB in the past . . . Note the date of
this blog post I wrote . . . over two years ago.
http://www.embeddedhobbyist.com/2013/07/beaglebone-black-usb-boot/

On Fri, Feb 5, 2016 at 10:34 AM, Robert Nelson 
wrote:

> On Fri, Feb 5, 2016 at 11:31 AM, Rikk Sullenberger
>  wrote:
> > I am trying to attatch a 360gig USB2 NTFS hard drive to a Beaglebone
> Black.
> > The drive does not show up under the /dev/ tree, doesn't show up with
> lsusb,
> > doesn't show up in dmesg..
> >
> > The drive is self powered, I have tried a different hub, different hard
> > drive, the hard drive works on a raspberry..
> >
> > Anyone had this happen? I bought this BBB a year ago and just started
> > playing with it...
>
> > [   17.647683] usb usb2: Manufacturer: Linux 3.8.13-bone47 musb-hcd
> > [   17.647694] usb usb2: SerialNumber: musb-hdrc.0.auto
> > [   17.648205] usb usb2: usb_probe_device
> > [   17.648223] usb usb2: configuration #1 chosen from 1 choice
> > [   17.648269] usb usb2: adding 2-0:1.0 (config #1, interface 0)
> > [   17.648396] hub 2-0:1.0: usb_probe_interface
> > [   17.648410] hub 2-0:1.0: usb_probe_interface - got id
> > [   17.648428] hub 2-0:1.0: USB hub found
> > [   17.648452] hub 2-0:1.0: 1 port detected
> > [   17.648463] hub 2-0:1.0: standalone hub
> > [   17.648473] hub 2-0:1.0: individual port power switching
> > [   17.648483] hub 2-0:1.0: no over-current protection
> > [   17.648493] hub 2-0:1.0: Single TT
> > [   17.648505] hub 2-0:1.0: TT requires at most 8 FS bit times (666 ns)
> > [   17.648516] hub 2-0:1.0: power on to power good time: 10ms
> > [   17.648540] hub 2-0:1.0: local power source is good
> > [   17.648599] hub 2-0:1.0: enabling power on all ports
> > [   17.748539] hub 2-0:1.0: state 7 ports 1 chg  evt 
> > [   17.748600] hub 2-0:1.0: hub_suspend
> > [   17.748629] usb usb2: bus auto-suspend, wakeup 1
>
>
> 3.8.13-bone47 is pretty old.. How are you powering the bbb? 5volt dc
> jack right
>
> Give one of the jessie lxqt shapshots a try with a more modern kernel:
>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots
>
> 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.
>

-- 
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] Simple exemple for Timer beaglebone

[nadhem . zaraii]

Im trying to use the timer to blink led in kernel module but i don't know 
how :( Can someone help me !!

-- 
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 see USB hard drive

[William Hermans]

By the way, I would not recommend following that information for current up
to date Debian images. I should probably write up an update for newer
images . . .

On Fri, Feb 5, 2016 at 11:14 AM, William Hermans  wrote:

> If the drive does not show up from the output of lsusb, then the hardware
> isn't connecting to the OS. So, I would suggest bypassing the USB HUB for a
> temporary test, and see if the drive shows up like that.
>
> 3.8.13-bone47 might be old, but I know it works with external self powered
> USB hard drives. As I've booted from USB in the past . . . Note the date of
> this blog post I wrote . . . over two years ago.
> http://www.embeddedhobbyist.com/2013/07/beaglebone-black-usb-boot/
>
> On Fri, Feb 5, 2016 at 10:34 AM, Robert Nelson 
> wrote:
>
>> On Fri, Feb 5, 2016 at 11:31 AM, Rikk Sullenberger
>>  wrote:
>> > I am trying to attatch a 360gig USB2 NTFS hard drive to a Beaglebone
>> Black.
>> > The drive does not show up under the /dev/ tree, doesn't show up with
>> lsusb,
>> > doesn't show up in dmesg..
>> >
>> > The drive is self powered, I have tried a different hub, different hard
>> > drive, the hard drive works on a raspberry..
>> >
>> > Anyone had this happen? I bought this BBB a year ago and just started
>> > playing with it...
>>
>> > [   17.647683] usb usb2: Manufacturer: Linux 3.8.13-bone47 musb-hcd
>> > [   17.647694] usb usb2: SerialNumber: musb-hdrc.0.auto
>> > [   17.648205] usb usb2: usb_probe_device
>> > [   17.648223] usb usb2: configuration #1 chosen from 1 choice
>> > [   17.648269] usb usb2: adding 2-0:1.0 (config #1, interface 0)
>> > [   17.648396] hub 2-0:1.0: usb_probe_interface
>> > [   17.648410] hub 2-0:1.0: usb_probe_interface - got id
>> > [   17.648428] hub 2-0:1.0: USB hub found
>> > [   17.648452] hub 2-0:1.0: 1 port detected
>> > [   17.648463] hub 2-0:1.0: standalone hub
>> > [   17.648473] hub 2-0:1.0: individual port power switching
>> > [   17.648483] hub 2-0:1.0: no over-current protection
>> > [   17.648493] hub 2-0:1.0: Single TT
>> > [   17.648505] hub 2-0:1.0: TT requires at most 8 FS bit times (666 ns)
>> > [   17.648516] hub 2-0:1.0: power on to power good time: 10ms
>> > [   17.648540] hub 2-0:1.0: local power source is good
>> > [   17.648599] hub 2-0:1.0: enabling power on all ports
>> > [   17.748539] hub 2-0:1.0: state 7 ports 1 chg  evt 
>> > [   17.748600] hub 2-0:1.0: hub_suspend
>> > [   17.748629] usb usb2: bus auto-suspend, wakeup 1
>>
>>
>> 3.8.13-bone47 is pretty old.. How are you powering the bbb? 5volt dc
>> jack right
>>
>> Give one of the jessie lxqt shapshots a try with a more modern kernel:
>>
>>
>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots
>>
>> 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.
>>
>
>

-- 
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] Can't see USB hard drive

[Rikk Sullenberger]

I am trying to attatch a 360gig USB2 NTFS hard drive to a Beaglebone Black. 
The drive does not show up under the /dev/ tree, doesn't show up with 
lsusb, doesn't show up in dmesg..

The drive is self powered, I have tried a different hub, different hard 
drive, the hard drive works on a raspberry..

Anyone had this happen? I bought this BBB a year ago and just started 
playing with it...


Thanks in advance!



[2.727936] ALSA device list:
[2.731094]   #0: TI BeagleBone Black
[2.735564] Freeing init memory: 236K
[2.826313] systemd-udevd[103]: starting version 204
[3.856617] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly 
filesystem
[3.864311] EXT4-fs (mmcblk0p2): write access will be enabled during 
recovery
[4.534415] EXT4-fs (mmcblk0p2): recovery complete
[4.543216] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null)
[5.337433] init: plymouth-upstart-bridge main process (157) terminated 
with status 1
[5.348831] init: plymouth-upstart-bridge main process ended, respawning
[5.437441] init: plymouth-upstart-bridge main process (167) terminated 
with status 1
[5.447799] init: plymouth-upstart-bridge main process ended, respawning
[5.545417] init: plymouth-upstart-bridge main process (170) terminated 
with status 1
[5.553746] init: plymouth-upstart-bridge main process ended, respawning
[5.563192] init: ureadahead main process (160) terminated with status 5
[6.821907] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[7.935120] systemd-udevd[303]: starting version 204
[   11.948356] net eth0: initializing cpsw version 1.12 (0)
[   11.957658] net eth0: phy found : id is : 0x7c0f1
[   11.957694] libphy: PHY 4a101000.mdio:01 not found
[   11.962740] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   12.003000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.472403] init: avahi-cups-reload main process (418) terminated with 
status 1
[   15.036066] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
[   15.036129] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   17.628080]  gadget: using random self ethernet address
[   17.628829] usb0: MAC 82:18:a7:d0:42:8d
[   17.628843] usb0: HOST MAC d0:ff:50:56:e4:1d
[   17.646131]  gadget: Mass Storage Function, version: 2009/09/11
[   17.646156]  gadget: Number of LUNs=1
[   17.646183]  lun0: LUN: removable file: /dev/mmcblk0p1
[   17.646311]  gadget: Multifunction Composite Gadget
[   17.646341]  gadget: g_multi ready
[   17.646383] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
[   17.646710] musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned 
bus number 2
[   17.647514] musb-hdrc musb-hdrc.0.auto: supports USB remote wakeup
[   17.647597] usb usb2: default language 0x0409
[   17.647634] usb usb2: udev 1, busnum 2, minor = 128
[   17.647648] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[   17.647661] usb usb2: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[   17.647672] usb usb2: Product: MUSB HDRC host driver
[   17.647683] usb usb2: Manufacturer: Linux 3.8.13-bone47 musb-hcd
[   17.647694] usb usb2: SerialNumber: musb-hdrc.0.auto
[   17.648205] usb usb2: usb_probe_device
[   17.648223] usb usb2: configuration #1 chosen from 1 choice
[   17.648269] usb usb2: adding 2-0:1.0 (config #1, interface 0)
[   17.648396] hub 2-0:1.0: usb_probe_interface
[   17.648410] hub 2-0:1.0: usb_probe_interface - got id
[   17.648428] hub 2-0:1.0: USB hub found
[   17.648452] hub 2-0:1.0: 1 port detected
[   17.648463] hub 2-0:1.0: standalone hub
[   17.648473] hub 2-0:1.0: individual port power switching
[   17.648483] hub 2-0:1.0: no over-current protection
[   17.648493] hub 2-0:1.0: Single TT
[   17.648505] hub 2-0:1.0: TT requires at most 8 FS bit times (666 ns)
[   17.648516] hub 2-0:1.0: power on to power good time: 10ms
[   17.648540] hub 2-0:1.0: local power source is good
[   17.648599] hub 2-0:1.0: enabling power on all ports
[   17.748539] hub 2-0:1.0: state 7 ports 1 chg  evt 
[   17.748600] hub 2-0:1.0: hub_suspend
[   17.748629] usb usb2: bus auto-suspend, wakeup 1
[   19.873871] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   23.877937] init: plymouth-upstart-bridge main process ended, respawning


lsusb
ubuntu@arm:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

df-h

ubuntu@arm:~$ df -h
Filesystem  Size  Used Avail Use% Mounted on
/dev/mmcblk0p2  1.7G  1.2G  461M  72% /
none4.0K 0  4.0K   0% /sys/fs/cgroup
udev247M  4.0K  247M   1% /dev
tmpfs50M  252K   50M   1% /run
none5.0M 0  5.0M   0% /run/lock
none249M 0  249M   0% /run/shm
none100M 0  100M   0% /run/user
/dev/mmcblk0p1   96M   73M   24M  76% /boot/uboot




-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message 

Re: [beagleboard] Adafruit BBIO USR LED fix (was: BeagleBone Green Grove i2c issues)

[chnyc]

Wow! Thanks for wrangling the AdaFruit library, Drew. I should'a thought 
the /sys/ path was the culprit...

 I'd thrown in the towel on this one many moons ago and stuck with PyBBIO 
which, as you note, always handled USR LEDs well. Glad to hear your fix did 
the trick. 

Charles (chnyc)


On Thursday, February 4, 2016 at 6:18:31 PM UTC-5, Drew Fustini wrote:
>
> On Oct 20, 2015 11:22 PM, "William Hermans"  > wrote:
> > https://github.com/graycatlabs/PyBBIO
> > Check out the documentation links.
> >
> > Here is his USR LED blink example.
> > https://github.com/graycatlabs/PyBBIO/blob/master/examples/blink.py
>
> I was reading this old thread and just wanted to note that the built-in 
> LEDs did not work with the Adafruit BBIO library until my fix was merged 
> last month:
> https://github.com/adafruit/adafruit-beaglebone-io-python/pull/88
>
> The excellent PyBBIO always handled this correctly.
>

-- 
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 see USB hard drive

[William Hermans]

Well then Rikk, your best option at this point may be to google something
like "LInux USB hard drive x.y.z", find unique fixes, and experiment. But
"x.y.z" would be whatever keyword that returns useful results. Which may
also require some experimentation . . .

On Fri, Feb 5, 2016 at 12:04 PM, Rikk Sullenberger 
wrote:

> Just tried the drive minus the hub,  no luck.  I tried with a split cable
> (power/USB)  and a standard cable (peed from the  BBB...  Sane issue.  :(
> On Feb 5, 2016 1:14 PM, "William Hermans"  wrote:
>
>> If the drive does not show up from the output of lsusb, then the hardware
>> isn't connecting to the OS. So, I would suggest bypassing the USB HUB for a
>> temporary test, and see if the drive shows up like that.
>>
>> 3.8.13-bone47 might be old, but I know it works with external self
>> powered USB hard drives. As I've booted from USB in the past . . . Note the
>> date of this blog post I wrote . . . over two years ago.
>> http://www.embeddedhobbyist.com/2013/07/beaglebone-black-usb-boot/
>>
>> On Fri, Feb 5, 2016 at 10:34 AM, Robert Nelson 
>> wrote:
>>
>>> On Fri, Feb 5, 2016 at 11:31 AM, Rikk Sullenberger
>>>  wrote:
>>> > I am trying to attatch a 360gig USB2 NTFS hard drive to a Beaglebone
>>> Black.
>>> > The drive does not show up under the /dev/ tree, doesn't show up with
>>> lsusb,
>>> > doesn't show up in dmesg..
>>> >
>>> > The drive is self powered, I have tried a different hub, different hard
>>> > drive, the hard drive works on a raspberry..
>>> >
>>> > Anyone had this happen? I bought this BBB a year ago and just started
>>> > playing with it...
>>>
>>> > [   17.647683] usb usb2: Manufacturer: Linux 3.8.13-bone47 musb-hcd
>>> > [   17.647694] usb usb2: SerialNumber: musb-hdrc.0.auto
>>> > [   17.648205] usb usb2: usb_probe_device
>>> > [   17.648223] usb usb2: configuration #1 chosen from 1 choice
>>> > [   17.648269] usb usb2: adding 2-0:1.0 (config #1, interface 0)
>>> > [   17.648396] hub 2-0:1.0: usb_probe_interface
>>> > [   17.648410] hub 2-0:1.0: usb_probe_interface - got id
>>> > [   17.648428] hub 2-0:1.0: USB hub found
>>> > [   17.648452] hub 2-0:1.0: 1 port detected
>>> > [   17.648463] hub 2-0:1.0: standalone hub
>>> > [   17.648473] hub 2-0:1.0: individual port power switching
>>> > [   17.648483] hub 2-0:1.0: no over-current protection
>>> > [   17.648493] hub 2-0:1.0: Single TT
>>> > [   17.648505] hub 2-0:1.0: TT requires at most 8 FS bit times (666 ns)
>>> > [   17.648516] hub 2-0:1.0: power on to power good time: 10ms
>>> > [   17.648540] hub 2-0:1.0: local power source is good
>>> > [   17.648599] hub 2-0:1.0: enabling power on all ports
>>> > [   17.748539] hub 2-0:1.0: state 7 ports 1 chg  evt 
>>> > [   17.748600] hub 2-0:1.0: hub_suspend
>>> > [   17.748629] usb usb2: bus auto-suspend, wakeup 1
>>>
>>>
>>> 3.8.13-bone47 is pretty old.. How are you powering the bbb? 5volt dc
>>> jack right
>>>
>>> Give one of the jessie lxqt shapshots a try with a more modern kernel:
>>>
>>>
>>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots
>>>
>>> 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.
>>>
>>
>> --
>> 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/IfCgSUqeRsQ/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.
>

-- 
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: Beaglebone Cloud9 Default User

[Wally Bkg]

On Friday, February 5, 2016 at 1:48:53 PM UTC-6, William Hermans wrote:
>
> *After giving him a configured BBG (he'd have been dead in the water with 
>> the image that came in the BBG eMMC, which really breaks the ideal for a 
>> newbie idea) and showing him how to install the Windows drivers and connect 
>> to the BBG with Chrome web browser, it clearly was a great starting point 
>> for him.*
>>
>
> Anything of this nature still has a learning curve. Personally, I think 
> things of this nature are a waste of time. Not because they're not handy, 
> or cool. But instead you have to spend a time investment to learn anything. 
> So you may as well learn the "underlying basics" so you're better prepared 
> in the future to deal with more complex problems.
>
> So a very quick example . . . Not knowing what Node-RED really is, I'd 
> have to spend a considerable amount of time learning this new "software 
> technology", when I could instead just write  my own code and be done with 
> it. Now sure, because I'm an experienced developer, who *now* has a decent 
> bit of javascript / Nodejs experience, this may be easier for me. However, 
> I had to learn all of this, just like anyone else, and in fact I'm by far 
> not a Nodejs "expert". And in fact, I knew very little of  Nodejs 3 years 
> ago when we got our first BBB's . . .
>
>
What you say is true, but I'm afraid its been so long since you've started 
with zero programming knowledge that you've forgotten how difficult that 
first step is, its mind numbingly complex when you throw in all the GPIO 
mux options and restrictions of the Beaglebone

A GUI tool like node-red lets a rank beginner do something useful, without 
spending weeks learning programming and languages.  Drag and drop, wire, 
and deploy can result it a rather sophisticated program with distributed 
processing -- a sensor in one building communicating with a actuator in 
another building over a WiFi network using mqtt protocol and mosquito 
broker running on one of the Beaglebones -- all done like drawing a 
schematic diagram -- something people with a hardware background find 
"intuitive".  To use a GPIO as input or output, you drag the node to the 
"tab", double click it, and fill in the necessary "properties" to make the 
function.  The choices are limited to what is available with the "default" 
pin mux settings but for a beginner its feature, not a bug.  If only the 
PWM worked, and there were UART nodes it could do most anything that needs 
response times on the order of human reaction times or longer.

What's nice is that starting with node-red lets my friend ease into 
programming with some cut and paste of nodejs examples and modifying them 
in a "function" node within an otherwise working "flow" (program) to add 
functionality, instead of starting with a blank page and a "Programming 
Language Du-jour for Dummies" book in hand.

Node-red has some rough edges but it has tremendous potential for helping 
"subject matter experts" quickly get into programming  prototype solutions 
to their problems.  I've always said that its far easier to teach a 
Biochemist enough programming to solve a biochemistry problem than is is to 
teach a programmer enough biochemistry to solve a biochemistry problem.  
Things like node-red really lower the bar!


Go to the node-red website and look at the "your second flow" example -- it 
"polls" the UK power grid at 5 minute intervals and reports true or false 
if the frequency is 50 Hz or greater (below 50 hz, maybe delay starting 
that induction motor a bit to let the grid recover -- minimal impact from 
my one motor, but if millions of motors are making this decision before 
starting, the effect on peak load could be enormous with near zero impact 
to the refrigerators, etc. driven by these motors).  Now list all the 
libraries and protocols you'd have to know about to be able do this in your 
favorite programming language, and tell me this is not a better starting 
point for an appliance manufacturing looking to make a "smart" product.

When I stumbled on to this, it just blew me away!

-- 
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: Use GPIO as non-root user?

[William Hermans]

The "safest" way I can think of is put a very specific line in the sudoers
file ( via visudo ). What this does, is allow you to issue a command, using
sudo, potentially without using a passwd. So for example:

sudo sh -c "echo '1' > /sys/class/gpio/gpio67/value"

The above  can be made to run without using a passwd. So what this
**is** is a way to allow a very specific command to be run
as root, without using a passwd. What this **is not** is a way to
secure somethign similar on a multi user system.

So this method does have it's perks, e.g. allowing a very specific
command, say read a GPIO value, that is not really a security
risk, while the rest of the GPIO bank could represent an issue.

I do believe one can achieve something very similar to what I suggest
above using udev rules, but I'm honestly not all that well
versed with udev. . .


On Fri, Feb 5, 2016 at 3:35 PM, jmelson  wrote:

>
>
> On Friday, February 5, 2016 at 4:13:34 PM UTC-6, Drew Fustini wrote:
>>
>> I noticed that the Raspberry Pi kernel adopted /dev/gpiomem to provide a
>> way for non-root users to access GPIO:
>>
>>
>> The poor man's way is to make the executable file be owned  by root, and
> then set the S bit so it takes execute permissions from the file owner.
> You do this with :
>
> sudo chown root:root filename
> sudo chmod u+s filename
>
> This requires a valid root user to be set up.
>
>
> Jon
>
> --
> 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: Use GPIO as non-root user?

[jmelson]

On Friday, February 5, 2016 at 4:13:34 PM UTC-6, Drew Fustini wrote:
>
> I noticed that the Raspberry Pi kernel adopted /dev/gpiomem to provide a 
> way for non-root users to access GPIO:
>
>
> The poor man's way is to make the executable file be owned  by root, and 
then set the S bit so it takes execute permissions from the file owner.
You do this with :

sudo chown root:root filename
sudo chmod u+s filename

This requires a valid root user to be set up.


Jon

-- 
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] Use GPIO as non-root user?

[Drew Fustini]

I noticed that the Raspberry Pi kernel adopted /dev/gpiomem to provide a 
way for non-root users to access GPIO:

Add /dev/gpiomem device for rootless user GPIO access:
https://github.com/raspberrypi/linux/pull/1112

Is there anything comparable for BeagleBone?  Anyone have ideas/plans?

I started thinking about this after seeing this post on the Adafruit forum:

Trying to use Adafruit_BBIO library and run as non-root user
https://forums.adafruit.com/viewtopic.php?f=49=89338=450036#p450036


thanks,
drew

-- 
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 see USB hard drive

[Wally Bkg]

Its not an external drive, but I just plugged a 1GB USB memory stick into 
my BBG running "latest" 2015-11-12 with all upgrades as of about five days 
ago.  While nothing auto mounted, and lsusb didn't show anything I could 
recognize as the USB stick, /dev/sd and /dev/sda1 appeared

mount -t vfat /dev/sda1 /mnt let me list the files.


Are the ntfs tools installed on your system?  ('m not certain of the actual 
package name),  are they installed on the beaglebone.org images?



On Friday, February 5, 2016 at 1:04:32 PM UTC-6, Rikk Sullenberger wrote:
>
> Just tried the drive minus the hub,  no luck.  I tried with a split cable 
> (power/USB)  and a standard cable (peed from the  BBB...  Sane issue.  :(
> On Feb 5, 2016 1:14 PM, "William Hermans"  
> wrote:
>
>> If the drive does not show up from the output of lsusb, then the hardware 
>> isn't connecting to the OS. So, I would suggest bypassing the USB HUB for a 
>> temporary test, and see if the drive shows up like that.
>>
>> 3.8.13-bone47 might be old, but I know it works with external self 
>> powered USB hard drives. As I've booted from USB in the past . . . Note the 
>> date of this blog post I wrote . . . over two years ago. 
>> http://www.embeddedhobbyist.com/2013/07/beaglebone-black-usb-boot/
>>
>> On Fri, Feb 5, 2016 at 10:34 AM, Robert Nelson > > wrote:
>>
>>> On Fri, Feb 5, 2016 at 11:31 AM, Rikk Sullenberger
>>>  wrote:
>>> > I am trying to attatch a 360gig USB2 NTFS hard drive to a Beaglebone 
>>> Black.
>>> > The drive does not show up under the /dev/ tree, doesn't show up with 
>>> lsusb,
>>> > doesn't show up in dmesg..
>>> >
>>> > The drive is self powered, I have tried a different hub, different hard
>>> > drive, the hard drive works on a raspberry..
>>> >
>>> > Anyone had this happen? I bought this BBB a year ago and just started
>>> > playing with it...
>>>
>>> > [   17.647683] usb usb2: Manufacturer: Linux 3.8.13-bone47 musb-hcd
>>> > [   17.647694] usb usb2: SerialNumber: musb-hdrc.0.auto
>>> > [   17.648205] usb usb2: usb_probe_device
>>> > [   17.648223] usb usb2: configuration #1 chosen from 1 choice
>>> > [   17.648269] usb usb2: adding 2-0:1.0 (config #1, interface 0)
>>> > [   17.648396] hub 2-0:1.0: usb_probe_interface
>>> > [   17.648410] hub 2-0:1.0: usb_probe_interface - got id
>>> > [   17.648428] hub 2-0:1.0: USB hub found
>>> > [   17.648452] hub 2-0:1.0: 1 port detected
>>> > [   17.648463] hub 2-0:1.0: standalone hub
>>> > [   17.648473] hub 2-0:1.0: individual port power switching
>>> > [   17.648483] hub 2-0:1.0: no over-current protection
>>> > [   17.648493] hub 2-0:1.0: Single TT
>>> > [   17.648505] hub 2-0:1.0: TT requires at most 8 FS bit times (666 ns)
>>> > [   17.648516] hub 2-0:1.0: power on to power good time: 10ms
>>> > [   17.648540] hub 2-0:1.0: local power source is good
>>> > [   17.648599] hub 2-0:1.0: enabling power on all ports
>>> > [   17.748539] hub 2-0:1.0: state 7 ports 1 chg  evt 
>>> > [   17.748600] hub 2-0:1.0: hub_suspend
>>> > [   17.748629] usb usb2: bus auto-suspend, wakeup 1
>>>
>>>
>>> 3.8.13-bone47 is pretty old.. How are you powering the bbb? 5volt dc
>>> jack right
>>>
>>> Give one of the jessie lxqt shapshots a try with a more modern kernel:
>>>
>>>
>>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Image_Testing_Snapshots
>>>
>>> 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...@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 a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/IfCgSUqeRsQ/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@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: Beaglebone Cloud9 Default User

[William Hermans]

>
> *After giving him a configured BBG (he'd have been dead in the water with
> the image that came in the BBG eMMC, which really breaks the ideal for a
> newbie idea) and showing him how to install the Windows drivers and connect
> to the BBG with Chrome web browser, it clearly was a great starting point
> for him.*
>

Anything of this nature still has a learning curve. Personally, I think
things of this nature are a waste of time. Not because they're not handy,
or cool. But instead you have to spend a time investment to learn anything.
So you may as well learn the "underlying basics" so you're better prepared
in the future to deal with more complex problems.

So a very quick example . . . Not knowing what Node-RED really is, I'd have
to spend a considerable amount of time learning this new "software
technology", when I could instead just write  my own code and be done with
it. Now sure, because I'm an experienced developer, who *now* has a decent
bit of javascript / Nodejs experience, this may be easier for me. However,
I had to learn all of this, just like anyone else, and in fact I'm by far
not a Nodejs "expert". And in fact, I knew very little of  Nodejs 3 years
ago when we got our first BBB's . . .


On Fri, Feb 5, 2016 at 11:54 AM, Wally Bkg  wrote:

> I agree that if you plan to have your Beaglebone connected directly to the
> Internet the current default setups are woefully inadequate,  I'm
> comfortable with my IOT stuff behind a solid firewall on a trusted subnet,
> but having just setup a friend with a BBG Cloud9 BoneScript and Node-Red
> and the USB "gadget", it is a pretty setup to explain and demo.
>
> Knowing better tools made me ignore it all starting with my Rev A6 BBW,
> but when a friend very experienced in electronics, but total newbie at
> programming, asked me about Arduino vs. Raspberry Pi vs.  Beaglebone -- he
> was aware of them all but unsure where to start,  I had to play with the
> newbie stuff a bit myself before actually recommending anything.
>
> After giving him a configured BBG (he'd have been dead in the water with
> the image that came in the BBG eMMC, which really breaks the ideal for a
> newbie idea) and showing him how to install the Windows drivers and connect
> to the BBG with Chrome web browser, it clearly was a great starting point
> for him.
>
>
> On Friday, February 5, 2016 at 12:27:59 PM UTC-6, William Hermans wrote:
>>
>>
>>>
>>> * I very much appreciate the reply.  I was accessing Cloud9 through eth0
>>> not usb0 so root access from the network was possible.  Were I only
>>> accessing the BeagleBone over the usb network I wouldn't have been
>>> concerned.  However I remotely connected over port 3000 and saw a command
>>> line running with root.I tried chasing down the problem but found the
>>> Cloud9 IDE just too convoluted to figure out.  I tried but failed to change
>>> the default user and password in the configuration file referred to in my
>>> earlier post.  At that point I simply killed Cloud9, and just used Byobu
>>> (tmux) terminals to work with node.js.*
>>
>>
>> You're not alone with finding cloud9 too convoluted to even bother
>> messing with. Personally, I have years experience with Debian( think over
>> 20 ), and am a very experienced programmer in a few different languages. So
>> I'm not exactly computer illiterate, and can usually solve most problems
>> rather quickly. Not so with the current default base Debian image with
>> cloud9 etc.
>>
>> I actually found it much easier to build my own Debian images from
>> scratch, based on Roberts kernel build guide, compiling Nodejs personally,
>> and installing it via a package, than using the cloud9 images with
>> bonescript, and all that fluff.
>>
>> I just use a very basic custom image that is less than 200M in size, with
>> Nodejs + Express + NPM installed, and then ssh in to write code on a NFS
>> share <--- This is so I can edit code for the BBB on a local system running
>> Windows, in my editor of choice. VIM, and all that is kind of neat, but is
>> not exactly my sort of "thing" . . .
>>
>>
>> On Fri, Feb 5, 2016 at 9:44 AM, Paul Wolfson  wrote:
>>
>>> I very much appreciate the reply.  I was accessing Cloud9 through eth0
>>> not usb0 so root access from the network was possible.  Were I only
>>> accessing the BeagleBone over the usb network I wouldn't have been
>>> concerned.  However I remotely connected over port 3000 and saw a command
>>> line running with root.
>>>
>>> I tried chasing down the problem but found the Cloud9 IDE just too
>>> convoluted to figure out.  I tried but failed to change the default user
>>> and password in the configuration file referred to in my earlier post.  At
>>> that point I simply killed Cloud9, and just used Byobu (tmux) terminals to
>>> work with node.js.
>>>
>>> In the latest build Debian r43 build Cloud9 is not installed by default
>>> so it's all good.  Robert's little connmanctl tutorial post yesterday made
>>> 

Re: [beagleboard] Can't see USB hard drive

[William Hermans]

>
> *Its not an external drive, but I just plugged a 1GB USB memory stick into
> my BBG running "latest" 2015-11-12 with all upgrades as of about five days
> ago.  While nothing auto mounted, and lsusb didn't show anything I could
> recognize as the USB stick, /dev/sd and /dev/sda1 appeared*
>

OK that's odd . . .

So what I was going to before, was to run *fdisk -l* and see if the drive
shows up there, but lsusb always showed my usb driver controller for my
external hard drive. Maybe this is some sort of USB thumb drive sort of
thing ? *shrug*

On Fri, Feb 5, 2016 at 1:02 PM, Wally Bkg  wrote:

> Its not an external drive, but I just plugged a 1GB USB memory stick into
> my BBG running "latest" 2015-11-12 with all upgrades as of about five days
> ago.  While nothing auto mounted, and lsusb didn't show anything I could
> recognize as the USB stick, /dev/sd and /dev/sda1 appeared
>
> mount -t vfat /dev/sda1 /mnt let me list the files.
>
>
> Are the ntfs tools installed on your system?  ('m not certain of the
> actual package name),  are they installed on the beaglebone.org images?
>
>
>
> On Friday, February 5, 2016 at 1:04:32 PM UTC-6, Rikk Sullenberger wrote:
>>
>> Just tried the drive minus the hub,  no luck.  I tried with a split cable
>> (power/USB)  and a standard cable (peed from the  BBB...  Sane issue.  :(
>> On Feb 5, 2016 1:14 PM, "William Hermans"  wrote:
>>
>>> If the drive does not show up from the output of lsusb, then the
>>> hardware isn't connecting to the OS. So, I would suggest bypassing the USB
>>> HUB for a temporary test, and see if the drive shows up like that.
>>>
>>> 3.8.13-bone47 might be old, but I know it works with external self
>>> powered USB hard drives. As I've booted from USB in the past . . . Note the
>>> date of this blog post I wrote . . . over two years ago.
>>> http://www.embeddedhobbyist.com/2013/07/beaglebone-black-usb-boot/
>>>
>>> On Fri, Feb 5, 2016 at 10:34 AM, Robert Nelson 
>>> wrote:
>>>
 On Fri, Feb 5, 2016 at 11:31 AM, Rikk Sullenberger
  wrote:
 > I am trying to attatch a 360gig USB2 NTFS hard drive to a Beaglebone
 Black.
 > The drive does not show up under the /dev/ tree, doesn't show up with
 lsusb,
 > doesn't show up in dmesg..
 >
 > The drive is self powered, I have tried a different hub, different
 hard
 > drive, the hard drive works on a raspberry..
 >
 > Anyone had this happen? I bought this BBB a year ago and just started
 > playing with it...

 > [   17.647683] usb usb2: Manufacturer: Linux 3.8.13-bone47 musb-hcd
 > [   17.647694] usb usb2: SerialNumber: musb-hdrc.0.auto
 > [   17.648205] usb usb2: usb_probe_device
 > [   17.648223] usb usb2: configuration #1 chosen from 1 choice
 > [   17.648269] usb usb2: adding 2-0:1.0 (config #1, interface 0)
 > [   17.648396] hub 2-0:1.0: usb_probe_interface
 > [   17.648410] hub 2-0:1.0: usb_probe_interface - got id
 > [   17.648428] hub 2-0:1.0: USB hub found
 > [   17.648452] hub 2-0:1.0: 1 port detected
 > [   17.648463] hub 2-0:1.0: standalone hub
 > [   17.648473] hub 2-0:1.0: individual port power switching
 > [   17.648483] hub 2-0:1.0: no over-current protection
 > [   17.648493] hub 2-0:1.0: Single TT
 > [   17.648505] hub 2-0:1.0: TT requires at most 8 FS bit times (666
 ns)
 > [   17.648516] hub 2-0:1.0: power on to power good time: 10ms
 > [   17.648540] hub 2-0:1.0: local power source is good
 > [   17.648599] hub 2-0:1.0: enabling power on all ports
 > [   17.748539] hub 2-0:1.0: state 7 ports 1 chg  evt 
 > [   17.748600] hub 2-0:1.0: hub_suspend
 > [   17.748629] usb usb2: bus auto-suspend, wakeup 1


 3.8.13-bone47 is pretty old.. How are you powering the bbb? 5volt dc
 jack right

 Give one of the jessie lxqt shapshots a try with a more modern kernel:


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

 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...@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 a topic in the
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/IfCgSUqeRsQ/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> beagleboard...@googlegroups.com.
>>> For more options, 

Re: [beagleboard] Re: BeagleBone Black QT GUI Application

[Zola]

You cannot have two windowing systems running at the same time, they 
interfere with each other.

On Thursday, July 31, 2014 at 2:07:41 AM UTC+2, amey@sjsu.edu wrote:
>
> hey the link 
>
> http://harmattan-dev.nokia.com/docs/library/html/qt4/qt-embedded-pointer.html 
> 
> is broken can u please tell what you did..
> Thanks in advance
> On Tuesday, November 5, 2013 6:58:09 PM UTC-8, barne...@gmail.com wrote:
>>
>> Thanks lisarden.
>>
>> I fixed this issue by the following commands.
>> export QWS_MOUSE_PROTO=linuxinput:/dev/input/event1 
>>
>>
>> lisarden於 2013年11月5日星期二UTC+8下午10時44分08秒寫道：
>>>
>>>
>>> http://harmattan-dev.nokia.com/docs/library/html/qt4/qt-embedded-pointer.html
>>>  
>>> 
>>>
>>> you can also use google sometimes ;)
>>>
>>>
>>> 2013/11/5 
>>>
 I used Beaglebone Black without LCD/touchscreen module, just with HDMI 
 out to my Monitor.
 When I execute "systemctl disable gdm.service" and "./myQtHelloWorld 
 -qws",
 I can see the window display to my Monitor but the mouse hanged(can not 
 be moved).
 Can you give me some suggestions for this issue?


 lisarden於 2013年10月13日星期日UTC+8上午10時46分45秒寫道：
>
> Disable gdm at all
> 11.10.2013 20:39 пользователь "MCU Solution"  
> написал:
>
>> when i use the command "pkill gdm" then run my application , its 
>> running. but Mouse operation nill. how can i run the button like graphic 
>> application without using the command pkill gdm
>>
>> any idea ??
>>
>> On Friday, October 11, 2013 9:05:31 PM UTC+5:30, MCU Solution wrote:
>>>
>>> Yes i have it.
>>>
>>> On Friday, October 11, 2013 10:10:23 AM UTC+5:30, MCU Solution wrote:

 is it possible to run QT GUI Application on Beaglebone Black with 
 HDMI Output?

 i try the QT GUI Example ,No Output in the Monitor .but i try hello 
 world in the terminal  its show hello world but i try GUI application 
 example like Buttons ,not shown any Output.

 Any 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...@googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
> -- 
 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...@googlegroups.com.
 For more options, visit https://groups.google.com/groups/opt_out.

>>>
>>>
>>>
>>> -- 
>>> LinkedIn - http://www.linkedin.com/in/maximpodbereznyy
>>> Company - http://www.linkedin.com/company/mentorel
>>> Facebook - https://www.facebook.com/mentorel.company
>>>
>>

-- 
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] Technical info for beaglebone black board.

[namithapavithran94]

Hi,

I am searching for a board on which i can flash my USB gadget driver in 
linux environment. We need a kit with Peripheral Device Controller along 
with its driver interface to flash and validate our Gadget driver. Can 
anyone suggest me whether beaglebone black will serve my requirement or is 
there any other better option.

Thanks in advance
Namitha Pavithran.

-- 
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] Beaglebone Black, Chipsee and Python

[Harke Smits]

Dear experienced group,

I am looking for control software in Python for a 4.3 inch Chipsee display. 
I have installed Debian 7.9 LXDE 2015-11-03, that works very well, with the 
display (the browser works great, touching works, reset button works) and 
with other I/O control software, from me in Python. For my application I 
want to control the display via Python. I googled but found not very 
usefull info. It looks like the manufacturer has provided an old version of 
the os, but as my current version works well, and I have lost a lot of time 
with older versions, I am very reluctant to change the Debian version. Even 
then I see no Python support at all. Is there a more generic solution?
What is the best way to proceed?
Any help greatly appreciated,
Harke

-- 
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] Large Arrays in DDR via PRU. Does prussdrv_map_extmem() always give contiguous physical addresses?

[Bill Gray]

Hi,

I've got PRU0 of my BBB pulling in 12 Bytes of data from a ADC with a 
sampling frequency of 31250hz.

I want to stash all of this data in an array that lives in DDR memory.  I 
would like to make the array 0x4000 bytes (16kB) large.  This would give me 
1365 12 byte records and about 43ms of data to play with.

I'm currently using prussdrv_map_extmem() to hook me up with the DDR 
memory.  It provides me with a memory block that is 256kB, so I have plenty 
of room.

The question I have is... can I count on the physical address in this 256kB 
block of memory to be contiguous?

I'm pretty new to linux memory management, but I see that the "page size" 
is only 4kB... so I imagine that the virtual memory system might chop my 
256kB block up into bits which might not necessarily have contiguous 
addresses.

If I can count on contiguous addresses, this radically simplifies the 
memory access code in the PRU.  If I can't... well, then I can't, and I've 
got to figure something else out.

When I run experiments I see that the physical addresses are contiguous, 
but are they guaranteed to be? or has this just been "lucky"?

Thanks,

Bill


-- 
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] Large Arrays in DDR via PRU. Does prussdrv_map_extmem() always give contiguous physical addresses?

[William Hermans]

>
> *When I run experiments I see that the physical addresses are contiguous,
> but are they guaranteed to be? or has this just been "lucky"?*
>

If memory serves, I think they have to be. But, if as you say you've tested
and they've come up contiguous already, then I'm very sure this can not
change. Not unless they memory is somehow freed using free(), and I do not
think that is possible . . .

On Fri, Feb 5, 2016 at 5:33 PM, Bill Gray  wrote:

> Hi,
>
> I've got PRU0 of my BBB pulling in 12 Bytes of data from a ADC with a
> sampling frequency of 31250hz.
>
> I want to stash all of this data in an array that lives in DDR memory.  I
> would like to make the array 0x4000 bytes (16kB) large.  This would give me
> 1365 12 byte records and about 43ms of data to play with.
>
> I'm currently using prussdrv_map_extmem() to hook me up with the DDR
> memory.  It provides me with a memory block that is 256kB, so I have plenty
> of room.
>
> The question I have is... can I count on the physical address in this
> 256kB block of memory to be contiguous?
>
> I'm pretty new to linux memory management, but I see that the "page size"
> is only 4kB... so I imagine that the virtual memory system might chop my
> 256kB block up into bits which might not necessarily have contiguous
> addresses.
>
> If I can count on contiguous addresses, this radically simplifies the
> memory access code in the PRU.  If I can't... well, then I can't, and I've
> got to figure something else out.
>
> When I run experiments I see that the physical addresses are contiguous,
> but are they guaranteed to be? or has this just been "lucky"?
>
> Thanks,
>
> Bill
>
>
> --
> 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] Use GPIO as non-root user?

[Brian Anderson]

Err, why?

Groups are frequently used to restrict access to resources. Android exploits 
groups for permissions and to sandbox applications.  And the kernel enforces 
access.

Using sudo seems much less secure as it exposes the application to being 
exploited for security flaws. And since the application is running as root, it 
has access to everything.

But maybe I'm missing something?

ba

-- 
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: Make a backup of contents of one beaglebone black and install said contents on a second BBB

[canis]

On Thursday, February 4, 2016 at 6:12:45 PM UTC-8, canis wrote:
>
> Hi Wally,
>
> Thanks for getting back.  Missed getting back yesterday- I'll try 
> following your suggestions tonight.
>
> (I'm a bit fearful of accidentally altering the board I'm trying to copy).
>
> Canis
>
> On Tuesday, February 2, 2016 at 2:39:34 PM UTC-8, Wally Bkg wrote:
>>
>> I'll try to walk you through this, step by step but it may take awhile.  
>> I'll try to check this thread everyday.
>>
>> Since you are using the eMMC the easiest backup will be if you can "hot 
>> plug" a micro SD card.  Get an 8GB Class 10 card.  After you boot your 
>> Beaglebone open a terminal window (the root console tab in Cloud9 will 
>> work, although putty or ssh will be better) and do the command:  ls 
>> /dev/mmc*
>> you should see something like:
>> /dev/mmcblk0  /dev/mmcblk0p1  /dev/mmcblk1boot0
>>
>> Next plug in the SD card and repeat the ls /dev/mmc* command, you should 
>> then see something like:
>> /dev/mmcblk0/dev/mmcblk1   /dev/mmcblk1boot1  /dev/mmcblk1p2
>> /dev/mmcblk0p1  /dev/mmcblk1boot0  /dev/mmcblk1p1
>>
>> If these appear you should be able to use dd to clone your eMMC to the SD 
>> card.  Try this and let me know what you find.  Use a card larger than the 
>> eMMC so the command won't fail if your SD card is a bit smaller than the 
>> eMMC, that is why I suggest an 8GB card.
>>
>> Hope this helps, If your card doesn't "hot plug"  post the links to what 
>> procedures you've found and I can try to help you follow the one I think 
>> should work with the least hassle.
>>
>>
>>
>> On Monday, February 1, 2016 at 3:19:24 PM UTC-6, canis wrote:
>>>
>>> Hi Wally
>>>
>>> Many thanks.  I'll apologize in advance- there are terms I'm not 
>>> familiar with; I fear I'll have to take small steps
>>>
>>> First question, is your system running from an SD card or the eMMC?
>>>
>>> Running the eMMC
>>>
>>> If running from an SD card, just "clone" or duplicate the card using 
>>> Windows or Linux tools.  If its running from the eMMC (on-board storage).  
>>> It'll require knowing some Linux commands.   For a beginner, I'd suggest 
>>> downloading an image as close to what is in your eMMC as you can, write 
>>> it to an SD and then mounting the SD card using a USB to SD card adapter 
>>> (this gets you the correct partition layout) on the BBB and using rsync or 
>>> dd to clone (copy) the / (root) and /boot partitions from your eMMC to the 
>>> SD card.
>>>
>>> Is the image the list of files & folders visible upon opening BBB on my 
>>> laptop OR the list of folders and files within Cloud 9 OR something else?
>>>
>>> Thanks again,
>>> canis
>>>
>>>
>>>
>>>
>>>

-- 
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 WIFI in Debian?

[DeKay]

Networkmanager and nmtui makes wireless setup trivial.  And I'd recommend 
setting GOVERNOR="performance" while you are at it.

http://madscientistlabs.blogspot.ca/2015/01/wifi-on-beaglebone-black-with-systemd.html

On Thursday, 4 February 2016 12:11:37 UTC-6, RobertCNelson wrote:
>
> On Thu, Feb 4, 2016 at 12:05 PM, Hugo Mallo  > wrote: 
> > Hello everybody, I am quite new in BBB's world and I feel stuck in a 
> > ridiculous way as I am not able to connect BBB by WIFI, by editing 
> > /etc/network/interfaces and as I am trying to  connect with and WPA 
> WIFI, I 
> > ought to edit the file /etc/wpa_supplicant/wpa_supplicant.conf . 
>
> nah use connman, i have it installed by default on jessie images. ;) 
>
> ~$ sudo connmanctl 
> connmanctl> enable wifi 
> Enabled wifi 
>
> connmanctl> scan wifi 
> Scan completed for wifi 
>
> connmanctl> services 
> *AO Wiredethernet_74d435b65be6_cable 
> Avenger  wifi_14cc201db6f6_4176656e676572_managed_psk 
>
> connmanctl> agent on 
> Agent registered 
>
> connmanctl> connect wifi_14cc201db6f6_4176656e676572_managed_psk 
> Agent RequestInput wifi_14cc201db6f6_4176656e676572_managed_psk 
>   Passphrase = [ Type=psk, Requirement=mandatory ] 
>
> Passphrase? wine n dine 
> Connected wifi_14cc201db6f6_4176656e676572_managed_psk 
>
> connmanctl> quit 
>
> check: 
>
> sudo ifconfig -a 
>
> 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] Beaglebone Black cannot cannot to ethernet

[desk . abhimanyu]

I have trying for hours and my board suddenly stopped connecting to my host 
(ubuntu 14). I have tried re-flashing the OS. But still no luck. I'm new 
with this. 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] UART1 using BB-UART1 vs cape-universal

[Brian Anderson]

I have a sensor hooked up to UART1.  This seems to work just fine using 
cape-universal and config-pin to setup P9-24 and P9-26 in uart mode.

When I modify uEnv.txt to use BB-UART1 overlay, I am unable to read data 
from the sensor.

Relevant portions of uEnv.txt looks like this:

# Don't enable cape-universal
cmdline=coherent_pool=1M quiet

# Enable UART1 and I2C1 overlays
cape_enable=bone_capemgr.enable_partno=BB-I2C1,BB-UART1

And I have commented out the original cmdline:

#cmdline=coherent_pool=1M quiet cape_universal=enable

Slots look like this:

 0: PF  -1 
 1: PF  -1 
 2: PF  -1 
 3: PF  -1 
 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-I2C1
 5: P-O-L-   1 Override Board Name,00A0,Override Manuf,BB-UART1

Kernel and rootfs:

debian@bbb2:~$ uname -r
4.1.16-ti-rt-r44
debian@bbb2:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-01-17

I have also pulled the latest bb.org-overlays and run install.sh.

I have this working on another system with 4.1.13-ti-r35 with the 
2015-11-09 rootfs.  If I am correct in analyzing the BB-UART1 dtb that is 
working on this system, it appears as if P9_24 is configured with a 
pulldown resistor and P9_26 is configured with a pullup resistor.  The 
BB-UART1 dtb on the system where this is not work (and the current version 
from bb.org-overlays) has no pullup/pulldown resistors configured for those 
pins.  Looking at cape-universal (that works), it appears as if P9_24 and 
P9_26 are both configured with pullups.

So, I'm assuming that this is why my current BB-UART1 setup is not working.

Is the configuration of the current BB-UART1 (actually all of them) without 
pullup/pulldown for UART mode by design?  If so, why?  And of course, the 
converse question for cape-universal.

Not being a H/W guy, maybe someone can inform me as to why my current 
BB-UART1 doesn't work and why these dtb's are thusly configured.

ba

-- 
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] UART1 using BB-UART1 vs cape-universal

[Brian Anderson]

OK, thanks Robert. I'll try an updated kernel and see what happens. Curious, 
what was the issue and why didn't it manifest itself with the different 
settings in cape-universal?

Still interested in why the pull-up/pull-down values are different in 
cape-universal vs BB-UART.

ba

-- 
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] Use GPIO as non-root user?

[William Hermans]

>
> *Using sudo seems much less secure as it exposes the application to being
> exploited for security flaws. And since the application is running as root,
> it has access to everything.*
>

So, we have a device on a system that can potentially cause physical damage
to external hardware when something like a wrong GPIO state is toggled, or
such. How would sudo be less secure in this context? In fact under certain
conditions it would be less safe using groups.

Also, "root has access to everything" is wrong. Reread what I've written
above about running specific commands through sudo.

On Fri, Feb 5, 2016 at 6:05 PM, Brian Anderson  wrote:

> Err, why?
>
> Groups are frequently used to restrict access to resources. Android
> exploits groups for permissions and to sandbox applications.  And the
> kernel enforces access.
>
> Using sudo seems much less secure as it exposes the application to being
> exploited for security flaws. And since the application is running as root,
> it has access to everything.
>
> But maybe I'm missing something?
>
> ba
>
> --
> 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] Use GPIO as non-root user?

[John Syne]

This is why Unix/Linux has groups. Do the following:

ls -la /dev

You will see groups such as i2c, dialout, tty, etc. If you want to access these 
devices from a regular user account, add your user to those groups. If you need 
to use a device that has root:root, then change the group and add your user 
account to that group. 


Regards,
John




> On Feb 5, 2016, at 2:13 PM, Drew Fustini  wrote:
> 
> I noticed that the Raspberry Pi kernel adopted /dev/gpiomem to provide a way 
> for non-root users to access GPIO:
> 
> Add /dev/gpiomem device for rootless user GPIO access:
> https://github.com/raspberrypi/linux/pull/1112
> 
> Is there anything comparable for BeagleBone?  Anyone have ideas/plans?
> 
> I started thinking about this after seeing this post on the Adafruit forum:
> 
> Trying to use Adafruit_BBIO library and run as non-root user
> https://forums.adafruit.com/viewtopic.php?f=49=89338=450036#p450036
> 
> 
> thanks,
> drew
> 
> -- 
> 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: Use GPIO as non-root user?

[William Hermans]

So, here is an example of what I mean above.
http://unix.stackexchange.com/questions/18830/how-to-run-a-specific-program-as-root-without-a-password-prompt

3rd post has a decent example.


On Fri, Feb 5, 2016 at 4:26 PM, William Hermans  wrote:

> The "safest" way I can think of is put a very specific line in the sudoers
> file ( via visudo ). What this does, is allow you to issue a command, using
> sudo, potentially without using a passwd. So for example:
>
> sudo sh -c "echo '1' > /sys/class/gpio/gpio67/value"
>
> The above  can be made to run without using a passwd. So what this **is** is 
> a way to allow a very specific command to be run
> as root, without using a passwd. What this **is not** is a way to secure 
> somethign similar on a multi user system.
>
> So this method does have it's perks, e.g. allowing a very specific command, 
> say read a GPIO value, that is not really a security
> risk, while the rest of the GPIO bank could represent an issue.
>
> I do believe one can achieve something very similar to what I suggest above 
> using udev rules, but I'm honestly not all that well
> versed with udev. . .
>
>
> On Fri, Feb 5, 2016 at 3:35 PM, jmelson  wrote:
>
>>
>>
>> On Friday, February 5, 2016 at 4:13:34 PM UTC-6, Drew Fustini wrote:
>>>
>>> I noticed that the Raspberry Pi kernel adopted /dev/gpiomem to provide a
>>> way for non-root users to access GPIO:
>>>
>>>
>>> The poor man's way is to make the executable file be owned  by root, and
>> then set the S bit so it takes execute permissions from the file owner.
>> You do this with :
>>
>> sudo chown root:root filename
>> sudo chmod u+s filename
>>
>> This requires a valid root user to be set up.
>>
>>
>> Jon
>>
>> --
>> 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] Use GPIO as non-root user?

[William Hermans]

>
> *This is why Unix/Linux has groups. Do the following:*
>

Using groups is not necessarily the safest way to go about things John. But
I do agree it is a possibility. The only real contention that I have with
using groups. Is . . . my sudo example can be used on a very specific
command, only allowing that very specific command, where all others, no
matter how similar, if not exactly the same will not run. My example if not
really a good illustration of this but imagine this:

echo '1' > /sys/class/gpio/gpio67/value /* allowed */
echo '0' > /sys/class/gpio/gpio67/value /* not allowed */

Obviously the above is very contrived, but there can be a need for
something similar.



Also, when using groups, you do not really want to change groups, but add
groups. e.g. you *do not* want to change group root to wheel ( or whatever
group you want ) for a specific item. Since the system likely needs root to
have access to given items for various reasons. You also want to be as
specific as possible when creating / using groups. As using groups,
wrongly, is a perfect way to add a huge gaping security hole into a system.

On Fri, Feb 5, 2016 at 4:34 PM, John Syne  wrote:

> This is why Unix/Linux has groups. Do the following:
>
> ls -la /dev
>
> You will see groups such as i2c, dialout, tty, etc. If you want to access
> these devices from a regular user account, add your user to those groups.
> If you need to use a device that has root:root, then change the group and
> add your user account to that group.
>
>
> Regards,
> John
>
>
>
>
> On Feb 5, 2016, at 2:13 PM, Drew Fustini  wrote:
>
> I noticed that the Raspberry Pi kernel adopted /dev/gpiomem to provide a
> way for non-root users to access GPIO:
>
> Add /dev/gpiomem device for rootless user GPIO access:
> https://github.com/raspberrypi/linux/pull/1112
>
> Is there anything comparable for BeagleBone?  Anyone have ideas/plans?
>
> I started thinking about this after seeing this post on the Adafruit forum:
>
> Trying to use Adafruit_BBIO library and run as non-root user
>
> https://forums.adafruit.com/viewtopic.php?f=49=89338=450036#p450036
>
>
> thanks,
> drew
>
> --
> 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.
>

-- 
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] UART1 using BB-UART1 vs cape-universal

[Robert Nelson]

On Fri, Feb 5, 2016 at 5:55 PM, Brian Anderson  wrote:
> I have a sensor hooked up to UART1.  This seems to work just fine using
> cape-universal and config-pin to setup P9-24 and P9-26 in uart mode.
>
> When I modify uEnv.txt to use BB-UART1 overlay, I am unable to read data
> from the sensor.
>
> Relevant portions of uEnv.txt looks like this:
>
> # Don't enable cape-universal
> cmdline=coherent_pool=1M quiet
>
> # Enable UART1 and I2C1 overlays
> cape_enable=bone_capemgr.enable_partno=BB-I2C1,BB-UART1
>
> And I have commented out the original cmdline:
>
> #cmdline=coherent_pool=1M quiet cape_universal=enable
>
> Slots look like this:
>
>  0: PF  -1
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>  4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-I2C1
>  5: P-O-L-   1 Override Board Name,00A0,Override Manuf,BB-UART1
>
> Kernel and rootfs:
>
> debian@bbb2:~$ uname -r
> 4.1.16-ti-rt-r44
> debian@bbb2:~$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2016-01-17
>
> I have also pulled the latest bb.org-overlays and run install.sh.
>
> I have this working on another system with 4.1.13-ti-r35 with the 2015-11-09
> rootfs.  If I am correct in analyzing the BB-UART1 dtb that is working on
> this system, it appears as if P9_24 is configured with a pulldown resistor
> and P9_26 is configured with a pullup resistor.  The BB-UART1 dtb on the
> system where this is not work (and the current version from bb.org-overlays)
> has no pullup/pulldown resistors configured for those pins.  Looking at
> cape-universal (that works), it appears as if P9_24 and P9_26 are both
> configured with pullups.
>
> So, I'm assuming that this is why my current BB-UART1 setup is not working.
>
> Is the configuration of the current BB-UART1 (actually all of them) without
> pullup/pulldown for UART mode by design?  If so, why?  And of course, the
> converse question for cape-universal.
>
> Not being a H/W guy, maybe someone can inform me as to why my current
> BB-UART1 doesn't work and why these dtb's are thusly configured.

Sorry, just fixed this today, my edma fix for spi/mcasp, broke usart1/2..

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --ti-rt-channel --lts-4_1

BB-UART1 & BB-UART2 will work again...

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.

Re: [beagleboard] Use GPIO as non-root user?

[Brian Anderson]

My comments are really to do with what I perceive as best practices on how 
one would approach building systems that are "security conscious".  Of 
course, "convenience" may direct us in different directions during 
development.  I am not sure what you are trying to imply by "safe" as in 
protecting the GPIOs from misuse.  I don't actually see any way to 
accomplish that.  What I do think one can do is to be aware of security 
considerations and not unnecessarily present an attack surface that can 
compromise the entire system.


*Using sudo seems much less secure as it exposes the application to being 
>> exploited for security flaws. And since the application is running as root, 
>> it has access to everything.*
>>
>
> So, we have a device on a system that can potentially cause physical 
> damage to external hardware when something like a wrong GPIO state is 
> toggled, or such. How would sudo be less secure in this context?
>

It wouldn't.  And that is not my point.  I am not talking about how to 
protect the GPIOs from "bad behaved" programs that are "trusted" as implied 
by the fact that they are running as a normal user in the group that has 
access to those GPIOs.  If an application is trusted (is a member of the 
appropriate group or for that matter can sudo), it is a hopeless task to 
protect the GPIOs from misuse.  What I am trying to point out is that 
running an app as "root" (sudo, set uid, whatever) exposes a security 
attack vector...a vector that has access to _all_ system resources.  I 
would claim that it is an unnecessary exposure...from a security point of 
view.  YMMV when it comes to "convenience".
 

> In fact under certain conditions it would be less safe using groups.
>

How would an application running at a non-root level using groups to access 
protected resources be less "safe" than an application running as root 
using sudo?
 

>
> Also, "root has access to everything" is wrong. Reread what I've written 
> above about running specific commands through sudo.
>

Errr, an application running as root, by definition, has access to _all_ 
system resources.  The fact that you are limiting just a single 
application/user to run sudo doesn't limit the attack surface for that 
application.  If your root application is compromised in some way, then the 
entire system can be compromised.  Running as a normal user does not 
present the same attack surface...its much smaller and sandboxed by the 
kernel.  Running as root affords no protection enforcement by the kernel.

ba
 

>
> On Fri, Feb 5, 2016 at 6:05 PM, Brian Anderson  > wrote:
>
>> Err, why?
>>
>> Groups are frequently used to restrict access to resources. Android 
>> exploits groups for permissions and to sandbox applications.  And the 
>> kernel enforces access.
>>
>> Using sudo seems much less secure as it exposes the application to being 
>> exploited for security flaws. And since the application is running as root, 
>> it has access to everything.
>>
>> But maybe I'm missing something?
>>
>> ba
>>
>> --
>> 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...@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.