Adding rs485-rx-during-tx to the .dts do the trick.
fragment@2 {
target = <&uart2>;
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&pb_uart2_rs485_pins>;
rs485-rts-delay = <0 0>;
rts-gpio = <&gpio2 25 1>; /* GPIO_ACTIVE_HIGH>; */
rs485-rts-active-high;
* rs485-rx-during-tx; *
linux,rs485-enabled-at-boot-time;
};
};
Thanks
El lunes, 27 de agosto de 2018, 12:53:06 (UTC-3), Pablo Rodriguez escribió:
>
>
> Hi,
> I'm using omap serial driver to do some rs485 writing and reading. The rts
> gpio is toggling correctly and the RE pin is grounded, so rx is always
> enabled.
> Have done test with other rs485 board and it can write and read.
>
> The issue is that the uart is not receiving what it has wrote, so can't
> check if a bus collision occurs when writing.
> I have been using the same setup with the 8250 serial driver but with
> manual rts toogling and the loopback was ok.
>
> Is this the expected behavior of the omap serial driver?
> Is possible to configure to enable loopback?
>
> using kernel
> 4.14.63-bone16
>
> Thanks,
> Pablo
>
--
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/6bbf8db3-4e49-42a6-9071-6fdd8f9658c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
