I get to step 3 where it should be booting from TFTP but I'm not sure it actually does.
Here is my output after the flash commands and booting the device:
U-Boot 2009.08-00049-g0ee25dd Meraki MX60 (Jul 27 2012 - 14:59:20)
CPU: AMCC PowerPC UNKNOWN (PVR=12c41c83) at 800 MHz (PLB=200, OPB=100, EBC=10 0 MHz)
Bootstrap Option D - Boot ROM Location NAND wo/ECC 2k page (8 bits), boot ing from NAND
32 kB I-Cache 32 kB D-Cache
Board: Buckminster Wireless - Meraki Buckminster Wireless Cloud Managed Router
BoardID: 0 0
Reset Button Status: 1
DRAM: 512 MB
NAND: 1024 MiB
I2c read: failed 4
I2c read: failed 4
I2c read: failed 4
Initializing Bluestone Ethernet Port ...
Disabling port 0
Disabling port 1
Disabling port 2
Disabling port 3
ENET Speed is 1000 Mbps - FULL duplex connection (EMAC0)
*** ERROR: ping address not given
RESET is un-pushed
Set serverpath and run meraki_netboot to netboot
Hit any key to stop autoboot: 0
Creating 1 MTD partitions on "nand0":
0x000000240000-0x000040000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=2"
UBI: MTD device size: 1021 MiB
UBI: number of good PEBs: 8168
UBI: number of bad PEBs: 6
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 4
UBI: available PEBs: 3398
UBI: total number of reserved PEBs: 4770
UBI: number of PEBs reserved for bad PEB handling: 81
UBI: max/mean erase counter: 268/264
kernel volume not found
recovery volume not found
Any thoughts as to what I'm doing wrong?
I have a Cat5e cable plugged into WAN1 and the IP address set to 192.168.1.101/24 on my laptop as well as running tftp32 but the document also refers to a "buck.bin" which I'm not sure where that file is.
This means you already wiped the partitions. You need to boot the TFTP image to:
access the UBI software
ensure you deleted the other partitions
rearrange the board-config to ubi0_0
to create the recovery partition and flash the BIN file to it
to access LuCI and flash the sysupgrade TAR file (please note that I was only able to flash the MX60 sysupgrade - see thread linked in my post above).
That's the OpenWRT BIN file you download from downloads.openwrt.org. You must rename it to buck.bin so that it will TFTP and boot the router.
You also need that BIN file to save as the recovery image (please note there's a LAN issue with the BIN files, my thread above links to workarounds in order to proceed (A. - editing the network config; or B. - using a second device and editing the firewall to access LuCI via the WAN). Also, if you accidentally erased board-config already, the threads above has access to a copy for you.
From there, you perform the steps in my other post. If you read the threads I linked, you will see there's 2 options to get the network operational in order to flash recovery and 17.01.4 MX60 (in my case) to the router.
In post 1 of the "Issues with Meraki MX60 and MX60W Images" thread:
There are 2 links.
The first is from someone else who used the serial to edit eth0.2 to LAN, then applied the changes after confirming they were accurate. They seem to have then accessed LuCI and flashed the router (I have not confirmed this procedure).
In the other, I independently came to the same issue (but noticed that WAN was making DHCP requests) and used a second device to make a tagged LAN port that used VLAN ID 2. I then made an iptables rule to allow port 80 on WAN. I then accessed LuCI and flashed the MX60 image.
This is not necessarily a N00b issue, the Merakis are newer device being supported (likely because most are still under support by their OEM)...the images for version 17 have a slight config issue.
If you have already successfully moved board-config to 0_0, then you should be able to wipe all other UBI using similar commands on the github site.
Will list all the partitions.
From there you can delete them using the remove command with -N (do not delete board-config at 0_0!!!) and then re-create the recovery, get the image, flash it to 0_1, etc.
From there, you sysupgrade. Please recall if you ever have to hold the reset button to boot recovery will have to access LuCI again the same way...until v18 is released - and you flash that BIN to recovery.
(I'm not sure the instruction make the U-Boot environment edit the reset button to boot recovery, I think it only boots if the main image is missing.)
UPDATE: I think you should get a copy of your 0_1 (board-config.img) move it to /etc/config so you can use LuCI to get a backup config of it....and use a HEX Editor to verify it is in fact the board config.