View Chinese description | 查看中文说明
How to use GitHub Actions cloud to compile OpenWrt, and many of the content in this documentation, from P3TERX, Flippy and many other technology innovators and resource sharers. Because of the dedication of everyone, let us use OpenWrt in TV Boxes So Easy.
GitHub Actions is a service launched by Microsoft. It provides a virtual server environment with very good performance configuration. Based on it, projects can be built, tested, packaged, and deployed. The public repository can be used for free without time limit, and the single compilation time is up to 6 hours, which is enough for compiling OpenWrt (we can usually complete a compilation in about 3 hours). Sharing is only for the exchange of experience. Please understand the deficiencies. Please do not initiate various bad attacks on the Internet, and do not maliciously use it.
- How to make and use OpenWrt
- Tutorial directory
- 1. Register your own GitHub account
- 2. Set the privacy variable GitHub_TOKEN
- 3. Fork repository and set GH_TOKEN
- 4. Personalized OpenWrt firmware customization file description
- 5. Compile the firmware
- 6. Save the firmware
- 7. Download the firmware
- 8. Install the firmware
- 9. Update firmware
- 10. Personalized firmware customization update tutorial
- 10.1 Know the complete .config file
- 10.2 Know the workflow file
- 10.3 Custom banner information
- 10.4 Custom feeds configuration file
- 10.5 Custom software default configuration information
- 10.6 Opkg Package Manager
- 10.7 Manage packages using web interface
- 10.8 How to restore the original Android TV system
- 10.9 If you can’t startup after using the Mainline u-boot
- 10.10 Set the box to boot from USB/TF/SD
- 10.11 Required options for OpenWrt
Register your own account, so that you can continue to customize the firmware. Click the Sign up button in the upper right corner of the github.com website and follow the prompts to register your account.
Set the GitHub privacy variable GitHub_TOKEN. After the firmware is compiled, we need to upload the firmware to GitHub Releases. We set this variable according to the official requirements of GitHub. The method is as follows:
Personal center: Settings > Developer settings > Personal access tokens > Generate new token ( Name: GitHub_TOKEN, Select: public_repo ). Other options can be selected according to your needs. Submit and save, copy the Encrypted KEY Value generated by the system, and save it to your computer's notepad first. This value will be used in the next step. The icons are as follows:
Now you can Fork the repository, open the repository https://github.com/ophub/amlogic-s9xxx-openwrt, click the Fork button on the upper right, Will copy a copy of the repository code to your account, wait a few seconds, and prompt the Fork to complete Later, go to your account to access amlogic-s9xxx-openwrt in your repository. In the upper right corner of Settings > Secrets > Actions > New repostiory secret (Name: GH_TOKEN, Value: Fill in the value of GitHub_TOKEN just now), save it. And select Read and write permissions under Actions > General > Workflow permissions in the left nav and save. The icons are as follows:
After the previous 3 steps of preparation, let's start personalized firmware customization now. Have some files in the config-openwrt/lede-master directory. The 3 files for customizing OpenWrt firmware. In this chapter, we only make the simplest instructions, so that you can experience the happiness of personalized customization with your hands. I put more complex customization operations in Section 10, which requires you to have a little foundation.
The .config file is the core file for personalized customization of the OpenWrt software package. It contains all the configuration information. Each line of code in the file represents a personalized configuration option. Although there are many projects, management is very simple. Let's get started.
in # National language packs, luci-i18n-base: Take France as an example, if you enable French language support, just put
# CONFIG_PACKAGE_luci-i18n-base-fr is not setchange into
CONFIG_PACKAGE_luci-i18n-base-fr=yAll the personalized customization in the .config file can be done in this way. For items you don't need, fill in # at the beginning of the line, and change =y to is not set at the end of the line. For the items you need, remove the # at the beginning of the line and change is not set to =y at the end
in #LuCI-app: The practice of enabling and deleting the default software package is the same as above. This time we delete the luci-app-zerotier plug-in in the default software package, just put
CONFIG_PACKAGE_luci-app-zerotier=ychange into
# CONFIG_PACKAGE_luci-app-zerotier is not setI think you already know how to personalize the configuration. Each line of the .config file represents a configuration item. You can use this method to enable or delete the default configuration in the firmware. The complete content of this file has several thousand lines, I provide This is only a simplified version. How to obtain a complete configuration file for more complex and personalized customization is introduced in Section 10.
The scripts diy-part1.sh and diy-part2.sh are executed before and after the update and installation of feeds respectively. When we introduce the OpenWrt source code library for personalized firmware compilation, sometimes we want to rewrite part of the code in the source code library, or add Some third-party software packages, delete or replace some software packages in the source code library, such as modifying the default IP, host name, theme, adding/deleting software packages, etc., these modification instructions to the source code library can be written to these two Script. Let's take the OpenWrt source code library provided by coolsnowwolf as the compilation object, to give a few examples.
Our following operations are based on this source code library: https://github.com/coolsnowwolf/lede
The first step is to add the following code to diy-part2.sh:
git clone https://github.com/jerrykuku/luci-app-ttnode.git package/lean/luci-app-ttnodeThe second step is to add the activation code of this third-party software package to the .config file
CONFIG_PACKAGE_luci-app-ttnode=yThis completes the integration of third-party software packages and expands the software packages that are not in the current source code repository.
Replace the existing software package with the same name in the current source code library with a third-party software package. The first step is to add the following code to diy-part2.sh:
First delete the original software package in the source code library, and Introduce a third-party package of the same name.
rm -rf package/lean/luci-theme-argon
git clone https://github.com/jerrykuku/luci-theme-argon.git package/lean/luci-theme-argonThe second step is to add third-party software packages to the .config file.
CONFIG_PACKAGE_luci-theme-argon=yThis realizes the use of a third-party software package to replace the existing software package with the same name in the current source code library.
To achieve certain requirements by modifying the code in the source code library. We have added luci-app-cpufreq support for aarch64 so that it can be used in our firmware (some modifications need to be cautious, you must know what you are doing).
Source file address: luci-app-cpufreq/Makefile
sed -i 's/LUCI_DEPENDS.*/LUCI_DEPENDS:=\@\(arm\|\|aarch64\)/g' package/lean/luci-app-cpufreq/MakefileThis realizes the modification of the source code.
Through diy-part1.sh and diy-part2.sh two scripts, we add operation commands to make more powerful functions.
The official website of OpenWrt provides the prepared openwrt-imagebuilder-*-armvirt-64.Linux-x86_64.tar.xz file (download address: https://downloads.openwrt.org/releases), you can use the official Image Builder to add packages and plug-ins to this file, usually Create an openwrt-rootfs.tar.gz file in just a few minutes. For the production method, please refer to the official document: Using the Image Builder
This repository provides a one-click production service. You only need to pass the branch parameters into the imagebuilder script to complete the production.
-
Localized make command: You can run the
sudo ./config-openwrt/openwrt-imagebuilder/imagebuilder.sh 21.02.3command in the~/amlogic-s9xxx-openwrtroot directory to generate it. The parameter21.02.3is the version number ofreleasescurrently available for download. The generated files are in theopenwrt/bin/targets/armvirt/64directory. -
Use github.com's
Actionsto make: Build OpenWrt with Image Builder
The firmware compilation process is controlled in the .github/workflows/build-openwrt-with-lede.yml file. There are other yml files in the workflows directory to achieve other different functions. There are many ways to compile firmware, you can set timed compilation, manual compilation, or set some specific events to trigger compilation. Let's start with simple operations.
In the navigation bar of your repository, click the Actions button, and then click Build OpenWrt > Run workflow > Run workflow to start the compilation, wait about 3 hours, and complete the compilation after all the processes are over. The icons are as follows:
In the .github/workflows/build-openwrt-with-lede.yml file, use cron to set the timing compilation. The 5 different positions represent min (0 - 59) / hour (0 - 23) / day of month (1 - 31) / month (1 - 12) / day of week (0 - 6)(Sunday - Saturday). Set the time by modifying the values of different positions. The system uses UTC standard time by default, please convert it according to the time zone of your country.
schedule:
- cron: '0 17 * * *'The settings saved by the firmware are also controlled in the .github/workflows/build-openwrt-with-lede.yml file. We will automatically upload the compiled firmware to the Actions and Releases officially provided by GitHub through scripts, or upload it to a third party (such as WeTransfer).
Now the longest storage period of Actions in GitHub is 90 days, Releases is permanent, and third parties such as WeTransfer are 7 days. First of all, we thank these service providers for their free support, but we also ask you to use it sparingly. We advocate the reasonable use of free services.
- name: Upload artifact to Actions
uses: kittaakos/upload-artifact-as-is@master
if: ${{ steps.build.outputs.status }} == 'success' && env.UPLOAD_FIRMWARE == 'true' && !cancelled()
with:
path: ${{ env.FILEPATH }}/- name: Upload OpenWrt Firmware to Release
uses: ncipollo/release-action@main
if: ${{ env.PACKAGED_STATUS }} == 'success' && !cancelled()
with:
tag: openwrt_amlogic_s9xxx_lede_${{ env.PACKAGED_OUTPUTDATE }}
artifacts: ${{ env.PACKAGED_OUTPUTPATH }}/*
allowUpdates: true
token: ${{ secrets.GH_TOKEN }}
body: |
This is OpenWrt firmware for Amlogic s9xxx tv box
* Firmware information
Default IP: 192.168.1.1
Default username: root
Default password: password
Default WIFI name: OpenWrt
Default WIFI password: none
Install to EMMC: Login to OpenWrt → System → Amlogic Service → Install OpenWrt- name: Upload OpenWrt Firmware to WeTransfer
if: ${{ steps.build.outputs.status }} == 'success' && env.UPLOAD_WETRANSFER == 'true' && !cancelled()
run: |
curl -fsSL git.io/file-transfer | sh
./transfer wet -s -p 16 --no-progress ${{ env.FILEPATH }}/{openwrt_s9xxx_*,openwrt_n1_*} 2>&1 | tee wetransfer.log
echo "WET_URL=$(cat wetransfer.log | grep https | cut -f3 -d" ")" >> $GITHUB_ENVDownload our compiled openwrt firmware.
Click the Actions button in the repository navigation bar. In the All workflows list, click the compiled firmware list. In the firmware list inside, select the firmware corresponding to the model of your Amlogic s9xxx TV Boxes. The icons are as follows:
Enter from the GitHub Releases section at the bottom right corner of the repository homepage, and select the firmware corresponding to the model of your Amlogic s9xxx TV Boxes. The icons are as follows:
In the .github/workflows/build-openwrt-with-lede.yml file, upload to the third party is closed by default. If you need, change false to true, and upload to the third party when the compilation is completed next time. The third-party URL can be seen in the log of the firmware compilation process, and can also be output to the compilation information.
UPLOAD_COWTRANSFER: false
UPLOAD_WETRANSFER: falseThe support for uploading to a third party comes from Mikubill/transfer. If you need it, you can add more third-party support according to his instructions (control your creativity and don't waste too many free resources). The icons are as follows:
svn co https://github.com/ophub/luci-app-amlogic/trunk/luci-app-amlogic package/luci-app-amlogic- Execute make
menuconfigand selectluci-app-amlogicunderLuCI ---> 3. Applications ---> <*> luci-app-amlogic
For more instructions on the plug-in, see：https://github.com/ophub/luci-app-amlogic
Choose the corresponding firmware according to your box. Then write the IMG file to the USB hard disk through software such as Rufus or balenaEtcher. Insert the USB hard disk into the box.
Log in to the default IP: 192.168.1.1 → Login in to openwrt → system menu → Amlogic Service → Install OpenWrt
Log in to the default IP: 192.168.1.1 → Login in to openwrt → system menu → TTYD terminal → input command:
openwrt-install-amlogicThe same type of TV Boxes, the firmware is common, such as openwrt_s905x3_v*.img firmware can be used for x96max plus, hk1, h96 and other s905x3 type TV Boxes. When the installation script writes OpenWrt to EMMC, you will be prompted to choose your own box, please choose the correct one according to the prompt.
In addition to the default 13 models of TV Boxes are automatically installed, when you select 0 for optional .dtb file installation, you need to fill in the specific .dtb file name, you can check the exact file name from here and fill in it, see amlogic-dtb
Log in to your OpenWrt system, under the System menu, select the Amlogic Service, select the Update OpenWrt to update. (You can update from a higher version such as 5.15.50 to a lower version such as 5.10.125, or from a lower version such as 5.10.125 to a higher version such as 5.15.50. The kernel version number does not affect the update, and you can freely update/downgrade.)
Log in to your OpenWrt system → under the System menu → Amlogic Service → upload openwrt*.img.gz (Support suffix: *.img.xz, *.img.gz, *.7z, *.zip) to /mnt/mmcblk*p4/, enter the system menu → TTYD terminal → input command:
openwrt-update-amlogic💡Tips: You can also put the update file in the /mnt/mmcblk*p4/ directory, the openwrt-update-amlogic script will automatically find the update file from the /mnt/mmcblk*p4/ directories.
If there is only one update file in the /mnt/mmcblk*p4/ directory, you can just enter the openwrt-update-amlogic command without specifying a specific update file. The openwrt-update-amlogic script will vaguely look for update file from this directory and try to update. If there are multiple update file in the /mnt/mmcblk*p4/ directory, please use the openwrt-update-amlogic openwrt_s905x3_v5.10.125_2021.03.17.0412.img.gz command to specify the update file.
- The
openwrt-update-amlogicupdate file search order
| Directory | /mnt/mmcblk*p4/ 1-6 |
|---|---|
| Oeder | specified_update_file → *.img → *.img.xz → *.img.gz → *.7z → *.zip → |
- Log in to the default IP: 192.168.1.1 →
Login in to openwrt→system menu→Amlogic Service→ Upload kernel package (There are 3 files：boot-xxx.tar.gz, dtb-xxx.tar.gz, modules-xxx.tar.gz) to/mnt/mmcblk*p4/, enter thesystem menu→TTYD terminal→ input the Kernel replacement command:
openwrt-kernel💡Tips: You can also put the kernel files in the /mnt/mmcblk*p4/ directory, the openwrt-kernel script will automatically find the kernel file from the /mnt/mmcblk*p4/ directories.
Replacing the OpenWrt kernel is only a kernel replacement, and the various personalized configurations of the firmware remain unchanged. It is the easiest way to update. Support replacement of kernel high/low version.
If you see this step in the tutorial, I believe you already know how to play happily. If you don’t continue to read what is said later, I believe you will not be at ease. But, but ah, if you continue to explore in depth, you will start an extraordinary journey of tossing. You will encounter a lot of problems. This requires you to be prepared for continuous exploration, and you must be good at using search engines to solve problems. The time can go to various OpenWrt communities to learn.
Use the official source code library of OpenWrt or the source code library of other branches to perform a localized compilation. For example, select the source code library of coolsnowwolf/lede, and install the Ubuntu system locally and deploy the environment according to its compilation instructions. And complete a local compilation. In the local compilation configuration interface, you can also see a lot of rich instructions, which will strengthen your understanding of the OpenWrt compilation process.
After you complete the OpenWrt personalized configuration locally, save and exit the configuration interface. You can find the .config file in the root directory of the local OpenWrt source code library. You can upload this file directly to your repository on github.com, Replace the config-openwrt/lede-master/config file.
The official GitHub gave a detailed explanation. Regarding the use of GitHub Actions, you can start to get to know it from here: Quickstart for GitHub Actions
Let’s make a few brief introductions based on the files being used in the repository: build-openwrt-with-lede.yml
#On Line 63: Source code library address
REPO_URL: https://github.com/coolsnowwolf/lede
#On Line 64: Branch name
REPO_BRANCH: masterYou can modify it to other, such as official:
REPO_URL: https://github.com/openwrt/openwrt
REPO_BRANCH: openwrt-21.02Near line 139, find Build OpenWrt firmware, Code snippet like this:
- name: Build OpenWrt firmware
if: ${{ steps.compile.outputs.status }} == 'success' && !cancelled()
uses: ophub/amlogic-s9xxx-openwrt@main
with:
openwrt_path: openwrt/bin/targets/*/*/*rootfs.tar.gz
openwrt_board: ${{ inputs.openwrt_board }}
openwrt_kernel: ${{ inputs.openwrt_kernel }}
auto_kernel: ${{ inputs.auto_kernel }}
openwrt_size: ${{ inputs.openwrt_size }}
gh_token: ${{ secrets.GH_TOKEN }}Refer to the related parameter description of the packaging command. The above setting options can be set by writing fixed values, or they can be selected through the Actions panel:
The default /etc/banner information is as follows, you can use the banner generator Customize your own personalized banner information(The style below is slant), just overwrite the file with the same name.
____ _ __ __ ____
/ __ \____ ___ ____| | / /____/ /_ / __ )____ _ __
/ / / / __ \/ _ \/ __ \ | /| / / ___/ __/_____/ __ / __ \| |/_/
/ /_/ / /_/ / __/ / / / |/ |/ / / / /_/_____/ /_/ / /_/ /> <
\____/ .___/\___/_/ /_/|__/|__/_/ \__/ /_____/\____/_/|_|
/_/ H E L L O - W O R L D W I R E L E S S - F R E E D O M
───────────────────────────────────────────────────────────────────────When you look at the feeds.conf.default file in the source code repository, do you find that there are a lot of package libraries introduced here? You understand that right, we can find the source code library officially provided by OpenWrt on GitHub, as well as the branches of OpenWrt shared by many people. If you know them, you can add them from here. For example, feeds.conf.default in the coolsnowwolf source code library.
When we use OpenWrt, we have already configured many software. Most of the configuration information of these software is stored in your OpenWrt's /etc/config/ and other related directories. Copy the storage files of these configuration information to In the files folder under the root directory of the repository in GitHub, please keep the directory structure and files the same. During OpenWrt compilation, the storage files of these configuration information will be compiled into your firmware. The specific method is in the .github/workflows/build-openwrt-with-lede.yml file. Let's take a look at this code together:
- name: Load custom configuration
run: |
[[ -d "files" ]] && mv -f files openwrt/files
[[ -e "${CONFIG_FILE}" ]] && cp -f ${CONFIG_FILE} openwrt/.config
chmod +x ${DIY_P2_SH}
cd openwrt
${GITHUB_WORKSPACE}/${DIY_P2_SH}Please do not copy the configuration information files that involve privacy. If your repository is public, then the files you put in the files directory are also public. Do not disclose the secrets. Some passwords and other information can be used using the private key settings you just learned in Quickstart for GitHub Actions. You must understand what you are doing.
Like most Linux distributions (or mobile device operating systems like say Android or iOS), the functionality of the system can be upgraded rather significantly by downloading and installing pre-made packages from package repositories (local or on the Internet).
The opkg utility is the lightweight package manager used for this job. which is designed to add software to stock firmware of embedded devices. Opkg is a full package manager for the root file system, including kernel modules and drivers.
The package manager opkg attempts to resolve dependencies with packages in the repositories - if this fails, it will report an error and abort the installation of that package.
Missing dependencies with third-party packages are probably available from the source of the package.
To ignore dependency errors, pass the --force-depends flag.
-
If you are using a snapshot / trunk / bleeding edge version, installing packages may fail if the package in the repository is for a newer kernel version than the kernel version you have. In this case, you will get the error message “Cannot satisfy the following dependencies for…”. For such usage of OpenWrt firmware,
it's warmly recommended to use the Image Builder to make a flashable image containing all packages you need. -
Non-openwrt.org official plug-ins, such as
luci-app-uugamebooster,luci-app-xlnetacc, etc., need to be personalized during firmware compilation. These packages cannot be directly installed from the mirror server using opkg, But you can manuallyupload to openwrt and use opkg to install. -
When on trunk/snapshot, kernel and kmod packages are flagged as hold, the
opkg upgradecommand won't attempt to update them.
Common commands:
opkg update #Update list of available packages
opkg upgrade <pkgs> #Upgrade packages
opkg install <pkgs> #Install package(s)
opkg install --force-reinstall <pkgs> #Force reinstall package(s)
opkg configure <pkgs> #Configure unpacked package(s)
opkg remove <pkgs | regexp> #Remove package(s)
opkg list #List available packages
opkg list-installed #List installed packages
opkg list-upgradable #List installed and upgradable packages
opkg list | grep <pkgs> #Find similar packages names
For more instructions please see: opkg
After you have flashed the OpenWrt firmware to your device, you can install additional software packages via WebUI.
- Navigate to LuCI → System → Software.
- Click Update lists button to fetch a list of available packages.
- Fill in Filter field and click Find package button to search for a specific package.
- Switch to Available packages tab to show and install available packages.
- Switch to Installed packages tab to show and remove installed packages.
Search and install luci-app-* packages if you want to configure services using LuCI.
For more instructions please see: packages
Usually use openwrt-ddbr backup to restore, or use Amlogic usb burning tool to restore the original Android TV system.
It is recommended that you make a backup of the original Android TV system that comes with the current box before installing the OpenWrt system in a new box, so that you can use it when you need to restore the system. Please boot the OpenWrt system from TF/SD/USB, enter the openwrt-ddbr command, and then enter b according to the prompts to backup the system. The backup file is stored in the path /ddbr/BACKUP-arm-64-emmc. img.gz , please download and save. When you need to restore the Android TV system, upload the previously backed up files to the same path of the TF/SD/USB device, enter the openwrt-ddbr command, and then enter r according to the prompt to restore the system.
-
Under normal circumstances, re-insert the USB hard disk and install it again.
-
If you cannot start the OpenWrt system from the USB hard disk again, connect the Amlogic s9xxx TV Boxes to the computer monitor. If the screen is completely black and there is nothing, you need to restore the Amlogic s9xxx TV Boxes to factory settings first, and then reinstall it. First download the amlogic_usb_burning_tool system recovery tool and install it. Prepare a USB dual male data cable, Prepare a paper clip.
-
Take x96max+ as an example. Find the two short-circuit points on the motherboard, Download the Android TV firmware. The Android TV system firmware of other common devices and the corresponding short circuit diagrams can also be downloaded and viewed here.
Operation method:
1. Open the USB Burning Tool:
[ File → Import image ]: X96Max_Plus2_20191213-1457_ATV9_davietPDA_v1.5.img
[ Check ]：Erase flash
[ Check ]：Erase bootloader
Click the [ Start ] button
2. Use a [ paper clip ] to connect the [ two shorting points ] on the main board of the box,
and use a [ USB dual male data cable ] to connect the [ box ] to the [ computer ] at the same time.
3. Loosen the short contact after seeing the [ progress bar moving ].
4. After the [ progress bar is 100% ], the restoration of the original Android TV system is completed.
Click [ stop ], unplug the [ USB male-to-male data cable ] and [ power ].
5. If the progress bar is interrupted, repeat the above steps until it succeeds.
If the progress bar does not respond after the short-circuit, plug in the [ power ] supply after the short-circuit.
Generally, there is no need to plug in the power supply.
When the factory reset is completed, the box has been restored to the Android TV system, and other operations to install the OpenWrt system are the same as the requirements when you installed the system for the first time before, just do it again.
- A very small number of devices may fail to boot after choosing to write to the main line
u-boot. The fault phenomenon is usually the=>prompt of u-boot automatically. The reason is that TTL lacks a pull-up resistor or pull-down resistor and is easily interfered by surrounding electromagnetic signals. The solution is to solder a 5K-10K resistor (pull-down) between TTL RX and GND, or solder a resistor between RX and 3.3V. A resistance of 5K-10K (pull-up).
If you choose to use the mainline u-boot during installation and it fails to start, please connect the Amlogic S905x3 box to the monitor. If the screen shows the following prompt:
Net: eth0: ethernet0ff3f0000
Hit any key to stop autoboot: 0
=>
You need to install a resistor on the TTL: X96 Max Plus's V4.0 Motherboard
####################################################### #####################################################
# # # #
# Resistor (pull-down): between TTL's RX and GND # # Resistor (pull-up): between TTL's 3.3V and RX #
# # # #
# 3.3V RX TX GND # OR # 3.3V RX TX GND #
# ┖————█████████————┚ # # ┖————█████████————┚ #
# Resistor (5~10K) # # Resistor (5~10K) #
# # # #
####################################################### #####################################################
- Write the firmware to USB/TF/SD, insert it into the box after writing.
- Open the developer mode: Settings → About this machine → Version number (for example: X96max plus...), click on the version number for 5 times in quick succession, See the prompt of
Enable Developer Modedisplayed by the system. - Turn on USB debugging: System → Advanced options → Developer options again (after entering, confirm that the status is on, and the
USB debuggingstatus in the list is also on). EnableADBdebugging. - Install ADB tools: Download adb and unzip it, copy the three files
adb.exe,AdbWinApi.dll, andAdbWinUsbApi.dllto the two filessystem32andsyswow64under the directory ofc://windows/Folder, then open thecmdcommand panel, useadb --versioncommand, if it is displayed, it is ready to use. - Enter the
cmdcommand mode. Enter theadb connect 192.168.1.137command (the ip is modified according to your box, and you can check it in the router device connected to the box), If the link is successful, it will displayconnected to 192.168.1.137:5555 - Enter the
adb shell reboot updatecommand, the box will restart and boot from the USB/TF/SD you inserted, access the firmware IP address from a browser, or SSH to enter the firmware. - Log in to the system: Connect the computer and the s9xxx box with a network interface → turn off the wireless wifi on the computer → enable the wired connection → manually set the computer ip to the same network segment ip as openwrt, ipaddr such as
192.168.1.2. The netmask is255.255.255.0, and others are not filled in. You can log in to the openwrt system from the browser, Enter OpwnWrt's IP Address:192.168.1.1, Account:root, Password:password, and then log in OpenWrt system.
This list is organized based on the development guide of unifreq. In order to ensure that scripts such as installation/update can run normally in OpenWrt, when using make menuconfig to configure, you need to add the following mandatory options:
Target System -> QEMU ARM Virtual Machine
Subtarget -> QEMU ARMv8 Virtual Machine (cortex-a53)
Target Profile -> Default
Target Images -> tar.gz
Kernel modules -> Wireless Drivers -> kmod-brcmfmac(SDIO)
-> kmod-brcmutil
-> kmod-cfg80211
-> kmod-mac80211
Languages -> Perl
-> perl-http-date
-> perlbase-file
-> perlbase-getopt
-> perlbase-time
-> perlbase-unicode
-> perlbase-utf8
Network -> WirelessAPD -> hostapd-common
-> wpa-cli
-> wpad-basic
-> iw
Utilities -> Compression -> bsdtar、pigz
-> Disc -> blkid、fdisk、lsblk、parted
-> Filesystem -> attr、btrfs-progs(Build with zstd support)、chattr、dosfstools、
e2fsprogs、f2fs-tools、f2fsck、lsattr、mkf2fs、xfs-fsck、xfs-mkfs
-> Shells -> bash
-> acpid、coremark、coreutils(-> coreutils-base64、coreutils-nohup)、gawk、getopt、
losetup、pv、tar、uuidgen