Changes between Initial Version and Version 1 of OpenWrt/Configuration

10/22/2017 05:28:45 AM (5 years ago)



  • OpenWrt/Configuration

    v1 v1  
     3= Custom Configuration OpenWrt =
     5Gateworks uses OpenWrt and it boots up by default properly. 
     7However, the install can be tweaked however the user wants.
     9This must be done at '''COMPILE''' time however.
     12== make menuconfig ==
     13At the command prompt in the '''trunk''' directory where the Gateworks code was checked out, type the command:
     16/gateworks-openwrt-x/gateworks-openwrt/trunk$ make menuconfig
     19You will be presented with a GUI that looks like so:
     23You can now make any changes, using the space bar to select different items.  Select the asterisk next to the line item you want.[[BR]][[BR]]
     25'''NOTE:'''Once you make any changes, exit and save.
     29'''There is a config file in the gateworks-openwrt directory as well as the trunk directory.'''  If a 'make cns3xxx' (Laguna) is ran after doing a make menuconfig, it will '''wipe out''' the changes done in make menuconfig.[[BR]][[BR]]
     31Therefore, run a make -j8 V=99 in the OpenWrt trunk directory, followed by a make images/laguna in the upper directory to get a fresh firmware. 
     33/gateworks-openwrt/trunk$ make -j8 V=99
     37The newly generated firmware will contain the packages selected.  The individual IPK files should also be listed at (for Laguna boards) /trunk/bin/cns3xxx/packages [[BR]][[BR]]
     42Then, the make images/laguna command (Laguna) compiles the artifacts from trunk into a firmware binary (.bin) to be flashed to the board.
     45make images/laguna
     49== Specific Examples ==
     50=== Turning on GDB Server ===
     52If you desire to turn on GDBServer you can do that in the make menuconfig.  Go to the main menu item titled 'Development' and you will see it in there.  Use the space bar to select the line with an asterisk as seen below:
     56=== Configuring an IP Address ===
     58By default, Gateworks boards ship with as the default IP address.  Sometimes this conflicts with other IP addresses.  If desired, a configuration can be created to have the board come up with a different IP address.
     60Please note, the below is ONLY for building a image.  It is VERY easy to change the IP address manually once the board is booted.  Only use the below method if you have a specific reason as it is much more difficult than configuring the board via serial once it is up and booted.
     62WARNING: There is a 'preinit' network configuration is for preinit/failsafe (ie hit 'f' during boot for a failsafe terminal).  This most likely is not what people usually need. Rather, see below.
     65For customizing the IP address which is in the configuration file /etc/config/network (or any other files) the correct way is to put files in a 'files' directory in the build directory:
     69cd trunk ;   # openwrt trunk
     70mkdir -p files/etc/config
     71cat << EOF >> files/etc/config/network
     72config interface lan
     73        option ifname   eth0
     74        option type     bridge
     75        option proto    static
     76        option ipaddr
     77        option netmask
     83DHCP would be:
     85option 'interface' 'lan'
     86    option 'ifname' 'eth0'
     87    option 'type' 'bridge'
     88    option 'defaultroute' '0'
     89    option 'peerdns' '0'
     90    option 'proto' 'dhcp'
     97This will modify the rootfs that was created in the build directory (ie trunk/target-arm_v6k_uClibc-