On Sat, Nov 18, 2017 at 4:37 PM, Juliusz Chroboczek wrote:
> > What would that mean -- does Bluetooth provide an IP address? Is there
> an
> > interface I can access from bash scripts? An API from C/C++?
>
> As explained by Hunyue Yau, you'll need to layer something over
> BlueTooth, either BNE
>
> So if we assume the BeagleBone Green = BeagleBone Black (minus) HDMI
> (audio/video)...
>
...and the addition of the two GROVE ports. Not sure if that's important,
but in my case the software behaves differently and initializes different
things if running on a BBG since we expect certain devi
>
> Is it really worth it thou? ;)
>
Sorry, Robert, you lost me, I'm not familiar with the things you're
pointing out. From an end-user perspective, all I need to know is how can
I determine what type of board my code is running? I used to look at
/proc/device-tree/compatible but that no longer
On Mon, Oct 9, 2017 at 12:39 PM, Stephane Charette <
stephanechare...@gmail.com> wrote:
> In the past, I used to identify the type of device by reading the file
> /proc/device-tree/compatible. For example, see this:
>
> > hexdump -C /proc/device-tree/compatible
> 74 69 2c 61 6d 33 33 35
>
> > Did I install the wrong build? Is this a bug, or is there a new/better
> way
> > for me to identify the difference between BBB, BBG, BBGW, etc?
>
> Please run:
>
> sudo /opt/scripts/tools/version.sh
>
> as something didn't get assembled right...
>
Was that supposed to fix it, or do you just
>
> What I'd really like to see is a "mission statement".
>
Best I have is the documentation I already wrote:
https://www.ccoderun.ca/eps/api/index.html#introduction
In that first image, EPS is the IP addresses in "green". Note how they're
all on the same network, even if they're physically spre
Feel free to do as you wish. The whole thing is open source. You can
choose to compile yourself, download a .deb or .rpm, modify it or not, or
just ignore it. :)
I was simply posting it here because I'm using it on my Beaglebones and it
helps me out with all my devices installed at various clie
On Tue, Nov 22, 2016 at 7:36 AM, 'Ian Watts' via BeagleBoard <
beagleboard@googlegroups.com> wrote:
> ...
> although it will not complete a boot sequence via the built-in eMMC (not
> so good news)
> it WILL complete a boot sequence via the uSD card (-2-) (good news) and it
> does appear to (re-) f
On Fri, Nov 4, 2016 at 10:59 AM, Robert Nelson
wrote:
> Any change with v4.9.x-ti?
>
> cd /opt/scripts/tools/ ; git pull ; sudo ./update_kernel.sh --lts-4_9
>
>
Unfortunately no, trying the 4.9 kernel didn't help:
[ 47.550490] wlcore: ERROR SW watchdog interrupt received! starting
recovery.
[
On Fri, Nov 4, 2016 at 9:12 AM, Robert Nelson
wrote:
>
> Please download this kernel and give it a quick test:
>
That kernel didn't change anything:
[ 51.462966] wlcore: ERROR SW watchdog interrupt received! starting
recovery.
[ 54.113033] wlcore: ERROR SW watchdog interrupt received! sta
>
> [...]
> However for you, just grab:
>
> https://rcn-ee.net/rootfs/bb.org/testing/2016-10-30/seeed-iot/
>
> https://rcn-ee.net/rootfs/bb.org/testing/2016-10-30/seeed-
> iot/BBGW-blank-debian-8.6-seeed-iot-armhf-2016-10-30-4gb.img.xz
>
Perfect. I had misunderstood the purpose of the flasher im
On Sun, Oct 2, 2016 at 10:15 AM, Jason Kridner wrote:
> Have you tried etcher.io instead of dd?
>
Just tried it. Definitely more friendly than dd. Thanks for the
suggestion.
Stéphane
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are su
12 matches
Mail list logo
