128
edits
Difference between revisions of "Mesh/Flashing extender nodes"
Jump to navigation
Jump to search
adding notes concerning Nanostation M2
Redconfetti (talk | contribs) m (adding link to article involving Picostation M2HP) |
Redconfetti (talk | contribs) (adding notes concerning Nanostation M2) |
||
| Line 62: | Line 62: | ||
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms | 64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms | ||
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms | 64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms | ||
== Nanostation M2 == | |||
=== Firmware check failure === | |||
Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error. | |||
$ tftp 192.168.1.20 | |||
tftp> bin | |||
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin | |||
Error code 2: Firmware check failed | |||
Sent 4609024 bytes in 12.6 seconds | |||
You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5. | |||
Board: Ubiquiti Networks XM board (rev 1.0 e012) | |||
DRAM: 32 MB | |||
Flash: 8 MB | |||
PCIe WLAN Module found (#1). | |||
Net: eth0, eth1 | |||
Hit any key to stop autoboot: 0 | |||
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: | | |||
Receiving file from 192.168.1.10:35456 | |||
Received 4609501 bytes | |||
Firmware check failed! (-2) | |||
The method outlined for the Nanostation M5 below doesn't work with the M2. | |||
== Nanostation M5 == | == Nanostation M5 == | ||
=== Firmware check failure === | === Firmware check failure === | ||
Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error. | |||
If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware. | If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware. | ||
| Line 130: | Line 164: | ||
minicom: cannot open /dev/tty8: Permission denied | minicom: cannot open /dev/tty8: Permission denied | ||
Run the program so that it starts the program on the USB converter that is connected by adding | Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. | ||
You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including | You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>. | ||
sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8 | sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8 | ||