[beagleboard] How can a mobile app wi-fi discover a Beagleboard?

[Eddie Sutton]

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 makes life easy for
the mobile app user.

Thanks in advance,

-Ed

-- 
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] Console on other than UART0?

[H . Hüseyin ERKOL]

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 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; however, it would not be difficult to add this support.
> What is your use-case?
>
> Regards,
> Peter Hurley
>
> --
> 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/W7j7lsJ7haQ/unsubscribe.
> To unsubscribe from this group and all its topics, 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] RS485 support in kernel 4.1.12-ti-r28

[Micka]

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 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 don't use the hardware control of the PIN, We
> use other Pins to control the DE/RE .
>
> Good point, thanks.
>
> Regards,
> Peter Hurley
>
> --
> 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] Console on other than UART0?

[Peter Hurley]

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; however, it would not be difficult to add this support.
What is your use-case?

Regards,
Peter Hurley

-- 
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] RS485 support in kernel 4.1.12-ti-r28

[Peter Hurley]

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 don't use the hardware control of the PIN, We use 
> other Pins to control the DE/RE .

Good point, thanks.

Regards,
Peter Hurley

-- 
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] RS485 support in kernel 4.1.12-ti-r28

[Micka]

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 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 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 don't use the hardware control of the PIN, We
>> use other Pins to control the DE/RE .
>>
>> Good point, thanks.
>>
>> Regards,
>> Peter Hurley
>>
>> --
>> 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] RS485 support in kernel 4.1.12-ti-r28

[Florian Feldbauer]

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 use the hardware control of the PIN, We
> use other Pins to control the DE/RE .
>
>
> Floriant, I don't have time yet to work on this case, ( maybe on
> december ). But could you do some test on your own ?
Not for November 23, since I will be on a business trip next week.
But after that I will try to look into it.
>  That the official documentation of the RS485 with the kernel 4.1 : 
> http://lxr.free-electrons.com/source/Documentation/serial/serial-rs485.txt?v=4.1
>
> Also I remember that the kernel 4.1 is build by default with not the
> OMAP configured, you need to build the kernel yourself :
>
> git clone https://github.com/RobertCNelson/bb-kernel.git
> ..
>
> and activate omap as a serial driver.
>
>
> Micka,
>
>
>
> Le mar. 10 nov. 2015 à 15:29, Robert Nelson  > a écrit :
>
> 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 use to configure the pinmux
> settings can be
> > found here:
> > https://github.com/Sillern/BB-RS485/blob/master/BB-RS485-00A0.dts
> >
> > When I load this overlay and try to configure the port in my C
> program, I
> > always get the error message "inappropriate ioctl for device"
> > when using the command
> > ioctl( fd, TIOCSRS485,  )
> > where rs485conf is a struct serial_rs485
> >
> > The image uses kernel version 4.1.12-ti-r28. Has this kernel
> version RS485
> > support enabled for the UART interfaces?
> > If not, is there a kernel version (preferable 4.1.X) which
> supports RS485 on
> > the UARTs of the BBB?
>
> There are a few patches being discussed, please follow
>
> http://www.spinics.net/lists/linux-serial/msg19564.html
>
> http://www.spinics.net/lists/linux-serial/
>
> I'd like to backport what ever comes out of above ^
>
> 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.
>


-- 

| Dr. Florian Feldbauer|
|  |
| Helmholtz-Institut Mainz /   |
| Johannes Gutenberg-Universität Mainz |
| Johann-Joachim-Becher-Weg 36 |
| D-55128 Mainz|
|  |
| Office: SB1 / 00-213 |
| Phone:  (+49)6131 / 39-29608 |


-- 
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: Console on other than UART0?

[H . Hüseyin ERKOL]

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
root@beaglebone:~# minicom -D /dev/ttyO4 -b 9600 for example

31 Ekim 2015 Cumartesi 23:08:01 UTC+2 tarihinde dlchambers yazdı:
>
> 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, and/or run another 
> instance of the console on a different UART while concurrently running a 
> console on UART0 ?
>
> If this is possible, the procedure to do it on Debian would be appreciated.
>
> 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.

Re: [beagleboard] GPIO's and Built-In Pull-Up Resistors

[Jaron Horst]

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 get the GPIO to 
> work.  One thing I noticed is that Adafruit Pull-up resistor command in 
> their Python GPIO package only seams to work on certain GPIO's.  Ex: I 
> could get it to work on P8_7 to P8_10 but not P8_11 to P8_14.  Where can I 
> find documentation on what GPIO's support pull up/down resistors and which 
> do not? (that is, assuming I didn't just stumble on a bug in the Adafruit 
> GPIO library!)  Thanks!
>
> import Adafruit_BBIO.GPIO as GPIO
> GPIO.setup("PA_7", GPIO.IN, pull_up_down = GPIO.PUD_UP)
>
> My bet is you haven’t disabled the LCD in the device tree.
>
> Regards,
> John
>
>
> -- 
> 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 .
> 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] BBB don't boot sometimes

[Fohnbit]

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 reliable.
> You have not said what specs your power supply is or where you got it 
> from. 
>
>
>
> On 11/9/2015 8:02 AM, Fohnbit wrote:
>
> Hello!
>
> Sometimes my BBB Rev C dont boot, when I connect the 5V.
> The Power LED is on but the 4 USR LED are off.
>
> This happen not really often ... So I have no debug information.
>
> But maybe someone has the same problem and know where the problem is?
>
> 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...@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] BBB don't boot sometimes

[evilwulfie]

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 10:30 AM, Fohnbit wrote:
> 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 reliable.
> You have not said what specs your power supply is or where you got
> it from.
>
>
>
> On 11/9/2015 8:02 AM, Fohnbit wrote:
>> Hello!
>>
>> Sometimes my BBB Rev C dont boot, when I connect the 5V.
>> The Power LED is on but the 4 USR LED are off.
>>
>> This happen not really often ... So I have no debug information.
>>
>> But maybe someone has the same problem and know where the problem is?
>>
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout
>> .
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google
> Groups "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to beagleboard+unsubscr...@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

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

Re: [beagleboard] Re: How to enable UART1 using dtb-rebuilder?

[Davide Picchi]

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 

 
didn't help further. I have that flag as default in my beagle.

The only working way seems to be:

/boot/uEnv.txt  // open that file and write the following:
 
cape_enable=bone_capemgr.enable_partno=BB-UART1

But I thought that this is just an alternative, not the first choice.

Any idea?
 



Am Montag, 9. November 2015 21:16:10 UTC+1 schrieb William Hermans:
>
>
> http://www.embeddedhobbyist.com/2015/09/beaglebone-black-updating-device-tree-files/
>
> On Mon, Nov 9, 2015 at 11:48 AM, Robert Nelson  > wrote:
>
>> On Mon, Nov 9, 2015 at 12:45 PM, Davide Picchi > > wrote:
>> >> 4.1-ti supports overlays, so you can either do it like "3.8".
>> >>
>> >>
>> >> 
>> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART1-00A0.dts
>> >>
>> >> or create a custom *.dtb
>> >
>> >
>> > That's nice,
>> > but I cannot find any guide that helps me to install the new cape like 
>> in
>> > the first tutorial I posted above.
>> >
>> > How do I use such overlays?
>> > 
>> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART1-00A0.dts
>> >
>> > Should I copy them somewhere?
>>
>> Follow steps 1 -> 3:
>>
>> https://github.com/beagleboard/bb.org-overlays/blob/master/readme.md
>>
>> Then either:
>>
>> sudo sh -c "echo 'BB-UART1' > /sys/devices/platform/bone_capemgr/slots"
>>
>> or:
>>
>> /boot/uEnv.txt
>>
>> cape_enable=bone_capemgr.enable_partno=BB-UART1
>>
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

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

[beagleboard] CUPS printing issue

[Ison Thomas]

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 : " 
/usr/lib/cups/filter/hpcups failed "

The error_log output is :

I [10/Nov/2015:09:44:51 +] Saving job.cache...
I [10/Nov/2015:09:44:52 +] Listening to [v1.::1]:631 (IPv6)
I [10/Nov/2015:09:44:52 +] Listening to 127.0.0.1:631 (IPv4)
I [10/Nov/2015:09:44:52 +] Listening to /var/run/cups/cups.sock (Domain)
I [10/Nov/2015:09:44:52 +] Remote access is disabled.
D [10/Nov/2015:09:44:52 +] Added auto ServerAlias beaglebone
I [10/Nov/2015:09:44:52 +] Loaded configuration file 
"/etc/cups/cupsd.conf"
I [10/Nov/2015:09:44:52 +] Using default TempDir of 
/var/spool/cups/tmp...
I [10/Nov/2015:09:44:52 +] Configured for up to 100 clients.
I [10/Nov/2015:09:44:52 +] Allowing up to 100 client connections per 
host.
I [10/Nov/2015:09:44:52 +] Using policy "default" as the default.
I [10/Nov/2015:09:44:52 +] Full reload is required.
I [10/Nov/2015:09:44:52 +] Loaded MIME database from 
"/usr/share/cups/mime" and "/etc/cups": 39 types, 56 filters...
D [10/Nov/2015:09:44:52 +] Loading printer HP...
D [10/Nov/2015:09:44:52 +] load_ppd: Loading /var/cache/cups/HP.data...
D [10/Nov/2015:09:44:52 +] Calling DeleteDevice(cups-HP)
D [10/Nov/2015:09:44:52 +] failed to DeleteDevice: 
org.freedesktop.DBus.Error.InvalidArgs:Type of message, `(s)', does not 
match expected type `(o)'
D [10/Nov/2015:09:44:52 +] Using profile id of HP-Gray..
D [10/Nov/2015:09:44:52 +] Calling CreateProfile(HP-Gray..,temp)
D [10/Nov/2015:09:44:52 +] created profile 
/org/freedesktop/ColorManager/profiles/HP_Gray__
D [10/Nov/2015:09:44:52 +] Using profile id of HP-RGB..
D [10/Nov/2015:09:44:52 +] Calling CreateProfile(HP-RGB..,temp)
D [10/Nov/2015:09:44:52 +] created profile 
/org/freedesktop/ColorManager/profiles/HP_RGB__
I [10/Nov/2015:09:44:52 +] Registering ICC color profiles for "HP"
D [10/Nov/2015:09:44:52 +] Calling CreateDevice(cups-HP,temp)
D [10/Nov/2015:09:44:52 +] created device 
/org/freedesktop/ColorManager/devices/cups_HP
D [10/Nov/2015:09:44:52 +] Calling 
/org/freedesktop/ColorManager/devices/cups_HP:AddProfile(/org/freedesktop/ColorManager/profiles/HP_Gray__)
 
[soft]
D [10/Nov/2015:09:44:52 +] Calling 
/org/freedesktop/ColorManager/devices/cups_HP:AddProfile(/org/freedesktop/ColorManager/profiles/HP_RGB__)
 
[soft]
D [10/Nov/2015:09:44:52 +] cupsdRegisterPrinter(p=0xb6feb638(HP))
I [10/Nov/2015:09:44:52 +] Loading job cache file 
"/var/cache/cups/job.cache"...
I [10/Nov/2015:09:44:52 +] Full reload complete.
D [10/Nov/2015:09:44:52 +] cupsdCleanFiles(path="/var/spool/cups/tmp", 
pattern="(null)")
I [10/Nov/2015:09:44:52 +] Cleaning out old files in 
"/var/spool/cups/tmp"...
D [10/Nov/2015:09:44:52 +] cupsdCleanFiles(path="/var/cache/cups", 
pattern="*.ipp")
I [10/Nov/2015:09:44:52 +] Cleaning out old files in 
"/var/cache/cups"...
E [10/Nov/2015:09:44:52 +] Unable to open listen socket for address 
[v1.::1]:631 - Address family not supported by protocol.
I [10/Nov/2015:09:44:52 +] Listening to 127.0.0.1:631 on fd 9...
I [10/Nov/2015:09:44:52 +] Listening to /var/run/cups/cups.sock:631 on 
fd 10...
I [10/Nov/2015:09:44:52 +] Resuming new connection processing...
D [10/Nov/2015:09:44:52 +] Avahi client started
D [10/Nov/2015:09:44:52 +] cupsdRegisterPrinter(p=0xb6feb638(HP))
D [10/Nov/2015:09:44:52 +] cupsdSetBusyState: newbusy="Not busy", 
busy="Not busy"
D [10/Nov/2015:09:44:52 +] Discarding unused server-started event...
D [10/Nov/2015:09:44:53 +] Report: clients=0
D [10/Nov/2015:09:44:53 +] Report: jobs=0
D [10/Nov/2015:09:44:53 +] Report: jobs-active=0
D [10/Nov/2015:09:44:53 +] Report: printers=1
D [10/Nov/2015:09:44:53 +] Report: printers-implicit=0
D [10/Nov/2015:09:44:53 +] Report: stringpool-string-count=2200
D [10/Nov/2015:09:44:53 +] Report: stringpool-alloc-bytes=9256
D [10/Nov/2015:09:44:53 +] Report: stringpool-total-bytes=41544
D [10/Nov/2015:09:44:59 +] cupsdAcceptClient: 15 from localhost (Domain)
D [10/Nov/2015:09:44:59 +] cupsdReadClient: 15 POST / HTTP/1.1
D [10/Nov/2015:09:44:59 +] cupsdSetBusyState: newbusy="Active clients", 
busy="Not busy"
D [10/Nov/2015:09:44:59 +] cupsdAuthorize: No authentication data 
provided.
D [10/Nov/2015:09:44:59 +] cupsdReadClient: 15 1.1 CUPS-Get-Printers 1
D [10/Nov/2015:09:44:59 +] CUPS-Get-Printers
D [10/Nov/2015:09:44:59 +] Returning IPP successful-ok for 
CUPS-Get-Printers (no URI) from localhost
D [10/Nov/2015:09:44:59 +] cupsdSetBusyState: newbusy="Not busy", 
busy="Active clients"
D [10/Nov/2015:09:44:59 +] cupsdReadClient: 15 POST / HTTP/1.1
D 

Re: [beagleboard] BBB don't boot sometimes

[Fohnbit]

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
> 
>   
> 
>   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 10:30 AM, Fohnbit wrote:
> 
> 
> 
>   
> 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 reliable.
> 
>   You have not said what specs your power supply is or where
>   you got it from. 
> 
>   
> 
>   
> 
>   
> 
>   On 11/9/2015 8:02 AM, Fohnbit wrote:
> 
> 
> 
>   
> Hello!
> 
> 
> 
> Sometimes my BBB Rev C dont boot, when I connect the 5V.
> 
> The Power LED is on but the 4 USR LED are off.
> 
> 
> 
> This happen not really often ... So I have no debug
> information.
> 
> 
> 
> But maybe someone has the same problem and know where
> the problem is?
> 
> 
> 
> 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...@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...@googlegroups.com.
> 
>   For more options, visit https://groups.google.com/d/optout.

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

[beagleboard] UIO and Pruss

[Tou Parish]

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_ether10156  3 usb_f_ecm,g_ether,usb_f_rndis
libcomposite   38699  3 usb_f_ecm,g_ether,usb_f_rndis
*uio_pruss   2372  0* 
omap_serial_rs485  16943  0 
root@localhost:/sys/class/uio# 

And finally...

root@localhost:/sys/class/uio# ls
root@localhost:/sys/class/uio# 

So after installing uio_pruss nothing shows up in the uio directory for it.

Any ideas?

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.

Re: [beagleboard] UIO and Pruss

[William Hermans]

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 = <>;
   __overlay__ {
  status = "okay";

   };
};

};

So, the target is  Looking in the am335x-boneblack.dts file there is
no mention of  But this file does have two includes at the top.

#include "am33xx.dtsi"
#include "am335x-bone-common.dtsi"

Searching through am33xx.dtsi for "pruss" turns up this fragment.

pruss: pruss@4a30 {
compatible = "ti,pruss-v2";
ti,hwmods = "pruss";
ti,deassert-hard-reset = "pruss", "pruss";
reg = <0x4a30 0x08>;
ti,pintc-offset = <0x2>;
interrupt-parent = <>;
status = "disabled";
interrupts = <20 21 22 23 24 25 26 27>;
};

So, I believe you have a couple options. First, you can create an overlay
like file, and #include it in am335x-boneblack.dts. IN order to do this you
will need to copy your current dtbo file, decompile it,  edit the file, etc
,etc, then recompile the file. Back up, and move the old
am335x-boneblack.dts file out of the way. Replace with your newly compiled
file. The second option is pretty much the same thing, but your change the
am335x-boneblack.dtbo file directly.

Anyway, there is actually a third option. Get rid of that 3.14.x kernel,
and use a 4.x kernel . . . a kernel that can actually use cape manager.


On Tue, Nov 10, 2015 at 4:29 PM, William Hermans  wrote:

> 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 |grep pru
> uio_pruss   4143  0
> uio 8006  2 uio_pruss,uio_pdrv_genirq
>
> So, anyway, the module you're missing is *uio_pdrv_genirq* but this
> minimal generic driver module needs parameters when loaded. That much I
> know, but what I do not know is how to load that module. Well not exactly.
> That, and I'm not sure how to dissect the Linux Image I have now to find
> out . . .
>
> On Tue, Nov 10, 2015 at 2:50 PM, Tou Parish 
> wrote:
>
>> 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_ether10156  3 usb_f_ecm,g_ether,usb_f_rndis
>> libcomposite   38699  3 usb_f_ecm,g_ether,usb_f_rndis
>> *uio_pruss   2372  0*
>> omap_serial_rs485  16943  0
>> root@localhost:/sys/class/uio#
>>
>> And finally...
>>
>> root@localhost:/sys/class/uio# ls
>> root@localhost:/sys/class/uio#
>>
>> So after installing uio_pruss nothing shows up in the uio directory for
>> it.
>>
>> Any ideas?
>>
>> 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.
>>
>
>

-- 
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] ALSA can't find midi controller on BeagleBone Black

[eriknatanaelgustafsson]

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 
(Ubuntu Studio) it works plug & play, but on the BBB SuperCollider can't 
find it at all and SC gets its midi in/out from ALSA so it must be that 
ALSA can't find it for some reason. 

"lsusb" shows it and "cat /dev/midi1" gives me live output from it. It even 
shows up in "cat /proc/asound/cards". The USB sound card on the same USB 
hub works like a charm.

lsmod gives me

Module  Size  Used by
snd_seq46038  1 
snd_seq_device  5895  1 snd_seq
g_ether23958  0 
libcomposite   15028  1 g_ether
snd_usb_audio 100405  3 
snd_hwdep   4885  1 snd_usb_audio
snd_usbmidi_lib15375  1 snd_usb_audio
omap_rng4062  0 
mt7601Usta458758  0 

which seems like it might be some module missing. Originally I used an old 
BBB debian version, but I have now upgraded with a fresh flash of the eMMC 
and recompiled jack2 and SuperCollider without any luck. What should I do?

Cheers,

Erik Natanael Gustafsson

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

[beagleboard] BeagleBone Green does not load driver for UWN200 WiFi adaptor

[wittend]

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, 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] UIO and Pruss

[William Hermans]

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 |grep pru
uio_pruss   4143  0
uio 8006  2 uio_pruss,uio_pdrv_genirq

So, anyway, the module you're missing is *uio_pdrv_genirq* but this minimal
generic driver module needs parameters when loaded. That much I know, but
what I do not know is how to load that module. Well not exactly. That, and
I'm not sure how to dissect the Linux Image I have now to find out . . .

On Tue, Nov 10, 2015 at 2:50 PM, Tou Parish  wrote:

> 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_ether10156  3 usb_f_ecm,g_ether,usb_f_rndis
> libcomposite   38699  3 usb_f_ecm,g_ether,usb_f_rndis
> *uio_pruss   2372  0*
> omap_serial_rs485  16943  0
> root@localhost:/sys/class/uio#
>
> And finally...
>
> root@localhost:/sys/class/uio# ls
> root@localhost:/sys/class/uio#
>
> So after installing uio_pruss nothing shows up in the uio directory for it.
>
> Any ideas?
>
> 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.
>

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

Re: [beagleboard] BeagleBone Green does not load driver for UWN200 WiFi adaptor

[Robert Nelson]

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 just lead deeper into the swamp.

reflash:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2015-11-03

The "3.8.13-bone71.1" as a custom build so the modules aren't in the repo...

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] auto execute a a simple python script on the BBB

[jship1962]

 

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 executing systemctl start blink.service does work. 
This makes me think

all of the setup to use the systemctl is ok.


I have included the below text that represents how systemctl start 
blink.service is edited:


[Unit]

Description=blink.py client

[Service]

Type=simple 

WorkingDirectory=/root/

ExecStart=/usr/bin/python blink.py

Restart=always

RestartSec=5

StartLimitInterval=0

[Install]

WantedBy=multi-user.target



I am new to this type of forum and would also like to know if this is the 
proper way to post

this issue and also how can I view any post I have submitted.

I did look at the suggested post but there seem to be only a couple and 
none of the responses

seemed to address my quest to get the simple script to work in the way I 
was hoping for.

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.

Re: [beagleboard] UIO and Pruss

[William Hermans]

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 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 = <>;
>__overlay__ {
>   status = "okay";
>
>};
> };
>
> };
>
> So, the target is  Looking in the am335x-boneblack.dts file there
> is no mention of  But this file does have two includes at the top.
>
> #include "am33xx.dtsi"
> #include "am335x-bone-common.dtsi"
>
> Searching through am33xx.dtsi for "pruss" turns up this fragment.
>
> pruss: pruss@4a30 {
> compatible = "ti,pruss-v2";
> ti,hwmods = "pruss";
> ti,deassert-hard-reset = "pruss", "pruss";
> reg = <0x4a30 0x08>;
> ti,pintc-offset = <0x2>;
> interrupt-parent = <>;
> status = "disabled";
> interrupts = <20 21 22 23 24 25 26 27>;
> };
>
> So, I believe you have a couple options. First, you can create an overlay
> like file, and #include it in am335x-boneblack.dts. IN order to do this you
> will need to copy your current dtbo file, decompile it,  edit the file, etc
> ,etc, then recompile the file. Back up, and move the old
> am335x-boneblack.dts file out of the way. Replace with your newly compiled
> file. The second option is pretty much the same thing, but your change the
> am335x-boneblack.dtbo file directly.
>
> Anyway, there is actually a third option. Get rid of that 3.14.x kernel,
> and use a 4.x kernel . . . a kernel that can actually use cape manager.
>
>
> On Tue, Nov 10, 2015 at 4:29 PM, William Hermans 
> wrote:
>
>> 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 |grep pru
>> uio_pruss   4143  0
>> uio 8006  2 uio_pruss,uio_pdrv_genirq
>>
>> So, anyway, the module you're missing is *uio_pdrv_genirq* but this
>> minimal generic driver module needs parameters when loaded. That much I
>> know, but what I do not know is how to load that module. Well not exactly.
>> That, and I'm not sure how to dissect the Linux Image I have now to find
>> out . . .
>>
>> On Tue, Nov 10, 2015 at 2:50 PM, Tou Parish 
>> wrote:
>>
>>> 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_ether10156  3 usb_f_ecm,g_ether,usb_f_rndis
>>> libcomposite   38699  3 usb_f_ecm,g_ether,usb_f_rndis
>>> *uio_pruss   2372  0*
>>> omap_serial_rs485  16943  0
>>> root@localhost:/sys/class/uio#
>>>
>>> And finally...
>>>
>>> root@localhost:/sys/class/uio# ls
>>> root@localhost:/sys/class/uio#
>>>
>>> So after installing uio_pruss nothing shows up in the uio directory for
>>> it.
>>>
>>> Any ideas?
>>>
>>> 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.
>>>
>>
>>
>

-- 
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] Ethernet-over-USB problems under 4.1.10-ti-r21

[Guido Paoluzi Cusani]

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, Nov 9, 2015 at 11:12 AM, Guido Paoluzi Cusani
>  wrote:
> > No clue...
>
> So you didn't download it from somewhere? it was just given to you?
>
> cat /etc/dogtag
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.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/nzdsU8oR-zw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] Re: Cannot apt-get install packages - led_aging.sh missing LSB tags and overrides

[curtiswpaul]

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 looks like I do not have the 
> /usr/bin/led_acc program at all. Just wondering if I should remove the 
> script using update-rc.d as Simon suggests or get a hold of 
> /usr/bin/led_acc somewhere.
>
> Best regards,
> Steve
>
> On Friday, June 20, 2014 at 1:19:15 PM UTC-4, Simon wrote:
>>
>> Hello,
>>
>> I have 3 stock Rev.C element14 BeagleBone Black boards and cannot apt-get 
>> install packages on any of them due to errors caused by an init script 
>> called 'led-aging.sh'.
>> Here's what I get:
>>
>> insserv: warning: script 'S18led_aging' missing LSB tags and overrides
>>>
>>> insserv: warning: script 'led_aging.sh' missing LSB tags and overrides
>>>
>>> insserv: There is a loop between service rmnologin and mountnfs if 
>>> started
>>>
>>> insserv:  loop involving service mountnfs at depth 7
>>>
>>> insserv:  loop involving service networking at depth 6
>>>
>>> insserv: There is a loop between service led_aging and mountall if 
>>> started
>>>
>>> insserv:  loop involving service mountall at depth 5
>>>
>>> insserv:  loop involving service checkroot-bootclean at depth 4
>>>
>>> insserv:  loop involving service urandom at depth 7
>>>
>>> insserv:  loop involving service checkfs at depth 5
>>>
>>> insserv: There is a loop between service rmnologin and mountdevsubfs if 
>>> started
>>>
>>> insserv:  loop involving service mountdevsubfs at depth 2
>>>
>>> insserv:  loop involving service udev at depth 1
>>>
>>> insserv: There is a loop at service rmnologin if started
>>>
>>> insserv: There is a loop between service rmnologin and 
>>> mountnfs-bootclean if started
>>>
>>> insserv:  loop involving service mountnfs-bootclean at depth 2
>>>
>>> insserv:  loop involving service mountall-bootclean at depth 1
>>>
>>> insserv:  loop involving service kbd at depth 11
>>>
>>> insserv: Starting led_aging.sh depends on rmnologin and therefore on 
>>> system facility `$all' which can not be true!
>>>
>>> [...]
>>>
>>> insserv: Max recursions depth 99 reached
>>>
>>> insserv:  loop involving service capemgr.sh at depth 1
>>>
>>> insserv: Starting led_aging.sh depends on rmnologin and therefore on 
>>> system facility `$all' which can not be true!
>>>
>>> [...]
>>>
>>> insserv: There is a loop at service led_aging if started
>>>
>>> insserv: Starting led_aging.sh depends on rmnologin and therefore on 
>>> system facility `$all' which can not be true!
>>>
>>> insserv:  loop involving service hwclock at depth 4
>>>
>>> insserv: Starting led_aging.sh depends on rmnologin and therefore on 
>>> system facility `$all' which can not be true!
>>>
>>> [...]
>>>
>>> insserv: There is a loop between service led_aging and 
>>> mountall-bootclean if started
>>>
>>> insserv: Starting led_aging.sh depends on rmnologin and therefore on 
>>> system facility `$all' which can not be true!
>>>
>>> insserv: Starting led_aging.sh depends on rmnologin and therefore on 
>>> system facility `$all' which can not be true!
>>>
>>> insserv: exiting now without changing boot order!
>>>
>>> update-rc.d: error: insserv rejected the script header
>>>
>> Removing the script altogether using update-rc.d causes the problem to go 
>> away, but I'd rather not solve it this way...
>> What does the script do? Is this an element14 BBB-specific issue?
>> I couldn't find any information about the script except for one forum 
>> post in Chinese regarding LED driver development.
>>
>> Thanks in advance,
>> Simon
>>
>

-- 
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] RS485 support in kernel 4.1.12-ti-r28

[Robert Nelson]

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 use to configure the pinmux settings can be
> found here:
> https://github.com/Sillern/BB-RS485/blob/master/BB-RS485-00A0.dts
>
> When I load this overlay and try to configure the port in my C program, I
> always get the error message "inappropriate ioctl for device"
> when using the command
> ioctl( fd, TIOCSRS485,  )
> where rs485conf is a struct serial_rs485
>
> The image uses kernel version 4.1.12-ti-r28. Has this kernel version RS485
> support enabled for the UART interfaces?
> If not, is there a kernel version (preferable 4.1.X) which supports RS485 on
> the UARTs of the BBB?

There are a few patches being discussed, please follow

http://www.spinics.net/lists/linux-serial/msg19564.html

http://www.spinics.net/lists/linux-serial/

I'd like to backport what ever comes out of above ^

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] RS485 support in kernel 4.1.12-ti-r28

[Peter Hurley]

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 configure the pinmux settings can be 
> found here:
> https://github.com/Sillern/BB-RS485/blob/master/BB-RS485-00A0.dts
> 
> When I load this overlay and try to configure the port in my C program, I 
> always get the error message "inappropriate ioctl for device"
> when using the command
> ioctl( fd, TIOCSRS485,  )
> where rs485conf is a struct serial_rs485
> 
> The image uses kernel version 4.1.12-ti-r28. Has this kernel version RS485 
> support enabled for the UART interfaces?
> If not, is there a kernel version (preferable 4.1.X) which supports RS485 on 
> the UARTs of the BBB?

The 4.x-series ti kernels use the omap8250 driver which does not
have RS485 support (yet). An initial patchset was just recently
submitted for 8250 support of RS485 but needs some more work before
it will be accepted into mainline (4.5 at the earliest).

If you can build your own kernel, you can switch back to the
omap-serial driver which still offers RS485 support. Note if you
do switch, you will need to change your user-space console/tty ports
back to ttyO*.

Regards,
Peter Hurley

-- 
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] RS485 support in kernel 4.1.12-ti-r28

[Micka]

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 Pins to control the DE/RE .


Floriant, I don't have time yet to work on this case, ( maybe on december
). But could you do some test on your own ?

 That the official documentation of the RS485 with the kernel 4.1 :
http://lxr.free-electrons.com/source/Documentation/serial/serial-rs485.txt?v=4.1

Also I remember that the kernel 4.1 is build by default with not the OMAP
configured, you need to build the kernel yourself :

git clone https://github.com/RobertCNelson/bb-kernel.git
..

and activate omap as a serial driver.


Micka,



Le mar. 10 nov. 2015 à 15:29, Robert Nelson  a
écrit :

> 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 use to configure the pinmux settings can
> be
> > found here:
> > https://github.com/Sillern/BB-RS485/blob/master/BB-RS485-00A0.dts
> >
> > When I load this overlay and try to configure the port in my C program, I
> > always get the error message "inappropriate ioctl for device"
> > when using the command
> > ioctl( fd, TIOCSRS485,  )
> > where rs485conf is a struct serial_rs485
> >
> > The image uses kernel version 4.1.12-ti-r28. Has this kernel version
> RS485
> > support enabled for the UART interfaces?
> > If not, is there a kernel version (preferable 4.1.X) which supports
> RS485 on
> > the UARTs of the BBB?
>
> There are a few patches being discussed, please follow
>
> http://www.spinics.net/lists/linux-serial/msg19564.html
>
> http://www.spinics.net/lists/linux-serial/
>
> I'd like to backport what ever comes out of above ^
>
> 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.

[beagleboard] RS485 support in kernel 4.1.12-ti-r28

[florian . feldbauer85]

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:
https://github.com/Sillern/BB-RS485/blob/master/BB-RS485-00A0.dts

When I load this overlay and try to configure the port in my C program, I 
always get the error message "inappropriate ioctl for device"
when using the command
ioctl( fd, TIOCSRS485,  )
where rs485conf is a struct serial_rs485

The image uses kernel version 4.1.12-ti-r28. Has this kernel version RS485 
support enabled for the UART interfaces?
If not, is there a kernel version (preferable 4.1.X) which supports RS485 
on the UARTs of the BBB?

Any help appreciated!
Regards,
Florian

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