Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| toh:meraki:mx60 [2018/12/22 13:36] – [Flashing] new method chunkeey | toh:meraki:mx60 [2022/09/18 01:21] – IP 192.168.1.2 is not used in the flashing procedure, references removed lleachii | ||
|---|---|---|---|
| Line 30: | Line 30: | ||
| ==== Prerequisites ==== | ==== Prerequisites ==== | ||
| * 1x Meraki MX60/MX60W | * 1x Meraki MX60/MX60W | ||
| - | * 1x UART adapter wired to the MX60/MX60W (speed is 115200). | + | * 1x UART adapter wired to the MX60/MX60W (speed is 115200 |
| * Local computer (Static IP of 192.168.1.101) directly wired to the WAN port. | * Local computer (Static IP of 192.168.1.101) directly wired to the WAN port. | ||
| * A local TFTP server. | * A local TFTP server. | ||
| Line 36: | Line 36: | ||
| ==== Flashing ==== | ==== Flashing ==== | ||
| - | Note that older builds (17.01, 18.06.1) have a different flashing method due to changes made in the image. Please ensure you are following the correct instructions for the build you are installing. Instructions for the previous version can be found in the Repo Readme at [[https:// | + | Note that older builds (e.g. 17.01, 18.06 and 21.02) have a different flashing method due to changes made in the image. Please ensure you are following the correct instructions for the build you are installing. Instructions for the previous version can be found in the Repo Readme at [[https:// |
| - | === Snapshots | + | === OpenWrt 22.03.0 and above === |
| - | 1. Download the current meraki_mx60-initramfs-kernel.bin from [[http:// | + | 1. Download the current meraki_mx60-initramfs-kernel.bin from [[https:// |
| - | 2. Start your TFTP server at 192.168.1.2 and connect the MX60(W) to the WAN Port. | + | 2. Start your TFTP server |
| 3. Power on the MX60(W), and interrupt u-boot (accessible on the serial console). At the prompt, enter the following commands to update your boot settings: | 3. Power on the MX60(W), and interrupt u-boot (accessible on the serial console). At the prompt, enter the following commands to update your boot settings: | ||
| Line 53: | Line 53: | ||
| setenv owrt_bootargs setenv bootargs console=ttyS0, | setenv owrt_bootargs setenv bootargs console=ttyS0, | ||
| setenv owrt_boot run meraki_ubi owrt_bootargs\; | setenv owrt_boot run meraki_ubi owrt_bootargs\; | ||
| + | setenv owrt510_boot run meraki_ubi owrt_bootargs\; | ||
| + | setenv bootcmd run owrt510_boot | ||
| + | saveenv | ||
| + | </ | ||
| + | |||
| + | |||
| + | **<color # | ||
| + | |||
| + | < | ||
| setenv bootcmd run owrt_boot | setenv bootcmd run owrt_boot | ||
| saveenv | saveenv | ||
| </ | </ | ||
| + | |||
| 4. Now enter the following commands to TFTP boot the initramfs image hosted on your local computer. | 4. Now enter the following commands to TFTP boot the initramfs image hosted on your local computer. | ||
| Line 62: | Line 72: | ||
| setenv ipaddr 192.168.1.1 | setenv ipaddr 192.168.1.1 | ||
| setenv bootargs console=ttyS0, | setenv bootargs console=ttyS0, | ||
| - | tftpboot | + | tftpboot $meraki_loadaddr buck.bin; |
| bootm $fileaddr | bootm $fileaddr | ||
| </ | </ | ||
| - | 4. Once OpenWrt boots and you are at a root prompt, you can Cleanup for maximum space. < | + | 5. Once OpenWrt boots and you are at a root prompt, you can Cleanup for maximum space. < |
| ubirmvol /dev/ubi0 -N part1 | ubirmvol /dev/ubi0 -N part1 | ||
| ubirmvol /dev/ubi0 -N part2 | ubirmvol /dev/ubi0 -N part2 | ||
| Line 72: | Line 82: | ||
| </ | </ | ||
| - | 5. Create a optional recovery UBI partition. This will host an initramfs build so our board can have a failback image in case of a bad flash, or sysupgrade issue. You can also manually boot to recovery by holding the reset button while powering on the device. The recovery ip will always be 192.168.1.1, | + | 6. Create a optional recovery UBI partition. This will host an initramfs build so our board can have a failback image in case of a bad flash, or sysupgrade issue. You can also manually boot to recovery by holding the reset button while powering on the device. The recovery ip will always be 192.168.1.1, |
| < | < | ||
| Line 81: | Line 91: | ||
| </ | </ | ||
| - | 6. Once done, you can now load up LuCI at 192.168.1.1, | + | 7.You will want to upload a copy of the squashfs-sysupgrade.bin image to the board (which can be done with SCP/HTTP Server). Once done, you can now use the sysupgrade option to flash the full image to the device using the sysupgrade file named '' |
| + | |||
| + | < | ||
| + | # Be sure to replace the FILENAME with the correct squashfs-sysupgrade.bin image that you have loaded via SCP/HTTP | ||
| + | sysupgrade / | ||
| + | </ | ||
| ===== Hardware ===== | ===== Hardware ===== | ||
| ==== Info ==== | ==== Info ==== | ||
| Line 427: | Line 442: | ||
| ===== Tags ===== | ===== Tags ===== | ||
| [[meta: | [[meta: | ||
| - | {{tag> | + | {{tag>apm821xx |