Honestly I don't know. I though this might be useful info :)
Three is no problem to disable I2C-2, but I am using those pins for CAN0.
That is why I want to use custom gpio to drive RS485 DE which doesn't work.

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

> *cat /proc/tty/driver/serial*
>
> *serinfo:1.0 driver revision:*
> *0: uart:8250 mmio:0x44E09000 irq:158 tx:2451 rx:0 RTS|CTS|DTR|DSR*
> *1: uart:8250 mmio:0x48022000 irq:159 tx:24 rx:0 CTS|DSR|CD|RI*
> *2: uart:8250 mmio:0x48024000 irq:160 tx:0 rx:0 CTS|DSR*
> *3: uart:unknown port:00000000 irq:0*
> *4: uart:8250 mmio:0x481A8000 irq:161 tx:2 rx:1 brk:1 CTS|DSR*
>
> *5: uart:unknown port:00000000 irq:0*
>
> What is this supposed to mean ? That says UART0 has RTS, CTS, etc, but
> they're not connected to anything. So the CTS on UART1 means nothing.
> Because it's connected to I2C-2, which I'm sure you would have all kinds of
> fun disabling I2C-2 . . .
>
>
> On Mon, Apr 25, 2016 at 1:14 PM, 'Artur Festyn' via BeagleBoard <
> [email protected]> wrote:
>
>> cat /proc/tty/driver/serial
>> serinfo:1.0 driver revision:
>> 0: uart:8250 mmio:0x44E09000 irq:158 tx:2451 rx:0 RTS|CTS|DTR|DSR
>> *1: uart:8250 mmio:0x48022000 irq:159 tx:24 rx:0 CTS|DSR|CD|RI*
>> 2: uart:8250 mmio:0x48024000 irq:160 tx:0 rx:0 CTS|DSR
>> 3: uart:unknown port:00000000 irq:0
>> 4: uart:8250 mmio:0x481A8000 irq:161 tx:2 rx:1 brk:1 CTS|DSR
>> 5: uart:unknown port:00000000 irq:0
>>
>>
>> 2016-04-25 21:12 GMT+01:00 Artur Festyn <[email protected]>:
>>
>>> 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/CAAPjYCaM58KxhqX_s1DwsdJ7z2tdemEoCVHjZj0D780CpxQTug%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CAAPjYCaM58KxhqX_s1DwsdJ7z2tdemEoCVHjZj0D780CpxQTug%40mail.gmail.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 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/CALHSORrEpSMUET0monBs3YB-qonsfYPzCjQex%3DZdhZ-KMskn%2BA%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORrEpSMUET0monBs3YB-qonsfYPzCjQex%3DZdhZ-KMskn%2BA%40mail.gmail.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/CAAPjYCawdcQZ1%2BOvszmEj0Zp4yPfS7qDfMfOn-R1OZZ1u29KmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to