Changes

no edit summary
Line 1: Line 1:  
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.03</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 provided Readme file.
+
<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 provided Readme file.
    
__TOC__
 
__TOC__
Line 135: Line 135:  
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. 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.
   −
==Changing default settings==
+
==Changing Default Password==
    
To create a firmware with different default settings, you must change the default in the config files, which are contained in <b>/openwrt-gpl-ipq40xx.Linux-x86_64/package/</b>. However, there is no unifying system regarding where one should look for config files related to specific services. Therefore, it is very important to acquaint yourself with the <b>UCI system</b> (RutOS configuration file system) in order to successfully navigate through the files:
 
To create a firmware with different default settings, you must change the default in the config files, which are contained in <b>/openwrt-gpl-ipq40xx.Linux-x86_64/package/</b>. However, there is no unifying system regarding where one should look for config files related to specific services. Therefore, it is very important to acquaint yourself with the <b>UCI system</b> (RutOS configuration file system) in order to successfully navigate through the files:
Line 144: Line 144:  
</ul>
 
</ul>
 
----
 
----
In many cases you will find that service names as they are displayed in the router's WebUI are similar to the names of the programs responsible for these services. For instance, [[RUTX11_Firewall|Firewall]] settings can be changed in the /openwrt-gpl-ipq40xx.Linux-x86_64/package/<b>network/config/firewall/files</b> directory. However, if you open the aforementioned directory, you will find that it contains four files:
  −
  −
[[File:Networking_rutx_sdk_instructions_3.png|border|class=tlt-border]]
  −
  −
As you can see from the image above, only one of the files holds the Firewall configuration, while other files contain scripts related to the service. This will be different for each case. For example, among Mobile Utilities files, which can be found in /openwrt-gpl-ipq40xx.Linux-x86_64/package/mobutils/src/, you will find even more items, including different config files which serve a different purpose:
  −
  −
[[File:Networking_rutx_sdk_instructions_4.png|border|class=tlt-border]]
  −
  −
==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:
Line 169: Line 160:     
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.
 
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*:
 +
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.05.3_WEBUI
 +
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
    
==Changing Default IP Address==
 
==Changing Default IP Address==
Line 199: Line 194:  
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*:
 
  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.05.3_WEBUI
'''file name''': RUTX_R_GPL_00.07.05.3_WEBUI
+
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
    +
==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:
   −
==Selecting packages==
+
~/Downloads/RUTX_R_GPL_00.07.05.3/rutos-ipq40xx-rutx-gpl/package/base-files/files
   −
To select which packages should be compiled into the firmware is through a special menu called <b>Kconfig</b>.  
+
[[File:SSH1.jpg|border|class=tlt-border]]
To enter the <b>Kconfig</b>, standing in your projects root directory execute this command in the terminal:
     −
make menuconfig
+
Make sure that the file that we want to edit is in the similar file path as below.
   −
After executing this command you should see a view like in the picture below.
+
[[File:Ssh2.jpg|border|class=tlt-border]]
[[File:menuconfig_main_page_v1.png|border|class=tlt-border|700px]]
     −
To move around in the <b>Kconfig</b> use the arrows on the keyboard, space bar to select or to unselect the package, and enter key to enter sub directories of packages.
+
It shall open up as  below , after making the desired changes to the banner, you can then save those modifications.
   −
<b>Note</b>: Do not unselect any package if you do not know what you are doing.
+
[[File:SSH3.jpg|border|class=tlt-border]]
----
  −
<li>Packages have three markings:
  −
<ol>
  −
<li><*> - this symbol says that the package will be compiled an added to the firmware</li>
  −
<li><M> - this symbol says that the package will be compiled but will not be added to the firmware</li>
  −
<li>< > - this symbols says that the package will not be compiled and will not be added to the firmware</li>
  −
</ol>[[File:menuconfig_package_marking_v1.png|border|class=tlt-border|700px]]
  −
</li>
  −
----
  −
By default all packages that were marked as to be compiled in the process, can be found separately from the firmware. Packages can be found in directory <b>~/RUT_X/openwrt-gpl-ipq40xx.Linux-x86_64/bin/packages/arm_cortex-a7_neon-vfpv4</b>.
     −
This directory also has five sub directories. Packages are categorized in these directories by there type.
+
After making changes and saving them to the directory, we may build compile using the following commands:
   −
==Compiling a single package==
+
1- ./scripts/feeds update -a
   −
If you ever need to compile a single package you do not need to compile the whole firmware. As an example we will try to compile a text editor called <b>Nano</b>.
+
2- make clean
----
     −
<li>Now we need to do this steps:</li>
+
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.
<ol>
  −
<li>Open the <b>Kconfig</b> by executing this command in the terminal:
  −
<pre>make menuconfig</pre></li>
  −
<li>Navigate to the menu section of <b>Nano</b> text editor. It can be found under “Utilities→Editors”</li>
  −
<li>Select <b>nano</b> package</li>
  −
<li>Three times press the “<b>Exit</b>” entry</li>
     −
[[File:selecting_nano_package_v1.png|border|class=tlt-border|700px]]
+
The firmware can then be found in the directory listed below *Depends on the target*:
<li>Save the configuration by selecting “<b>Yes</b>” in the prompted window</li>
+
rutos-ath79-rut9-gpl>bin>targets>ath79>generic>tltFws>RUTX_R_GPL_00.07.05.3_WEBUI
[[File:saving_menuconfig_v1.png|border|class=tlt-border|700px]]
+
'''file name''': RUTX_R_GPL_00.07.05.X_WEBUI
</ol>
  −
</li>
  −
----
  −
<li>When the package is selected we need to compile and install it:
  −
<ol>
  −
<li>While standing in root directory of the project execute this command in the terminal:
  −
<pre>make package/nano/compile</pre></li>
  −
[[File:nano_compile.gif]]
  −
<li>The compiled package can be found in the directory <b>~/RUT_X/openwrt-gpl-ipq40xx.Linux-x86_64/bin/packages/arm_cortex-a7_neon-vfpv4/packages</b>. Upload the <b>nano</b> install file into the router by executing this command in the terminal:
  −
<pre>scp bin/packages/arm_cortex-a7_neon-vfpv4/packages/nano_4.3-1_arm_cortex-a7_neon-vfpv4.ipk root@<router_ip_addr>:/tmp</pre></li>
  −
<li>Connect to your routers command line interface by executing this command in the therminal:
  −
<pre>ssh root@<router_ip_addr></pre></li>
  −
<li>Change your directory to <b>/tmp</b> directory</li>
  −
<li>Install the <b>nano</b> text editor by executing this command in the terminal:
  −
<pre>opkg install nano_4.3-1_arm_cortex-a7_neon-vfpv4.ipk</pre></li>
  −
<li>Try out the nano text editor by executing this command:
  −
<pre>nano example</pre></li>
  −
</ol>[[File:nano_install_v1.gif]]
  −
</li>
  −
<b>Note:</b> If the package that you want to compile isn't selected in the <b>Kconfig</b>, the install file of the package will not be created
     −
[[Category:Other Topics]]
+
==Changing Company Links==

Navigation menu