165
edits
Changes
RUTOS Software Development Kit (SDK) Instruction (view source)
Revision as of 09:56, 16 January 2024
, 16 January→Changing Device brand
A <b>software development kit</b> (<b>SDK</b>) is a set of software development tools that provides the possibility to create applications for a certain software package, software framework, computer system or similar development platform.
A <b>Software Development Kit</b> (<b>SDK</b>) is a set of software development tools that provides the possibility to create applications for a certain software package, software framework, computer system or similar development platform.
<b>Note:</b> The information in this page is in accordance to using SDK version <b>R_00.07.05</b>. The included Readme file in SDK archive file contains information for each separate SDK version and might differ from the older version or information provided in this wiki page. Please always follow the instruction provided in Readme file.
<b>Note:</b> The information in this page is in accordance to using SDK version <b>R_00.07.06</b>. The included Readme file in SDK archive file contains information for each separate SDK version and might differ from the older version or information provided in this wiki page. Please always follow the instruction provided in Readme file.
__TOC__
__TOC__
<li>Teltonika Router running RutOS</li>
<li>Teltonika Router running RutOS</li>
<li>[https://ubuntu.com/download/desktop/ Ubuntu 22.04.3 LTS OS]</li>
<li>[https://ubuntu.com/download/desktop/ Ubuntu 22.04.3 LTS OS]</li>
<li>SDK version <b>R_00.07.05.x</b></li>
<li>SDK version <b>R_00.07.06.x</b></li>
</ul>
</ul>
The examples apply to various RUTOS routers, SDK versions and operating systems. The key concepts should apply regardless of the device, version, or system. The availability of SDK Firmware branding begins from version 7.05, although some of these modifications may be accessible on earlier firmware versions.
The examples apply to various RUTOS routers, SDK versions and operating systems. The key concepts should apply regardless of the device, version, or system. The availability of SDK Firmware branding begins from version 7.06, although some of these modifications may be accessible on earlier firmware versions.
Most examples provided in this page are independent from each other. But it is highly recommended to acquaint yourself with the basics by reading the "[[#Prerequisites|Prerequisites]]" and "[[#Compiling_a_standard_firmware|Compiling a standard firmware]]" sections first as they contain information that will be necessary in order to understand some aspects of the other examples.
Most examples provided in this page are independent from each other. But it is highly recommended to acquaint yourself with the basics by reading the "[[#Prerequisites|Prerequisites]]" and "[[#Compiling_a_standard_firmware|Compiling a standard firmware]]" sections first as they contain information that will be necessary in order to understand some aspects of the other examples.
1. You can download latest '''Ubuntu''' version can be found here: [https://ubuntu.com/download/desktop Ubuntu]
1. You can download latest '''Ubuntu''' version can be found here: [https://ubuntu.com/download/desktop Ubuntu]
[[File:Ubunto.png|border|class=tlt-border]]
[[File:Ubunto.png|1100px|border|class=tlt-border]]
2. After initiating VMware, click '''Create a New Virtual Machine'''
2. After initiating VMware, click '''Create a New Virtual Machine'''
[[File:Ubuntu2.jpg|border|class=tlt-border]]
[[File:Ubuntu2.jpg|1100px|border|class=tlt-border]]
3. Choose '''Typical''' -> choose the downloaded '''Ubuntu .iso file'''
3. Choose '''Typical''' -> choose the downloaded '''Ubuntu .iso file'''. Then click '''Next'''.
[[File:Ubuntu3.jpg|border|class=tlt-border]]
[[File:Ubuntu3.jpg|border|class=tlt-border]]
4. Input Name, username, and password. Then input the Virtual Machine Name and the save path. Then click '''Next'''.
4. Input Name, username, and password. Then input the Virtual Machine Name and the save path.
'''Note:''' allocate at least 30-50GB GB for disk size and click Store virtual disk as a single file.
'''Note:''' allocate at least 30-50GB GB for disk size and click Store virtual disk as a single file.
[[File:Ubuntu4.jpg|border|class=tlt-border]]
[[File:Ubuntu4.jpg|border|class=tlt-border]]
5. Select '''Customize Hardware'''. Allow for 4GB or more of memory and 2 or more processors, depending on your machine. Finally, click '''Finish'''.
5. Select '''Customize Hardware'''. Allow for 4GB or more of memory and 2 or more processors *more is preferable* depending on your machine.
[[File:Ubuntu5.jpg|border|class=tlt-border]]
[[File:Ubuntu5.jpg|border|class=tlt-border]]
Ubuntu will initialize. Choose your language. The example will be in English.
Ubuntu will initialize. Choose your language. The example will be in English.
8. Once Ubuntu is now running. Open a browser and download the SDK file from Teltonika Networks wiki. You can find it out here: [https://wiki.teltonika-networks.com/view/Software_Development_Kit Software Development Kit]
8. Once Ubuntu is now running. Open a browser and download the SDK file from Teltonika Networks wiki. You can find it out here: [https://wiki.teltonika-networks.com/view/Software_Development_Kit Software Development Kit]
==Compiling a standard firmware==
==Compiling a standard firmware==
sudo apt install nodejs
sudo apt install nodejs
sudo apt install npm *v12.22.9*
sudo apt install npm
sudo apt install build-essential ccache ecj fastjar file flex g++ gawk \ gettext git java-propose-classpath java-wrappers jq libelf-dev \ libffi-dev libncurses5-dev libncursesw5-dev libssl-dev libtool \ python python2.7-dev python3 python3-dev python3-distutils \ python3-setuptools rsync subversion swig time u-boot-tools \ unzip wget xsltproc zlib1g-dev bison
sudo apt install binutils binutils-gold bison build-essential bzip2 \ ca-certificates curl default-jdk device-tree-compiler devscripts \ ecj file flex fuse g++ gawk gcc gcc-multilib gengetopt gettext \ git gnupg groff help2man java-wrappers java-propose-classpath jq \ libc6-dev libffi-dev libncurses5-dev libpcre3-dev libsqlite3-dev \ libssl-dev libxml-parser-perl lz4 make ocaml ocaml-findlib \ ocaml-nox patch pkg-config python3 python3-dev python3-distutils \ python3-yaml rsync ruby sharutils subversion swig u-boot-tools \ unzip uuid-dev vim-common wget zip zlib1g-dev
'''Note''': It is suggested to install '''NodeJS v12 (or newer)''' and '''NPM v6.9 (or newer)'''. You can check NodeJS and NPM version by running these commands respectively:
node -v
npm -v
Create a new folder (for this example I'll be using a directory called <i>RUTX_R</i> found at my <b>home</b> directory) and extract the SDK archive inside it.
Create a new folder (for this example I'll be using a directory called <i>RUTX_R</i> found at my <b>home</b> directory) and extract the SDK archive inside it.
[[File:SDK_EXTRACT.jpg|border|class=tlt-border]]
[[File:DL.png|border|class=tlt-border]]
You can achieve this with drag and drop or by executing this command via '''Terminal''':
You can achieve this with drag and drop or by executing this command via '''Terminal''':
cd ~/Downloads
cd ~/Downloads
Extract the '''tar.gz''' file:
Extract the '''tar.gz''' file:
tar -xzvf RUTX_R_GPL_00.07.05.X.tar.gz
tar -xzvf RUTX_R_GPL_00.07.06.X.tar.gz
This command will extract the contents of the RUTX_R_GPL_00.07.05.X.tar.gz file into the current directory, After running this command, you should find the extracted files in the same directory where you ran the command.
This command will extract the contents of the RUTX_R_GPL_00.07.06.X.tar.gz file into the current directory, After running this command, you should find the extracted files in the same directory where you ran the command.
<b>Note</b>: don't forget to replace the file name and path in accordance with your own circumstances
<b>Note</b>: don't forget to replace the file name and path in accordance with your own circumstances
If all is in order, the output should look something like this:
If all is in order, the output should look something like this:
[[File:Make_without_jobs_v1.gif]]
[[File:Make_SDK.gif|1100px|border|class=tlt-border]]
<b>Note</b>: the first time you compile a firmware file it may take up to <b>30 minutes</b> before it is complete. Don't close the Terminal window up until then. Once it is finished, you will find the firmware in the <i>./bin/targets/ipq40xx/generic</i> directory. It should contain a file openwrt-ipq40xx-qcom-ipq4018-rutx-squashfs-apps.bin, it can be used to upgrade your router's firmware via its web interface.
<b>Note</b>: the first time you compile a firmware file it may take up to <b>30 minutes</b> before it is complete. Don't close the Terminal window up until then. Once it is finished, you will find the firmware in the <i>./bin/targets/ipq40xx/generic</i> directory. It should contain a file openwrt-ipq40xx-qcom-ipq4018-rutx-squashfs-apps.bin, it can be used to upgrade your router's firmware via its web interface.
make -j<nproc_output>
make -j<nproc_output>
[[File:make_with_jobs_v1.gif]]
[[File:Make_nproc.gif|1100px|border|class=tlt-border]]
'''Troubleshooting tips:'''
'''Troubleshooting tips:'''
3. Try running `make distclean` if you believe that your SDK installation is corrupt. This will recompile the firmware from scratch.
3. Try running `make distclean` if you believe that your SDK installation is corrupt. This will recompile the firmware from scratch.
4. Allowing us to run command. “make -j<nproc_output> V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
4. Start compilation by running '''make -j<nproc_output> V=sc''' for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
==Changing Default Password==
==Changing Default Password==
To change the default device password, changes need to be made inside:
To change the default device password, changes need to be made inside:
"RUTX_R_GPL_00.07.05/package/base-files/files/lib/preinit/84_set_password"
"RUTX_R_GPL_00.07.06/package/base-files/files/lib/preinit/84_set_password"
Change "'''admin01'''" to your password on line '''[ -z "$passwd" ] && passwd="$(mkpasswd
Change "'''admin01'''" to your password on line '''[ -z "$passwd" ] && passwd="$(mkpasswd
admin01)"'''
admin01)"'''
Additionally, devices on newer batch are having unique passwords from MNF info. The new password should also be added under '''passwd''' in '''push_password''' list
[[File:Mkpswd.png|border|class=tlt-border]]
To disable the option to change the '''default password for the first time''', kindly follow the professional instructions outlined below.
To disable the option to change the '''default password for the first time''', kindly follow the professional instructions outlined below.
make clean
make clean
Following that, when compiling firmware using '''make''' command, specifying the number of processors to be used is possible, thus speeding it up. To determine the number of available processors, you can use '''nproc''' command. Then, pass this number to the '''-j''' option in '''make''' command.
make -j1 V=sc
The firmware can then be found in the directory listed below '''*Depends on the target*''':
The exact path to the firmware depends on the target. In this example, the firmware can be found in the following directory:
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.05.3_WEBUI
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.06.1_WEBUI
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
'''file name''': RUTX_R_GPL_00.07.06.X_WEBUI
==Changing Default IP Address==
==Changing Default IP Address==
make clean
make clean
Following that, when compiling firmware using '''make''' command, specifying the number of processors to be used is possible, thus speeding it up. To determine the number of available processors, you can use '''nproc''' command. Then, pass this number to the '''-j''' option in '''make''' command.
make -j1 V=sc
The firmware can then be found in the directory listed below '''*Depends on the target*''':
The exact path to the firmware depends on the target. In this example, the firmware can be found in the following directory:
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.05.3_WEBUI
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.06.1_WEBUI
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
'''file name''': RUTX_R_GPL_00.07.06.X_WEBUI
==Changing SSH Banner==
==Changing SSH Banner==
To modify the '''SSH banner''', you can make use of the file search tool in the extracted GPL. To access this, follow these steps from the root directory of your project, '''you can find the file from route below''':
To modify the '''SSH banner''', you can make use of the file search tool in the extracted GPL. To access this, follow these steps from the root directory of your project, '''you can find the file from route below''':
~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/base-files/files/etc
~/Downloads/RUTX_R_GPL_00.07.06/rutos-ipq40xx-rutx-gpl/package/base-files/files/etc
[[File:Image (18).png|border|class=tlt-border]]
[[File:Blogo.png|border|class=tlt-border]]
Make sure that the file that we want to edit is in the similar file path as above.
Make sure that the file that we want to edit is in the similar file path as above.
[[File:Image (16).png|border|class=tlt-border]]
[[File:Bannernew.png|border|class=tlt-border]]
The contents of the file should look similar to the image above. after making the desired changes to the banner, you can then save those modifications.
The contents of the file should look similar to the image above. after making the desired changes to the banner, you can then save those modifications.
Make sure that your are in the same directory which contains the banner.logo file.
Make sure that your are in the same directory which contains the banner.logo file.
[[File:Figlet.png|border|class=tlt-border]]
[[File:Figlet.png|1100px|border|class=tlt-border]]
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
make clean
make clean
Following that, when compiling firmware using '''make''' command, specifying the number of processors to be used is possible, thus speeding it up. To determine the number of available processors, you can use '''nproc''' command. Then, pass this number to the '''-j''' option in '''make''' command.
make -j1 V=sc
The firmware can then be found in the directory listed below '''*Depends on the target*''':
The exact path to the firmware depends on the target. In this example, the firmware can be found in the following directory:
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.05.3_WEBUI
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.06.1_WEBUI
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
'''file name''': RUTX_R_GPL_00.07.06.X_WEBUI
'''RESULTS:'''
'''RESULTS:'''
[[File:BANNERRESULTS.png|border|class=tlt-border]]
[[File:Sshnew.png|border|class=tlt-border]]
==Changing Firmware Version==
==Changing Firmware Version==
To modify the firmware version like Prefix, go to the directory where '''gpl_version''' file is located (''/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl''). Then run this command to edit file content.
To modify the firmware version like Prefix, go to the directory where '''gpl_version''' file is located (''/Downloads/RUTX_R_GPL_00.07.06.1/rutos-ipq40xx-rutx-gpl''). Then run this command to edit file content.
nano gpl_version
nano gpl_version
Replace the content to the desired firmware version. To save, type '''Ctrl + X'''. Then, click '''Y'''. The output should be similar to this:
Replace the content to the desired firmware version. To save, type '''Ctrl + X'''. Then, click '''Y'''.
[[File:FWV.png|border|class=tlt-border]]
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
./scripts/feeds update -a
[[File:FWV.png|thumb]]
make clean
Following that, when compiling firmware using '''make''' command, specifying the number of processors to be used is possible, thus speeding it up. To determine the number of available processors, you can use '''nproc''' command. Then, pass this number to the '''-j''' option in '''make''' command.
make -j1 V=sc
The exact path to the firmware depends on the target. In this example, the firmware can be found in the following directory:
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>Company_Ex_99.99.99_WEBUI
'''file name''': Company_Ex_99.99.99_WEBUI
'''RESULTS:'''
[[File:Version1.png|border|class=tlt-border]]
[[File:Version2.png|border|class=tlt-border]]
==Changing Company Links==
==Changing Company Links==
To modify the '''Company Links''', you can make use of the file search tool in the extracted GPL. To access this, follow these steps from the root directory of your project, '''you can find the file from route below:'''
To modify the '''Company Links''', you can make use of the file search tool in the extracted GPL. To access this, follow these steps from the root directory of your project, '''you can find the file from route below:'''
~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/brand
~/Downloads/RUTX_R_GPL_00.07.06.1/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/brand
[[File:COMP1.jpg|border|class=tlt-border]]
[[File:Brandjson.png|1100px|border|class=tlt-border]]
Make sure that the file that we want to edit is in the similar file path as above.
Make sure that the file that we want to edit is in the similar file path as above.
[[File:Image (17).png|border|class=tlt-border]]
[[File:Brandnew.png|border|class=tlt-border]]
The contents of the file should look similar to the image above. After making the desired changes to the banner, you can then save those modifications.
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
make clean
make clean
Following that, when compiling firmware using '''make''' command, specifying the number of processors to be used is possible, thus speeding it up. To determine the number of available processors, you can use '''nproc''' command. Then, pass this number to the '''-j''' option in '''make''' command.
make -j1 V=sc
The firmware can then be found in the directory listed below '''*Depends on the target*''':
The exact path to the firmware depends on the target. In this example, the firmware can be found in the following directory:
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.05.3_WEBUI
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.06.1_WEBUI
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
'''file name''': RUTX_R_GPL_00.07.06.X_WEBUI
'''RESULTS:'''
'''RESULTS:'''
[[File:RESULTSCOMPANY.png|border|class=tlt-border]]
[[File:Companylink.png|1100px|border|class=tlt-border]]
==Changing Device brand==
==Changing Device brand==
'''First File:'''
'''First File:'''
~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin
~/Downloads/RUTX_R_GPL_00.07.06/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist
[[File:BRANDTELT.png|border|class=tlt-border]]
[[File:BRANDTELT.png|1100px|border|class=tlt-border]]
'''Second File:'''
'''Second File:'''
~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/ tlt-icons
~/Downloads/RUTX_R_GPL_00.07.06/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/ tlt-icons
[[File:BRANDTELT2.png|border|class=tlt-border]]
[[File:BRANDTELT2.png|1100px|border|class=tlt-border]]
'''Note:''' If you have a brand in a different format, you can convert it to SVG using any online converter, please keep in mind that online converters can cause scalability issues.
'''Note:''' If you have a brand in a different format, you can convert it to SVG using any online converter, please keep in mind that online converters can cause scalability issues.
Afterwards, compress the file to .gz file as per screenshot below:
Afterwards, compress the file to .gz file as per screenshot below:
gzip [file]
gzip [file]
If your logo is compressed to'''.gz format''', you can extract it *if needed* via terminal by following command:
If your logo is compressed to'''.gz format''', you can extract it, if needed, via terminal by following command:
gzip -d [file]
gzip -d [file]
'''Note''': It is worth that the logo has been changed to tlt-icons/tlt_networks_logo_white.The svg on the log in page is displayed on a blue background, however the tlt_networks_logo.svg displayed following the logging in line at the top is displayed on a white backdrop. The usual size of both logos is 266px x 31px.
'''Note''': It is worth that the logo has been changed to tlt-icons/tlt_networks_logo_white.The svg on the log in page is displayed on a blue background, however the tlt_networks_logo.svg displayed following the logging in line at the top is displayed on a white backdrop. The usual size of both logos is '''266px x 31px'''.
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
make clean
make clean
Following that, when compiling firmware using '''make''' command, specifying the number of processors to be used is possible, thus speeding it up. To determine the number of available processors, you can use '''nproc''' command. Then, pass this number to the '''-j''' option in '''make''' command.
make -j1 V=sc
The firmware can then be found in the directory listed below '''*Depends on the target*''':
The exact path to the firmware depends on the target. In this example, the firmware can be found in the following directory:
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.05.3_WEBUI
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.06.1_WEBUI
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
'''file name''': RUTX_R_GPL_00.07.06.X_WEBUI
'''RESULTS:'''
'''RESULTS:'''
[[File:BRANDRESULTS2.png|border|class=tlt-border]]
[[File:brand_transparent.png|border|1100px|class=tlt-border]]
[[File:BRANDRESULTS1.png|border|class=tlt-border]]
[[File:Companybrand.png|1100px|border|class=tlt-border]]
==Changing Favicon==
==Changing Favicon==
'''First File:'''
'''First File:'''
~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin
~/Downloads/RUTX_R_GPL_00.07.06.1/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin
[[File:Logo1.png|border|class=tlt-border]]
[[File:Favicon.png|1100px|border|class=tlt-border]]
'''Second File:'''
'''Second File:'''
~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/assests
~/Downloads/RUTX_R_GPL_00.07.06.1/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/assests
[[File:Logo2.png|border|class=tlt-border]]
[[File:Logo2.png|border|class=tlt-border]]
gzip [file]
gzip [file]
If your logo is compressed to'''.gz format''', you can extract it *if needed* via terminal by following command:
If your logo is compressed to'''.gz format''', you can extract it, if needed, via terminal by following command:
gzip -d [file]
gzip -d [file]
'''Note''': It is worth that the logo has been changed to tlt-icons/tlt_networks_logo_white.The svg on the log in page is displayed on a blue background, however the tlt_networks_logo.svg displayed following the logging in line at the top is displayed on a white backdrop. The usual size of both logos is 266px x 31px.
'''Note''': It is worth that the logo has been changed to tlt-icons/tlt_networks_logo_white.The svg on the log in page is displayed on a blue background, however the tlt_networks_logo.svg displayed following the logging in line at the top is displayed on a white backdrop. The usual size of both logos is '''266px x 31px'''.
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
make clean
make clean
Following that, when compiling firmware using '''make''' command, specifying the number of processors to be used is possible, thus speeding it up. To determine the number of available processors, you can use '''nproc''' command. Then, pass this number to the '''-j''' option in '''make''' command.
make -j1 V=sc
The firmware can then be found in the directory listed below '''*Depends on the target*''':
The exact path to the firmware depends on the target. In this example, the firmware can be found in the following directory:
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.05.3_WEBUI
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.06.1_WEBUI
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
'''file name''': RUTX_R_GPL_00.07.06.X_WEBUI
[[File:LOGORESULTS1.png|border|class=tlt-border]]
[[File:LOGORESULTS1.png|border|class=tlt-border]]
==Changing WebUI Color==
To modify color designs for the WebUI, locate '''brand.css''' file. In this configuration, it is in ''/RUTX_R_GPL_00.07.06/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/brand'' directory. Run '''ls''' command to see the contents of the directory. It should have a zip file entitled '''brand.css.gz'''. To extract brand.css.gz, run:
gzip -d brand.css.gzip
[[File:Brand1.png|border|class=tlt-border]]
Run '''nano brand.css''' on the same directory to edit color values. Color schemes are using HTML color codes in HEX. You can generate '''HEX color codes''' with the help of this link: https://htmlcolorcodes.com/
[[File:Color5.png|border|1100px|class=tlt-border]]
For demo purposes, let us change the '''border color '''and''' font-color''' to '''#03ECFC''' and '''#06C46F''' respectively.
[[File:Color2.png|border|class=tlt-border]]
To save, type '''Ctrl + X'''. Then, click '''Y'''.
After making changes and saving them to the directory, we may '''build compile''' using the following commands:
./scripts/feeds update -a
make clean
Following that, when compiling firmware using '''make''' command, specifying the number of processors to be used is possible, thus speeding it up. To determine the number of available processors, you can use '''nproc''' command. Then, pass this number to the '''-j''' option in '''make''' command.
make -j1 V=sc
The exact path to the firmware depends on the target. In this example, the firmware can be found in the following directory:
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.06.1_WEBUI
'''file name''': RUTX_R_GPL_00.07.06.X_WEBUI
'''RESULTS:'''
[[File:Color4.png|border|1100px|class=tlt-border]]
==Disclaimer==
==Disclaimer==
It may not be necessary to update scripts and make clean after making firmware changes; this will depend on the changes undertaken. In these cases, the commands were used to assure clean compilation and the removal of any potential artifacts from previous environments.
It may not be necessary to update scripts and make clean after making firmware changes; this will depend on the changes undertaken. In these cases, the commands were used to assure clean compilation and the removal of any potential artifacts from previous environments.
[[Category:Other Topics]]