Hello,
I am very new to OpenWRT (this is my first project) so there is possibly something very simply that I am doing wrong.
I am trying to install OpenWRT on to a Open-Mesh MR1750 using ap51-flash in Win10. ap51-flash detects the router but then states "is of type 'MR1750' that we have no image for"
As best I can tell my device matches the hardware listed here which should be supported by 23.05.0 and as far as i can tell ap51-flash is one of the recommended install option. Techdata: Open-Mesh MR1750 v1
Can anyone explain what I am doing wrong or direct me to a resource that might help?
You might try the uboot tftp recovery method. The tech data page doesn't provide details about the implementation here, so it's not entirely clear if the device has a tftp server or client and the addresses. But take a look at the link below:
Thank you for the redirect. I also found this towards the end of yesterday. It seems that Open-Mesh may have locked the the device down as described in the this article.
The unlock procedure is getting well outside my normal skill set.
Some of the information they provided around SSH involves getting information from Cloudtrax which I can't use as the AP MAC is listed as already in use (I got these second hand from a junk store). Although it looks like SSH might not be available anyway.
Not at all sure about the build process etc. for the unlock. There seems to be a prebuild for OpenMesh OM5P-AC v2 but not for MR1750. If I get time I might do some learning and see if I can get it do work. However, this has gone form a potentially "easy" project to quite difficult. The two MR1750 only owe me $1 so I might just look for some different hardware. Shame to bin them but...
Cloudtrax gets really problematic after Datto purchased Openmesh.
It's worth looking for something else to get on with, maybe a couple of a Meraki MR18s?
Just for future reference if anybody else tries to install on an Open Mesh MR1750.
Serial is useful but not 100% needed.
Setup a tftp server at 192.168.100.8
Download openwrt 22.03.6 initramfs and rename it to vmlinux-initramfs.bin
Put the vmlinux-initramfs.bin file on the tftp server
Press the reset button and keep it pressed
Power on the MR1750 and allow a few seconds for tftp to start downloading the initramfs file
Release the reset button
Wait for a minute or so to allow the device to fully boot
Connect to 192.168.1.1 and use sysupgrade to install to the flash chip
Reboot
Sysupgrade and 1st boot afterwards are quite slow so be patient.
Initramfs from 23.05.2 does not work due to some lmza decompress error.
The serial pins on the board are quite short so I recommend to slide the black plastic bit off with a small screwdriver.
UART / serial does show output but does not seem to respond to key presses. Based on the info on similar boards it may be that the small resistors next to the pins need to be removed.
Hello,
unfortunately it does not work.
When I follow this procedure exactly with firmware: cp Downloads/openwrt-22.03.6-ath79-generic-openmesh_mr1750-v1-initramfs-kernel.bin /srv/tftp/vmlinux-initramfs.bin
then I see in the tftp logs this:
Apr 5 18:58:58 workstation in.tftpd[12201]: RRQ from 192.168.100.9 filename vmlinux-initramfs.bin
Apr 5 19:03:21 workstation in.tftpd[12466]: RRQ from 192.168.100.9 filename fwupgrade.cfg
Apr 5 19:03:21 workstation in.tftpd[12466]: sending NAK (1, File not found) to 192.168.100.9
Apr 5 19:03:22 workstation in.tftpd[12469]: RRQ from 192.168.100.9 filename fwupgrade.cfg
Apr 5 19:03:22 workstation in.tftpd[12469]: sending NAK (1, File not found) to 192.168.100.9
Apr 5 19:05:33 workstation in.tftpd[12599]: RRQ from 192.168.100.9 filename fwupgrade.cfg
Apr 5 19:05:33 workstation in.tftpd[12599]: sending NAK (1, File not found) to 192.168.100.9
Apr 5 19:05:34 workstation in.tftpd[12602]: RRQ from 192.168.100.9 filename fwupgrade.cfg
Apr 5 19:05:34 workstation in.tftpd[12602]: sending NAK (1, File not found) to 192.168.100.9
So the device will not flashed and I have no clue how to provide the missed file fwupgrade.cfg.
If I press the reset button very long after power on - the device seems to stuck and only the power led and the lan led are activ permanently with no progress.
Yes - after very long pressing the reset button and only the power led and the lan led is active - this is the sign to connect via ssh to 192.168.1.1!
So I will suggest this minimal changed procedure:
Setup a tftp server at 192.168.100.8
Download openwrt 22.03.6 initramfs Link and rename it to vmlinux-initramfs.bin
Put the vmlinux-initramfs.bin file on the tftp server
Press the reset button and keep it pressed
Power on the MR1750 and allow a few seconds for tftp to start downloading the initramfs file
Release the reset button not before only the power led and the lan led is active
Check after release the reset button, that really only the pwoer led and the lan led is permanent lighting
Connect to 192.168.1.1 and use sysupgrade to install to the flash chip
Reboot
