Teltonika Networks Wiki

Changes

RUTOS Software Development Kit (SDK) Instruction (view source)

Revision as of 16:26, 15 November 2023

164 bytes added ,  16:26, 15 November 2023
no edit summary
Line 81: Line 81:  
  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 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
Line 155: Line 155:  
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:
   −
./scripts/feeds update -a
+
1- ./scripts/feeds update -a
   −
make clean
+
2- make clean
   −
Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
+
3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
    
The firmware can then be found in the directory listed below *Depends on the target*:
 
The firmware can then be found in the directory listed below *Depends on the target*:
Line 187: Line 187:  
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:
   −
./scripts/feeds update -a
+
1- ./scripts/feeds update -a
   −
make clean
+
2- make clean
   −
Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
+
3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
    
The firmware can then be found in the directory listed below *Depends on the target*:
 
The firmware can then be found in the directory listed below *Depends on the target*:
Line 202: Line 202:  
  ~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/base-files/files
 
  ~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/base-files/files
   −
[[File:Image (18).png|border|class=tlt-border]]
+
[[File:SSH1.jpg|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:Ssh2.jpg|border|class=tlt-border]]
    
It shall open up as  above , after making the desired changes to the banner, you can then save those modifications.
 
It shall open up as  above , after making the desired changes to the banner, you can then save those modifications.
Line 212: Line 212:  
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:
   −
./scripts/feeds update -a
+
1- ./scripts/feeds update -a
   −
make clean
+
2- make clean
   −
Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
+
3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
    
The firmware can then be found in the directory listed below *Depends on the target*:
 
The firmware can then be found in the directory listed below *Depends on the target*:
Line 235: Line 235:  
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:COMPANYLINKS.png|border|class=tlt-border]]
    
It shall open up as  above , after making the desired changes to the banner, you can then save those modifications.
 
It shall open up as  above , after making the desired changes to the banner, you can then save those modifications.
Line 241: Line 241:  
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:
   −
./scripts/feeds update -a
+
1- ./scripts/feeds update -a
   −
make clean
+
2- make clean
   −
Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
+
3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
    
The firmware can then be found in the directory listed below *Depends on the target*:
 
The firmware can then be found in the directory listed below *Depends on the target*:
Line 263: Line 263:  
  ~/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.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin
   −
[[File:BRAND.png|border|class=tlt-border]]
+
[[File:BRANDTELT.png|border|class=tlt-border]]
    
'''Second File:'''
 
'''Second File:'''
Line 269: Line 269:  
  ~/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.05.3/rutos-ipq40xx-rutx-gpl/package/feeds/vuci/vuci-ui-core/bin/dist/ tlt-icons
   −
[[File:Brand22.png|border|class=tlt-border]]
+
[[File:BRANDTELT2.png|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.
Line 279: Line 279:  
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:
   −
./scripts/feeds update -a
+
1- ./scripts/feeds update -a
   −
make clean
+
2- make clean
   −
Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
+
3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
    
The firmware can then be found in the directory listed below *Depends on the target*:
 
The firmware can then be found in the directory listed below *Depends on the target*:
Line 292: Line 292:  
'''RESULTS:'''
 
'''RESULTS:'''
   −
[[File:RESULTSBRAND.jpg|border|class=tlt-border]]
+
[[File:BRANDRESULTS2.png|border|class=tlt-border]]
 +
 
 +
[[File:BRANDRESULTS1.png|border|class=tlt-border]]
   −
==Changing favicon==
+
==Changing Device Logo==
−
To modify the favicon, you can make use search tool in the extracted GPL. To access this, follow these steps from the root directory of your project, you can find the TWO files from route below:
+
To modify the Device logo, you can make use search tool in the extracted GPL. To access this, follow these steps from the root directory of your project, you can find the TWO files from route below:
    
'''First File:'''
 
'''First File:'''
Line 308: Line 310:     
[[File:Logo2.png|border|class=tlt-border]]
 
[[File:Logo2.png|border|class=tlt-border]]
 +
 +
For example, I will use Burj Khalifa logo in order to perform the changes here.
    
'''Note:''' If you have a brand in a different format, you can convert it to ico 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 ico using any online converter, please keep in mind that online converters can cause scalability issues.
Line 313: Line 317:  
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:
   −
./scripts/feeds update -a
+
1- ./scripts/feeds update -a
   −
make clean
+
2- make clean
   −
Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
+
3- Following that, we must execute the "nproc" command to determine the number of processors, and it will return a number, such as 1, allowing us to run command. “make -j1 V=sc” for verbose output. This way you will see more logs that may help to troubleshoot compilation issues.
    
The firmware can then be found in the directory listed below *Depends on the target*:
 
The firmware can then be found in the directory listed below *Depends on the target*:
Retrieved from "https://wiki.teltonika-networks.com/view/Special:MobileDiff/116250"