Maybe, but the problem is somewhere else.
If you take a look at the ramdisk boot commands
setenv serverpath; setenv netloadmethod tftpboot; setenv bootargs console=ttyS0,${baudrate} rootfstype=squashfs mtdoops.mtddev=oops; run meraki_load_net meraki_checkpart meraki_bootlinux
and then look at the printenv
meraki_bootlinux=bootm ${meraki_loadaddr_kernel} ${meraki_loadaddr_ramdisk} ${meraki_loadaddr_fdt}
meraki_loadaddr=800000
meraki_loadaddr_kernel=810000
meraki_loadaddr_fdt=800400
meraki_loadaddr_ramdisk=a00000
you see that something isn't quite right.
The whole apm821xx-nand-meraki_mx60-initramfs-kernel.bin gets placed starting from 0x800000.
the DTB/FDT has to be located at 0x800400 - 0x80ffff (64,512 Bytes)
The kernel has to be located at 0x810000 - 0x9fffff (1984 KiB)
and the ramdisk should be from 0xa00000.
However, if you look at any of the openwrt/lede releases you'll notice that this can't be right. The kernel is much bigger than the 1984 KiB and as result, the ramdisk addr points to "something" inside the gzipped kernel and as a result u-boot complains about it:
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
now, how to fix this: There are several options. It's possible that the MX60(w) u-boot supports mult-image in this case the whole MX60 could be converted to something that the MR24 already does for it's initramfs image. But this will require the device in order to develop and test this.
As for a in-place quick fix: you could edit the ramdisk address (meraki_loadaddr_ramdisk) and move it to the proper location. If I'm not totally off, you should have a chance with:
setenv meraki_loadaddr_ramdisk 0xbffc00
setenv serverpath
setenv netloadmethod tftpboot;
setenv bootargs console=ttyS0,${baudrate} rootfstype=squashfs mtdoops.mtddev=oops;
run meraki_load_net meraki_checkpart meraki_bootlinux
As for "meraki_checkpart " yeaah, that serves no real purpose and can be removed at some point.