Re: [beagleboard] Beagle bone serial console

[SriRam Chadalavada]

On Friday, April 1, 2016 at 4:41:15 PM UTC-5, RobertCNelson wrote:
>
> On Fri, Apr 1, 2016 at 4:33 PM, SriRam Chadalavada  > wrote: 
> > This may be a naive question but how might I be able to obtain access to 
> BBB 
> > J1 connector from a Cape board stacked on it? In other words, how and 
> where 
> > should I attach the 3.3V TTL serial console cable that I used with BBB 
> J1 
> > connector when a cape is stacked? 
> > 
> > According to: 
> > 
> http://www.toptechboy.com/wp-content/uploads/2015/06/beaglebone-black-pinout.jpg,
>  
>
> > serial console UART0 from J1 connector is NOT exposed over the 40 pins. 
> Is 
> > that correct? If so, what is the alternative to connect to serial 
> console 
> > prompt? 
>
> Option 1: 
>
> Plug in a usb mini cable to the port under the led's.. 
>
> "/dev/ttyACM0" should show up on your linux desktop; 
>
> gtkterm -s 115200 -p /dev/ttyACM0 
>
> Option 2: 
>
> Or these also work nice: 
>
> http://elinux.org/CircuitCo:Right_Angle_Serial_Adapter 
>
> If you order from boardzoo, don't forget to ping them via email, 
> sometimes they can be a little slow.. ;) 
>
> Regards, 
>

 Thanks! I'll order the part right away.

Cheers,
Sriram 

-- 
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] SGX not installing

[James S]

Still not working, even tried rebooting.

debian@beaglebone:/opt/gfxinstall$ sudo /etc/init.d/sgx-startup.sh start
sgx: Starting PVR
debian@beaglebone:/opt/gfxinstall$ lsmod | grep omaplfb
debian@beaglebone:/opt/gfxinstall$ lsmod | grep omaplfb
debian@beaglebone:/opt/gfxinstall$ sudo reboot

Last login: Fri Apr  1 22:15:11 2016 from base2.lan
debian@beaglebone:~$ lsmod | grep omaplfb
debian@beaglebone:~$



On Friday, April 1, 2016 at 11:34:13 PM UTC+1, RobertCNelson wrote:
>
> On Fri, Apr 1, 2016 at 5:17 PM, James S  
> wrote: 
> > Oops! I did a reboot and lsmod | grep omaplfb but nothing shows up. 
>
> sudo /etc/init.d/sgx-startup.sh start 
>
> 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] SGX not installing

[Robert Nelson]

On Fri, Apr 1, 2016 at 5:17 PM, James S  wrote:
> Oops! I did a reboot and lsmod | grep omaplfb but nothing shows up.

sudo /etc/init.d/sgx-startup.sh start

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] SGX not installing

[James S]

Oops! I did a reboot and lsmod | grep omaplfb but nothing shows up.

On Friday, April 1, 2016 at 11:12:13 PM UTC+1, James S wrote:
>
> Purrfect Robert, thank you for the prompt response!
>
> On Friday, April 1, 2016 at 11:07:07 PM UTC+1, RobertCNelson wrote:
>>
>> On Fri, Apr 1, 2016 at 5:03 PM, James S  wrote: 
>> > I followed the instructions here 
>> > http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black 
>>  and 
>> > the install fails at the BBB with: 
>> > debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh 
>> > ./sgx-install.sh: 29: ./sgx-install.sh: lsb_release: not found 
>> > 
>> > The build on Ubuntu completes without reporting a fault and produces 
>> > GFX_5.01.01.02_es8.x.tar.gz. 
>> > 
>> > 
>> > What am I doing wrong? 
>> > James. 
>> > 
>> > debian@beaglebone:/opt/gfxinstall$ uname -r 
>> > 4.1.20-bone20 
>> > 
>> > debian@beaglebone:/opt/gfxinstall$ cat /etc/dogtag 
>> > BeagleBoard.org Debian Image 2016-03-27 
>>
>>
>> sudo apt-get update ; sudo apt-get install lsb-release 
>>
>> then rerun: 
>>
>> debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh 
>>
>> 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] SGX not installing

[James S]

Purrfect Robert, thank you for the prompt response!

On Friday, April 1, 2016 at 11:07:07 PM UTC+1, RobertCNelson wrote:
>
> On Fri, Apr 1, 2016 at 5:03 PM, James S  
> wrote: 
> > I followed the instructions here 
> > http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black 
>  and 
> > the install fails at the BBB with: 
> > debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh 
> > ./sgx-install.sh: 29: ./sgx-install.sh: lsb_release: not found 
> > 
> > The build on Ubuntu completes without reporting a fault and produces 
> > GFX_5.01.01.02_es8.x.tar.gz. 
> > 
> > 
> > What am I doing wrong? 
> > James. 
> > 
> > debian@beaglebone:/opt/gfxinstall$ uname -r 
> > 4.1.20-bone20 
> > 
> > debian@beaglebone:/opt/gfxinstall$ cat /etc/dogtag 
> > BeagleBoard.org Debian Image 2016-03-27 
>
>
> sudo apt-get update ; sudo apt-get install lsb-release 
>
> then rerun: 
>
> debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh 
>
> 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] SGX not installing

[Robert Nelson]

On Fri, Apr 1, 2016 at 5:03 PM, James S  wrote:
> I followed the instructions here
> http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black  and
> the install fails at the BBB with:
> debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh
> ./sgx-install.sh: 29: ./sgx-install.sh: lsb_release: not found
>
> The build on Ubuntu completes without reporting a fault and produces
> GFX_5.01.01.02_es8.x.tar.gz.
>
>
> What am I doing wrong?
> James.
>
> debian@beaglebone:/opt/gfxinstall$ uname -r
> 4.1.20-bone20
>
> debian@beaglebone:/opt/gfxinstall$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2016-03-27


sudo apt-get update ; sudo apt-get install lsb-release

then rerun:

debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh

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] SGX not installing

[James S]

I followed the instructions here  
http://elinux.org/BeagleBoardDebian#SGX_BeagleBone.2FBeagleBone_Black  and 
the install fails at the BBB with:
debian@beaglebone:/opt/gfxinstall$ sudo ./sgx-install.sh
*./sgx-install.sh: 29: ./sgx-install.sh: lsb_release: not found*

The build on Ubuntu completes without reporting a fault and 
produces GFX_5.01.01.02_es8.x.tar.gz.


What am I doing wrong?
James.

debian@beaglebone:/opt/gfxinstall$ uname -r
4.1.20-bone20

debian@beaglebone:/opt/gfxinstall$ cat /etc/dogtag
BeagleBoard.org Debian Image 2016-03-27



-- 
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] Beagle bone serial console

[Josh Datko]

On Fri, 2016-04-01 at 14:33 -0700, SriRam Chadalavada wrote:
> This may be a naive question but how might I be able to obtain access
> to BBB J1 connector from a Cape board stacked on it? In other words,
> how and where should I attach the 3.3V TTL serial console cable that
> I used with BBB J1 connector when a cape is stacked?

When I've had to do this I use clips and clip to RX and GND under the
cape. I haven't had to this in a while though as I can usually just ssh
into the cape over ethernet.

Josh

-- 
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] Beagle bone serial console

[Robert Nelson]

On Fri, Apr 1, 2016 at 4:33 PM, SriRam Chadalavada  wrote:
> This may be a naive question but how might I be able to obtain access to BBB
> J1 connector from a Cape board stacked on it? In other words, how and where
> should I attach the 3.3V TTL serial console cable that I used with BBB J1
> connector when a cape is stacked?
>
> According to:
> http://www.toptechboy.com/wp-content/uploads/2015/06/beaglebone-black-pinout.jpg,
> serial console UART0 from J1 connector is NOT exposed over the 40 pins. Is
> that correct? If so, what is the alternative to connect to serial console
> prompt?

Option 1:

Plug in a usb mini cable to the port under the led's..

"/dev/ttyACM0" should show up on your linux desktop;

gtkterm -s 115200 -p /dev/ttyACM0

Option 2:

Or these also work nice:

http://elinux.org/CircuitCo:Right_Angle_Serial_Adapter

If you order from boardzoo, don't forget to ping them via email,
sometimes they can be a little slow.. ;)

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] Beagle bone serial console

[SriRam Chadalavada]

This may be a naive question but how might I be able to obtain access to 
BBB J1 connector from a Cape board stacked on it? In other words, how and 
where should I attach the 3.3V TTL serial console cable that I used with 
BBB J1 connector when a cape is stacked?

According to:
http://www.toptechboy.com/wp-content/uploads/2015/06/beaglebone-black-pinout.jpg,
 
serial console UART0 from J1 connector is NOT exposed over the 40 pins. Is 
that correct? If so, what is the alternative to connect to serial console 
prompt?

Thanks!

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

[beagleboard] Re: build_mainline.sh: cape manager patch not applied?

[Robert Nelson]

On Fri, Apr 1, 2016 at 3:51 PM, Drew Fustini  wrote:
> Robert  - am I missing a step?
>
> I just ran build_mainline.sh on a fresh clone of
> https://github.com/RobertCNelson/linux-dev and noticed that the cape
> manager patch does not seem to get applied.
>
> The build_mainline.sh I'm using is from commit 7865e5d on March 16.

build_mainline.sh doesn't call patch.sh, it just builds the default
multi_v7_defconfig...

For me, it was useful in the 3.10.x erra when the multi platforms
first started being integrated, for test comparisons. I haven't really
ran it since that time.

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] Re: WLAN0 and ETH0

['Barry Day' via BeagleBoard]

Missing an i on iface

#iface wlan0 inet dhcp

> face wlan0 inet static
> wpa-ssid SSID NAME
> wpa-psk SSID PASSKEY
> address 192.168.0.21
> netmask 255.255.255.0
> gateway 192.168.0.1
> dns-nameservers 8.8.8.8
>
>
>

-- 
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] build_mainline.sh: cape manager patch not applied?

[Drew Fustini]

Robert  - am I missing a step?

I just ran build_mainline.sh on a fresh clone of
https://github.com/RobertCNelson/linux-dev and noticed that the cape
manager patch does not seem to get applied.

The build_mainline.sh I'm using is from commit 7865e5d on March 16.

It also seems to lack many modules I would have expected in the
default config for beaglebone like fbtft & iio sensors:
[linux-dev]$ find |grep ko$ |grep cape
[linux-dev]$ find |grep ko$ |grep fbtft
[linux-dev]$ find |grep ko$ |grep iio
./KERNEL/drivers/iio/adc/at91_adc.ko
./KERNEL/drivers/iio/adc/berlin2-adc.ko
./KERNEL/drivers/iio/adc/exynos_adc.ko
./KERNEL/drivers/iio/adc/vf610_adc.ko

 thanks!
drew

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

Re: [beagleboard] Re: versions puzzle with mifare card reader

[toni]

On 01-04-16 18:51, Josh Datko wrote:

The card emulation example worked which was cool. I have a low
expectation of nfc things working on linux though :)


For simple read/write via java pcsc-lite works like a charm for mifare 
cards.  It only takes a lot of time to figure out those silly protocols.



Yeah, google groups :( If you subscribe you can pretty much respond to
mail the old fashion way in a old-school mail client though and not
bother with any of the google stuff.


That is a good idea! thx!

I now have tested/concluded that all jessie version are broken w.r.t. 
acr122u. Somehow the driver (libacsccid1) isn't used..




--
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: versions puzzle with mifare card reader

[Josh Datko]

On Fri, 2016-04-01 at 07:32 -0700, toni incog wrote:
> pcsc-lite is a userspace solution, the blacklist is to prevent kernel
> modules interfering. It's libnfc that's using the kernel drivers?
> Anyway, thanks but I can fall back to wheezy. Just curious where it
> goes bananas. Now trying latest 'offical' jessie release.

Ah ok. I've been playing around with the Adafruit PN532 breakout shield
and their FDTI cable (not on a BBB, but soon I'll migrate to that) with
libnfc.

The card emulation example worked which was cool. I have a low
expectation of nfc things working on linux though :)

My use case is pretty simple, read a NDEF text message from a forum 2
tag and write a NDEF text message to a forum 2 tag.

This info may not be interesting/helpful to you but I've encountered
few NFC hackers out there so I'd figured I'd share.

> 
> google asking me to post again? I really don't get this webbased
> eventually inconsistent crap. And why 2 post buttons.. Well here we
> go (again)

Yeah, google groups :( If you subscribe you can pretty much respond to
mail the old fashion way in a old-school mail client though and not
bother with any of the google stuff.


-- 
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: osx 10.11.3 connectivity problem - HoRNDIS?

[Fred Patrick]

Got new HoRNDIS driver from joshua wise and it all seems to be working
https://nyus.joshuawise.com/HoRNDIS-rel8pr1.pkg and it seems to be working 
now.

On Tuesday, February 23, 2016 at 3:30:37 PM UTC-6, Fred Patrick wrote:
>
> I have been using OSX 10.11.3 for several months. I had a problem with my 
> BeagleBone Black and had to replace it. When I went to boot using USB 
> connection, it seemed to work several times. Then it stopped connecting and 
> the Mac no longer sees 192.168.7.2. I found website of Joshua Wise in which 
> he describes problems with HoRNDIS driver (apparently he maintains it) with 
> El Capitan.
>
> Has anyone else had problems with El Capitan?
>
>

-- 
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: node-red-node-beaglebone install broke node-red on 2016-03-27 image

[Wally Bkg]

Some extra follow-up possibly related to the issue above.

Doing apt-get update, apt-get upgrade on 2015-11-12 the 
bb-node-red-installer upgrade failed
...
Setting up libjasper1:armhf (1.900.1-debian1-2.4+deb8u1) ...
Setting up bb-node-red-installer (0.13.4-0rcnee1~bpo80+20160321+1) ...
bb-node-red-installer:npm: [1.4.21]
bb-node-red-installer:node: [v0.10.42]
bb-node-red-installer:Installing: systemd-0.2.6 (for node-red)
systemd@0.2.6 /usr/local/lib/node_modules/systemd
bb-node-red-installer:Installing: node-red-0.13.4 (for node-red)
 
> bcrypt@0.8.5 install 
/usr/local/lib/node_modules/node-red/node_modules/bcrypt
> node-gyp rebuild

make: Entering directory 
'/usr/local/lib/node_modules/node-red/node_modules/bcrypt/build'
make: Warning: File 'bcrypt_lib.target.mk' has modification time 2.4 s in 
the future
  CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
  CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
Killed
dpkg: error processing package bb-node-red-installer (--configure):
 subprocess installed post-installation script returned error exit status 
137
Setting up c9-core-installer 
(3.1.1670+git20160304-0rcnee2~bpo80+20160307+1) ...
c9-core-installer:npm: [3.8.2]
c9-core-installer:node: [v0.10.42]
...
Setting up pastebinit (1.5-1~bpo80+20160303+1) ...
Processing triggers for initramfs-tools 
(0.120+deb8u1-1rcnee1~bpo80+20160229+1) ...
update-initramfs: Generating /boot/initrd.img-4.1.18-ti-r49
Processing triggers for libc-bin (2.19-18+deb8u3) ...
Errors were encountered while processing:
 bb-node-red-installer
E: Sub-process /usr/bin/dpkg returned an error code (1)


This system is kernel 4.1.18-ti-r49 and I've been doing apt-get update, 
apt-get upgrade pretty regularly (monthly?) so as to not fall to far out of 
date.
Have I managed to end up with the wrong kernel as things have evolved?

Is there a package to install that would track the current kernel series 
updates when doing an apt-get upgrade?

-- 
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] State of uio_pruss in 4.1.18-ti and later kernels?

[Wally Bkg]

Please, pretty please could you map which kernel versions work correctly 
with what Beaglebone functions on the elinux site.  It seems we can't have 
it all with a single kernel at the moment.  I've been sticking with either 
the kernels in "Latest" at beagleboard.org or your testing images -- some 
of which have been -ti, others -ti-rt  Seems I may be chasing my tail with 
some things doomed from the start by the "wrong" kernel version :(

I see at least the following features that need kernel choice guidance, I 
suspect there are others:

Full Cape Support
uio_pruss
other pru development methods -- pruss_remoteproc, and perhaps others I'm 
not aware of
Bonescript/Node-red



On Thursday, March 31, 2016 at 10:19:56 PM UTC-5, RobertCNelson wrote:
>
> On Thu, Mar 31, 2016 at 9:42 PM, Rick Mann  > wrote: 
> > I'm getting back into my BBB project after MANY months away. I've got 
> the 3/27 build of 8.3/4.1.18-rt installed on a BBGreen. I'm working toward 
> installing all the components for my project, and one of them is uio_pruss. 
> > 
> > Does anyone know the status of uio_pruss in 4.1.18? I've lost track of 
> which kernels supported it and which didn't. I feel like a -ti kernel won't 
> have support for it. I also think I need to get a much more recent kernel 
> installed to properly support the audio stuff I want to do, but I don't 
> have my old BBB accessible at the moment to see what it's got installed. 
>
> the non-ti have uio_pruss: 
>
> sudo apt-get update 
> sudo apt-get install linux-image-4.1.20-bone-rt-r20 
> sudo reboot 
>
> 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] Re: Beaglebone and Chromebook connection

[Wally Bkg]

What Beaglebone image are you running?   I've found many of the recent 
images have issues with getting the "USB gadget" Ethernet over USB to work 
reliably.   Without the USB gadget interface the ssh debian@192.168.7.2 
will not work.  Can you try a wired Ethernet connection?  Then the ssh 
login should work to the IP your router assigns to the Beaglebone.

On Thursday, March 31, 2016 at 7:47:48 PM UTC-5, christi...@gmail.com wrote:
>
> Hi all,
> I'm trying to connect a Beaglebone to a Chromebook without any luck. The 
> network connection doesn't seem to get established.
> Only time it worked was when I had to reboot the Chromebook after I 
> received an OS update. Once I logged in, the network was up. I didn't 
> manage to get the connection up again after that once time.
>
> Thanks for your help.
> Christian
>

-- 
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] node-red-node-beaglebone install broke node-red on 2016-03-27 image

[Wally Bkg]

The 2016-03-27 image got off to a very good start for me with node-red 
working out of the box and all the Bonescript issues I'd had with earlier 
images appear fixed -- analogRead/Write, digitalRead/Write and 
attachInterrupt in the Cloud9 examples all appear to run correctly without 
throwing spurious error messages.   I mentioned in another thread that only 
the START.htm link to http://192.168.7.2/bone101/Support/bone101/ didn't 
work -- Navigation Bar on the left was broken and all the Interactive 
buttons were grayed out. 


But when I tried to install node-red-node-beaglebone with:

sudo -i
cd .node-red
npm install -g --unsafe-perm node-red-node-beaglebone


Things went horribly wrong:
./src/i2c.cc: In function ‘v8::Handle WriteWord(const int&)’:
../src/i2c.cc:282:1: warning: control reaches end of non-void function 
[-Wreturn-type]
 }
 ^
i2c.target.mk:85: recipe for target 'Release/obj.target/i2c/src/i2c.o' 
failed
make: *** [Release/obj.target/i2c/src/i2c.o] Error 1
make: Leaving directory 
'/usr/local/lib/node_modules/node-red-node-beaglebone/node_modules/i2c/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit 
(/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at ChildProcess.emit (events.js:110:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit 
(child_process.js:1078:12)
gyp ERR! System Linux 4.1.18-ti-r55
gyp ERR! command "node" 
"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" 
"rebuild"
gyp ERR! cwd 
/usr/local/lib/node_modules/node-red-node-beaglebone/node_modules/i2c
gyp ERR! node -v v0.12.12
gyp ERR! node-gyp -v v3.3.1
gyp ERR! not ok 
npm WARN install:i2c@0.1.8 i2c@0.1.8 install: `node-gyp rebuild`
npm WARN install:i2c@0.1.8 Exit status 1
/usr/local/lib
└── node-red-node-beaglebone@0.1.5 


And after I rebooted something is running on port 1880 but the web browser 
never connects.
Any ideas how to fix?

-- 
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: versions puzzle with mifare card reader

[toni incog]

pcsc-lite is a userspace solution, the blacklist is to prevent kernel 
modules interfering. It's libnfc that's using the kernel drivers?
Anyway, thanks but I can fall back to wheezy. Just curious where it goes 
bananas. Now trying latest 'offical' jessie release.

google asking me to post again? I really don't get this webbased eventually 
inconsistent crap. And why 2 post buttons.. Well here we go (again)

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

[beagleboard] Re: Beaglebone and Chromebook connection

[Greg]

Here is one method.  Get the "Secure Shell" extension.  This will give you 
a Linux style terminal in a tab.  See if you can:

ssh root@192.168.7.2

If your IP address is different, adjust in the above command.

I've tried this and it works.  I didn't do anything beyond testing to see 
if it works.  I normally use a Linux desktop to work with my Beaglebones.

Regards,
Greg

-- 
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: versions puzzle with mifare card reader

[Joshua Datko]

Maybe another option is to use libnfc? IIRC, that was all user space and
didn't require the kernel driver.
On Apr 1, 2016 04:58, "toni incog"  wrote:

> fired-up an amd64 jessie and that is working even without libacsccid1,
> puzzling.
>
> --
> 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: Play audio throuhg HDMI on BeagleBone Black

[yolcopc]

Kernel is updated to TI's branch: "*4.1.15-ti-r40*".

Now, VLC player does not show any error message and plays the sound sample, 
but no sound is reproduced.
I have checked the basics, volume, mute option and similar. These are not 
the failures.

*Which could the missing part for making the sound audible? Maybe codecs?*

Testing the sound configuration, next instructions are launched:

*ls /dev/snd*

ls /proc/asound

cat /proc/asound/cards
cat /proc(asound/devices
aplay -l
cat /proc/asound/card0/pcm0p/sub0/hw_params 


With output:

*Black  card0  cards  devices  oss  pcm  seq  timers  version*
* 0 [Black  ]: TI_BeagleBone_B - TI BeagleBone Black*
*  TI BeagleBone Black*
*  2: [ 0]   : control*
*  3: [ 0- 0]: digital audio playback*
*  4: [ 0- 0]: digital audio capture*
* 33:: timer*
* List of PLAYBACK Hardware Devices *
*card 0: Black [TI BeagleBone Black], device 0: HDMI hdmi-hifi-0 []*
*  Subdevices: 0/1*
*  Subdevice #0: subdevice #0*
*access: MMAP_INTERLEAVED*
*format: S32_LE*
*subformat: STD*
*channels: 2*
*rate: 32000 (32000/1)*
*period_size: 1024*
*buffer_size: 16384*


But there is no sound.

-- 
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: versions puzzle with mifare card reader

[toni incog]

fired-up an amd64 jessie and that is working even without libacsccid1, 
puzzling.

-- 
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] versions puzzle with mifare card reader

[toni incog]

Hi, 
I have a  working acr122U usb card reader @bbb|g:

1.bbb, wheezy, kernel 4.1.18-r56
2.bbg, wheezy, kernel 3.8.13-bone71.1 (ex works Debian Image 2015-03-01)

with following recipe:

modprobe.d/rfid-blacklist

blacklist pn533
blacklist nfc

apt-get install libpcsclite1 pcsc-tools pcscd libacsccid1

nice. 

But now I pimped a bbg to jessie and latest kernel and it fails:

sudo pcscd -f  --error 
0935 ifdwrapper.c:371:IFDStatusICC() Card not transacted: 612
0555 eventhandler.c:233:EHSpawnEventHandler() Initial Check Failed on ACS 
ACR122U 00 00
0514 readerfactory.c:361:RFAddReader() ACS ACR122U init failed.
00042066 hotplug_libudev.c:501:HPAddDevice() Failed adding USB device: ACS 
ACR122U
03016030 ccid_usb.c:798:ReadUSB() read failed (1/4): -7 Resource temporarily 
unavailable

Seems the only diff is jessie vs wheezy. But somehow it can't read the usb like 
the blacklist didn't work.

Ideas? I'm out of.


-- 
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: Play audio throuhg HDMI on BeagleBone Black

[yolcopc]

Kernel is updated to TI's branch: "*4.1.15-ti-r40*".

Now, VLC player does not show any error message and plays the sound sample, 
but no sound is reproduced.
I have checked the basics, volume, mute option and similar. These are not 
the failures.

Which could the missing part for making the sound audible? Maybe codecs?

-- 
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: Play audio throuhg HDMI on BeagleBone Black

[yolcopc]

Thanks Robert!
I have an issue with ntp update at boot. I have solved it temporary.

Well, I have just tried to launch the '*update_kernel*' script:

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


But it fails due to there is not space left on device. 

cp: failed to extend '/boot/uboot/initrd.img': No space left on device


Checking device with '*df -h*', output is:

/dev/mmcblk0p1 96M 96M 100% /boot/uboot


Is there any option to extend this partition? Or maybe, can I remove some 
file from "*/boot/uboot*" without blocking the system? 
If '*_bak' folders are removed the result is the same, no space left 
neither, and at reboot, BBB is bricked.




El martes, 29 de marzo de 2016, 18:07:44 (UTC+2), RobertCNelson escribió:
>
> On Tue, Mar 29, 2016 at 4:53 AM,   wrote: 
> > Moreover, if I follow next steps: 
> > 
> > cd /opt/scripts/tools/ 
> > git pull 
> > sudo ./update_kernel.sh --ti-channel --lts-4_1 
> > 
> > 
> > I get this message: 
> > 
> > ERROR: The certificate of 'rcn-ee.com' is not trusted. 
> > 
> > The certificate has not yet been activated. 
>
> Update your bbb's clock: 
>
> we use "Let's Encrypt Authority X1" certificate, which has a narrow 
> time window: "3/16/16" -> "6/14/16".. 
>
> 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] Difference between Beaglebone Console and IOT images?

[Jason Kridner]

> On Mar 30, 2016, at 2:12 PM, Robert Nelson  wrote:
> 
>> On Wed, Mar 30, 2016 at 2:09 PM, Wally Bkg  wrote:
>> I'm curious as to difference between the Beaglebone Console and IOT images
>> and the reason(s) for choosing one over the other.
>> 
>> Even on my BBW I prefer an lxde or lxqt image as I like to be able to do ssh
>> -X for things like gedit or geany from time to time, and I like the easy
>> back-up and/or cloning of SD cards over flashing eMMC, but I'd like to know
>> when an alternate image might make sense.
> 
> The iot image = lxqt image - lxqt/xorg...

I believe 'ssh -X' should still be useful for you since you'd be running the X 
Server on your host and don't need it on the Bone.

To take this a bit further, I wonder how X11 in the browser is these days:
* https://archive.fosdem.org/2015/schedule/event/webx11/
* https://m.youtube.com/watch?v=6zJ8TNcWTyo=1
* https://magcius.github.io/xplain/article/

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