It looks like there is the same issue with the Mikrotik RBLHG-2nD as the Mikrotik RBLHG-5nD.
Using the pxser I can boot up using the elf file.
Going to setup and uploading the bin file getting "Bad Gateway"
Here is the information..
node: NOCALL-122-118-2 model: MikroTik RouterBOARD RBLHG-2nD !!!! UNSUPPORTED DEVICE !!!! boardid: MikroTik RouterBOARD RBLHG-2nD Device has not been tested. Please file a ticket with your experiences. br-lan 48:8F:5A:7B:76:02 eth0 48:8F:5A:7B:76:02 eth0.1 48:8F:5A:7B:76:02 eth0.2 48:8F:5A:7B:76:02 tunl0 00-00-00-00-00-00-00-44-00-00-00-00-00-00-00-00 wlan0 48:8F:5A:7A:76:02 /proc/cpuinfo system type : Qualcomm Atheros QCA9533 ver 2 rev 0 machine : MikroTik RouterBOARD RBLHG-2nD processor : 0 cpu model : MIPS 24Kc V7.4 BogoMIPS : 432.53 wait instruction : yes microsecond timers : yes tlb_entries : 16 extra interrupt vector : yes hardware watchpoint : yes, count: 4, address/irw mask: [0x0ffc, 0x0ffc, 0x0ffb, 0x0ffb] isa : mips1 mips2 mips32r1 mips32r2 ASEs implemented : mips16 Options implemented : tlb 4kex 4k_cache prefetch mcheck ejtag llsc dc_aliases perf_cntr_intr_bit nan_legacy nan_2008 perf shadow register sets : 1 kscratch registers : 0 package : 0 core : 0 VCED exceptions : not available VCEI exceptions : not available nvram hsmmmesh.settings=settings hsmmmesh.settings.wifimac='48:8f:5a:7a:76:02' hsmmmesh.settings.mac2='122.118.2' hsmmmesh.settings.node='NOCALL-122-118-2' hsmmmesh.settings.dtdmac='122.118.1'
I tried both the stable and nightly builds
--
Bill (KA2FNK)
I'll put together a test image, today or tomorrow.
Joe AE6XE
Thank you
KA2FNK,
Please try the test images here:
https://drive.google.com/drive/folders/1PhjMYoOBv1t-_OFGC6HS3BEdDR77NWqE...
I need a support data file, link at bottom of Administration page. Please upload back here. From this data, it's possible another change to the power limits may be needed.
Joe AE6XE
Joe,
Loaded both the elf and bin without a problem. The unit is now up.
I have the supportdate file. I can not upload to the google drive location. I do not have permission.
So I have attached the file here
Bill KA2FNK
Bill, check to see, looks like a support data file for an GL-AR150, and not the LHG. Something got swapped around.
Joe
Joe,
Here is the correct file
Thank you
This isnt taking the nightly build thru PXE. Starts to read then nothing. Made several attempts including stable release. AKA Same issue here :)
Thanks
Chad
KA7HAK
Chad, if unable to load the .elf file via PXE program, there must be something else going on. The .elf has been loading on these devices, but when trying to flash with the .bin, it doesn't recognize the model string (if new and not seen before).
Joe AE6XE
This is a new unit purchased via amazon recently. windows pxesrv assigns the IP and starts the read. then the nic in windows just cycles and unplugged status. Like it's boot looping? I've yet to see if I can use my ttl serial interface on this board to look at the console.
KA7HAK
sudo dnsmasq -i enp0s25 --dhcp-range=192.168.1.100,192.168.1.200 --dhcp-boot=/home/ubuntu/Downloads/rb.elf --enable-tftp -tftp-root=/home/ubuntu/Downloads/ -d -u ubuntu -p0 -K --log-dhcp --bootp-dynamic
dnsmasq: started, version 2.80 DNS disabled
dnsmasq: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile
dnsmasq-dhcp: DHCP, IP range 192.168.1.100 -- 192.168.1.200, lease time 1h
dnsmasq-tftp: TFTP enabled
dnsmasq-dhcp: 1491786020 available DHCP range: 192.168.1.100 -- 192.168.1.200
dnsmasq-dhcp: 1491786020 vendor class: Mips_boot
dnsmasq-dhcp: 1491786020 tags: bootp, enp0s25
dnsmasq-dhcp: 1491786020 BOOTP(enp0s25) 192.168.1.160 48:8f:5a:7a:76:9d
dnsmasq-dhcp: 1491786020 bootfile name: /home/ubuntu/Downloads/rb.elf
dnsmasq-dhcp: 1491786020 next server: 192.168.1.10
dnsmasq-dhcp: 1491786020 sent size: 4 option: 1 netmask 255.255.255.0
dnsmasq-dhcp: 1491786020 sent size: 4 option: 28 broadcast 192.168.1.255
dnsmasq-dhcp: 1491786020 sent size: 4 option: 3 router 192.168.1.10
dnsmasq-tftp: sent /home/ubuntu/Downloads/rb.elf to 192.168.1.160
KA7HAK, at this point, we'd have to open the cover and put a console on the serial port to see what is going on. I am assuming after the .elf is sent, that the device's power stays on. If it is in a reboot loop at that point, then we'd need to get on the console to see the error.
Joe AE6XE
After running the tftp I get this. Using 115200 8n1. It's not readable images attached
Change the terminal type to ansii or something different. Also, might need to try different baud rates, but I'd have thought this would work. trial-n-error different things to see if it becomes ledgiable.
Joe AE6XE
no luck yet with the serial but I decided to use a different power supply and had some success but the sysupgrade will not take.
confirm, only a current nightly build image will work.
Joe AE6XE
aredn-1866-bf944df-ar71xx-mikrotik-vmlinux-initramfs (no untested message)
current version: 1866-bf944df
hardware type: (ar71xx/mikrotik) mikrotik (rb-lhg-5nd)
uploading aredn-3.20.3.1-ar71xx-mikrotik-rb-nor-flash-16M-sysupgrade
DO NOT REMOVE POWER UNTIL UPDATE IS FINISHED
!!!! UNTESTED HARDWARE !!!!
Firmware Update
current version: 3.20.3.1
hardware type: (ar71xx/mikrotik) mikrotik (unknown)
also tried the nightly but got bad gateway
so it boots on its own and the frequencies are messed up. no -2
The sysupgrade version also has to be from the nightly build #1866. Looks like, "uploading aredn-3.20.3.1-ar71xx-mikrotik-rb-nor-flash-16M-sysupgrade", and 3.20.3.1 does not know about this new model string.
Bad Gateway The process did not produce any response
aredn-1866-bf944df-ar71xx-mikrotik-rb-nor-flash-16M-sysupgrade
loaded the .elf image first, correct? Then went into AREDN UI to upload the sysupgrade image, correct? (the .elf and .bin images must both be the latest nightly build.) Then if still getting bad gatway error, suggest to try the command line to scp up the sysupgrade image to /tmp on the node and do the manual "sysupgrade -n <image>" to see what errors come back.
Joe
Finally got it working! It's using all the nightly build files. I think the my problem was the wrong power supply and thinking I could load the release version sys upgrade. Thank you!!
Chad
KA7HAK