From e9837c612d451cb5ddb5939981f77a88bedbbd76 Mon Sep 17 00:00:00 2001
From: thegroove <535855+thegroove@users.noreply.github.com>
Date: Thu, 7 Mar 2024 04:09:32 +0100
Subject: [PATCH] Create trouble-network-hi35xx.md

---
 en/trouble-network-hi35xx.md | 119 +++++++++++++++++++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 en/trouble-network-hi35xx.md

diff --git a/en/trouble-network-hi35xx.md b/en/trouble-network-hi35xx.md
new file mode 100644
index 0000000..c63e134
--- /dev/null
+++ b/en/trouble-network-hi35xx.md
@@ -0,0 +1,119 @@
+# OpenIPC Wiki
+[Table of Content](../README.md)
+
+## Troubleshooting: Network does not work on hi35xx
+If network is not working on your hi35xx device after installing OpenIPC (no link), you may have to tune the MII (Media Independent Interface) settings.  
+For U-Boot, this is done by setting values for `phyaddru`, `phyaddrd` and `mdio_intf`.
+Possible values for `phyaddru` and `phyaddrd` are: `0-3`, possible values for `mdio_intf` are: `rmii`, `rgmii`,  `gmii`.  
+For the Linux kernel / OS, values can be set through the `extras` boot variables `hieth.phyaddru`, `hieth.phyaddrd`, `hieth.mdioifu` and `hieth.mdioifd`.
+
+Often the correct values can be found in your stock firmware. Viewing the boot logs or running [ipctool](https://github.com/OpenIPC/ipctool) on your stock firmware may provide clues.
+
+Below are some combinations you can try:
+
+### For ethernet in Linux:
+
+In Linux console run this:
+```
+fw_setenv extras 'hieth.phyaddru=0 hieth.phyaddrd=1' && reboot
+```
+If the above settings did not work, try this instead:
+```
+fw_setenv extras 'hieth.phyaddru=1 hieth.phyaddrd=0' && reboot
+```
+Or:
+```
+fw_setenv extras 'hieth.mdioifu=0 hieth.mdioifd=0' && reboot
+```
+Or:
+```
+fw_setenv extras 'hieth.mdioifu=1 hieth.mdioifd=1' && reboot
+```
+Or:
+```
+fw_setenv extras hieth.mdioifu=0 hieth.mdioifd=0 hieth.phyaddru=1 hieth.phyaddrd=2 && reboot
+```
+Or:
+```
+fw_setenv extras hieth.phyaddru=3 hieth.mdioifu=0 && reboot
+```
+
+*Note: if a certain combination causes your device to fail to boot, you can clear the variable(s) in the U-Boot prompt by calling `setenv <variable>`, i.e. set the variable using an empty argument, followed by `saveenv`.*
+
+### For ethernet in U-boot:
+
+Set `phyaddru` and `phyaddrd` variables from U-Boot console:
+```
+setenv phyaddru 0; setenv phyaddrd 1; saveenv; reset
+```
+If the above settings did not work, try this instead
+```
+setenv phyaddru 1; setenv phyaddrd 0; saveenv; reset
+```
+Or:
+```
+setenv phyaddru 0; setenv phyaddrd 0; saveenv; reset
+```
+Or:
+```
+setenv phyaddru 1; setenv phyaddrd 1; saveenv; reset
+```
+
+*Note: to initialize and test network connectivity in U-Boot, the `ping` command can be used.*  
+
+Some known combinations for specific boards:
+
+### XiongMai, HI3518EV100
+*For U-boot network:*
+```
+    setenv phyaddru 1
+    setenv phyaddrd 2
+    setenv mdio_intf rmii
+    saveenv
+```
+*For Linux network:*
+```
+    setenv extras 'hieth.phyaddru=1 hieth.phyaddrd=2'
+    saveenv
+```
+
+### XiongMai IPG-53H20AF, HI3516CV100
+
+*For Linux network:*
+```
+   setenv hieth.mdioifu=0 hieth.mdioifd=0 hieth.phyaddru=1 hieth.phyaddrd=2
+   saveenv
+```
+
+### CamHi/HiChip/Xin, HI3518EV200
+
+*For U-boot network:*
+```
+    setenv phyaddru 0
+    setenv phyaddrd 1
+    saveenv
+```
+
+### HiWatch, HI3518CV100
+
+*For U-boot network:*
+```
+    setenv phyaddru 3
+    saveenv
+```
+
+*For Linux network:*
+```
+    setenv extras 'hieth.phyaddru=3 hieth.mdioifu=0'
+    saveenv
+```
+
+### Harex (5013A-CF/5020A-FF), HI3516CV100
+
+*For U-boot network:*
+```
+    setenv extras 'hieth.phyaddru=1 hieth.mdioifu=0'
+    saveenv
+```
+
+If nothing of the above worked for you, please ask in [our Telegram channel](https://t.me/openipc).