.
Regards
Terje
-Original Message-
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On
Behalf Of Charles Steinkuehler
Sent: 5. desember 2014 15:33
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] xeno_16550A driver install on Debian 3.8.13-bone67
On 12/5/20
On 12/5/2014 7:41 AM, Peter Gregory wrote:
> Have you looked into using a PRU for the real time data capture?
I'd recommend considering this for the SPI interface.
The PRU can probably bit-bang the SPI fast enough for your needs, and
you won't have any issues generating small 1-2 uS pauses. Basi
Have you looked into using a PRU for the real time data capture?
There are two PRU units that run independently from the am335x processor.
They are dedicated 200mz 32 bit microcontrollers with 8k program & 8k data.
They also have the ability to interface with the BBB pins - even shift in up to
28
ct: Re: [beagleboard] xeno_16550A driver install on Debian 3.8.13-bone67
Dear Terje,
Did you find how to use the 8250 driver with * .dts?
Pour utiliser le pilote 8250, vous aurez aussi besoin de modifier le fichier *
.dts.
Le mercredi 12 novembre 2014 18:32:11 UTC+1, Terje Froysa a écrit :
Thanks Rob
Dear Terje,
Did you find how to use the 8250 driver with * .dts?
Pour utiliser le pilote 8250, vous aurez aussi besoin de modifier le fichier
* .dts.
Le mercredi 12 novembre 2014 18:32:11 UTC+1, Terje Froysa a écrit :
>
> Thanks Robert,
> for taking your time to enlight a newbie.
>
> The fog
Thanks Robert,
for taking your time to enlight a newbie.
The fog is slowly lifting
Regards
Terje
On Wednesday, November 12, 2014 6:01:52 PM UTC+1, RobertCNelson wrote:
> On Wed, Nov 12, 2014 at 10:50 AM, Terje Froysa > wrote:
> > Robert,
> > just for my curiosity and pease of mind:
>
On Wed, Nov 12, 2014 at 10:50 AM, Terje Froysa wrote:
> Robert,
> just for my curiosity and pease of mind:
>
> If the 8250 have been "no mainline" for several years and there are no
> dtbo's to enable it.
> Why is the ttySx still there and the 8250 by default enabled in the -bone67
> ?
The histor
Robert,
just for my curiosity and pease of mind:
If the 8250 have been "no mainline" for several years and there are
no dtbo's to enable it.
Why is the ttySx still there and the 8250 by default enabled in the -bone67
?
Regards
Terje
On Wednesday, November 12, 2014 5:07:59 PM UTC+1, RobertCN
Thanks Robert,
Just the answer I exepected (and lectured to my colleagues).
I think I will try to settle for xenomai rtdm drivers on the GPIO's and
std. Linux drivers on the uarts and spi for the time beeing.
Regards
Terje
On Wednesday, November 12, 2014 5:07:59 PM UTC+1, RobertCNelson wrote:
On Wed, Nov 12, 2014 at 9:56 AM, Terje Froysa wrote:
> Ok Robert,
>
> If I enable the 8250/16550 in the menuconfig this driver connects to
> /dev/ttySx.
> The ttyO[1,2,4] appears and vanishes with the BB-UARTx dtbo's
>
> The ttySx devices does not work anyhow (while not enabled via any dtbo)
> Is
Ok Robert,
If I enable the 8250/16550 in the menuconfig this driver connects to
/dev/ttySx.
The ttyO[1,2,4] appears and vanishes with the BB-UARTx dtbo's
The ttySx devices does not work anyhow (while not enabled via any dtbo)
Is there any method of enabling the ttySx devices if a 8250 driver i
Ok Charles,
It doesn't seem very promising this comment from Gilles:
I just had a quick look at the omap-serial.c driver and:
- it does not do anything that I can see to enable its clocks
- it does NOT use byte access but word access, that is, its registers are
16 bits wide.
Unfortunately, as
Gilles' 3rd option is what I was referring to trying.
The other two options seem workable as well. The best choice depends on
what you're more comfortable working with.
On 11/12/2014 8:41 AM, Terje Froysa wrote:
> Thanks Charles,
>
> I appreciate your ideas.
> I seem stuck "between a rock and a
On Wed, Nov 12, 2014 at 8:41 AM, Terje Froysa wrote:
> Thanks Charles,
>
> I appreciate your ideas.
> I seem stuck "between a rock and a hard place" with very little substantial
> experiences to collect from the communities.
>
> I will try a couple of permutations more before I may revert to using
Thanks Charles,
I appreciate your ideas.
I seem stuck "between a rock and a hard place" with very little substantial
experiences to collect from the communities.
I will try a couple of permutations more before I may revert to using the
standard Linux drivers.
I also got some comments from Xeno
On 11/12/2014 6:21 AM, Terje Froysa wrote:
>
> Everything seem correct.
> But the UARTs are now occupied by the omap_serial driver.
> According to Xenomai (http://xenomai.org/serial-16550a-driver/) the driver
> should be disabled by the setserial command.
> I can't get this command working. It
Tried with an alias for the ttyO4:
alias char-major-248-4 xeno_16550A
But no reaction or error messages in dmesg, nor a change in driver link:
lrwxrwxrwx 1 root root 0 Nov 12 13:41 /sys/dev/char/248:4/device/driver ->
../../../bus/platform/drivers/omap_uart
Do the aliases require the kernel mo
Hello again,
While having problems with the command:
setserial /dev/ttyOx usart none
I started to look at /lib/modprobe.d/aliases.conf
I wonder if it is possible to set the xeno_16550A as an alias to the major
number 248 (ttyOx):
alias char-major-248-1 xeno_16540A
alias char-major-248-2 x
Hello Charles,
I have now carefully checked your suggestions.
- I have checked that the UART dtbo are loaded at boot-time (by uEnv.txt)
- I have built (and booted) the kernel with the xeno_16550A as loadable
module.
- I have checked the functionality of the /dev/ttyOx by running ph
Hi Charles,
Thanks a lot for your quick reply and reflected suggestions.
I will check them out point-by-point and check out if I find any flaws in
my configurations.
Best regards
Terje Froysa
On Tuesday, November 11, 2014 3:59:51 PM UTC+1, Charles Steinkuehler wrote:
> On 11/11/2014 8:42 AM,
On 11/11/2014 8:42 AM, Terje Froysa wrote:
>
>
> Dear forum,
>
> I have struggled for 4 days and I am out of ideas/suggestions on how to
> make this xeno_16550A driver work.
> 1. I have successfully installed the Xenomai 2.6.4 and the Debian 3.8.13.
> 2. Self-developed RTDM driver is working
21 matches
Mail list logo
