[beagleboard] Re: Beaglebone Green - Experience and Notes

[Chris M]

me (Chris M change) 

7:43 PM (46 minutes ago) 
Restarting going to use universala for uart, pwm, and gpio (MRAA and 
ADAFruit_BBIO both work in python)
web cam will be using python-v4l2capture 

> VERSION
> # uname -a
> Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l 
> GNU/Linux
> UPDATE apt-get database 
> # apt-get update
> REMOUNT EXT SD CARD
> # mkdir /extsd
> # mount /dev/mmcblk0p1 /extsd
> # vi /etc/fstab
> /dev/mmcblk0p1  /extsd  ext4defaults0   0
> reboot and check
> INSTALL PACKAGES
>
 

# apt-get upgrade

installing v4l2capture

# git clone https://github.com/philips/libv4l
# cd libv4l
# make
#make install

install  v4l2capture

git clone https://github.com/gebart/python-v4l2capture
python-v4l2capture uses distutils.
To build: ./setup.py build
To build and install: ./setup.py install

pip install pillow

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a1bfb173-b364-4d30-8cdb-f600d133f527%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB IoT image with Pi-Hole: Success, but may have to remove connman and nodejs

[neutrinos4all]

That was very helpful / super informative, thanks!

On Wednesday, January 4, 2017 at 9:21:42 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Jan 4, 2017 at 8:08 PM, neutrinos4all  > wrote: 
> > Ah, hmm that's interesting. Thanks for the tip. 
> > 
> > By "makes wifi easier," you mean that it makes managing wifi connections 
> > easier yeah? 
>
> Specially from the command line: 
>
> sudo connmanctl 
>
> #connmanctl> enable wifi 
> #connmanctl> scan wifi 
> #connmanctl> services 
> #connmanctl> agent on 
> #connmanctl> connect wifi_*_managed_psk 
> #connmanctl> quit 
>
> (no playing with wpa_passphase, etc...) 
>
> > Also, since one of connman's advertised strengths is its light resource 
> use, 
> > just wondering: is it a substantial savings over something like network 
> > manager? 
>
> Well, if nmcli was cut out of the debian network-manager, then connman 
> vs nmcli would be a wash.. 
>
> But since network-manager (in debian) brings in a lot of gtk3 
> dependices, it's not worth it unless you want a gtk3 based desktop. 
>
> Since we went for qt (qt's always had a eglfs layer so sgx graphics 
> could be used), there's a small gui for connman (CMST) 
>
> https://github.com/andrew-bibb/cmst/wiki/Screenshots 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/95cdf0b1-17be-4f78-a36e-4247257f24be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB IoT image with Pi-Hole: Success, but may have to remove connman and nodejs

[Robert Nelson]

On Wed, Jan 4, 2017 at 8:08 PM, neutrinos4all  wrote:
> Ah, hmm that's interesting. Thanks for the tip.
>
> By "makes wifi easier," you mean that it makes managing wifi connections
> easier yeah?

Specially from the command line:

sudo connmanctl

#connmanctl> enable wifi
#connmanctl> scan wifi
#connmanctl> services
#connmanctl> agent on
#connmanctl> connect wifi_*_managed_psk
#connmanctl> quit

(no playing with wpa_passphase, etc...)

> Also, since one of connman's advertised strengths is its light resource use,
> just wondering: is it a substantial savings over something like network
> manager?

Well, if nmcli was cut out of the debian network-manager, then connman
vs nmcli would be a wash..

But since network-manager (in debian) brings in a lot of gtk3
dependices, it's not worth it unless you want a gtk3 based desktop.

Since we went for qt (qt's always had a eglfs layer so sgx graphics
could be used), there's a small gui for connman (CMST)

https://github.com/andrew-bibb/cmst/wiki/Screenshots

Regards,

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

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

Re: [beagleboard] BBB IoT image with Pi-Hole: Success, but may have to remove connman and nodejs

[neutrinos4all]

Ah, hmm that's interesting. Thanks for the tip. 

By "makes wifi easier," you mean that it makes managing wifi connections 
easier yeah?

Also, since one of connman's advertised strengths is its light resource 
use, just wondering: is it a substantial savings over something like 
network manager?

On Wednesday, January 4, 2017 at 8:48:48 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Jan 4, 2017 at 4:52 PM, neutrinos4all  > wrote: 
> > I was redirected here from your Twitter account maintainer to post my 
> > experience installing pi-hole on a BBB with a freshly-flashed IoT image 
> > (version information below). Hopefully this will help someone else in 
> the 
> > future. 
> > 
> > What I'm using 
> > 
> > element14 BeagleBone Black rev. C, connected via ethernet to router 
> > Asus NT-66R router 
> > Debian 8.6 ("Jessie") IoT image, retrieved from here. 
> > 
> > What happened 
> > After flashing the IoT image to onboard eMMC and installing pi-hole 
> > successfully, I had no DNS connectivity: could ping IPs, but not visit 
> > websites by URL from any machine on the LAN. What's more, dnsmasq was 
> not 
> > running. I determined that connman was binding to port 53 rather than 
> > dnsmasq, thereby preventing dnsmasq from resolving DNS requests for 
> pi-hole 
> > (confirm using command lsof +M -nPi :53 to see the services bound to 
> that 
> > port). Uninstalling connman and restarting the network service allowed 
> > dnsmasq to run, fixing the DNS problem. Web browsing was immediately 
> > restored across the LAN. 
>
> Depending what is hooked up wifi/ethernet/etc, we dynamically 
> enable/disable conman's dnsproxy option: 
>
> So instead of purging connman, you do below: 
>
> sudo systemctl stop connman.service 
> sudo sed -i -e 's:connmand -n:connmand -n --nodnsproxy:g' 
> /lib/systemd/system/connman.service 
> sudo systemctl daemon-reload 
> sudo systemctl start connman.service 
>
> Then dnsmasq will fire up just fine, and you can still use connman for 
> managing your connections (connman makes wifi easier).. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f02fae14-e940-4bc9-8dc2-41936f19e26e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: [beagle-alpha] Re: debian testing: 2017-01-03 (U-Boot Cape Manager edition)

[Robert Nelson]

On Wed, Jan 4, 2017 at 7:53 PM, Baozhu Zuo  wrote:
> Yes, you can see
> root@beaglebone:/sys# cat ./devices/platform/bone_capemgr/slots
>  0: P---L-   0 Beaglebone green hdmi cape,00A0,Seeed,BB-GREEN-HDMI
>  1: PF  -1
>  2: PF  -1
>  3: PF  -1
>
> This dirver will be pull soon. display is fine. auido has a bit noise.

Yay!!! that original it66121 driver we had for 3.8.x just looked way
to yucky...  I'm glad you got it working on later kernel's!

Regards,


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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYh5s1BnUAZ-wTBceoQ634_6%2BC_XTMjNpsz3_3HPTEJWvw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB IoT image with Pi-Hole: Success, but may have to remove connman and nodejs

[Robert Nelson]

On Wed, Jan 4, 2017 at 4:52 PM, neutrinos4all  wrote:
> I was redirected here from your Twitter account maintainer to post my
> experience installing pi-hole on a BBB with a freshly-flashed IoT image
> (version information below). Hopefully this will help someone else in the
> future.
>
> What I'm using
>
> element14 BeagleBone Black rev. C, connected via ethernet to router
> Asus NT-66R router
> Debian 8.6 ("Jessie") IoT image, retrieved from here.
>
> What happened
> After flashing the IoT image to onboard eMMC and installing pi-hole
> successfully, I had no DNS connectivity: could ping IPs, but not visit
> websites by URL from any machine on the LAN. What's more, dnsmasq was not
> running. I determined that connman was binding to port 53 rather than
> dnsmasq, thereby preventing dnsmasq from resolving DNS requests for pi-hole
> (confirm using command lsof +M -nPi :53 to see the services bound to that
> port). Uninstalling connman and restarting the network service allowed
> dnsmasq to run, fixing the DNS problem. Web browsing was immediately
> restored across the LAN.

Depending what is hooked up wifi/ethernet/etc, we dynamically
enable/disable conman's dnsproxy option:

So instead of purging connman, you do below:

sudo systemctl stop connman.service
sudo sed -i -e 's:connmand -n:connmand -n --nodnsproxy:g'
/lib/systemd/system/connman.service
sudo systemctl daemon-reload
sudo systemctl start connman.service

Then dnsmasq will fire up just fine, and you can still use connman for
managing your connections (connman makes wifi easier)..

Regards,

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

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

[beagleboard] Re: [beagle-alpha] Re: debian testing: 2017-01-03 (U-Boot Cape Manager edition)

[Robert Nelson]

On Wed, Jan 4, 2017 at 7:13 PM, Baozhu Zuo  wrote:
> can we put  clk_mcasp0 to cape dts now ?
> https://github.com/RobertCNelson/dtb-rebuilder/blob/4.1-ti/src/arm/am335x-boneblack-audio.dts#L17-L28

We should be able to now, it'll need a v4.4.x-ti or v4.9.x+ kernel, see:

BB-HDMI-TDA998x-00A0.dts

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-HDMI-TDA998x-00A0.dts

When loaded via u-boot, video came up at work. (no hdmi-audio devices at work)

You must be working on the it66121 cape?

Please create two overlays..

BB-HDMI-IT66121-00A0.dts (video & audio)
BB-NHDMI-IT66121-00A0.dts (no audio)

that board had an eeprom on it right? (i have one at my desk at work)..

Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYj_Y3w2faL_zK%3DAbo7i4kA9RxiNn%2BrDw%3DgZW6fD4TVVKg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Green - Experience and Notes

[Chris M]

Restarting going to use universala for uart, pwm, and gpio (MRAA and 
ADAFruit_BBIO both work in python)

> VERSION
> # uname -a
> Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l 
> GNU/Linux
> UPDATE apt-get database 
> # apt-get update
> REMOUNT EXT SD CARD
> # mkdir /extsd
> # mount /dev/mmcblk0p1 /extsd
> # vi /etc/fstab
> /dev/mmcblk0p1  /extsd  ext4defaults0   0
> reboot and check
> INSTALL PACKAGES
>
 

# apt-get upgrade

installing v4l2capture

git clone https://github.com/philips/libv4l
make
make install
pip install  v4l2capture







On Sunday, November 13, 2016 at 4:09:06 PM UTC-6, Chris M wrote:
>
> Some thoughts and findings as I begin to learn the BBG (Beaglebone Green) 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ea431428-a10c-4831-b397-2f5d0990c31f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Are Windows Driver Signings Going to be Updated?

[Jared McIntyre]

The Window's drivers haven't been install-able without turning off sign 
checking for several months. I have a number of machines that I can't do 
that on due to IT policy. Is there going to be an updated installer with 
updated signings?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9ee18166-e1bc-4b51-9c61-c107d6f2a84e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Clock running slow when gpio0[11] pulled high

[chao.ruth via BeagleBoard]

On Thu, 1/5/17, Justin Pearson  wrote:

 Subject: Re: [beagleboard] Clock running slow when gpio0[11] pulled high
 To: beagleboard@googlegroups.com
 Date: Thursday, January 5, 2017, 1:19 AM
 
 Thanks
 Gerald! Did I reference the correct version (CircuitCo's
 GitHub)?
 -Justin
 On Wed, Jan 4, 2017 at 3:15
 PM, Gerald Coley 
 wrote:
 That brings tears to my eyes seeing someone
 quoting the manual.
 Yes,
 don't screw up the SYS_BOOT pins.
 
 Gerald
 
 On Wed, Jan 4, 2017 at 5:12 PM,
 Justin Pearson 
 wrote:
 Expanding
 Chad's comment, in the Beaglebone Black System Reference
 Manual (Rev B, Jan 20, 2014)
 https://github.com/CircuitCo/B
 eagleBone-Black/blob/390c46a03
 e039661aeca6eab22e6c383d8d537f
 8/BBB_SRM.pdf
 "Figure 39. Processor Boot
 Configuration" in "Section 6.8 Default Boot
 Options" says that the top two bits of the SYSBOOT
 register, SYSBOOT[15:14], seem to select which oscillator is
 used (19.2MHz, 24MHz, 25MHz, 26MHz). 
 "Figure 38. Processor Boot
 Configuration Design" shows that SYS_BOOT14 and 15 are
 physically lcd_data14 and 15.
 "Table 12. Expansion Header P8
 Pinout" shows that lcd_data14 and 15 are GPIO0[10] and
 GPIO0[11] in MODE0.
 Section "8.1.1 LCD Pins"
 contains the warning:
 "These pins are also the
 SYSBOOT pins. DO NOT drive them before the SYS_RESETN signal
 goes high. If you do, the board may not boot because you
 would be changing the boot order of the
 processor."
 In
 Fig 39, I see that SYSBOOT[15:14] == 01b results in 24 MHz,
 whereas 11b results in 26MHz, whose 8% difference may
 account for your ~5 sec offset per minute. (If 24MHz is the
 default, I'm not sure.)
 Best,Justin
 
 
 On Wednesday, January 4, 2017 at 5:12:24 AM
 UTC-8, cmbaker3 wrote:
   
 
   
   
 Johan,
 
   That pin is used during the boot operation.
 
   Check in the SRM for the default boot options.
 
   
 
   On 1/4/2017 5:39 AM, Johan Ribenfors wrote:
 
 
 
   We've recently found a
 strange problem.  Repeatable
 across all eleven boards we've tried so far.
 
 
 
 When pin 32 on P8 (gpoi0[11]) is pulled high
 via a resistor
   on boot, the clock on the BBB runs ~7000 seconds
 slow a day.
   (~5 seconds a minute)
 
 
 
 If the pin is pulled low or left floating on
 boot, the
   clock keeps time.
 
 
 
 The device tree overlay was set to 0x37 for
 this pin - fast
   slew, output, pullup, mode 7, but changing this
 has no effect.
 
 
 
 We were using Debian 7.9 with various programs
 installed, a
   few device tree overlays applied and a custom cape
 when we
   noticed this, but it's still the case using
 the Debian 8.6
   image with no modifications, no dto and no
 cape.
 
 
 
 We haven't been able to find anything
 online and don't
   really know where to start looking.
 
 
 
 Any ideas?
   
   -- 
 
   For more options, visit http://beagleboard.org/discuss
 
   --- 
 
   You received this message because you are subscribed
 to the Google
   Groups "BeagleBoard" group.
 
   To unsubscribe from this group and stop receiving
 emails from it,
   send an email to beagleboard...@googlegroups.co m.
 
   To view this discussion on the web visit https://groups.google.com/d/ms
 gid/beagleboard/e0647cb0-ac27-
 44ed-a11b-a6f71b7ef077%40googl egroups.com.
 
   For more options, visit https://groups.google.com/d/op
 tout.
 
 
 
 
 
 
 
 -- 
 
   Chad Baker
   Memphis, TN
   
 
 
 
 
 
 -- 
 
 For more options, visit http://beagleboard.org/discuss
 
 --- 
 
 You received this message because you are subscribed to the
 Google Groups "BeagleBoard" group.
 
 To unsubscribe from this group and stop receiving emails
 from it, send an email to beagleboard+unsubscribe@google
 groups.com.
 
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/beagleboard/79bac7d6-3011-
 44b5-95ac-61c43cb8525c%40googl egroups.com.
 
 For more options, visit https://groups.google.com/d/op
 tout.
 
 
 
 
 -- 
 Gerald
  
 ger...@beagleboard.org
 http://beagleboard.org/gcol...@emprodesign.com
 
 
 
 
 
 -- 
 
 For more options, visit http://beagleboard.org/discuss
 
 --- 
 
 You received this message because you are subscribed to a
 topic in the Google Groups "BeagleBoard" group.
 
 To unsubscribe from this topic, visit https://groups.google.com/d/
 topic/beagleboard/mFBxTSWl7Ro/ unsubscribe.
 
 To unsubscribe from this group and all its topics, send an
 email to beagleboard+unsubscribe@
 googlegroups.com.
 
 To view this discussion on the web visit https://groups.google.com/d/
 msgid/beagleboard/CAHK_S%2Bc0% 3DS__LXv5wbF_%
 2B9xP9chLWxErTbCvcxOyejQv8pASZ w%40mail.gmail.com.
 
 For more options, visit https://groups.google.com/d/
 optout.
 
 
 
 
 
 
 -- 
 
 For

Re: [beagleboard] Clock running slow when gpio0[11] pulled high

[Gerald Coley]

That is the correct document. It is there, at least for now.

Gerald

On Wed, Jan 4, 2017 at 5:19 PM, Justin Pearson 
wrote:

> Thanks Gerald! Did I reference the correct version (CircuitCo's GitHub)?
>
> -Justin
>
> On Wed, Jan 4, 2017 at 3:15 PM, Gerald Coley 
> wrote:
>
>> That brings tears to my eyes seeing someone quoting the manual.
>>
>> Yes, don't screw up the SYS_BOOT pins.
>>
>> Gerald
>>
>>
>> On Wed, Jan 4, 2017 at 5:12 PM, Justin Pearson 
>> wrote:
>>
>>> Expanding Chad's comment, in the Beaglebone Black System Reference
>>> Manual (Rev B, Jan 20, 2014)
>>>
>>> https://github.com/CircuitCo/BeagleBone-Black/blob/390c46a03
>>> e039661aeca6eab22e6c383d8d537f8/BBB_SRM.pdf
>>>
>>> "Figure 39. Processor Boot Configuration" in "Section 6.8 Default Boot
>>> Options" says that the top two bits of the SYSBOOT register,
>>> SYSBOOT[15:14], seem to select which oscillator is used (19.2MHz, 24MHz,
>>> 25MHz, 26MHz).
>>>
>>> "Figure 38. Processor Boot Configuration Design" shows that SYS_BOOT14
>>> and 15 are physically lcd_data14 and 15.
>>>
>>> "Table 12. Expansion Header P8 Pinout" shows that lcd_data14 and 15 are
>>> GPIO0[10] and GPIO0[11] in MODE0.
>>>
>>> Section "8.1.1 LCD Pins" contains the warning:
>>>
>>> "These pins are also the SYSBOOT pins. DO NOT drive them before the
>>> SYS_RESETN signal goes high. If you do, the board may not boot because you
>>> would be changing the boot order of the processor."
>>>
>>> In Fig 39, I see that SYSBOOT[15:14] == 01b results in 24 MHz, whereas
>>> 11b results in 26MHz, whose 8% difference may account for your ~5 sec
>>> offset per minute. (If 24MHz is the default, I'm not sure.)
>>>
>>> Best,
>>> Justin
>>>
>>>
>>>
>>> On Wednesday, January 4, 2017 at 5:12:24 AM UTC-8, cmbaker3 wrote:

 Johan,
 That pin is used during the boot operation.
 Check in the SRM for the default boot options.

 On 1/4/2017 5:39 AM, Johan Ribenfors wrote:

 We've recently found a strange problem.  Repeatable across all eleven
 boards we've tried so far.

 When pin 32 on P8 (gpoi0[11]) is pulled high via a resistor on boot,
 the clock on the BBB runs ~7000 seconds slow a day. (~5 seconds a minute)

 If the pin is pulled low or left floating on boot, the clock keeps time.

 The device tree overlay was set to 0x37 for this pin - fast slew,
 output, pullup, mode 7, but changing this has no effect.

 We were using Debian 7.9 with various programs installed, a few device
 tree overlays applied and a custom cape when we noticed this, but it's
 still the case using the Debian 8.6 image with no modifications, no dto and
 no cape.

 We haven't been able to find anything online and don't really know
 where to start looking.

 Any ideas?
 --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google
 Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to beagleboard...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/beagleboard/e0647cb0-ac27-44ed-a11b-a6f71b7ef077%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.



 --
 Chad Baker Memphis, TN

>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/beagleboard/79bac7d6-3011-44b5-95ac-61c43cb8525c%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Gerald
>>
>> ger...@beagleboard.org
>> http://beagleboard.org/
>> gcol...@emprodesign.com
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>> pic/beagleboard/mFBxTSWl7Ro/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/CAHK_S%2Bc0%3DS__LXv5wbF_%2B9xP9chLWxErTbCvc
>> xOyejQv8pASZw%40mail.gmail.com
>> 

Re: [beagleboard] Clock running slow when gpio0[11] pulled high

[Justin Pearson]

Thanks Gerald! Did I reference the correct version (CircuitCo's GitHub)?

-Justin

On Wed, Jan 4, 2017 at 3:15 PM, Gerald Coley  wrote:

> That brings tears to my eyes seeing someone quoting the manual.
>
> Yes, don't screw up the SYS_BOOT pins.
>
> Gerald
>
>
> On Wed, Jan 4, 2017 at 5:12 PM, Justin Pearson 
> wrote:
>
>> Expanding Chad's comment, in the Beaglebone Black System Reference Manual
>> (Rev B, Jan 20, 2014)
>>
>> https://github.com/CircuitCo/BeagleBone-Black/blob/390c46a03
>> e039661aeca6eab22e6c383d8d537f8/BBB_SRM.pdf
>>
>> "Figure 39. Processor Boot Configuration" in "Section 6.8 Default Boot
>> Options" says that the top two bits of the SYSBOOT register,
>> SYSBOOT[15:14], seem to select which oscillator is used (19.2MHz, 24MHz,
>> 25MHz, 26MHz).
>>
>> "Figure 38. Processor Boot Configuration Design" shows that SYS_BOOT14
>> and 15 are physically lcd_data14 and 15.
>>
>> "Table 12. Expansion Header P8 Pinout" shows that lcd_data14 and 15 are
>> GPIO0[10] and GPIO0[11] in MODE0.
>>
>> Section "8.1.1 LCD Pins" contains the warning:
>>
>> "These pins are also the SYSBOOT pins. DO NOT drive them before the
>> SYS_RESETN signal goes high. If you do, the board may not boot because you
>> would be changing the boot order of the processor."
>>
>> In Fig 39, I see that SYSBOOT[15:14] == 01b results in 24 MHz, whereas
>> 11b results in 26MHz, whose 8% difference may account for your ~5 sec
>> offset per minute. (If 24MHz is the default, I'm not sure.)
>>
>> Best,
>> Justin
>>
>>
>>
>> On Wednesday, January 4, 2017 at 5:12:24 AM UTC-8, cmbaker3 wrote:
>>>
>>> Johan,
>>> That pin is used during the boot operation.
>>> Check in the SRM for the default boot options.
>>>
>>> On 1/4/2017 5:39 AM, Johan Ribenfors wrote:
>>>
>>> We've recently found a strange problem.  Repeatable across all eleven
>>> boards we've tried so far.
>>>
>>> When pin 32 on P8 (gpoi0[11]) is pulled high via a resistor on boot, the
>>> clock on the BBB runs ~7000 seconds slow a day. (~5 seconds a minute)
>>>
>>> If the pin is pulled low or left floating on boot, the clock keeps time.
>>>
>>> The device tree overlay was set to 0x37 for this pin - fast slew,
>>> output, pullup, mode 7, but changing this has no effect.
>>>
>>> We were using Debian 7.9 with various programs installed, a few device
>>> tree overlays applied and a custom cape when we noticed this, but it's
>>> still the case using the Debian 8.6 image with no modifications, no dto and
>>> no cape.
>>>
>>> We haven't been able to find anything online and don't really know where
>>> to start looking.
>>>
>>> Any ideas?
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/beagleboard/e0647cb0-ac27-44ed-a11b-a6f71b7ef077%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>>
>>>
>>> --
>>> Chad Baker Memphis, TN
>>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/79bac7d6-3011-44b5-95ac-61c43cb8525c%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Gerald
>
> ger...@beagleboard.org
> http://beagleboard.org/
> gcol...@emprodesign.com
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/beagleboard/mFBxTSWl7Ro/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/CAHK_S%2Bc0%3DS__LXv5wbF_%2B9xP9chLWxErTbCvcxOyejQv8pASZ
> w%40mail.gmail.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 su

Re: [beagleboard] Clock running slow when gpio0[11] pulled high

[Gerald Coley]

That brings tears to my eyes seeing someone quoting the manual.

Yes, don't screw up the SYS_BOOT pins.

Gerald


On Wed, Jan 4, 2017 at 5:12 PM, Justin Pearson 
wrote:

> Expanding Chad's comment, in the Beaglebone Black System Reference Manual
> (Rev B, Jan 20, 2014)
>
> https://github.com/CircuitCo/BeagleBone-Black/blob/
> 390c46a03e039661aeca6eab22e6c383d8d537f8/BBB_SRM.pdf
>
> "Figure 39. Processor Boot Configuration" in "Section 6.8 Default Boot
> Options" says that the top two bits of the SYSBOOT register,
> SYSBOOT[15:14], seem to select which oscillator is used (19.2MHz, 24MHz,
> 25MHz, 26MHz).
>
> "Figure 38. Processor Boot Configuration Design" shows that SYS_BOOT14 and
> 15 are physically lcd_data14 and 15.
>
> "Table 12. Expansion Header P8 Pinout" shows that lcd_data14 and 15 are
> GPIO0[10] and GPIO0[11] in MODE0.
>
> Section "8.1.1 LCD Pins" contains the warning:
>
> "These pins are also the SYSBOOT pins. DO NOT drive them before the
> SYS_RESETN signal goes high. If you do, the board may not boot because you
> would be changing the boot order of the processor."
>
> In Fig 39, I see that SYSBOOT[15:14] == 01b results in 24 MHz, whereas 11b
> results in 26MHz, whose 8% difference may account for your ~5 sec offset
> per minute. (If 24MHz is the default, I'm not sure.)
>
> Best,
> Justin
>
>
>
> On Wednesday, January 4, 2017 at 5:12:24 AM UTC-8, cmbaker3 wrote:
>>
>> Johan,
>> That pin is used during the boot operation.
>> Check in the SRM for the default boot options.
>>
>> On 1/4/2017 5:39 AM, Johan Ribenfors wrote:
>>
>> We've recently found a strange problem.  Repeatable across all eleven
>> boards we've tried so far.
>>
>> When pin 32 on P8 (gpoi0[11]) is pulled high via a resistor on boot, the
>> clock on the BBB runs ~7000 seconds slow a day. (~5 seconds a minute)
>>
>> If the pin is pulled low or left floating on boot, the clock keeps time.
>>
>> The device tree overlay was set to 0x37 for this pin - fast slew, output,
>> pullup, mode 7, but changing this has no effect.
>>
>> We were using Debian 7.9 with various programs installed, a few device
>> tree overlays applied and a custom cape when we noticed this, but it's
>> still the case using the Debian 8.6 image with no modifications, no dto and
>> no cape.
>>
>> We haven't been able to find anything online and don't really know where
>> to start looking.
>>
>> Any ideas?
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/e0647cb0-ac27-44ed-a11b-a6f71b7ef077%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>>
>> --
>> Chad Baker Memphis, TN
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/79bac7d6-3011-44b5-95ac-61c43cb8525c%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
gcol...@emprodesign.com

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAHK_S%2Bc0%3DS__LXv5wbF_%2B9xP9chLWxErTbCvcxOyejQv8pASZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Clock running slow when gpio0[11] pulled high

[Justin Pearson]

Expanding Chad's comment, in the Beaglebone Black System Reference Manual 
(Rev B, Jan 20, 2014)

https://github.com/CircuitCo/BeagleBone-Black/blob/390c46a03e039661aeca6eab22e6c383d8d537f8/BBB_SRM.pdf

"Figure 39. Processor Boot Configuration" in "Section 6.8 Default Boot 
Options" says that the top two bits of the SYSBOOT register, 
SYSBOOT[15:14], seem to select which oscillator is used (19.2MHz, 24MHz, 
25MHz, 26MHz). 

"Figure 38. Processor Boot Configuration Design" shows that SYS_BOOT14 and 
15 are physically lcd_data14 and 15.

"Table 12. Expansion Header P8 Pinout" shows that lcd_data14 and 15 are 
GPIO0[10] and GPIO0[11] in MODE0.

Section "8.1.1 LCD Pins" contains the warning:

"These pins are also the SYSBOOT pins. DO NOT drive them before the 
SYS_RESETN signal goes high. If you do, the board may not boot because you 
would be changing the boot order of the processor."

In Fig 39, I see that SYSBOOT[15:14] == 01b results in 24 MHz, whereas 11b 
results in 26MHz, whose 8% difference may account for your ~5 sec offset 
per minute. (If 24MHz is the default, I'm not sure.)

Best,
Justin



On Wednesday, January 4, 2017 at 5:12:24 AM UTC-8, cmbaker3 wrote:
>
> Johan,
> That pin is used during the boot operation.
> Check in the SRM for the default boot options.
>
> On 1/4/2017 5:39 AM, Johan Ribenfors wrote:
>
> We've recently found a strange problem.  Repeatable across all eleven 
> boards we've tried so far. 
>
> When pin 32 on P8 (gpoi0[11]) is pulled high via a resistor on boot, the 
> clock on the BBB runs ~7000 seconds slow a day. (~5 seconds a minute)
>
> If the pin is pulled low or left floating on boot, the clock keeps time.
>
> The device tree overlay was set to 0x37 for this pin - fast slew, output, 
> pullup, mode 7, but changing this has no effect.
>
> We were using Debian 7.9 with various programs installed, a few device 
> tree overlays applied and a custom cape when we noticed this, but it's 
> still the case using the Debian 8.6 image with no modifications, no dto and 
> no cape.
>
> We haven't been able to find anything online and don't really know where 
> to start looking.
>
> Any ideas?
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/e0647cb0-ac27-44ed-a11b-a6f71b7ef077%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
> -- 
> Chad Baker Memphis, TN
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/79bac7d6-3011-44b5-95ac-61c43cb8525c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB IoT image with Pi-Hole: Success, but may have to remove connman and nodejs

[neutrinos4all]

I was redirected here from your Twitter account maintainer to post my 
experience installing pi-hole  on a BBB with a 
freshly-flashed IoT image (version information below). Hopefully this will 
help someone else in the future.


*What I'm using*
   
   - element14 BeagleBone Black rev. C, connected via ethernet to router
   - Asus NT-66R router
   - Debian 8.6 ("Jessie") IoT image, retrieved from here. 
   

*What happened*
After flashing the IoT image to onboard eMMC and installing pi-hole 
successfully, I had no DNS connectivity: could ping IPs, but not visit 
websites by URL from any machine on the LAN. What's more, dnsmasq was not 
running. I determined that connman was binding to port 53 rather than 
dnsmasq, thereby preventing dnsmasq from resolving DNS requests for pi-hole 
(confirm using command lsof +M -nPi :53 to see the services bound to that 
port). Uninstalling connman and restarting the network service allowed 
dnsmasq to run, fixing the DNS problem. Web browsing was immediately 
restored across the LAN.

Upon installation, the web interface was inaccessible via browser. Running 
the same lsof command, but now for port 80, indicated node.js was sitting 
on it. This is problematic because pi-hole uses lighttpd to serve the 
content of the web interface--which of course requires port 80. Node.js is 
installed with this IoT image to facilitate BoneScript, among other things, 
and because we're using this BBB for a different purpose we don't really 
need it. Uninstalling and purging nodejs will also uninstall bonescript, as 
well as some software needed for the Cloud9 IDE (again, not needed if using 
your BBB for this type of project). Restarting lighttpd immediately 
restored the web interface.

As a note, remember you can always reboot the BBB if restarting these 
sevices for some reason doesn't bring them back up.


*Additional information*If you would like to see a more detailed 
walkthrough, please see my blog post here 
 that discusses my 
method and some reasoning behind it. Feedback would be greatly appreciated, 
especially if I got anything wrong.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e8202923-e134-4f1d-b450-5edf2ea09f27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBGW - Boot 3.8 kernel ?

[Robert Nelson]

On Wed, Jan 4, 2017 at 3:02 PM, Robert Nelson  wrote:
> On Wed, Jan 4, 2017 at 2:59 PM, Oliv'  wrote:
>>
>>
>> Le mardi 3 janvier 2017 02:02:57 UTC+1, RobertCNelson a écrit :
>>>
>>> On Mon, Jan 2, 2017 at 3:53 PM, Oliv'  wrote:
>>> > Small update, I tried to use the script "./update_kernel.sh
>>> > --bone-channel
>>> > --stable".
>>> > It starts to boot but give an error I am not able to understand, if
>>> > somebody
>>> > can help : "Unhandled fault: external abort on non-linefetch (0x1008) at
>>> > 0xe0858000"
>>> >
>>> > Full error log: http://pastebin.com/RQU0Ku10
>>>
>>> Yeah, on 3.8.13 it would help if i actually disabled the cpsw node,
>>> instead of just copying the device tree as is..
>>>
>>> I'll boot test it tomorrow..
>>>
>> Ok thanks, I understand what happens now. Did you had time to test it ?
>> I wanted to do it by myself but I did not find the 3.8 branch of your
>> repository :/
>
> Sorry got side tracked doing u-boot overlays for v4.4.x/v4.9.x kernel's .;)

fixed: 
https://github.com/RobertCNelson/bb-kernel/commit/4e8e17ef1246f692fde6b9ed130c60a2a83a4b8b

will push out to the build farm in a bit..

Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiGJOojX7j%3DDVYd3szh3QFT%2BkAUwi_BY4LxRJ5zHJ1HbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBGW - Boot 3.8 kernel ?

[Robert Nelson]

On Wed, Jan 4, 2017 at 2:59 PM, Oliv'  wrote:
>
>
> Le mardi 3 janvier 2017 02:02:57 UTC+1, RobertCNelson a écrit :
>>
>> On Mon, Jan 2, 2017 at 3:53 PM, Oliv'  wrote:
>> > Small update, I tried to use the script "./update_kernel.sh
>> > --bone-channel
>> > --stable".
>> > It starts to boot but give an error I am not able to understand, if
>> > somebody
>> > can help : "Unhandled fault: external abort on non-linefetch (0x1008) at
>> > 0xe0858000"
>> >
>> > Full error log: http://pastebin.com/RQU0Ku10
>>
>> Yeah, on 3.8.13 it would help if i actually disabled the cpsw node,
>> instead of just copying the device tree as is..
>>
>> I'll boot test it tomorrow..
>>
> Ok thanks, I understand what happens now. Did you had time to test it ?
> I wanted to do it by myself but I did not find the 3.8 branch of your
> repository :/

Sorry got side tracked doing u-boot overlays for v4.4.x/v4.9.x kernel's .;)

Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjY3HRfxuQ4ToB4akSyySt4%2BmK0iPS-6-_0zg1BV2m4iA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBGW - Boot 3.8 kernel ?

[Oliv']

Le mardi 3 janvier 2017 02:02:57 UTC+1, RobertCNelson a écrit :
>
> On Mon, Jan 2, 2017 at 3:53 PM, Oliv' > 
> wrote: 
> > Small update, I tried to use the script "./update_kernel.sh 
> --bone-channel 
> > --stable". 
> > It starts to boot but give an error I am not able to understand, if 
> somebody 
> > can help : "Unhandled fault: external abort on non-linefetch (0x1008) at 
> > 0xe0858000" 
> > 
> > Full error log: http://pastebin.com/RQU0Ku10 
>
> Yeah, on 3.8.13 it would help if i actually disabled the cpsw node, 
> instead of just copying the device tree as is.. 
>
> I'll boot test it tomorrow.. 
>
> Ok thanks, I understand what happens now. Did you had time to test it ? 
I wanted to do it by myself but I did not find the 3.8 branch of your 
repository  :/ 

Thank you
Oliv'

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4de03f1a-c45b-482b-9ad0-17279a9a4b75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] debian testing: 2017-01-03 (U-Boot Cape Manager edition)

[Robert Nelson]

Howdy!

So here we go, an Image with U-Boot Cape Manager installed.

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2017-01-03

U-Boot version:

U-Boot SPL 2017.01-rc3-3-gd2796a1cca (Jan 03 2017 - 12:44:32)
Trying to boot from MMC1

U-Boot 2017.01-rc3-3-gd2796a1cca (Jan 03 2017 - 12:44:32 -0600),
Build: jenkins-github_Bootloader-Builder-498

U-Boot will read the i2c eeprom on each of the 4 possible capes:

BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
/lib/firmware/BB-CAPE-DISP-CT4-00A0.dtbo
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:

It's of course disabled by default, to enable it open /boot/uEnv.txt

###EXPERIMENTAL###
#enable_uboot_overlays=1
#dtb_overlay=/lib/firmware/BB-UART2-00A0.dtbo
###EXPERIMENTAL###

and un-comment enable_uboot_overlays=1

###EXPERIMENTAL###
enable_uboot_overlays=1
#dtb_overlay=/lib/firmware/BB-UART2-00A0.dtbo
###EXPERIMENTAL###

loading /boot/dtbs/4.4.39-ti-r79/am335x-boneblack-emmc-overlay.dtb ...
53192 bytes read in 110 ms (471.7 KiB/s)
debug: [uboot_overlay_addr1=/lib/firmware/BB-CAPE-DISP-CT4-00A0.dtbo] ...
loading /lib/firmware/BB-CAPE-DISP-CT4-00A0.dtbo ...
4518 bytes read in 265 ms (16.6 KiB/s)
loading /boot/initrd.img-4.4.39-ti-r79 ...
5163687 bytes read in 374 ms (13.2 MiB/s)
debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
net.ifnames=0 quiet cape_universal=enable] ...
debug: [bootz 0x8200 0x8808:4ecaa7 8800] ...
## Flattened Device Tree blob at 8800
   Booting using the fdt blob at 0x8800
   reserving fdt memory region: addr=8800 size=e000
   Loading Ramdisk to 8fb13000, end 8aa7 ... OK
   Loading Device Tree to 8fb02000, end 8fb12fff ... OK

Starting kernel ...

If you'd like to enable a 5th cape, or one without an i2c eeprom, use
the dtb_overlay variable, for example to load BB-UART2-00A0.dtb

dtb_overlay=/lib/firmware/BB-UART2-00A0.dtbo

ToDo:

Split out eMMC, hdmi-video, hdmi-audio, ethernet, wl18xx, add a pin
manager so we know what to load..

Fix the /uEnv.txt to have backwards compatbilty... (for right now, you
have to [sudo rm /uEnv.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhrNtKdR061OqmTcCoiWSJs%2BFxf1TrpnZkep2oBiQVCTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Flashing BBB over microUSB

[arochagus via BeagleBoard]

On Wed, 1/4/17, Robert Nelson  wrote:

 Subject: Re: [beagleboard] Flashing BBB over microUSB
 To: "Beagle Board" 
 Cc: panad...@gmail.com
 Date: Wednesday, January 4, 2017, 5:47 PM
 
 On Wed, Jan 4, 2017 at 9:44 AM,
 DragosP 
 wrote:
 > Can BBB eMMC memory be flashed over microUSB? Is there
 any documentation or
 > links to describe the steps for this process?
 
 https://github.com/ungureanuvladvictor/BBBlfs
 
 Regards,
 
 -- 
 Robert Nelson
 https://rcn-ee.com/
 
 -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to the
 Google Groups "BeagleBoard" group.
 To unsubscribe from this group and stop receiving emails
 from it, send an email to beagleboard+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgYSUTTuVcFoyQugDuCpcsif3KTgYqJrZj6L5iJrqAUiw%40mail.gmail.com.
 For more options, visit https://groups.google.com/d/optout.
 cum  frati romani  cu aceeasi intelepciune  cu acelasi patriotism care ati 
aratat ieri la 11 iunie  trebuie sa ne purtam si de acum inainte  nu e destul 
ca am dobandit libertatea  trebuie sa ne aratam si vrednici de dansa  trebuie 
sa stim a pastra cerescul dar. Ceea ce dar trebuie facut mai nainte este 
organizatia unei guardii nationale spre pastrarea linistii si bunei oranduieli. 
Tot romanul isi va varsa cu bucurie cea mai dupa urma picatura de sange pentru 
patria sa si nici o putere omeneasca nu ne va putea rapi cerescul dar ce am 
dobandit... 

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

Re: [beagleboard] Flashing BBB over microUSB

[Robert Nelson]

On Wed, Jan 4, 2017 at 9:44 AM, DragosP  wrote:
> Can BBB eMMC memory be flashed over microUSB? Is there any documentation or
> links to describe the steps for this process?

https://github.com/ungureanuvladvictor/BBBlfs

Regards,

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

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

[beagleboard] Flashing BBB over microUSB

[DragosP]

Can BBB eMMC memory be flashed over microUSB? Is there any documentation or 
links to describe the steps for this process?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/451cd556-856b-498e-ae2b-4534c6e80d68%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

[Robert Nelson]

On Wed, Jan 4, 2017 at 3:02 AM, Linq John  wrote:
>
> I got similar testing results as imjoh...@gmail.com
> Most image failed to boot.
>
> BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
> and
> bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
> booted successfully,
> but wlan0 did not work.
>
> I did a lot of manual work on
> BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
> after that, I could make wlan0 working, but I didn't know what I was doing,
> just guessing, trial and error.
> And even wlan0 is working, it is not stable.
>
> I have to work on some other projects.
> Hope SEEED would provide a real fix.

The "seeed" variants add a WiFi captive portal along with their
documentation on the usb flash drive that pop's up.  Otherwise they
are exactly the same as the non-seeed images.

That WiFi captive portal can make things interesting if you try to
manually control the wlan0..

Give the generic iot image a try:

https://rcn-ee.net/rootfs/bb.org/testing/2017-01-03/iot/

To see if i've fixed some of the issues..

Remember to use connman to control wlan0

sudo connmanctl
#connmanctl> scan wifi
#connmanctl> services
#connmanctl> agent on
#connmanctl> connect wifi_*_managed_psk
#connmanctl> quit


Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgPUe3CT%3DcNDx-AMhiKe1DEZeqyfsq-qx6RcMNKyc5mdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

[Robert Nelson]

J,

On Mon, Jan 2, 2017 at 7:33 PM,   wrote:
> Robert,
> I tried that build and also the last one from yesterday (1/1) but I cannot
> make the wlan0 work on any of those builds.
> When I do a ifconfig I get this:
>
> root@beaglebone:~# ifconfig wlan0 up
> SIOCSIFFLAGS: No such file or directory
>
> And this is the dmesg:
>
> [   29.792544] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl1271-nvs.bin failed with error -2
> [   30.147603] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> [   30.243578] wlcore: loaded
> [  188.343428] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.343465] wlcore: ERROR could not get firmware
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  188.711351] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.711388] wlcore: ERROR could not get firmware
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.075369] wl18xx_driver wl18xx.2.auto: Direct firmware load for
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  189.075406] wlcore: ERROR could not get firmware
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.086887] wlcore: ERROR firmware boot failed despite 3 retries
>
>
> What do you think could be the problem here? Is this a problem with the
> ti-connectivity version?

What image was this?  It's missing the firmware.. Grab the iot from last night:

https://rcn-ee.net/rootfs/bb.org/testing/2017-01-03/iot/

Regards,

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

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

Re: [beagleboard] Problems installing latest JAVA

[Robert Nelson]

On Wed, Jan 4, 2017 at 9:01 AM, Robert Nelson  wrote:
> On Wed, Jan 4, 2017 at 8:55 AM, Patrick Ireland
>  wrote:
>> I am trying to install the latest Java on Debian.
>> I downloaded "jdk-8u111-linux-arm64-vfp-hflt.tar" from Oracle.
>
> "arm64"...
>
>> I uploaded using FileAilla to BBB to root.
>> I tried both auto and binary for Filezilla.
>> I have used Filezilla many times in the past with no problem so it is not my
>> candidate for the problem.
>> BTW, I think FileZilla is an excellent program for transfering files either
>> direction with the BBB and Windows 10.
>>
>> This is the issue I get when I try and tar the file:
>>
>> root@beaglebone:~# tar xzf jdk-8u111-linux-arm64-vfp-hflt.tar
>>
>> gzip: stdin: unexpected end of file
>> tar: Unexpected EOF in archive
>> tar: Unexpected EOF in archive
>> tar: Error is not recoverable: exiting now
>>
>> I am suspicious that the file may not be valid.
>> Did I down load the wrong file for the Debian BBB?
>> Was the download from Oracle corrupt (tried several times)?
>> Was the upload with FileZilla corrupting (I copied back down from BBB to
>> Window 10 and did a successful file match)?
>> I can only conclude that there is a problem with what file I got from
>> Oracle.
>> Any insight in my error of my procedure will be appreciated.
>
> you can use the "oracle-java8-installer" package in apt, it's
> "8u77+8u77arm" right now, just give me a moment to update it..

Okay:

oracle-java8-installer is now updated to 8u111+8u111arm
oracle-java9-installer is now updated to 9b149+9b149arm

Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiyirSM3vvoYBZS6%3Dqyuho3ecC6DQy0pQMcTDZmg%2BurTQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Problems installing latest JAVA

[Theodore A. Roth]

Try "tar xf jdk-8u111-linux-arm64-vfp-hflt.tar"

Since the file name doesn't end with ".tar.gz", I assume it is an
uncompressed tar file, the '-z' option is your problem.

I'd also run "file jdk-8u111-linux-arm64-vfp-hflt.tar". For example, on my
system:

$ file compat-wireless-2015-03-09.tar*
compat-wireless-2015-03-09.tar: POSIX tar archive (GNU)
compat-wireless-2015-03-09.tar.bz2: bzip2 compressed data, block size = 900k

But, Robert Nelson's reply is probably more relevant about arm64...

Ted Roth

On Wed, Jan 4, 2017 at 7:55 AM, Patrick Ireland 
wrote:

> I am trying to install the latest Java on Debian.
> I downloaded "jdk-8u111-linux-arm64-vfp-hflt.tar" from Oracle.
> I uploaded using FileAilla to BBB to root.
> I tried both auto and binary for Filezilla.
> I have used Filezilla many times in the past with no problem so it is not
> my candidate for the problem.
> BTW, I think FileZilla is an excellent program for transfering files
> either direction with the BBB and Windows 10.
>
> This is the issue I get when I try and tar the file:
>
> root@beaglebone:~# tar xzf jdk-8u111-linux-arm64-vfp-hflt.tar
>
> gzip: stdin: unexpected end of file
> tar: Unexpected EOF in archive
> tar: Unexpected EOF in archive
> tar: Error is not recoverable: exiting now
>
> I am suspicious that the file may not be valid.
> Did I down load the wrong file for the Debian BBB?
> Was the download from Oracle corrupt (tried several times)?
> Was the upload with FileZilla corrupting (I copied back down from BBB to
> Window 10 and did a successful file match)?
> I can only conclude that there is a problem with what file I got from
> Oracle.
> Any insight in my error of my procedure will be appreciated.
>
> Thanks,
>
> Pat
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/305d3d63-28fa-4c78-a717-43bb227dd26a%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAMyzTKGs15R4qud%2BjXA-WLrb_6%2BesS%2B8YRFSvjrO3DHJgoBuhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Problems installing latest JAVA

[Robert Nelson]

On Wed, Jan 4, 2017 at 8:55 AM, Patrick Ireland
 wrote:
> I am trying to install the latest Java on Debian.
> I downloaded "jdk-8u111-linux-arm64-vfp-hflt.tar" from Oracle.

"arm64"...

> I uploaded using FileAilla to BBB to root.
> I tried both auto and binary for Filezilla.
> I have used Filezilla many times in the past with no problem so it is not my
> candidate for the problem.
> BTW, I think FileZilla is an excellent program for transfering files either
> direction with the BBB and Windows 10.
>
> This is the issue I get when I try and tar the file:
>
> root@beaglebone:~# tar xzf jdk-8u111-linux-arm64-vfp-hflt.tar
>
> gzip: stdin: unexpected end of file
> tar: Unexpected EOF in archive
> tar: Unexpected EOF in archive
> tar: Error is not recoverable: exiting now
>
> I am suspicious that the file may not be valid.
> Did I down load the wrong file for the Debian BBB?
> Was the download from Oracle corrupt (tried several times)?
> Was the upload with FileZilla corrupting (I copied back down from BBB to
> Window 10 and did a successful file match)?
> I can only conclude that there is a problem with what file I got from
> Oracle.
> Any insight in my error of my procedure will be appreciated.

you can use the "oracle-java8-installer" package in apt, it's
"8u77+8u77arm" right now, just give me a moment to update it..

Regards,

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgkvhOF-8g%2BtOXdVvZsq7ZcaYep8WRdTPE%3DS2%3Dp97m8kw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Problems installing latest JAVA

[Patrick Ireland]

I am trying to install the latest Java on Debian.
I downloaded "jdk-8u111-linux-arm64-vfp-hflt.tar" from Oracle.
I uploaded using FileAilla to BBB to root.
I tried both auto and binary for Filezilla.
I have used Filezilla many times in the past with no problem so it is not 
my candidate for the problem.
BTW, I think FileZilla is an excellent program for transfering files either 
direction with the BBB and Windows 10.

This is the issue I get when I try and tar the file:

root@beaglebone:~# tar xzf jdk-8u111-linux-arm64-vfp-hflt.tar

gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now

I am suspicious that the file may not be valid.
Did I down load the wrong file for the Debian BBB?
Was the download from Oracle corrupt (tried several times)?
Was the upload with FileZilla corrupting (I copied back down from BBB to 
Window 10 and did a successful file match)?
I can only conclude that there is a problem with what file I got from 
Oracle.
Any insight in my error of my procedure will be appreciated.

Thanks,

Pat

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/305d3d63-28fa-4c78-a717-43bb227dd26a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Clock running slow when gpio0[11] pulled high

[Chad Baker]

Johan,
That pin is used during the boot operation.
Check in the SRM for the default boot options.

On 1/4/2017 5:39 AM, Johan Ribenfors wrote:
We've recently found a strange problem.  Repeatable across all eleven 
boards we've tried so far.


When pin 32 on P8 (gpoi0[11]) is pulled high via a resistor on boot, 
the clock on the BBB runs ~7000 seconds slow a day. (~5 seconds a minute)


If the pin is pulled low or left floating on boot, the clock keeps time.

The device tree overlay was set to 0x37 for this pin - fast slew, 
output, pullup, mode 7, but changing this has no effect.


We were using Debian 7.9 with various programs installed, a few device 
tree overlays applied and a custom cape when we noticed this, but it's 
still the case using the Debian 8.6 image with no modifications, no 
dto and no cape.


We haven't been able to find anything online and don't really know 
where to start looking.


Any ideas?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google 
Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to beagleboard+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e0647cb0-ac27-44ed-a11b-a6f71b7ef077%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.



--
Chad Baker Memphis, TN

--
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d761ed22-b64e-712d-ade7-7575e1b0ffbb%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to change default hwclock on BBB Debian to always be /dev/rtc1?

[Micka]

The problem have been discussed there :

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785445


Le lun. 10 oct. 2016 à 03:54, William Hermans  a écrit :

> The best way I found for myself. Was to simply install ntpdate, run it,
> then update the external real clock from system time. Then, if you
> *absolutely* need rtc0 updated. You update it from the system time. Or
> rtc1. No need to recompile the kernel.
>
> Sure, it's a couple of extra steps, but steps that can be done at boot
> with a simple script / service. Then if you need, or want to update the
> real time clock. Since time on computer can drift. You run a cron job every
> X time frame to run a script that pulls in system time from an atomic
> clock, then re-apply to rtc1.
>
> On Sun, Oct 9, 2016 at 3:21 PM, maxmike  wrote:
>
>
> I don~t think Robert recompiled the kernel. I am using 3.8.13 Debian.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/4e6fdc99-4137-4c04-8c1d-72fa9de5a6a4%40googlegroups.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CALHSORqDsbBWiO%2BJOUPuaeAsG1O%2B4dxiP6G3PqUkOxE1GeVhgA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAF%2BMRt%3Dgm_wZzgJjZYvF2PVdXwWZzj8bVgEWK-LBWYJOwDqeig%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Clock running slow when gpio0[11] pulled high

[Johan Ribenfors]

I should clarify that this is the system clock, not the hardware clock.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/98cc6706-b7e3-49be-8fdb-bf7f156ac407%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Clock running slow when gpio0[11] pulled high

[Johan Ribenfors]

We've recently found a strange problem.  Repeatable across all eleven 
boards we've tried so far.

When pin 32 on P8 (gpoi0[11]) is pulled high via a resistor on boot, the 
clock on the BBB runs ~7000 seconds slow a day. (~5 seconds a minute)

If the pin is pulled low or left floating on boot, the clock keeps time.

The device tree overlay was set to 0x37 for this pin - fast slew, output, 
pullup, mode 7, but changing this has no effect.

We were using Debian 7.9 with various programs installed, a few device tree 
overlays applied and a custom cape when we noticed this, but it's still the 
case using the Debian 8.6 image with no modifications, no dto and no cape.

We haven't been able to find anything online and don't really know where to 
start looking.

Any ideas?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e0647cb0-ac27-44ed-a11b-a6f71b7ef077%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Why BeagleBone Is not able to take camera Input using Open CV for python ?

[Akshath Varugeese]

 

Enter code here...

I am doing Live Video streaming using the camera Logitech C310 on BeaglBone 
Black. For checking whether it is working, I wrote a basic code for getting 
the frame and printing the frame in its array form but I always get an 
empty array. I tried the same code on my laptop with the same camera, In 
which I get some value. I don't why I am getting like this in Beaglebone 
black, Here is the code as well as the sample output. I have installed 
opencv 2.4.9.1 in beaglebone but opencv 3.0.0 in my laptop. 


*Code*


import numpy as np
import cv2

cap = cv2.VideoCapture(0)

while True:
  ret, frame = cap.read()
  print ret
  print frame

cap.release()


*Output from BeagleBone Black*

..., 
[[0 0 0]
[0 0 0]
[0 0 0]
..., 
[0 0 0]
[0 0 0]
[0 0 0]]

[[0 0 0]
[0 0 0]
[0 0 0]
..., 
[0 0 0]
[0 0 0]
[0 0 0]]

[[0 0 0]
[0 0 0]
[0 0 0]
..., 
[0 0 0]
[0 0 0]
[0 0 0]]]


*Output from my Laptop*


 [133 104  84]
 ..., 
 [138 148 148]
 [135 152 153]
 [138 155 156]]

 [[138 102  83]
 [139 103  84]
 [134 102  83]
 ..., 
 [127 143 146]
 [136 152 155]
 [141 157 160]]]
 [[[ 14  19  15]
 [ 13  18  14]
 [ 13  18  14]
 ..., 
 [ 79  79  80]
 [ 80  80  81]
 [ 79  79  80]]



-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/bd2ebc41-85be-448d-9ed4-a9fcffb65f33%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

[Linq John]

I got similar testing results as imjoh...@gmail.com
Most image failed to boot.

BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
and
bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
booted successfully,
but wlan0 did not work.

I did a lot of manual work on 
BBGW-blank-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz
after that, I could make wlan0 working, but I didn't know what I was doing, 
just guessing*,* trial and error.
And even wlan0 is working, it is not stable.

I have to work on some other projects.
Hope SEEED would provide a real fix.


imjoh...@gmail.com於 2017年1月3日星期二 UTC+8上午10時04分45秒寫道：
>
> Robert,
> I tried that build and also the last one from yesterday (1/1) but I cannot 
> make the wlan0 work on any of those builds.
> When I do a ifconfig I get this:
>
> root@beaglebone:~# ifconfig wlan0 up
> SIOCSIFFLAGS: No such file or directory
>
> And this is the dmesg:
>
> [   29.792544] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl1271-nvs.bin failed with error -2
> [   30.147603] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
> [   30.243578] wlcore: loaded
> [  188.343428] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.343465] wlcore: ERROR could not get firmware 
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  188.711351] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  188.711388] wlcore: ERROR could not get firmware 
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.075369] wl18xx_driver wl18xx.2.auto: Direct firmware load for 
> ti-connectivity/wl18xx-fw-4.bin failed with error -2
> [  189.075406] wlcore: ERROR could not get firmware 
> ti-connectivity/wl18xx-fw-4.bin: -2
> [  189.086887] wlcore: ERROR firmware boot failed despite 3 retries
>
>
> What do you think could be the problem here? Is this a problem with the 
> ti-connectivity version?
> Thanks for your help and time!
> Regards,
> J
>
> On Friday, December 30, 2016 at 6:44:55 AM UTC-8, RobertCNelson wrote:
>>
>> On Fri, Dec 30, 2016 at 2:37 AM, Linq John  wrote: 
>> > 
>> > I brought a Beaglebone Green Wireless. 
>> > At the first day, its wifi worked, so I did some apt-get 
>> > update/upgrade/dis-upgrade. 
>> > My main purpose is to use it to do some python work. UART/I2C/GPIO etc. 
>> > So I didn't discover that the wifi no longer working after the apt-get 
>> > upgrade. 
>> > I spent two working days trying to make its wifi working again, but no 
>> > success. 
>> > I didn't record the version info of the original working Debian. 
>> > And I can't find the pre-load image from 
>> > https://debian.beagleboard.org/images/ 
>> > What I can find are: 
>> > bone-debian-8.5-seeed-gcp-iot-armhf-2016-08-26-4gb.img.xz - failed to 
>> boot 
>> > bone-debian-8.6-iot-armhf-2016-12-09-4gb.img.xz - failed to boot 
>> > bone-debian-8.6-seeed-iot-armhf-2016-11-06-4gb.img.xz - wifi doesn't 
>> work 
>> > I also tried to use the kernel in *-iot-armhf-2016-12-09-* with 
>> > *seeed-iot-armhf-2016-11-06*, but no success. 
>> > (By changing uname_r of uEnv.txt, and even by renaming the files.) 
>> > After all these I found a thread in TI E2E: 
>> > 
>> https://e2e.ti.com/support/wireless_connectivity/wilink_wifi_bluetooth/f/307/p/541235/1978301
>>  
>> > So I guess it's a hardware problem, but without wifi, there is no 
>> internet 
>> > connection on BBGW, 
>> > then I am not able to install python packages, my BBGW becomes useless. 
>> > 
>> > And I guess the below images are not for BBGW. 
>> > https://rcn-ee.net/rootfs/2016-11-10/microsd/ 
>> > 
>> > Is there any work-around available for a general user? 
>>
>> Use this build: 
>>
>> https://rcn-ee.net/rootfs/bb.org/testing/2016-12-27/ 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/5affe43c-e6a6-4437-b12f-de8ea8ceeb7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.