Jump to content

ebalcsk

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

 Content Type 

Posts posted by ebalcsk

    Orange Pi One+ cannot communicate with UART3 on Armbian_21.02.1_Orangepioneplus_buster_current_5.10.12.img.xz

    in Allwinner sunxi

    Posted 

    root@orangepioneplus:~# dtc -@ -I dtb -O dts -o /root/sun50i-h6-orangepi-one-plus.dts-5.10.12 /boot/dtb/allwinner/sun50i-h6-orangepi-one-plus.dtb
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@480000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@720000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@816000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@888000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1080000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1320000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1488000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1608000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1704000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (unit_address_vs_reg): /cpu-opp-table/opp@1800000000: node has a unit name, but no reg property
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (graph_child_address): /soc/tcon-top@6510000/ports/port@0: graph node has single child node 'endpoint@0', #address-cells/#size-cells are not necessary
/root/sun50i-h6-orangepi-one-plus.dts-5.10.12: Warning (graph_child_address): /soc/tcon-top@6510000/ports/port@4: graph node has single child node 'endpoint@0', #address-cells/#size-cells are not necessary
root@orangepioneplus:~#

     

    sun50i-h6-orangepi-one-plus.dts-5.10.12

    0

    Orange Pi One+ cannot communicate with UART3 on Armbian_21.02.1_Orangepioneplus_buster_current_5.10.12.img.xz

    in Allwinner sunxi

    Posted

    it looks like exist: 

    root@orangepioneplus:~# ll /proc/device-tree/soc/serial@5000c00
total 0
-r--r--r-- 1 root root  8 Feb 10 21:50 clocks
-r--r--r-- 1 root root 17 Feb 10 21:50 compatible
-r--r--r-- 1 root root 12 Feb 10 21:50 interrupts
-r--r--r-- 1 root root  7 Feb 10 21:50 name
-r--r--r-- 1 root root  4 Feb 10 21:50 phandle
-r--r--r-- 1 root root  4 Feb 10 21:50 pinctrl-0
-r--r--r-- 1 root root  8 Feb 10 21:50 pinctrl-names
-r--r--r-- 1 root root  8 Feb 10 21:50 reg
-r--r--r-- 1 root root  4 Feb 10 21:50 reg-io-width
-r--r--r-- 1 root root  4 Feb 10 21:50 reg-shift
-r--r--r-- 1 root root  8 Feb 10 21:50 resets
-r--r--r-- 1 root root  5 Feb 10 21:50 status
root@orangepioneplus:~#

     

    0

    Orange Pi One+ cannot communicate with UART3 on Armbian_21.02.1_Orangepioneplus_buster_current_5.10.12.img.xz

    in Allwinner sunxi

    Posted

    Hello,

     

    I try to communicate on UART3 (pin 11/13) just TTL, but cannot see any data on the lines.

    After first attempt i added overlays=uart3 to /boot/armbianEnv.txt  and rebooted the system. 

    oot@orangepioneplus:~# cat /boot/armbianEnv.txt
verbosity=1
bootlogo=false
console=both
disp_mode=1920x1080p60
overlay_prefix=sun50i-h6
rootdev=UUID=d7bd3629-b17f-4c85-9031-909157a0ce7e
rootfstype=ext4
overlays=uart3
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

    Then i also executed update-initramfs -u and rebooted the board.

     

    None of these are helped :(

     

    I wonder what i am doing wrong?

     

    I see the following in the logs: 

    root@orangepioneplus:~# dmesg | egrep --color 'serial|ttyS'
[    1.944312] printk: console [ttyS0] disabled
[    1.944394] 5000000.serial: ttyS0 at MMIO 0x5000000 (irq = 31, base_baud = 1500000) is a 16550A
[    1.944599] printk: console [ttyS0] enabled
[    1.945269] sun50i-h6-pinctrl 300b000.pinctrl: pin-119 (5000c00.serial) status -517
[    1.945284] dw-apb-uart 5000c00.serial: Error applying setting, reverse things back
[    1.971491] sun50i-h6-pinctrl 300b000.pinctrl: pin-119 (5000c00.serial) status -517
[    1.971505] dw-apb-uart 5000c00.serial: Error applying setting, reverse things back
[    1.973846] sun50i-h6-pinctrl 300b000.pinctrl: pin-119 (5000c00.serial) status -517
[    1.973860] dw-apb-uart 5000c00.serial: Error applying setting, reverse things back
[    1.975764] sun50i-h6-pinctrl 300b000.pinctrl: pin-119 (5000c00.serial) status -517
[    1.975778] dw-apb-uart 5000c00.serial: Error applying setting, reverse things back
[    2.376127] sun50i-h6-pinctrl 300b000.pinctrl: pin-119 (5000c00.serial) status -517
[    2.376141] dw-apb-uart 5000c00.serial: Error applying setting, reverse things back
[    2.401927] 5000c00.serial: ttyS3 at MMIO 0x5000c00 (irq = 32, base_baud = 1500000) is a 16550A
[    5.035583] systemd[1]: Created slice system-serial\x2dgetty.slice.

    I think it is looks okey.

    Also i can connect to UART0.

    During testing i used the same setting on minicom as UART0
      

        +-----------------------------------------------------------------------+
    | A -    Serial Device      : /dev/ttyS3                                |
    | B - Lockfile Location     : /var/lock                                 |
    | C -   Callin Program      :                                           |
    | D -  Callout Program      :                                           |
    | E -    Bps/Par/Bits       : 9600 8N1                                  |
    | F - Hardware Flow Control : No                                        |
    | G - Software Flow Control : No                                        |
    |                                                                       |
    |    Change which setting?                                              |
    +-----------------------------------------------------------------------+

     

    Also just done a same test with a USB-serial adapter which is worked so i can rule out at least problem with my testing mythology.

     

    Thank you!

     

    0

    Network interface not come up automatically after disconnection / connection of the network cable

    in Allwinner sunxi

    Posted

    Hello,

     

    I am using a orangepi one plus, but that might be no connection with my issue.

     

    I am having the following network configuration: 

    # Network is managed by Network manager
auto lo
iface lo inet loopback


allow-hotplug eth0 eth0.1 eth0.10

auto eth0
iface eth0 inet manual
  pre-up ifconfig $IFACE up
  post-down ifconfig $IFACE down

auto eth0.1
iface eth0.1 inet static
  address 192.168.1.250
  netmask 255.255.255.0
  gateway 192.168.1.1

auto eth0.10
iface eth0.10 inet static
  address 192.168.10.1
  netmask 255.255.255.0

    if i disconnect the network cable and connect back the interface is not come up automatically

    from the state it is loks like up (docker interfaces are omitted): 

    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 46188  bytes 4058716 (3.8 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5741  bytes 592928 (579.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 19

eth0.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 54  bytes 3950 (3.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 80  bytes 7233 (7.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0.10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 10603  bytes 611155 (596.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 184  bytes 14270 (13.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    but cannot ping

     

    if i restart the interfaces connection is restored 

    ifdown eth0.10
ifdown eth0.1
ifdown eth0
ifup eth0
ifup eth0.1
ifup eth0.10

    interface output looks the same: 

    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 49742  bytes 4332006 (4.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 6201  bytes 637517 (622.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 19

eth0.1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.250  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::7:e8ff:fe23:49f2  prefixlen 64  scopeid 0x20<link>
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 61  bytes 4730 (4.6 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 155  bytes 12779 (12.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0.10: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.1  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::7:e8ff:fe23:49f2  prefixlen 64  scopeid 0x20<link>
        ether 02:07:e8:23:49:f2  txqueuelen 1000  (Ethernet)
        RX packets 1844  bytes 135220 (132.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 235  bytes 18193 (17.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

     

    I wonder what is the problem?

    Thank you

     

    0
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept