Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

johlnx

Members
  • Joined

  • Last visited

  1. The log shows the chip id of 0001 vs. 8800 on the 1.5 layout. This is strange, because the marking on the chip itself bears the exact same name. Maybe it contains an other silicon inside. Android log and the DTS file shows an other Wifi driver "seekwcn_sv6160lite". Luckily, retro98boy host a dkms driver , that that might work: https://github.com/retro98boy/swt6621s Furthermore, I found two different GPIOs. PCB v1.7 V1.5 sdio-pwrseq pin gpio1-7 pin gpio1-6 vcc5v0-host-regulator pin gpio4-12 pin gpio4-13 First try if changing the gpio ports and test it with the installed driver: appply this dts overlay file, reboot and and observe a change in the system log. dts-v1/; /plugin/; &{/} { compatible = "rockchip,rk3528"; sdio_pwrseq { reset-gpios = <&gpio1 7 1>; vcc5v0_host: vcc5v0-host-regulator { gpio = <&gpio4 13 0>; }; }; If that does not lead to success, install the new driver on target: #remove old dkms remove -m ea6621q -v 1.0 cd /usr/src git clone https://github.com/retro98boy/swt6621s.git mv seekwave-swt6621s seekwave-swt6621s-1.1.0 dkms add -mseekwave-swt6621s -v 1.1.0 dkms build -mseekwave-swt6621s -v 1.1.0 dkms install -mseekwave-swt6621s -v 1.1.0modify file /etc/modprobe.d/seek.conf: options skw_sdio_lite firmware_dir=seekwave options swt6621s_wifi firmware_dir=seekwave options skwbt firmware_dir=seekwave modyfy file /etc/modules-load.d/seek.conf: hidp rfcomm bnep skw_sdio_lite swt6621s_wifi skwbtApply dts overlay; dts-v1/; /plugin/; &{/} { seekwcn_sv6160lite { compatible = "seekwave,sv6160lite"; dma_type = <0x01>; status = "okay"; phandle = <0x1ca>; }; };reboot board and check: ip link system log | grep SKW not testet from my side. good success
  2. @JohnTaylor Hi, take a lock at https://github.com/joilg/ea6x21-dkms.git
  3. it seems that the chip is not correct powered. sdio_pwrseq reset-gpios is on my board on pin PA_6 = <&gpio1 6 1>; but is the same in dts1.7. android Software do sometimes not comply the dts. Hardware v1.7 could also have a kind of powermanagement or wake on wlan implemented. Do you have a USB-A to USB-A cable? It is posible to get on the commandline on Android and inspect the log with adb Software. https://developers.google.com/chromeos/app-development/develop/adb-over-wifi-and-ethernet?hl=de . Maybe it is posible to get into adb over LAN or Wifi. You have to activate the develloper extensions in you android settings.
  4. @CD38 Hi, Unfortunately, the x88pro13 is manufactured by various companies, often featuring different Wi-Fi chips and modified board layouts. I own an older board with an LGX8800 Wi-Fi chip, and have access to a V1.5 board equipped with an EA6521Q chip. Since your image also shows an EA6521Q chip, the driver on https://github.com/joilg/ea6x21-dkms.git should be fine, it is also included in my x88pro image . The PCB layout in the WiFi section differs significantly from that of version 1.5. I assume that the connections for the WiFi control GPIOs have been changed. Due to the modified board layout, it may be necessary to change the GPIO assignments in the dts. I cannot find any specifically assigned GPIOs for the Seekwave driver in your DTS file. They are likely hardcoded into the Android driver. First, check whether the chip is responsive. root@x88pro:~# dmesg | grep SDIO [ 1.726067] mmc2: new UHS-I speed SDR104 SDIO card at address 8800 address 8800 is the Chip ID of the EA6521Q. this is independent of the wifi driver, and controled from sdio_pwrseq , gpio1 6, which is the same in 1.7 dts. If you have access to the Android command line, for example, via ADB, the following commands could be helpful to inpect used Pins adb shell su gpioinfo cat /sys/kernel/debug/gpio cat /sys/kernel/debug/pinctrl/pinctrl-maps dmesg | grep skwyou can change the gpios numbers with dts overlays. Create a DTS overlay file rk3528-skw.dts: dts-v1/; /plugin/; &{/} { compatible = "rockchip,rk3528"; seekwcn_boot { gpio_host_wake = <&gpio1 18 1>; gpio_chip_wake = <&gpio1 17 1>; }; sdio_pwrseq { reset-gpios = <&gpio1 6 1>; };and apply it with: sudo armbian-add-overlay rk3528-skw.dts rebootPlay around with the GPIOs pins. <&gpio1 16 1> are used in some other rockchip boards. view dmesg | grep skw for anny changes on other gpios. please paste the debug Info to pastebin and show the link here with: armbianmonitor -u good luck with the testing johilg
  5. @serovan Thank you for contributing. The script now makes it possible to run the operating system from the integrated eMMC. You can download the latest OTA-Android update for the X88pro13 box at: https://boxput.notion.site/X88-Series-Fireware-6f707e5e9b06413aac2df3dc291e67aa Useing Binwalk detects and xtract several DTB files; one of them should be the correct one for version 1.7. Is it possible for you to open the device and take a photo of the version 1.7 board? Which Wi-Fi chip is installed? I might be able to modify the Wi-Fi driver.
  6. @ulumid Ram Initialstation ist done by U-Boot with a suitibal rkbin binary located in the first sectors of mmc. This ist spezific for your Board. connect PC to serial debug console and Test If Android Boot Starts and switchover to mmc if it is pluged.
  7. Use Armbian Imager to create SDcard with curent Release. Connect HDMI Monitor and USB Keyboard. Put Sdcard into sdcard Slot and Power the Box. Follow instruction on Monitor
  8. In case you're interested I’ve uploaded my experiments with the current and edge kernels for my board (X88pro13, RK3528) to GitHub x88pro. LAN and USB are working; HDMI is not. Wifi only in current with aic8800 chip. Device Tree for my Board : userpatches/kernel/archive/rockchip64-.../dt/x88pro.dts might interest you.
  9. @8lall0 Thank you very much for helpfull comittment. I put the changes into the Repro. New Release 0.7
  10. new Version avaliable https://github.com/joilg/x88pro/releases/tag/0.6 New: Support now Hardware Version 1.4+ (EA6521 WIFI Chip) for WIFI and Bluetooth Display driver for HT1628 IR Remote USB 3.0 SuperSpeed (5Gbps) Ubuntu resolute 26.04 target OS please Test it now.
  11. Please don't test it yet. I have a problem with my development environment. I will upload a new version once I've resolved it.
  12. I have posted a new release on GitHub. Improved version. https://github.com/joilg/x88pro New: Support for Seekwave EA6521 Wifi Chip on Hardware Version 1.4 Frontdisplay shows now Systen Clock. USB3 support now SuperSpeed (5Gbps) IR Remote control implenented Target OS Ubuntu resolute 26.01 LAN is limited to 100mbps. (major advantage is the low quiescent current in standby mode. An external PHY with 1Gbps consumes a significant amount of power in Wake-on-LAN mod) Feedback welcome.
  13. apply this patch for a working wifi: diff --git a/extensions/radxa-aic8800.sh b/extensions/radxa-aic8800.sh index e3e99eaa8..7ab721353 100644 --- a/extensions/radxa-aic8800.sh +++ b/extensions/radxa-aic8800.sh @@ -10,7 +10,7 @@ function extension_finish_config__install_kernel_headers_for_aic8800_dkms() { function post_install_kernel_debs__install_aic8800_dkms_package() { - if linux-version compare "${KERNEL_MAJOR_MINOR}" ge 6.20; then + if linux-version compare "${KERNEL_MAJOR_MINOR}" ge 7.1; then display_alert "Kernel version is too recent" "skipping aic8800 dkms for kernel v${KERNEL_MAJOR_MINOR}" "warn" return 0 fi
  14. @shexplorer here are the first 10MB of the internal emmc. Extracted with dd if=/dev/mmcblk1 count=10 bs=1M | gzip > x88pro13_first_10MB_of_mmcblk.gz. please unzip first. see also the solutuion of this page: x88pro13_first_10MB_of_mmcblk1.gz
  15. The holes are visible in the 4. Image of fedes_gl's first message. The holes are right to the display. The pins are connected to the AIP1628. This images are from the first layout version. I now have a second Board with V1.4 marked in the Layout. The holes are no longer present in this version. It has also has a different Wi-Fi chip, therefore Wi-Fi doesn't work in my current Armbian release with this v 1.4. box.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.