On 04/29/2016 12:06 PM, Taceant Omnes wrote:
On 29 April 2016 at 10:18, 'Florian Feldbauer' via BeagleBoard
<[email protected]> wrote:
Did I miss anything? I tried this with Kernel version 4.4.6-ti-r15 as well
as 4.4.8
I mounted the SD card and deleted the initrd.img-`uname -r` file. After
that, the BeagleBone was booting again.
But: Loading the BB-UART4-RS485 device tree overlay manually, I can now
receive data over the RS485 bus,
but I can no longer send data.
So it seems the OMAP driver is not working either. Actually now it is even
worse than before using the 8250 driver.
Sorry that it did not work.
What about trying a 4.1.x kernel as some people seem to have had
success with it? However I would suggest installing a Debian image
that comes with a 4.1 kernel rather than using a 4.1 kernel on your
current image. Last year I had a problem with some sort of systemd
incompatibility with a kernel when I upgraded a kernel whereby the BBB
would not boot.
Hey all,
I have to apologize for my last two mails, because I made a stupid
mistake...
If you look at the source of my test program (6th message in this thread)
I only set the SER_RS485_ENABLED flag in the struct serial_rs485.
This didn't work, so I uncommented the next two lines which were
rs485conf.flags |= SER_RS485_RTS_ON_SEND;
rs485conf.flags &= ~SER_RS485_RTS_ON_SEND;
Of course this tells the RTS signal to be always 0 which does not work...
Fixing this bug, RS485 is now working with both kernels, 4.1 and 4.4,
using the OMAP driver...
Many thanks for your help and support!
Cheers,
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/57235600.9060406%40googlemail.com.
For more options, visit https://groups.google.com/d/optout.
