date:20151219

Hey guys,

Thanks for the input.  I think my major disconnect was the fact that when I
was looking at the slots I didnt notice the O vs the L :)

So apparently it was not loaded.  Sorry guys.  Still learning the
BeagleBone.  This list has been very very helpful.

Riley

On Fri, Dec 18, 2015 at 1:40 AM, John Syne  wrote:

> As Robert described, your uEnv.txt should look like this:
>
> —
>
> *uname_r=3.8.13-bone79*
> *#uuid=*
> *#dtb=*
>
> *##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)*
>
> *##BeagleBone Black: HDMI (Audio/Video) disabled:*
> *#dtb=am335x-boneblack-emmc-overlay.dtb*
>
> *##BeagleBone Black: eMMC disabled:*
> *#dtb=am335x-boneblack-hdmi-overlay.dtb*
>
> *##BeagleBone Black: HDMI Audio/eMMC disabled:*
> *#dtb=am335x-boneblack-nhdmi-overlay.dtb*
>
> *##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:*
> *#dtb=am335x-boneblack-overlay.dtb*
>
> *##BeagleBone Black: wl1835*
> *#dtb=am335x-boneblack-wl1835mod.dtb*
>
> *##BeagleBone Black: replicape*
> *#dtb=am335x-boneblack-replicape.dtb*
>
> *##BeagleBone Green: eMMC disabled*
> *#dtb=am335x-bonegreen-overlay.dtb*
>
>
> *#In the event of edid real failures, uncomment this next line:*
> *#cmdline=coherent_pool=1M quiet init=/lib/systemd/systemd
> cape_universal=enable video=HDMI-A-1:1024x768@60e*
>
> *##Example v3.8.x*
> *#cape_disable=capemgr.disable_partno=*
> *#cape_enable=capemgr.enable_partno=*
>
> *##Example v4.1.x*
> *#cape_disable=bone_capemgr.disable_partno=*
> *#cape_enable=bone_capemgr.enable_partno=*
>
> *##Disable HDMI/eMMC (v3.8.x)*
>
> *cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G*
>
> *##Disable HDMI (v3.8.x)*
> *#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>
> *##Disable eMMC (v3.8.x)*
> *#cape_disable=capemgr.disable_partno=BB-BONE-EMMC-2G*
>
> *##Audio Cape (needs HDMI Audio disabled) (v3.8.x)*
> *#cape_disable=capemgr.disable_partno=BB-BONELT-HDMI*
> *#cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02*
>
>
> *##enable Generic eMMC Flasher:*
> *##make sure, these tools are installed: dosfstools rsync*
> *#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh*
>
> *cmdline=coherent_pool=1M quiet init=/lib/systemd/systemd
> cape_universal=enable*
>
> *—*
>
> *BTW, if you don’t need cape_universal, the last line should be:*
>
> *cmdline=coherent_pool=1M quiet init=/lib/systemd/systemd*
>
> *Regards,*
> *John*
>
>
> On Dec 17, 2015, at 9:08 PM, Riley Porter  wrote:
>
> Hey guys I have edited my uEnv.txt and uncommented the disable hdmi and
> emmc but a reboot does nothing?
>
> This is my kernel version:
>
> *Linux beaglebone 3.8.13-bone79 #1 SMP Tue Oct 13 20:44:55 UTC 2015 armv7l
> GNU/Linux*
>
> This is my /boot/uEnv.txt file:
>
> *Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
> *
>
> *uname_r=3.8.13-bone79*
> *#uuid=*
> *#dtb=*
>
> *##BeagleBone Black/Green dtb's for v4.1.x (BeagleBone White just works..)*
>
> *##BeagleBone Black: HDMI (Audio/Video) disabled:*
> *dtb=am335x-boneblack-emmc-overlay.dtb*
>
> *##BeagleBone Black: eMMC disabled:*
> *dtb=am335x-boneblack-hdmi-overlay.dtb*
>
> *##BeagleBone Black: HDMI Audio/eMMC disabled:*
> *dtb=am335x-boneblack-nhdmi-overlay.dtb*
>
> *##BeagleBone Black: HDMI (Audio/Video)/eMMC disabled:*
> *dtb=am335x-boneblack-overlay.dtb*
>
> *##BeagleBone Black: wl1835*
> *#dtb=am335x-boneblack-wl1835mod.dtb*
>
> *##BeagleBone Black: replicape*
> *#dtb=am335x-boneblack-replicape.dtb*
>
> *##BeagleBone Green: eMMC disabled*
> *dtb=am335x-bonegreen-overlay.dtb*
>
>
> *#In the event of edid real failures, uncomment this next line:*
> *#cmdline=coherent_pool=1M quiet init=/lib/systemd/systemd
> cape_universal=enable video=HDMI-A-1:1024x768@60e*
>
> *##Example v3.8.x*
> *#cape_disable=capemgr.disable_partno=*
> *#cape_enable=capemgr.enable_partno=*
>
> *##Example v4.1.x*
> *#cape_disable=bone_capemgr.disable_partno=*
> *#cape_enable=bone_capemgr.enable_partno=*
>
> *##Disable HDMI/eMMC (v3.8.x)*
>
> *cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G*
>
> *##Disable HDMI (v3.8.x)*
> *cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN*
>
> *##Disable eMMC (v3.8.x)*
> *cape_disable=capemgr.disable_partno=BB-BONE-EMMC-2G*
>
> *##Audio Cape (needs HDMI Audio disabled) (v3.8.x)*
> *cape_disable=capemgr.disable_partno=BB-BONELT-HDMI*
> *#cape_enable=capemgr.enable_partno=BB-BONE-AUDI-02*
>
>
> *##enable Generic eMMC Flasher:*
> *##make sure, these tools are installed: dosfstools rsync*
> *#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh*
>
> *cmdline=coherent_pool=1M quiet init=/lib/systemd/systemd
> cape_universal=enable*
>
> As you can see I pretty much disabled everything but when I:
>
> root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots
>  0: 54:PF---
>  1: 55:PF---
>  2: 56:PF---
>  3: 57:PF---
>  4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMM

Re: [beagleboard] /sys/class/hwmon not populated on Jessie

One can not help but wonder. Why have a "thing" at all, if it doesn't work
properly . . . and this isn't the first "thing" on this SoC which doesn't
work properly . . .

On Sat, Dec 19, 2015 at 2:55 PM, Robert Nelson 
wrote:

> On Sat, Dec 19, 2015 at 1:34 PM, Maurice H.  wrote:
> > I know this has been discussed and I understand TI's POV. I apologize if
> I
> > seemed pushy or something. That is not my intention. It's just that I
> > currently see data coming from my BBB that seems reasonable, although
> > slightly offset. There seems to be a nice correlation with changes in
> > room-temperature too.
>
> http://permalink.gmane.org/gmane.linux.linaro.devel/16501
>
> 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.

Re: [beagleboard] /sys/class/hwmon not populated on Jessie

On Sat, Dec 19, 2015 at 1:34 PM, Maurice H.  wrote:
> I know this has been discussed and I understand TI's POV. I apologize if I
> seemed pushy or something. That is not my intention. It's just that I
> currently see data coming from my BBB that seems reasonable, although
> slightly offset. There seems to be a nice correlation with changes in
> room-temperature too.

http://permalink.gmane.org/gmane.linux.linaro.devel/16501

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] BeagleBone Black - Building Custom Kernel

On Sat, Dec 19, 2015 at 2:29 PM, Bharath R  wrote:

>
> Hello,
>
> I'm trying to build a custom kernel for BBB using the source code from 
> *https://github.com/beagleboard/linux/tree/3.8
>  *.
>
> I did
>
> *1. make clean2. *
>
>
> *make ARCH=arm CROSS_COMPILE=arm-linux- bb.org_defconfig3. make ARCH=arm
> CROSS_COMPILE=arm-linux- *using tftpboot I downloaded the Linux uImage to
> 0x8200 address and run using bootm 0x8200.
>
>
>
>
>
>
>
>
>
>
>
>
>
> *U-boot~# bootm 8100 8200## Booting kernel from Legacy Image at
> 8100 ...   Image Name:   Embedded Linux-BBB   Created:  2015-12-19
> 17:12:31 UTC   Image Type:   ARM Linux Kernel Image (uncompressed)   Data
> Size:9234816 Bytes = 8.8 MiB   Load Address: 80008000   Entry Point:
> 80008000   Verifying Checksum ... OKStarting Linux kernel...*after the
> above message, kernel hangs. I believe the problem is due missing of debug
> serial port.
>

and where exactly did you load the device tree blob?

This isn't exactly new, as ever since the 3.8.x kernel came out.. (2013-02-18)
we've been using device tree's by DEFAULT on the beaglebone black..

So 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.

[beagleboard] BeagleBone Black - Building Custom Kernel


Hello,

I'm trying to build a custom kernel for BBB using the source code from 
*https://github.com/beagleboard/linux/tree/3.8 
 *. 

I did 

*1. make clean2. *


*make ARCH=arm CROSS_COMPILE=arm-linux- bb.org_defconfig3. make ARCH=arm 
CROSS_COMPILE=arm-linux- *using tftpboot I downloaded the Linux uImage to 
0x8200 address and run using bootm 0x8200.













*U-boot~# bootm 8100 8200## Booting kernel from Legacy Image at 
8100 ...   Image Name:   Embedded Linux-BBB   Created:  2015-12-19  
17:12:31 UTC   Image Type:   ARM Linux Kernel Image (uncompressed)   Data 
Size:9234816 Bytes = 8.8 MiB   Load Address: 80008000   Entry Point:  
80008000   Verifying Checksum ... OKStarting Linux kernel...*after the 
above message, kernel hangs. I believe the problem is due missing of debug 
serial port.

When I tried to configure the debug serial port i.e., UART1 in 
*make ARCH=arm CROSS_COMPILE=arm-linux- menuconfig*I don't find any UART 
here. 


This particular support should've been in Kconfig but I didn't find that. 
Can anyone please guide me how I could build the running kernel.

Regards,
Bharath
 

-- 
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] Running Qt gui application on BBB

2015-12-19 Thread Bremenpl

I am not sure, coz i wasnt building it- i fownloaded it from paxjage manager.

On December 19, 2015 7:51:18 PM John Syne wrote:

i haven’t done this in ages, but try to run your QT app with the "-platform
eglfs” option. I’m assuming you built QT with EGL.

Regards,
John

On Dec 19, 2015, at 3:46 AM, Bremenpl wrote:

Hello there,
I managed to set up qt 5.3.2 on the beaglebone. I have build everything
there and it took ages but it works :).

Next step is that I need to check either it is possible to run qt app on
bbb without gui with qws parameter. Because at the moment when i run it
with qws i get QXcbconnection: Could not connect to display. I need to do
it like this because thw gui is really really slow.

On December 15, 2015 6:10:13 AM John Syne wrote:

For purely building armhf code, Odroid XU4 might be a good choice:

http://www.hardkernel.com/main/main.php

This is an Octacore processor with 4 CortexA15 and 4 CortexA7 processors. I
don’t know how good their kernel/debian support is, but I know Robert had
looked at this board or a predecessor in the past, so perhaps he can give
his input here.

Clearly this board doesn’t have the flexibility of the BeagleBoard-x15 with
it’s dual DSP, Dual CortexM4, Quad PRU, SATA interface, PCIe interface, etc.

Regards,
John

On Dec 14, 2015, at 4:29 PM, William Hermans > wrote:

Anyway, the main problem with the rPI 2 is that it has no "fast" non
destructive storage. But the Omilex . . let me look it up.

https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2-4GB/open-source-hardware

Has SATA and GbE both. Dual cores too I think. However, you'd have to ask
someone who has one how well they think it would work as a build board.
RObert might know, as his Debian build guide also includes this board too I
believe.

On Mon, Dec 14, 2015 at 5:25 PM, William Hermans > wrote:

https://www.adafruit.com/product/2358

On Mon, Dec 14, 2015 at 5:23 PM, William Hermans > wrote:

The new board is armv7. Positively.

On Mon, Dec 14, 2015 at 5:24 PM, Bremenpl > wrote:

Okay, thank :P. I am quite sure raspberry pi is not hard float.

W dniu 2015-12-15 o 01:21, William Hermans pisze:
So just thinking for a minute. A Raspberry PI 2, the new board with quad
cores, and 1 GB ram would probably work fairly decent as a build system for
the Beaglebones. Granted, something like the X15, of that new nVidia ARM
board, or even the Omelex A20 board with SATA would probably be a much
better choice if cost is not a problem.

By the way, I have no idea what Robert is talking about. You need to ask him.

On Mon, Dec 14, 2015 at 5:15 PM, Bremenpl > wrote:
I have just flashed my BeagleBone Black emmc with lxqt image linked by
Robert. I cant seem to find qmake anywhere. I thought there would be qt
installed and all. Am I missing something again?

W dniu 2015-12-15 o 00:54, William Hermans pisze:
Not necessarily, but consider this. How much does an embedded systems
specialist in your area get paid per hour ? In my area, about 15-20 years
ago. The cost of a board like the X15 would have been absorbed in roughly
half a day. That is to say, an embedded systems specialist could buy a
board for $239 after working roughly half a day.

Now take into account that figuring out how to cross compile something like
this is a serious headache, and often takes days, if not weeks to get right
. . .

On Mon, Dec 14, 2015 at 4:32 PM, Bremenpl <
breme...@gmail.com >
wrote:
So if I understand correctly, I should have a second board that is more
powerfull than beagle just to compile the code for beagle?

W dniu 2015-12-15 o 00:26, William Hermans pisze:
I cant change the board right now, it has to be BeagleBone Black. Thats why
I need to build on my host. Did you succed on installing QT5.1 and
deploying it to BeagleBone Black? Maybe I should use it instead of 4.8.6 if
its easier?

No one was saying change boards. Use the same board, but use a faster, more
powerful ARM board to compile native ARM executable. The reasons are
simple. No need to mess with cross compiling, which in many cases is messy,
and sometimes near impossible.

You don't think Robert spends days, or weeks compiling packages do you ?
But why don't we ask Robert. Robert, hey what percentage of the packages
you build are compiled native to ARM, from some sort of beefy ARM board?
I'm guessing nearly 100% if not 100% but . . .

On Mon, Dec 14, 2015 at 4:00 PM, Bremenpl <
breme...@gmail.com >
wrote:

Ahh., thats the way, you are right...
Thank you for all the support guys,

Re: [beagleboard] /sys/class/hwmon not populated on Jessie

>
> *Yeah, it's easy to fix:*
>
> * sudo ln -s /dev/urandom /sys/class/hwmon/temp_sensor*
> *. . .*
>

LMAO !

On Sat, Dec 19, 2015 at 12:34 PM, Maurice H.  wrote:

> I know this has been discussed and I understand TI's POV. I apologize if I
> seemed pushy or something. That is not my intention. It's just that I
> currently see data coming from my BBB that seems reasonable, although
> slightly offset. There seems to be a nice correlation with changes in
> room-temperature too.
> Anyway, it was just me wondering. Never mind. I'll retire my code.
>
> Thanks for the answer. Really appreciating your effort.
>
> On Saturday, 19 December 2015 20:22:43 UTC+1, RobertCNelson wrote:
>>
>> On Sat, Dec 19, 2015 at 12:39 PM, Maurice H.  wrote:
>> >
>> > I did. Thanks.
>> >
>> > Any chance this could be implemented by a third-party? Or is the
>> TI-code a
>> > proprietary blob?
>>
>> Yeah, it's easy to fix:
>>
>> sudo ln -s /dev/urandom /sys/class/hwmon/temp_sensor
>>
>> okay so it's not "that" bad..  But /dev/urandom is more 'consistent'...
>>
>> But bad enough, TI hardware engineers told TI kernel developers to not
>> bother pushing it upstream.
>>
>> This has been discussed previously on this list..
>>
>> 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.

Re: [beagleboard] Re: Recommended Image



On Saturday, 19 December 2015 19:53:18 UTC+1, Kenneth Martin wrote:
>
> Yes, I am starting to see that Jessie has issues:
> [blabla...] 
>

> I don't know how to use it with unknown devices and unknown subnet without 
> using DHCP which doesn't allow for fixed IPs - which I need). Note: without 
> a network manager, you need to enable wpa_supplicant.service.
>
>
> IMHO, DHCP has no issues with a fixed IP. Either you define the IP in 
/etc/networks or (if the DNS is under your control) you can define a fixed 
IP for the MAC-address in question.

-- 
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] /sys/class/hwmon not populated on Jessie

I know this has been discussed and I understand TI's POV. I apologize if I 
seemed pushy or something. That is not my intention. It's just that I 
currently see data coming from my BBB that seems reasonable, although 
slightly offset. There seems to be a nice correlation with changes in 
room-temperature too.
Anyway, it was just me wondering. Never mind. I'll retire my code.

Thanks for the answer. Really appreciating your effort.

On Saturday, 19 December 2015 20:22:43 UTC+1, RobertCNelson wrote:
>
> On Sat, Dec 19, 2015 at 12:39 PM, Maurice H.  > wrote: 
> > 
> > I did. Thanks. 
> > 
> > Any chance this could be implemented by a third-party? Or is the TI-code 
> a 
> > proprietary blob? 
>
> Yeah, it's easy to fix: 
>
> sudo ln -s /dev/urandom /sys/class/hwmon/temp_sensor 
>
> okay so it's not "that" bad..  But /dev/urandom is more 'consistent'... 
>
> But bad enough, TI hardware engineers told TI kernel developers to not 
> bother pushing it upstream. 
>
> This has been discussed previously on this list.. 
>
> 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] /sys/class/hwmon not populated on Jessie

On Sat, Dec 19, 2015 at 12:39 PM, Maurice H.  wrote:
>
> I did. Thanks.
>
> Any chance this could be implemented by a third-party? Or is the TI-code a
> proprietary blob?

Yeah, it's easy to fix:

sudo ln -s /dev/urandom /sys/class/hwmon/temp_sensor

okay so it's not "that" bad..  But /dev/urandom is more 'consistent'...

But bad enough, TI hardware engineers told TI kernel developers to not
bother pushing it upstream.

This has been discussed previously on this list..

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: Recommended Image

On Sat, Dec 19, 2015 at 10:58 AM, Kenneth Martin  wrote:
> Yes, I am starting to see that Jessie has issues:
>
> 1) 7+ full 10 hour days (some larger not many smaller) to get wired and
> wired connections (and/or), with fixed IPs, com miserable at boot and
> compatible with either 192.168.0.0/24 or 192.168.1.0/24 subnets (subnet
> unknown at boot); finally successful (but can't help wining as this is only
> the very first step on getting the new flash upgrade to work), and a
> jury-rigged re-invent the wheel solution is guaranteed to be a problem (at
> least I'm getting better with bash scripting; yech!). Recommendation: we
> need a network manager not developed for desktops in fixed and known
> environments, but for headless computers with unknown devices and routers at
> boot. Also, maybe bashdb should included by default (a suggestion for Robert
> as if he doesn't have enough to do yet - any word on the X15? - is there
> still an FCC issue?)
>
> 2) BBB rev. C with Jessie, with both USB to ubuntu host, and with power to
> 5V connector (required for wireless dongle) almost always reboots at >sudo
> shutdown -h now; doesn't happen without the usb connection.

use:
sudo systemctl poweroff

>
> 3) Sometimes (not often but certainly occasionally) on >sudo reboot, BBB
> reboots, but no LEDs come on; it has booted up as holding the "power/reset"
> switch down of 10s does turn off the BBB.
>
> Good news, I can boot the BBB over either wireless (Tl-WN722N or TL-WN821N)
> or eth0 with both Asus (192.168.1.0/24 and TPLINK (192.168.0.0/24) routers,
> but the time from reboot to login can be quite large (time varies). This
> would not have been possible without the usb0 always coming up when it is
> hot-plugged in - this can sometimes take several minutes but seems to always
> work - thanks Robert (I assume this was you).
> Recommendation: do not use bash scripting unless you really need to; it has
> many many subtle gotchas, is very non-intuitive, is very complicated with
> many special ways of doing things that can only be learned using a lot of
> time and searching on how to do things (i.e. powerful but non-efficient for
> newbies). For a beginner, every line of code needs to be single stepped
> through using bashdb, get very familiar with >pr and >ev. Recommendation: I
> really wish I had started with pyroute2 (hoping to find time to redo). Other
> recommendations: get things working using > sudo ip (or #ip) before
> scripting, and get familiar with /sys/class/net.
>
> Item 0: I tried originally with connman, and got nowhere; I then tried with
> systemctl-networkd; this worked fine for a known environment, but I again I
> got nowhere with an unknown device and unknown sub-net; I gave up on both
> and went to custom bash scripts mostly using ip and ping (yech! this
> re-inventing the wheel should not be needed (and again is pretty well
> guaranteed to come back and get me in the future); unix was first written
> almost 45 years ago; if anything networking has deteriorated). I maybe
> should have installed NetworkManager and run with it, but it's not easily
> managed in an unknown environment (i.e. it's designed to have known devices
> described in /etc/network/interfaces, I don't know how to use it with
> unknown devices and unknown subnet without using DHCP which doesn't allow
> for fixed IPs - which I need). Note: without a network manager, you need to
> enable wpa_supplicant.service.
>
> Item 1: many of my initial problems were due to a route on eth0 being set
> even when the eth0 cable was not plugged in. This meant wlan0 (or wlan1
> depending usually but not necessarily on dongle used), could not be used
> without an >sudo route flush dev eth0. I now bring up a device, see if it
> works, and if not, flush everything (for that device) and bring it back down
> before bringing up the other device. With more time, I will use both wired
> and wireless, but that's for later. Currently, if both devices, wireless is
> used (I may change this).
>
> Item 2: adding an address (perhaps temporary) to a device, such as>sudo ip
> addr add 192.168.0.174/16 (for example - the important thing is the /16)
> allows both 192.168.0.1 to be pinged (kind of obvious), but also allows
> 192.168.1.1 to be pinged (this was not obvious to me, which allows one to
> determine which subnet the BBB is on). After determining the subnet, I go
> back to /24 addressing.
>
> Item 3: after bringing up a device, the time needed before successful
> pinging varies. Currently, I bring up a device, wait 3 seconds, try a ping,
> look at results, and if unsuccessful, try again up to 5 times, it usually
> works on iteration #2 (sometimes on #1 but not often), I've only seen 3
> iterations require once (well maybe twice - but after 7+ 10 hour days
> blindly attempted hundreds of different things, my memory and attention get
> hazy); I'm guessing this is very environment dependent.
>
> Question: is there something out there I am not aware of that wouldn't h

Re: [beagleboard] Re: Recommended Image

Dude, what are you yammering on about ?

On Sat, Dec 19, 2015 at 9:58 AM, Kenneth Martin 
wrote:

> Yes, I am starting to see that Jessie has issues:
>
> 1) 7+ full 10 hour days (some larger not many smaller) to get wired and
> wired connections (and/or), with fixed IPs, com miserable at boot and
> compatible with either 192.168.0.0/24 or 192.168.1.0/24 subnets (subnet
> unknown at boot); finally successful (but can't help wining as this is only
> the very first step on getting the new flash upgrade to work), and a
> jury-rigged re-invent the wheel solution is guaranteed to be a problem (at
> least I'm getting better with bash scripting; yech!). Recommendation: we
> need a network manager not developed for desktops in fixed and known
> environments, but for headless computers with unknown devices and routers
> at boot. Also, maybe bashdb should included by default (a suggestion for
> Robert as if he doesn't have enough to do yet - any word on the X15? - is
> there still an FCC issue?)
>
> 2) BBB rev. C with Jessie, with both USB to ubuntu host, and with power to
> 5V connector (required for wireless dongle) almost always reboots at >sudo
> shutdown -h now; doesn't happen without the usb connection.
>
> 3) Sometimes (not often but certainly occasionally) on >sudo reboot, BBB
> reboots, but no LEDs come on; it has booted up as holding the "power/reset"
> switch down of 10s does turn off the BBB.
>
> Good news, I can boot the BBB over either wireless (Tl-WN722N or
> TL-WN821N) or eth0 with both Asus (192.168.1.0/24 and TPLINK (
> 192.168.0.0/24) routers, but the time from reboot to login can be quite
> large (time varies). This would not have been possible without the usb0
> always coming up when it is hot-plugged in - this can sometimes take
> several minutes but seems to always work - thanks Robert (I assume this was
> you).
> Recommendation: do not use bash scripting unless you really need to; it
> has many many subtle gotchas, is very non-intuitive, is very complicated
> with many special ways of doing things that can only be learned using a lot
> of time and searching on how to do things (i.e. powerful but non-efficient
> for newbies). For a beginner, every line of code needs to be single stepped
> through using bashdb, get very familiar with >pr and >ev. Recommendation: I
> really wish I had started with pyroute2 (hoping to find time to redo).
> Other recommendations: get things working using > sudo ip (or #ip) before
> scripting, and get familiar with /sys/class/net.
>
> Item 0: I tried originally with connman, and got nowhere; I then tried
> with systemctl-networkd; this worked fine for a known environment, but I
> again I got nowhere with an unknown device and unknown sub-net; I gave up
> on both and went to custom bash scripts mostly using ip and ping (yech!
> this re-inventing the wheel should not be needed (and again is pretty well
> guaranteed to come back and get me in the future); unix was first written
> almost 45 years ago; if anything networking has deteriorated). I maybe
> should have installed NetworkManager and run with it, but it's not easily
> managed in an unknown environment (i.e. it's designed to have known devices
> described in /etc/network/interfaces, I don't know how to use it with
> unknown devices and unknown subnet without using DHCP which doesn't allow
> for fixed IPs - which I need). Note: without a network manager, you need to
> enable wpa_supplicant.service.
>
> Item 1: many of my initial problems were due to a route on eth0 being set
> even when the eth0 cable was not plugged in. This meant wlan0 (or wlan1
> depending usually but not necessarily on dongle used), could not be used
> without an >sudo route flush dev eth0. I now bring up a device, see if it
> works, and if not, flush everything (for that device) and bring it back
> down before bringing up the other device. With more time, I will use both
> wired and wireless, but that's for later. Currently, if both devices,
> wireless is used (I may change this).
>
> Item 2: adding an address (perhaps temporary) to a device, such as>sudo ip
> addr add 192.168.0.174/16 (for example - the important thing is the /16)
> allows both 192.168.0.1 to be pinged (kind of obvious), but also allows
> 192.168.1.1 to be pinged (this was not obvious to me, which allows one to
> determine which subnet the BBB is on). After determining the subnet, I go
> back to /24 addressing.
>
> Item 3: after bringing up a device, the time needed before successful
> pinging varies. Currently, I bring up a device, wait 3 seconds, try a ping,
> look at results, and if unsuccessful, try again up to 5 times, it usually
> works on iteration #2 (sometimes on #1 but not often), I've only seen 3
> iterations require once (well maybe twice - but after 7+ 10 hour days
> blindly attempted hundreds of different things, my memory and attention get
> hazy); I'm guessing this is very environment dependent.
>
> Question: is there something out there I am not aware of th

Re: [beagleboard] Re: Recommended Image

2015-12-19 Thread Kenneth Martin


Yes, I am starting to see that Jessie has issues:

1) 7+ full 10 hour days (some larger not many smaller) to get wired and 
wired connections (and/or), with fixed IPs, com miserable at boot and 
compatible with either 192.168.0.0/24 or 192.168.1.0/24 subnets (subnet 
unknown at boot); finally successful (but can't help wining as this is 
only the very first step on getting the new flash upgrade to work), and 
a jury-rigged re-invent the wheel solution is guaranteed to be a problem 
(at least I'm getting better with bash scripting; yech!). 
Recommendation: we need a network manager not developed for desktops in 
fixed and known environments, but for headless computers with unknown 
devices and routers at boot. Also, maybe bashdb should included by 
default (a suggestion for Robert as if he doesn't have enough to do yet 
- any word on the X15? - is there still an FCC issue?)


2) BBB rev. C with Jessie, with both USB to ubuntu host, and with power 
to 5V connector (required for wireless dongle) almost always reboots at 
>sudo shutdown -h now; doesn't happen without the usb connection.


3) Sometimes (not often but certainly occasionally) on >sudo reboot, BBB 
reboots, but no LEDs come on; it has booted up as holding the 
"power/reset" switch down of 10s does turn off the BBB.


Good news, I can boot the BBB over either wireless (Tl-WN722N or 
TL-WN821N) or eth0 with both Asus (192.168.1.0/24 and TPLINK 
(192.168.0.0/24) routers, but the time from reboot to login can be quite 
large (time varies). This would not have been possible without the usb0 
always coming up when it is hot-plugged in - this can sometimes take 
several minutes but seems to always work - thanks Robert (I assume this 
was you).
Recommendation: do not use bash scripting unless you really need to; it 
has many many subtle gotchas, is very non-intuitive, is very complicated 
with many special ways of doing things that can only be learned using a 
lot of time and searching on how to do things (i.e. powerful but 
non-efficient for newbies). For a beginner, every line of code needs to 
be single stepped through using bashdb, get very familiar with >pr and 
>ev. Recommendation: I really wish I had started with pyroute2 (hoping 
to find time to redo). Other recommendations: get things working using > 
sudo ip (or #ip) before scripting, and get familiar with /sys/class/net.


Item 0: I tried originally with connman, and got nowhere; I then tried 
with systemctl-networkd; this worked fine for a known environment, but I 
again I got nowhere with an unknown device and unknown sub-net; I gave 
up on both and went to custom bash scripts mostly using ip and ping 
(yech! this re-inventing the wheel should not be needed (and again is 
pretty well guaranteed to come back and get me in the future); unix was 
first written almost 45 years ago; if anything networking has 
deteriorated). I maybe should have installed NetworkManager and run with 
it, but it's not easily managed in an unknown environment (i.e. it's 
designed to have known devices described in /etc/network/interfaces, I 
don't know how to use it with unknown devices and unknown subnet without 
using DHCP which doesn't allow for fixed IPs - which I need). Note: 
without a network manager, you need to enable wpa_supplicant.service.


Item 1: many of my initial problems were due to a route on eth0 being 
set even when the eth0 cable was not plugged in. This meant wlan0 (or 
wlan1 depending usually but not necessarily on dongle used), could not 
be used without an >sudo route flush dev eth0. I now bring up a device, 
see if it works, and if not, flush everything (for that device) and 
bring it back down before bringing up the other device. With more time, 
I will use both wired and wireless, but that's for later. Currently, if 
both devices, wireless is used (I may change this).


Item 2: adding an address (perhaps temporary) to a device, such as>sudo 
ip addr add 192.168.0.174/16 (for example - the important thing is the 
/16) allows both 192.168.0.1 to be pinged (kind of obvious), but also 
allows 192.168.1.1 to be pinged (this was not obvious to me, which 
allows one to determine which subnet the BBB is on). After determining 
the subnet, I go back to /24 addressing.


Item 3: after bringing up a device, the time needed before successful 
pinging varies. Currently, I bring up a device, wait 3 seconds, try a 
ping, look at results, and if unsuccessful, try again up to 5 times, it 
usually works on iteration #2 (sometimes on #1 but not often), I've only 
seen 3 iterations require once (well maybe twice - but after 7+ 10 hour 
days blindly attempted hundreds of different things, my memory and 
attention get hazy); I'm guessing this is very environment dependent.


Question: is there something out there I am not aware of that wouldn't 
have taken so much time? Maybe I shouldn't ask this question as a Yes 
answer will make me look pretty foolish; at least I can now read bash 
code, for  example:

dev=

Re: [beagleboard] Running Qt gui application on BBB

2015-12-19 Thread John Syne

i haven’t done this in ages, but try to run your QT app with the "-platform 
eglfs” option. I’m assuming you built QT with EGL. 

Regards,
John




> On Dec 19, 2015, at 3:46 AM, Bremenpl  wrote:
> 
> Hello there,
> I managed to set up qt 5.3.2 on the beaglebone. I have build everything there 
> and it took ages but it works :).
> 
> Next step is that I need to check either it is possible to run qt app on bbb 
> without gui with qws parameter. Because at the moment when i run it with qws 
> i get QXcbconnection: Could not connect to display. I need to do it like this 
> because thw gui is really really slow.
> 
> On December 15, 2015 6:10:13 AM John Syne  wrote:
> 
>> For purely building armhf code, Odroid XU4 might be a good choice:
>> 
>> http://www.hardkernel.com/main/main.php 
>> 
>> 
>> This is an Octacore processor with 4 CortexA15 and 4 CortexA7 processors. I 
>> don’t know how good their kernel/debian support is, but I know Robert had 
>> looked at this board or a predecessor in the past, so perhaps he can give 
>> his input here.
>> 
>> Clearly this board doesn’t have the flexibility of the BeagleBoard-x15 with 
>> it’s dual DSP, Dual CortexM4, Quad PRU, SATA interface, PCIe interface, etc. 
>> 
>> Regards,
>> John
>> 
>> 
>> 
>> 
>>> On Dec 14, 2015, at 4:29 PM, William Hermans >> > wrote:
>>> 
>>> Anyway, the main problem with the rPI 2 is that it has no "fast" non 
>>> destructive storage. But the Omilex . . let me look it up.
>>> 
>>> https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2-4GB/open-source-hardware
>>>  
>>> 
>>>  Has SATA and GbE both. Dual cores too I think. However, you'd have to ask 
>>> someone who has one how well they think it would work as a build board. 
>>> RObert might know, as his Debian build guide also includes this board too I 
>>> believe.
>>> 
>>> On Mon, Dec 14, 2015 at 5:25 PM, William Hermans >> > wrote:
>>> https://www.adafruit.com/product/2358 
>>> 
>>> 
>>> On Mon, Dec 14, 2015 at 5:23 PM, William Hermans >> > wrote:
>>> The new board is armv7. Positively.
>>> 
>>> On Mon, Dec 14, 2015 at 5:24 PM, Bremenpl >> > wrote:
>>> Okay, thank :P. I am quite sure raspberry pi is not hard float.
>>> 
>>> W dniu 2015-12-15 o 01:21, William Hermans pisze:
 So just thinking for a minute. A Raspberry PI 2, the new board with quad 
 cores, and 1 GB ram would probably work fairly decent as a build system 
 for the Beaglebones. Granted, something like the X15, of that new nVidia 
 ARM board, or even the Omelex A20 board with SATA would probably be a much 
 better choice if cost is not a problem.
 
 By the way, I have no idea what Robert is talking about. You need to ask 
 him.
 
 On Mon, Dec 14, 2015 at 5:15 PM, Bremenpl >>> > wrote:
 I have just flashed my BeagleBone Black emmc  with lxqt image linked by 
 Robert. I cant seem to find qmake anywhere. I thought there would be qt 
 installed and all. Am I missing something again?
 
 W dniu 2015-12-15 o 00:54, William Hermans pisze:
> Not necessarily, but consider this. How much does an embedded systems 
> specialist in your area get paid per hour ? In my area, about 15-20 years 
> ago. The cost of a board like the X15 would have been absorbed in roughly 
> half a day. That is to say, an embedded systems specialist could buy a 
> board for $239 after working roughly half a day. 
> 
> Now take into account that figuring out how to cross compile something 
> like this is a serious headache, and often takes days, if not weeks to 
> get right . . .
> 
> On Mon, Dec 14, 2015 at 4:32 PM, Bremenpl < 
> breme...@gmail.com 
> > wrote:
> So if I understand correctly, I should have a second board that is more 
> powerfull than beagle just to compile the code for beagle?
> 
> W dniu 2015-12-15 o 00:26, William Hermans pisze:
>> I cant change the board right now, it has to be BeagleBone Black. Thats 
>> why I need to build on my host. Did you succed on installing QT5.1 and 
>> deploying it to BeagleBone Black? Maybe I should use it instead of 4.8.6 
>> if its easier?
>> 
>> No one was saying change boards. Use the same board, but use a faster, 
>> more powerful ARM board to compile native ARM executable. The reasons 
>> are simple. No need to mess with cross compiling, which in many cases is 
>> messy, and sometimes near impossible.
>> 
>> You don't think Robert spends days, or weeks compiling packages do you ? 
>> But why don't we ask Robert. Robert, hey what percentage of the packages 
>> you build

Re: [beagleboard] Re: bonescript - link to USR leds defective



On Saturday, 19 December 2015 18:37:03 UTC+1, RobertCNelson wrote:
>
> On Sat, Dec 19, 2015 at 7:12 AM, Maurice H.  > wrote: 
>
> bonescript hasn't been ported to v4.1.x yet 
>
>
>
That explains a lot. :-)
Thanks I'm back on 3.8 now. 

-- 
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] /sys/class/hwmon not populated on Jessie


I did. Thanks. 

Any chance this could be implemented by a third-party? Or is the TI-code a 
proprietary blob?


>
> Feel free to downgrae to 3.8.x if you need it: 
>
> cd /opt/scripts/tools/ 
> git pull 
> sudo ./update_kernel.sh --bone-channel --stable 
>
> 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] Updating Time on Boot in android OS

2015-12-19 Thread Sanket Nainani

I am running android 4.4.2 on a BeagleBone Black.

I have used a DS1307 RTC externally for the purpose of updating the Time 
everytime the OS boots up.
Or using the internal clock running on power off with a battery ?

Is there a way to do so on Boot ? 
or is there any code that can be put in an app to update time ?

Any sort of help is appreciated .. Extra languages or apps or hardware can 
be used.

Thank you.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBB's uboot-2015.10

Thank you so much Robert, now my u-boot is stable. But I'm having trouble 
in kernel console. I've posted a question requesting for support regarding 
this

https://groups.google.com/forum/#!category-topic/beagleboard/support/newbies/beaglebone-black/software/u-boot/07Nq1CYPpAI
 


I'm new to Linux. Sorry for my nuisance.

Regards,
Bharath

-- 
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] BBB Serial Console


Hello,

I'm trying to build the kernel for my BBB from the source downloaded from, 

* https://github.com/beagleboard/linux/tree/3.8 
*But once I download the 
built image from u-boot to DRAM, the kernel doesn't show any message. I 
believe it has to do with serial console.

In menuconfig, kernel hacking->kernel low-level debug this is what I've 
got. I don't see any UART here.



Can anyone please guide me, how to tackle this? and what the chances to be 
done in dts?

Regards,
Bharath

-- 
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

Hello,

I'm trying to build the kernel for my BBB from the source downloaded from, 

* https://github.com/beagleboard/linux/tree/3.8*But once I download the 
built image from u-boot to DRAM, the kernel doesn't show any message. I 
believe it has to do with serial console.

In menuconfig, kernel hacking->kernel low-level debug this is what I've 
got. I don't see any UART here.



Can anyone please guide me, how to tackle this? and what the chances to be 
done in dts?

Regards,
Bharath

-- 
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] BeagleBone Black does't start, Power ON LED blink once and other are off.

This is because your ad adapter sucks.  Get a new one.  That is the short
answer.  I had this EXACT same issue.  I got an adapter from adafruit and
boom it all worked perfectly.


Long answer:

https://groups.google.com/forum/#!searchin/beagleboard/riley$20power/beagleboard/TY9kfk9Ep5k/7RZeOyALCwAJ



On Sat, Dec 19, 2015 at 2:43 AM,  wrote:

> Hi guys,
>
>  I have a problem with my BeagleBone Black i purches it from
> element14, when i start first using it works fine, with using USB power.
> Now my BBB not started when i apply 5V DC 2Amp power supply and also by
> USB, it show all LED OFF and power LED Blinks Once when it power, and also
> pressing onboard power push button.
>what wrong with it do't know Please Help.
>
> Thanks for your help in advance
>
> Regards,
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> 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] BeagleBone Black does't start, Power ON LED blink once and other are off.

AC not ad.  Sorry!

On Sat, Dec 19, 2015 at 12:52 PM, Riley Porter 
wrote:

> This is because your ad adapter sucks.  Get a new one.  That is the short
> answer.  I had this EXACT same issue.  I got an adapter from adafruit and
> boom it all worked perfectly.
>
>
> Long answer:
>
>
> https://groups.google.com/forum/#!searchin/beagleboard/riley$20power/beagleboard/TY9kfk9Ep5k/7RZeOyALCwAJ
>
>
>
> On Sat, Dec 19, 2015 at 2:43 AM,  wrote:
>
>> Hi guys,
>>
>>  I have a problem with my BeagleBone Black i purches it from
>> element14, when i start first using it works fine, with using USB power.
>> Now my BBB not started when i apply 5V DC 2Amp power supply and also by
>> USB, it show all LED OFF and power LED Blinks Once when it power, and also
>> pressing onboard power push button.
>>what wrong with it do't know Please Help.
>>
>> Thanks for your help in advance
>>
>> Regards,
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> 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] BeagleBone Black does't start, Power ON LED blink once and other are off.

This is because your ad adapter sucks.  Get a new one.  That is the short
answer.  I had this EXACT same issue.  I got an adapter from adafruit and
boom it all worked perfectly.

Long answer:
https://mail.google.com/mail/u/0/#search/label%3Abeagleboard++riley/151706c64297dabb

:)

Riley

On Sat, Dec 19, 2015 at 2:43 AM,  wrote:

> Hi guys,
>
>  I have a problem with my BeagleBone Black i purches it from
> element14, when i start first using it works fine, with using USB power.
> Now my BBB not started when i apply 5V DC 2Amp power supply and also by
> USB, it show all LED OFF and power LED Blinks Once when it power, and also
> pressing onboard power push button.
>what wrong with it do't know Please Help.
>
> Thanks for your help in advance
>
> Regards,
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> 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: Recommended Image

On Sat, Dec 19, 2015 at 2:50 AM, Maurice H.  wrote:
> There are still a lot of roblems with the Jessie image. At this moment I'd
> advice to go for Wheezy.

All those problems you have are with the newer kernel..

Feel free to downgrade to 3.8.x

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --bone-channel --stable

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: bonescript - link to USR leds defective

On Sat, Dec 19, 2015 at 7:12 AM, Maurice H.  wrote:
> Also, this error bothers me:
> Dec 19 14:08:31 bbone ledsoff:
> Dec 19 14:08:31 bbone ledsoff: module.js:340
> Dec 19 14:08:31 bbone ledsoff: throw err;
> Dec 19 14:08:31 bbone ledsoff:   ^
> Dec 19 14:08:31 bbone ledsoff: Error: Cannot find module 'bonescript'
> Dec 19 14:08:31 bbone ledsoff: at Function.Module._resolveFilename
> (module.js:338:15)
> Dec 19 14:08:31 bbone ledsoff: at Function.Module._load
> (module.js:280:25)
> Dec 19 14:08:31 bbone ledsoff: at Module.require (module.js:364:17)
> Dec 19 14:08:31 bbone ledsoff: at require (module.js:380:17)
> Dec 19 14:08:31 bbone ledsoff: at Object.
> (/root/boneboot/ledsoff.js:1:69)
> Dec 19 14:08:31 bbone ledsoff: at Module._compile (module.js:456:26)
> Dec 19 14:08:31 bbone ledsoff: at Object.Module._extensions..js
> (module.js:474:10)
> Dec 19 14:08:31 bbone ledsoff: at Module.load (module.js:356:32)
> Dec 19 14:08:31 bbone ledsoff: at Function.Module._load
> (module.js:312:12)
> Dec 19 14:08:31 bbone ledsoff: at Function.Module.runMain
> (module.js:497:10)
>
> So even getting bonescript to detect the hardware correctly means it'll
> still not work :-(

bonescript hasn't been ported to v4.1.x yet

Feel free to downgrade to 3.8.x

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --bone-channel --stable

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] /sys/class/hwmon not populated on Jessie

On Sat, Dec 19, 2015 at 2:44 AM, Maurice H.  wrote:
> I tried this image:
> https://rcn-ee.com/rootfs/bb.org/testing/2015-12-13/lxqt-4gb/bone-debian-8.2-lxqt-4gb-armhf-2015-12-13-4gb.img.xz
>
> As I understand it this is the most recent jessie build.
> Unfortunately on this image /sys/class/hwmon is not populated.
>
> It *is* populated on the wheezy builds.
>
> Do I need to install a package or kernel-module that solves this problem?
> Or is there a fix in the pipeline?

TI deemed the internal temp sensor too "inaccurate" to push mainline..

Feel free to downgrae to 3.8.x if you need it:

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --bone-channel --stable

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] Need help with multiple variables over python socket.

2015-12-19 Thread Jerry Davis

there are several ways to accomplish this, limited to your imagination.
lets assume that the number of variables you want to send does not vary.

1. if they are binaries, you could pack it all into a string and send the
string, then unpack it on the receiving side (see struct module)

2. you could just format the variables into a string, with some delimiter
(like , or ;) in between the values.

3. you could use json (see the json module in python doc's, it really is
straightforward). json.dumps creates the json string, jso.loads does the
other side of the equation. just create the string, send it, and the other
side does a loads, and you now have the variables back.

4. others could be done, but this is all I can readily think of on a
Saturday morning.





--
Extra Ham Operator: K7AZJ
Registered Linux User: 275424
Raspberry Pi and Arduino developer


*The most exciting phrase to hear in science - the one that heralds new
discoveries - is not "Eureka!" but "That's funny...".*- Isaac. Asimov

*I*
*f you give someone a program, you will frustrate them for a day; if you
teach them how to program, you will frustrate them for a lifetime. *-
Anonymous


*If writing good code requires very little comments, then writing really
excellent code requires no comments at all!*- Ken Thompson

On Sat, Dec 19, 2015 at 8:52 AM, William Hermans  wrote:

> This is a programming 101 question that has nothing to do with the Beagle
> hardware. You should create an account on stackoverflow.com, and pose
> your question there. Assuming, someone has not already asked a similar
> question, as they do not realy care for duplicate questions . . .
> Basically, that means search their site before asking.
>
> On Fri, Dec 18, 2015 at 10:25 PM,  wrote:
>
>> I'm trying to build a wifi controlled rover with a BBB using python.
>> My basic plan is to use a joystick on the client, store multiple joystick
>> inputs to variables, then relay the variables via socket to the BBB.
>>
>> I initially thought this could easily be done by using socket until I
>> realized that I can't find a way to differentiate the variables from one
>> another. I've thought of sending a specific string before sending the
>> actual joystick value so that I could just add something simple like "if
>> recv=axis0 then recv=joystick variable", but this proved extremely slow and
>> unreliable during joystick movement, especially if it was more than one
>> axis being moved.
>> I read that json could be used but I didn't quite understand it.
>>
>> What I need is a simple and efficient way to send multiple variables over
>> an internet connection through python. It does not matter if all variables
>> are sent at once as long as they can be differentiated.
>>
>> Any help is really appreciated.
>>
>> --
>> 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] Need help with multiple variables over python socket.

This is a programming 101 question that has nothing to do with the Beagle
hardware. You should create an account on stackoverflow.com, and pose your
question there. Assuming, someone has not already asked a similar question,
as they do not realy care for duplicate questions . . . Basically, that
means search their site before asking.

On Fri, Dec 18, 2015 at 10:25 PM,  wrote:

> I'm trying to build a wifi controlled rover with a BBB using python.
> My basic plan is to use a joystick on the client, store multiple joystick
> inputs to variables, then relay the variables via socket to the BBB.
>
> I initially thought this could easily be done by using socket until I
> realized that I can't find a way to differentiate the variables from one
> another. I've thought of sending a specific string before sending the
> actual joystick value so that I could just add something simple like "if
> recv=axis0 then recv=joystick variable", but this proved extremely slow and
> unreliable during joystick movement, especially if it was more than one
> axis being moved.
> I read that json could be used but I didn't quite understand it.
>
> What I need is a simple and efficient way to send multiple variables over
> an internet connection through python. It does not matter if all variables
> are sent at once as long as they can be differentiated.
>
> Any help is really appreciated.
>
> --
> 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] BeagleBone Black does't start, Power ON LED blink once and other are off.

2015-12-19 Thread rupesh . khatpe

Hi guys,

 I have a problem with my BeagleBone Black i purches it from element14, 
when i start first using it works fine, with using USB power. Now my BBB 
not started when i apply 5V DC 2Amp power supply and also by USB, it show 
all LED OFF and power LED Blinks Once when it power, and also pressing 
onboard power push button.
   what wrong with it do't know Please Help.

Thanks for your help in advance

Regards,

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Need help with multiple variables over python socket.

2015-12-19 Thread brandoningram21

I'm trying to build a wifi controlled rover with a BBB using python.
My basic plan is to use a joystick on the client, store multiple joystick 
inputs to variables, then relay the variables via socket to the BBB.

I initially thought this could easily be done by using socket until I 
realized that I can't find a way to differentiate the variables from one 
another. I've thought of sending a specific string before sending the 
actual joystick value so that I could just add something simple like "if 
recv=axis0 then recv=joystick variable", but this proved extremely slow and 
unreliable during joystick movement, especially if it was more than one 
axis being moved.
I read that json could be used but I didn't quite understand it.

What I need is a simple and efficient way to send multiple variables over 
an internet connection through python. It does not matter if all variables 
are sent at once as long as they can be differentiated.

Any help is really appreciated.

-- 
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: Error: Cannot find module 'bonescript'

I've solved this by adding a line to the cron job that sets the environment 
variable NODE_PATH.

NODE_PATH=/usr/local/lib/node_modules
# m h dom mon dow user  command
@reboot   rootsleep 120 && /usr/bin/nodejs /root/boneboot/ledsoff.js 2>&
1 | logger -p info -t ledsoff


On Friday, 18 December 2015 22:38:53 UTC+1, Maurice H. wrote:
>
>
> I have this simple script that I want to execute at boot time.
>
> The script:
> root@bbone:~# cat boneboot/ledsoff.js
> var b=require('bonescript');
>
>
> b.pinMode('USR0', 'out');
> b.pinMode('USR1', 'out');
> b.pinMode('USR2', 'out');
> b.pinMode('USR3', 'out');
>
>
> b.digitalWrite('USR0', 0);
> b.digitalWrite('USR1', 0);
> b.digitalWrite('USR2', 0);
> b.digitalWrite('USR3', 0);
>
> To run it at boot I've created a file in /etc/cron.d which looks like this:
> root@bbone:~# cat /etc/cron.d/boneboot
> # m h dom mon dow user  command
> @reboot   rootsleep 120 && /usr/bin/nodejs /root/boneboot/ledsoff.js 2
> >&1 | logger -p info -t ledsoff
>
> Unfortunately, when I reboot the BBB the code is not executed succesfully 
> as shown by the log:
> root@bbone:~# cat /var/log/syslog
> Dec 18 21:54:49 bbone ledsoff:
> Dec 18 21:54:49 bbone ledsoff: module.js:340
> Dec 18 21:54:49 bbone ledsoff: throw err;
> Dec 18 21:54:49 bbone ledsoff:   ^
> Dec 18 21:54:50 bbone ledsoff: Error: Cannot find module 'bonescript'
> Dec 18 21:54:50 bbone ledsoff: at Function.Module._resolveFilename (
> module.js:338:15)
> Dec 18 21:54:50 bbone ledsoff: at Function.Module._load (module.js:280
> :25)
> Dec 18 21:54:50 bbone ledsoff: at Module.require (module.js:364:17)
> Dec 18 21:54:50 bbone ledsoff: at require (module.js:380:17)
> Dec 18 21:54:50 bbone ledsoff: at Object. (/root/boneboot/
> ledsoff.js:1:69)
> Dec 18 21:54:50 bbone ledsoff: at Module._compile (module.js:456:26)
> Dec 18 21:54:50 bbone ledsoff: at Object.Module._extensions..js (
> module.js:474:10)
> Dec 18 21:54:50 bbone ledsoff: at Module.load (module.js:356:32)
> Dec 18 21:54:50 bbone ledsoff: at Function.Module._load (module.js:312
> :12)
> Dec 18 21:54:50 bbone ledsoff: at Function.Module.runMain (module.js:
> 497:10)
>
> However, when I logged in as root, the code executes normally.
>
> Any suggestions on how to proceed?
>
>
>
>

-- 
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: bonescript - link to USR leds defective

Also, this error bothers me:
Dec 19 14:08:31 bbone ledsoff:
Dec 19 14:08:31 bbone ledsoff: module.js:340
Dec 19 14:08:31 bbone ledsoff: throw err;
Dec 19 14:08:31 bbone ledsoff:   ^
Dec 19 14:08:31 bbone ledsoff: Error: Cannot find module 'bonescript'
Dec 19 14:08:31 bbone ledsoff: at Function.Module._resolveFilename (
module.js:338:15)
Dec 19 14:08:31 bbone ledsoff: at Function.Module._load (module.js:280:
25)
Dec 19 14:08:31 bbone ledsoff: at Module.require (module.js:364:17)
Dec 19 14:08:31 bbone ledsoff: at require (module.js:380:17)
Dec 19 14:08:31 bbone ledsoff: at Object. (/root/boneboot/
ledsoff.js:1:69)
Dec 19 14:08:31 bbone ledsoff: at Module._compile (module.js:456:26)
Dec 19 14:08:31 bbone ledsoff: at Object.Module._extensions..js (module.
js:474:10)
Dec 19 14:08:31 bbone ledsoff: at Module.load (module.js:356:32)
Dec 19 14:08:31 bbone ledsoff: at Function.Module._load (module.js:312:
12)
Dec 19 14:08:31 bbone ledsoff: at Function.Module.runMain (module.js:497
:10)

So even getting bonescript to detect the hardware correctly means it'll 
still not work :-(

-- 
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] Running Qt gui application on BBB

2015-12-19 Thread Bremenpl

Hello there,
I managed to set up qt 5.3.2 on the beaglebone. I have build everything
there and it took ages but it works :).

On December 15, 2015 6:10:13 AM John Syne wrote:

For purely building armhf code, Odroid XU4 might be a good choice:

http://www.hardkernel.com/main/main.php

Clearly this board doesn’t have the flexibility of the BeagleBoard-x15 with
it’s dual DSP, Dual CortexM4, Quad PRU, SATA interface, PCIe interface, etc.

Regards,
John

On Dec 14, 2015, at 4:29 PM, William Hermans wrote:

Anyway, the main problem with the rPI 2 is that it has no "fast" non
destructive storage. But the Omilex . . let me look it up.

https://www.olimex.com/Products/OLinuXino/A20/A20-OLinuXIno-LIME2-4GB/open-source-hardware

On Mon, Dec 14, 2015 at 5:25 PM, William Hermans > wrote:

https://www.adafruit.com/product/2358

On Mon, Dec 14, 2015 at 5:23 PM, William Hermans > wrote:

The new board is armv7. Positively.

On Mon, Dec 14, 2015 at 5:24 PM, Bremenpl > wrote:

Okay, thank :P. I am quite sure raspberry pi is not hard float.

By the way, I have no idea what Robert is talking about. You need to ask him.

Now take into account that figuring out how to cross compile something like
this is a serious headache, and often takes days, if not weeks to get right
. . .

On Mon, Dec 14, 2015 at 4:00 PM, Bremenpl <
breme...@gmail.com >
wrote:

Ahh., thats the way, you are right...
Thank you for all the support guys, I really mean it! Hope to get it
working in a while if i wont fall asleep on my desk!

On December 14, 2015 11:55:59 PM John Syne <
john3...@gmail.com >
wrote:

On Dec 14, 2015, at 2:34 PM, Bremenpl <
breme...@gmail.com >
wrote:

Okay

[beagleboard] Re: Recommended Image

There are still a lot of roblems with the Jessie image. At this moment I'd 
advice to go for Wheezy.

On Tuesday, 15 December 2015 21:45:25 UTC+1, Bit Pusher wrote:
>
> I'm starting to update from an outdated image and to be clean am planning 
> on starting from scratch with a newly flashed image.
> On http://beagleboard.org/latest-images there are two possible Debian 
> images from Nov. 12'th, Wheezy 7.9 and Jessie 8.2. It is not clear
> which image I should use. I'm using the PRU and SPI1 (which also 
> previously required SPI0 to be loaded) and many python modules. I load the 
> PRU, SPI0 and SPI1
> using three device tree overlays. Could someone recommend which image to 
> use? Thanks and appreciated.
>

-- 
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] bonescript - link to USR leds defective

I tried this 
image: 
https://rcn-ee.com/rootfs/bb.org/testing/2015-12-13/lxqt-4gb/bone-debian-8.2-lxqt-4gb-armhf-2015-12-13-4gb.img.xz

As I understand it this is the most recent jessie build. 

I tried to run this script:
root@bbone:~/boneboot# cat ledsoff.js
var b=require('bonescript');


b.pinMode('USR0', 'out');
b.pinMode('USR1', 'out');
b.pinMode('USR2', 'out');
b.pinMode('USR3', 'out');


b.digitalWrite('USR0', 0);
b.digitalWrite('USR1', 0);
b.digitalWrite('USR2', 0);
b.digitalWrite('USR3', 0);

This is the result:
root@bbone:~/boneboot# nodejs ledsoff.js
error: Unable to find LED: usr0
error: Unable to find LED: usr1
error: Unable to find LED: usr2
error: Unable to find LED: usr3
error: Unable to find gpio: /sys/class/leds/beaglebone::usr0/brightness
error: Unable to write to /sys/class/leds/beaglebone::usr0/brightness
error: Unable to find gpio: /sys/class/leds/beaglebone::usr1/brightness
error: Unable to write to /sys/class/leds/beaglebone::usr1/brightness
error: Unable to find gpio: /sys/class/leds/beaglebone::usr2/brightness
error: Unable to write to /sys/class/leds/beaglebone::usr2/brightness
error: Unable to find gpio: /sys/class/leds/beaglebone::usr3/brightness
error: Unable to write to /sys/class/leds/beaglebone::usr3/brightness

Nothing strange here:
root@bbone:~/boneboot# ls -al /sys/class/leds
total 0
drwxr-xr-x  2 root root 0 Dec 19 09:43 .
drwxr-xr-x 54 root root 0 Dec 19 09:30 ..
lrwxrwxrwx  1 root root 0 Dec 19 09:22 beaglebone:green:usr0 -> ../../
devices/platform/leds/leds/beaglebone:green:usr0
lrwxrwxrwx  1 root root 0 Dec 19 09:22 beaglebone:green:usr1 -> ../../
devices/platform/leds/leds/beaglebone:green:usr1
lrwxrwxrwx  1 root root 0 Dec 19 09:22 beaglebone:green:usr2 -> ../../
devices/platform/leds/leds/beaglebone:green:usr2
lrwxrwxrwx  1 root root 0 Dec 19 09:22 beaglebone:green:usr3 -> ../../
devices/platform/leds/leds/beaglebone:green:usr3

Any suggestions how to get this to work are welcome.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] /sys/class/hwmon not populated on Jessie