Can anyone recommend a zero config discovery scheme that a mobile app could
use to establish a wi-fi bi-directional connection to a Beagleboard device?
There are a lot of choices.
https://en.wikipedia.org/wiki/Zero-configuration_networking
Any recommendations? My preference is something that
when check UART on BBB you will see only UART0 If you want to use other.
You must defined others. There is tutorial maybe you can check this
http://tenderlovemaking.com/2014/01/19/enabling-ttyo1-on-beaglebone.html
2015-11-10 17:40 GMT+02:00 Peter Hurley :
> On
Well rs485 already work with the kernel 4.1 :
http://lxr.free-electrons.com/source/drivers/tty/serial/omap-serial.c#L293
There is everything that we need there !
Le mar. 10 nov. 2015 à 16:47, Peter Hurley a
écrit :
> On 11/10/2015 09:45 AM, Micka wrote:
> > Robert.N
On 10/31/2015 05:08 PM, dlchambers wrote:
> BBB's J1 connects to UART0, and this is used for the serial console.
>
> Is it possible to run the console on a different UART
Yes.
> run another instance of the console on a different UART while concurrently
> running a console on UART0 ?
No;
On 11/10/2015 09:45 AM, Micka wrote:
> Robert.N the patches are not exactly what we want for the beaglebone black (
> 8250_fintek 8250_lpc18xx ) ; correct me if I'm wrong.
That's not correct; the patches pointed to by Robert add software-driven
RTS control for RS485.
> And most of the time we
But it's with the driver omap which is what we want to avoid now ..
Le mar. 10 nov. 2015 à 16:50, Micka a écrit :
> Well rs485 already work with the kernel 4.1 :
>
> http://lxr.free-electrons.com/source/drivers/tty/serial/omap-serial.c#L293
>
> There is everything
On 11/10/2015 03:45 PM, Micka wrote:
> Not now I'm going to use RS485 working on the kernel 4.1 . ( I used
> 3.8 before ) .
>
> Robert.N the patches are not exactly what we want for the beaglebone
> black ( 8250_fintek 8250_lpc18xx ) ; correct me if I'm wrong.
>
> And most of the time we don't
Yes, you can use different UART and Run
check console ls -l /dev/ttyO*
Result
crw--w 1 root tty 248, 0 Jan 1 2000 /dev/ttyO0
crw-rw 1 root dialout 248, 1 Nov 10 13:23 /dev/ttyO1
crw-rw 1 root dialout 248, 4 Nov 10 14:37 /dev/ttyO4
than which want to open UART port
Ahh, I didn't realize that was enabled by default so that's probably the
issue. Thanks!
On Monday, November 9, 2015 at 10:46:18 PM UTC-5, john3909 wrote:
>
>
>
> On Nov 9, 2015, at 7:38 PM, Jaron Horst
> wrote:
>
> I'm converting from Raspberry Pi to BBB and am trying to
Hello,
I use this:
http://www.meanwell.com/webapp/product/search.aspx?prod=dr-15
DR-15-5
Am Montag, 9. November 2015 16:23:14 UTC+1 schrieb Wulf Man:
>
> As posted here a few times.
> If your power supply does not have a fast enough rise time getting up to
> voltage
> your BBB will not boot
rise time spec
1000ms setup 50ms rise time
maybe gerald can give his thumbs up on that spec
seems fast enough can you put a scope on it to be sure ?
maybe the power supply is out of spec some of the time
i have been using a cheap 5 dollar chinese supply for 2 years with no issues
On 11/10/2015
Thank both of you.
Your explanations did work very well and I can load capes without a problem.
The only problem is that no capes are loaded at boot startup process. So I
need to load the cape everytime.
The following answer
Hi,
I have installed cups(1.5.3) in my Beagleboard black based custom hardware
running on Debian 7.8 using 'apt-get install' command. I am trying to print
to HP deskjet 1112 usb printer from system line but nothing is getting
printed and the output of 'lpstat -t' shows the error : "
I forgot:
I power up the power supply ... So not only connected the BBB on the Running
power supply.
Trank you
Am Dienstag, 10. November 2015 18:58:40 UTC+1 schrieb Wulf Man:
> rise time spec
>
> 1000ms setup 50ms rise time
>
> maybe gerald can give his thumbs up on that spec
>
I've got a slight issue--
On my hardware:
root@localhost:/sys/class/uio# uname -r
3.14.54-ti-rt-r77
root@localhost:/sys/class/uio# lsmod
Module Size Used by
usb_f_ecm 7909 1
g_ether 1802 0
usb_f_rndis17719 2 g_ether
u_ether
So a bit more information. Here is the device tree overlay i've loaded
/dts-v1/;
/plugin/;
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
/* identification */
part-number = "pruss_enable";
version = "00A0";
fragment@0 {
target = <>;
Hi!
I've been trying to solve this problem all day and now I'm all out of
ideas. I have a BeagleBone Black rev C and I'm running SuperCollider on it
for a live performance thing. The problem arises when I try to connect a
midi controller to it (the Korg nanoKONTROL2). On my desktop computer
My BBB Blacks seemed to find the UWN200 (Ralink - from LogicSupply) Wifi
driver out of the box. Not so the BBB-Green from Seeed Studio (Linux
version 3.8.13-bone71.1). I find lots of WiFi documentation, but all
roads seem to just lead deeper into the swamp.
Dave
--
For more options,
I've just started learning about uio myself, but my guess is that you've
loaded the uio_pruss module manually. Yes ? So with a kernel that has cape
manager . . .
$ uname -r
4.1.9-bone-rt-r16
$ lsmod |grep pru
$ sudo sh -c "echo 'pru_enable' > /sys/devices/platform/bone_capemgr/slots"
$ lsmod
On Tue, Nov 10, 2015 at 3:42 PM, wrote:
> My BBB Blacks seemed to find the UWN200 (Ralink - from LogicSupply) Wifi
> driver out of the box. Not so the BBB-Green from Seeed Studio (Linux
> version 3.8.13-bone71.1). I find lots of WiFi documentation, but all roads
> seem to
After purchasing the book “Getting Started with Beaglebone” I purchased a
BBB.
Going through the chapters I generated a simple script (blink.py) and
wanted to use the example
in the book on having that script auto execute whenever the BBB is
restarted or rebooted.
It did not work, But
my bad, I missed a necessary point there. Basically you need to change
status = "disabled"; to status = "okay";
Then it is my best guess that everything you need to use uio_pruss will be
loaded correctly.
On Tue, Nov 10, 2015 at 5:17 PM, William Hermans wrote:
> So a bit
I flashed 4.1.10-ti-r21 image from a link you pointed me to in an email
from a different thread, to fix a USB problem.
Anyway:
owlstone@BBBKME9205EB:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2015-07-28
On 9 November 2015 at 17:15, Robert Nelson wrote:
> On Mon,
I have a build that doesn't contain led_acc either. Did you ever fine out
what to install to provide led_acc?
On Thursday, June 25, 2015 at 11:38:51 AM UTC-6, sho...@embeddediron.com
wrote:
>
> Guys, this solution did not work for me. I updated the
> /etc/init.d/led_agng.sh script but it
On Tue, Nov 10, 2015 at 7:02 AM, wrote:
>
> Hey all,
>
> I'm currently using the latest Debian Jessie image (2015-11-08) on my
> Beaglebone Black.
> I want to use UART4 as RS485 interface and use gpio3_19 as DE/RE signal.
>
> The device tree overlay which I
Hi Florian,
On 11/10/2015 08:02 AM, florian.feldbaue...@googlemail.com wrote:
> I'm currently using the latest Debian Jessie image (2015-11-08) on my
> Beaglebone Black.
> I want to use UART4 as RS485 interface and use gpio3_19 as DE/RE signal.
>
> The device tree overlay which I use to
Not now I'm going to use RS485 working on the kernel 4.1 . ( I used 3.8
before ) .
Robert.N the patches are not exactly what we want for the beaglebone black
( 8250_fintek 8250_lpc18xx ) ; correct me if I'm wrong.
And most of the time we don't use the hardware control of the PIN, We use
other
Hey all,
I'm currently using the latest Debian Jessie image (2015-11-08) on my
Beaglebone Black.
I want to use UART4 as RS485 interface and use gpio3_19 as DE/RE signal.
The device tree overlay which I use to configure the pinmux settings can be
found here:
28 matches
Mail list logo