I can't use RTS/CTS pins on UART4 because I need HDMI.
New RS485 patches suppose to help to use any gpio as RS485 RTS and in fact
any gpio for any UART as RTS/CTS.




2016-04-25 21:00 GMT+01:00 evilwulfie <[email protected]>:

> any reason you want to use uart1 ?
>
> if you use uart4 you can use the whole uart tx rx and rts. trying to
> bitbang rts for rs485 on uart1 sounds hard
>
>
>
> On 4/25/2016 12:24 PM, 'Jan Kinkazu' via BeagleBoard wrote:
>
> So i compiled (bb-kernel, all patches) and installed 4.5.2-bone4
> I have modified am335-boneblack.dts and compiled it.
>
> #include "am335x-peripheral-ttyS1.dtsi"
> #include "am335x-bone-pinmux-ttyS1.dtsi"
>
> &am33xx_pinmux {
>         uart1_pins: pinmux_uart1_pins {
>                 pinctrl-single,pins = <
>                         /* P9_23: uart1_de */
>                         BONE_P9_23 (PIN_OUTPUT_PULLDOWN | MUX_MODE7)
>                 >;
>         };
> };
>
> &uart1 {
>         pinctrl-names = "default";
>         pinctrl-0 = <&uart1_pins>;
>         status = "okay";
>         rts-gpios = <&gpio1 17 GPIO_ACTIVE_HIGH>;
>         rs485-rts-active-high;
>         rs485-rx-during-tx;
>         rs485-rts-delay = <1 1>;
>         linux,rs485-enabled-at-boot-time;
> };
>
> RS485 doesn't work, what do I do wrong?
>
> Kind regards
>
>
> On Friday, 12 February 2016 15:33:40 UTC, Taceant Omnes wrote:
>>
>> I would like to use RS485 with the BBB.
>>
>> root@beaglebone:~/test# uname -a
>> Linux beaglebone 4.1.15-ti-r40 #1 SMP PREEMPT Thu Jan 7 23:32:17 UTC
>> 2016 armv7l GNU/Linux
>>
>> I am using the kernel above. Its source code is at
>> https://github.com/RobertCNelson/linux-stable-rcn-ee/tree/4.1.15-ti-rt-r40
>>
>> ... however it does not include the changes in this patch:
>>
>> https://github.com/RobertCNelson/bb-kernel/blob/am33x-v3.8/patches/fixes/0007-omap-RS485-support-by-Michael-Musset.patch#L30
>>
>> Which kernel should I use that includes the changes in the patch or
>> something similar?
>>
> --
> 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/50692f39-69e3-4454-b8ba-ec03e4d86101%40googlegroups.com?utm_medium=email&utm_source=footer>
> https://groups.google.com/d/msgid/beagleboard/50692f39-69e3-4454-b8ba-ec03e4d86101%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=icon>
>  Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient&utm_term=link>
>
> --
> 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/nMtRpdWSJu0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/571E7751.2020206%40gmail.com
> <https://groups.google.com/d/msgid/beagleboard/571E7751.2020206%40gmail.com?utm_medium=email&utm_source=footer>
> .
>
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAAPjYCae4vGaqBNaAXsqKqMOuKKOKCBSFVG6ZKEa0BMKBSsmMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to