@YuzukiTsuru Hi, thanks for the guide to port the driver! I have the problem, that the D1 LicheeRV dock with tina linux is not getting any TCP broadcast or ARP messages. Therefore the device is not reachable within the network. But it is working the other way round. So the device is connected, has an IP, can ping the default gateway, has connection to the internet, ... But it is not possible to ping the device from another PC in the network.

"tcpdump arp" does not show any messages besides from the default gateway.

Is this problem familiar to you?

Hi,

how can I export a GPIO (e.g. PD 15 on the lichee RV Dock) in the device tree to be an internal pull-up, active high and direction input?

Thanks for any advice,

David

Did you solve the problem? If yes, can you tell me how?

@WhycanService Any advice?

@whycanservice 5.4

Hi,

how can I export a GPIO (e.g. PD 15 on the lichee RV Dock) in the device tree to be an internal pull-up, active high and direction input?

Thanks for any advice,

David

@whycan Ah I see. The problem only occurs on many I/O interrupts. So for example when executing "find /" on the console or via SSH. I could maybe workaround this problem on software side. Do you recommend another WIFI + BT chip which has 4 wire UART and is compatible with D1 without a lot of driver adaptions?

@whycan Yes, I connected RX TX RTS CTS to an oscilloscope yesterday. I observed that the Realtek chip is using his RTS line, but I saw nothing on the other line.

Hi, I suspect that UART flow control (RTS, CTS) does not work on the sipeed lichee rv dock (D1 chip) board with Tina linux. I came to the assumption after testing bluetooth (RTL8723DS). In general BT works, but if the CPU is very busy, I get "Bluetooth: Out-of-order packet arrived (6 != 7)" from the kernel. The device tree is configured as followed:

uart1_pins_a: uart1_pins@0 {
		pins = "PG6", "PG7", "PG8", "PG9";
		function = "uart1";
		drive-strength = <10>;
		bias-pull-up;
};

uart1_pins_b: uart1_pins {
		pins = "PG6", "PG7", "PG8", "PG9";
		function = "gpio_in";
};

&uart1 {
	uart-has-rtscts;
	pinctrl-names = "default";
	pinctrl-0 = <&uart1_pins_a>;
	pinctrl-1 = <&uart1_pins_b>;
	status = "okay";
};

I assume something is wrong in the device tree and CTS RTS is not activated. Is there something else to activate flow controls?

Is bluetooth working as well on your board?

@juwan Is bluetooth working on your device?

@lecndav Turns out it was a combination of a bug in our unifi access points and a (minor) bug in the driver. After updating the access points, broadcast and arp are working.