Difference between revisions of "Mesh/Flashing extender nodes"

Jump to navigation Jump to search
adding instructions for using serial to run tftp for successful flash of sudowrt
(adding instructions for using serial to run tftp for successful flash of sudowrt)
Line 244: Line 244:
This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.
This will cause the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line.


==== Transfering file to U-Boot over Serial ====
==== Running TFTPd ====


U-Boot supports two protocols for transfering files: kermit or y-modem. Minicom does not support the kermit protocol, however it does support the y-modem protocol.
Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.
 
We do not have to resort to a direct serial file transfer however.
 
  ar7240> mtdparts default
  ar7240> urescue
  Setting default IP 192.168.1.20
  Starting TFTP server...
  Using eth0 (192.168.1.20), address: 0x81000000
  Waiting for connection: \
 
In your other terminal window, run the ubi-flasher script.
 
  $ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
  Accessing http://192.168.1.20/login.cgi
  Connection timed out
  Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
  Firmware flashing begun!
  The firmware has been successfully sent to the router.
  In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
  This means that the router is flashing itself with the new firmware.
  Once the router goes back to having only the power LED lit, the router has been successfully flashed.
 
In the terminal running Minicom you should see the firmware successfully flashing.
 
  Receiving file from 192.168.1.10:52289
  Received 4325788 bytes
  Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
  Setting U-Boot environment variables
  Un-Protected 1 sectors
  Erasing Flash.... done
  Erased 1 sectors
  Writing to Flash... write addr: 9f040000
  done
  Protected 1 sectors
  Copying partition 'kernel' to flash memory:
 
  First 0x5 last 0x14 sector size 0x10000
  ................ done
  write addr: 9f050000
  Copying partition 'rootfs' to flash memory:
 
  First 0x15 last 0x6e sector size 0x10000
  .......................................................................................... done
  write addr: 9f150000
 
  Firmware update complete.
 
  Resetting...
 
  U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)
 
  DRAM:  64 MB
  Flash:  8 MB (0xc2, 0x20, 0x17)
  Net:  AR8236
  eth0, eth1
  Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
  Radio: 0777:e855
  Reset: Normal
  Hit any key to stop autoboot:  0
  ## Booting image at 9f050000 ...
    Image Name:  MIPS OpenWrt Linux-3.18.23
    Created:      2015-12-01  0:03:51 UTC
    Image Type:  MIPS Linux Kernel Image (lzma compressed)
    Data Size:    1135619 Bytes =  1.1 MB
    Load Address: 80060000
    Entry Point:  80060000
    Verifying Checksum at 0x9f050040 ...OK
    Uncompressing Kernel Image ... OK
 
  Starting kernel ...
 
  [    0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5
 
After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.
 
You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.
 
  [  25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
  [  25.660000] done.
  [  25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.
 
 
 
  BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)
 
 
    ._______.___    ._______.______  ._____  .___    .___ .______  ._____ 
    :_ ____/|  |  : .____/:_ _  \ :_ ___\ |  |  : __|:      \ :_ ___\
    |  _/  |  |  | : _/\ |  |  ||  |___|  |  | : ||      ||  |___
    |  |  |  |/\ |  /  \| . |  ||  /  ||  |/\ |  ||  |  ||  /  |
    |_. |  |  /  \|_.: __/|. ____/ |. __  ||  /  \|  ||___|  ||. __  |
      :/    |______/  :/    :/      :/ |. ||______/|___|    |___| :/ |. |
      :                      :        :  :/                        :  :/
                                          :                            :
  -------------------------------------------------------------------------
  sudo mesh v0.2 (fledgling.extender)
                                based on OpenWRT 15.05 (Chaos Calmer)
  -------------------------------------------------------------------------
  "When your rage is choking you, it is best to say nothing."
                                              - Octavia E. Butler, Fledgling
  -------------------------------------------------------------------------
 
  root@sudomesh-node:/#
128

edits

Navigation menu