Does that mean when I used BB-UART2 and /dev/ttyO2 on 3.8.13 I was actually using UART1?
Anyway on 4.1.15 I enabled all UARTs ( *cape_enable=bone_capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3,BB-UART4,BB-UART5*) in */boot/uEnv.txt* and I tried all tty files (*ttyO1, ttyO2, ttyO3, ttyO4, ttyO5*) however I didn't receive anything on any of the tty files. Only on ttyO2 - ttyO5 I received exactly 1 byte (that I didn't even send) at the very beginning, namely 0x00. *However with 3.8.13 I enable BB-UART2 and use /dev/ttyO2 and it works without problems!* So what's the difference here? (I use pyserial for serial access.) root@beaglebone:~# dmesg | grep serial [ 3.492130] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158, base_baud = 3000000) is a 8250 [ 3.500724] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 159, base_baud = 3000000) is a 8250 [ 3.501692] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 160, base_baud = 3000000) is a 8250 [ 4.145889] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 201, base_baud = 3000000) is a 8250 [ 4.149061] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 202, base_baud = 3000000) is a 8250 [ 4.151370] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 203, base_baud = 3000000) is a 8250 [ 16.842799] pinctrl-single 44e10800.pinmux: pin 44e108c0.0 already requested by 481aa000.serial; cannot claim for 0-0070 root@beaglebone:~# dmesg | grep bone [...] [ 3.885891] bone_capemgr bone_capemgr: compatible-baseboard=ti,beaglebone-black - #slots=4 [ 3.943363] bone_capemgr bone_capemgr: slot #0: No cape found [ 4.003334] bone_capemgr bone_capemgr: slot #1: No cape found [ 4.063335] bone_capemgr bone_capemgr: slot #2: No cape found [ 4.123333] bone_capemgr bone_capemgr: slot #3: No cape found [ 4.129143] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART1' VER 'N/A' PR '0' [ 4.129165] bone_capemgr bone_capemgr: slot #4: override [ 4.129181] bone_capemgr bone_capemgr: Using override eeprom data at slot 4 [ 4.129197] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-UART1' [ 4.129323] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART2' VER 'N/A' PR '0' [ 4.129337] bone_capemgr bone_capemgr: slot #5: override [ 4.129349] bone_capemgr bone_capemgr: Using override eeprom data at slot 5 [ 4.129364] bone_capemgr bone_capemgr: slot #5: 'Override Board Name,00A0,Override Manuf,BB-UART2' [ 4.129474] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART3' VER 'N/A' PR '0' [ 4.129488] bone_capemgr bone_capemgr: slot #6: override [ 4.129500] bone_capemgr bone_capemgr: Using override eeprom data at slot 6 [ 4.129515] bone_capemgr bone_capemgr: slot #6: 'Override Board Name,00A0,Override Manuf,BB-UART3' [ 4.129628] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART4' VER 'N/A' PR '0' [ 4.129641] bone_capemgr bone_capemgr: slot #7: override [ 4.129653] bone_capemgr bone_capemgr: Using override eeprom data at slot 7 [ 4.129668] bone_capemgr bone_capemgr: slot #7: 'Override Board Name,00A0,Override Manuf,BB-UART4' [ 4.129769] bone_capemgr bone_capemgr: enabled_partno PARTNO 'BB-UART5' VER 'N/A' PR '0' [ 4.129783] bone_capemgr bone_capemgr: slot #8: override [ 4.129795] bone_capemgr bone_capemgr: Using override eeprom data at slot 8 [ 4.129809] bone_capemgr bone_capemgr: slot #8: 'Override Board Name,00A0,Override Manuf,BB-UART5' [ 4.130608] bone_capemgr bone_capemgr: initialized OK. [ 4.134780] bone_capemgr bone_capemgr: slot #5: dtbo 'BB-UART2-00A0.dtbo' loaded; overlay id #1 [ 4.145526] bone_capemgr bone_capemgr: slot #4: dtbo 'BB-UART1-00A0.dtbo' loaded; overlay id #0 [ 4.146611] bone_capemgr bone_capemgr: slot #6: dtbo 'BB-UART3-00A0.dtbo' loaded; overlay id #2 [ 4.149773] bone_capemgr bone_capemgr: slot #7: dtbo 'BB-UART4-00A0.dtbo' loaded; overlay id #3 [ 4.151969] bone_capemgr bone_capemgr: slot #8: dtbo 'BB-UART5-00A0.dtbo' loaded; overlay id #4 [ 17.153124] pinctrl-single 44e10800.pinmux: could not request pin 48 (44e108c0.0) from group nxp_hdmi_bonelt_pins on device pinctrl-single [...] On Friday, June 10, 2016 at 10:11:28 PM UTC+2, [email protected] wrote: > > > Hello, > > I have an application that uses UART2. It runs fine under Debian 7 > ("Wheezy") however it doesn't under Debian 8 ("Jessie", kernel: > 4.1.15-ti-rt-r43); nothing arrives at the corresponding tty file > (/dev/ttyO2). > For enabling UARTs I declared > > cape_enable=capemgr.enable_partno=BB-UART2 (Debian 7) > > cape_enable=bone_capemgr.enable_partno=BB-UART2 (Debian 8) > > in */boot/uEnv.txt*. > > (Note that when I use UART4 instead of UART2 my application runs fine > under both operating systems.) > > So I tried to figure out the changes from Debian 7 to Debian 8 by looking > at the dts files. Looking at *cape-universal-00A0.dts* revealed: > > *Debian 7:* > > /************************/ > /* UARTs */ > /************************/ > > fragment@10 { > target = <&uart2>; /* really uart1 */ > __overlay__ { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <>; > }; > }; > > fragment@11 { > target = <&uart3>; /* really uart2 */ > __overlay__ { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <>; > }; > }; > > > > *Debian 8 (/opt/source/bb.org-overlays/src/arm/cape-universal-00A0.dts):* > /************************/ > /* UARTs */ > /************************/ > > fragment@10 { > target = <&uart2>; /* really uart1 */ > __overlay__ { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <>; > }; > }; > > fragment@11 { > target = <&uart3>; /* really uart2 */ > __overlay__ { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <>; > }; > }; > > *Debian 8 (/opt/source/bb.org-overlays/src/arm/cape-universal-00A0.dts):* > > /************************/ > /* UARTs */ > /************************/ > > fragment@10 { > target = <&uart1>; > __overlay__ { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <>; > }; > }; > > fragment@11 { > target = <&uart2>; > __overlay__ { > status = "okay"; > pinctrl-names = "default"; > pinctrl-0 = <>; > }; > }; > > I don't know what this exactly means, especially the "really uart<x>". Can > anyone clarify here? Also there are two different *cape-universal-00A0.dts > *files under Debian 8, which one is relevant? I see that in > */boot/uEnv.txt* the following line is enabled by default: > *cmdline=coherent_pool=1M > quiet cape_universal=enable*. Which dts (dtb) file does it refer to? > > Comparing */opt/source/bb.org-overlays/src/arm/BB-UART4-00A0.dts* and > */opt/source/bb.org-overlays/src/arm/BB-UART2-00A0.dts* under Debian 8 > revealed that apparently both pins have a different multiplexer mode (uart2 > -> MUX_MODE1, uart4 -> MUX_MODE6). Does this have any effect? I couldn't > find an equivalent dts file for Debian 7. > Probably related: from *cape-universal-00A0.dts* I see > > *UART2 (P9_21, P9_22):* > > [...] > P9_21_uart_pin: pinmux_P9_21_uart_pin { > pinctrl-single,pins = <0x154 0x31>; }; /* Mode 1, > Pull-Up, RxActive */ > > [...] > P9_22_uart_pin: pinmux_P9_22_uart_pin { > pinctrl-single,pins = <0x150 0x31>; }; /* Mode 1, > Pull-Up, RxActive */ > > *UART4 (P9_11, P9_13):* > > [...] > P9_11_uart_pin: pinmux_P9_11_uart_pin { > pinctrl-single,pins = <0x070 0x36>; }; /* Mode 6, > Pull-Up, RxActive */ > > [...] > P9_13_uart_pin: pinmux_P9_13_uart_pin { > pinctrl-single,pins = <0x074 0x36>; }; /* Mode 6, > Pull-Up, RxActive */ > > Is this relevant / exhibiting different behavior? > > I also realized that for UART2 there is an additional dts file under > Debian 8: */opt/source/bb.org-overlays/src/arm/BB-UART2-RTSCTS-00A0.dts* > For UART4 there is no equivalent. How is this related? > > The pin multiplexing declarations in *cape-universal-00A0.dts *(P9_21_pinmux, > P9_22_pinmux) seem to remain the same when going from Debian 7 to Debian 8. > > So does anyone know the reason why UART2 behaves differently on Debian 8 > (compared to Debian 7)? > > Many thanks in advance! Cheers, > > Dominik > -- 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/bda7002d-e00c-4786-9e97-52a0b2e46a7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
