On 29 April 2016 at 13:39, 'Florian Feldbauer' via BeagleBoard <beagleboard@googlegroups.com> wrote:
> 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... Great news that it is all working! I wonder, have you seen in the scope how many milliseconds does it take for DE/RE to switch from high to low after the BB finishes writing a block of data to the bus? Would you please post the .dts files you used with the 4.1 and 4.4 kernels to enable RS485? -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAKkGsYLjc3Amd6_EBFu0tu-aqsW5isswC%2B2Vfve-%3DPi_hmJORw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
