I'm attempting to install OpenWrt on my Meraki MX60 and I'm getting to the part in step 4 where the device is supposed to download buck.bin from TFTP, but I keep timing out.
=> setenv ipaddr 192.168.1.1
=> setenv bootargs console=ttyS0,$baudrate mtdoops.mtddev=oops;
=> tftpboot 192.168.1.2:$meraki_loadaddr buck.bin;
Disabling port 0
Disabling port 1
Disabling port 2
Disabling port 3
Using ppc_4xx_eth0 device
TFTP from server 192.168.1.101; our IP address is 192.168.1.1
Filename 'buck.bin'.
Load address: 0x192
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Using ppc_4xx_eth0 device
TFTP from server 192.168.1.101; our IP address is 192.168.1.1
Filename 'buck.bin'.
Load address: 0x192
Loading: T T T T T T T T T T
Retry count exceeded; starting again
It'll sit there forever retrying.
I've used the following TFTP clients(I'm using windows 10):
the built in command prompt application of TFTP through windows 10
All of them either time out, or in tftpd64, it doesn't do anything at all. My static IP for my computer I'm using is 192.168.1.101, I'm sending the file to 192.168.1.2. My NIC is connected to the WAN port on the device(the one labeled internet), and I have no other connections being made.
You need to be running a TFTP server on your PC, that would be tftpd64. Also you must shut down the Windows Firewall and any third-party firewalls for a TFTP server to work. This is safe to do since the only thing the PC is connected to at the time will be the router undergoing work.
Generally you use a LAN port on the router, but that is model-specific.
Correct. I'm using that exact file. I actually went and redownloaded it and tried again, and this time Tftpd64 is now connecting, then saying that there was an error and terminating the connection.
I'm not sure why you keep ruining the saveenv command. It only needs to be ran once. I'm hoping you didn't accidentally erase anything. Looking at my orginal environment before making changes, I have this:
I got mine to work a while ago, now that I have a second one, I am running into this issue. For the last one, I think I threw a "hail mary" and changed the load_addr, but I can't remember what I did. Does anyone know how to change the load address from 0x192 to something correct?
If that's the only thing that got broken, you can do
setenv meraki_loadaddr 800000
and then
printenv
to check/confirm/verify the setting (ideally you also run printenv before in that case). I don't have any MX60(W) so I don't know what a healthy u-boot env looks like on those. I think @lleachii has posted a few on the forums though.
How big is the board_config partition? ubinfo -a in the OpenWrt prompt should tell you. If it's tiny (1 MiB or less) then you probably need to mess with the board_config to begin with, unless you absolutely want to squeeze out every KiB there is. From what I know the MX60 has like a GigaByte of NAND so space is not really a problem there.
ubinfo -a found me my recovery partition of ubi0_0 which is what I couldn't find yesterday. Thanks for your help!
These are really nice devices actually, the only issue is the CPU is a little weak for high intensity tasks, but only compared to the new routers with quad core whatevers.
Thanks a bunch, I think someone who knows what they are talking about should mark this one solved and update the wiki commands.
This did it! I was able to get the image installed on the router, but the only issue is I can't access 192.168.1.1 or anything like that. However, I can still restart the router and have it still show have Open Wrt installed.
Not for me, it was loading into the wrong memory address, nothing to do with the firewall. Something about the wiki commands redirected the loading. The new command caused the load to occur in the correct memory, so it worked.
Now that it’s installed, just install luci through the command line.
