You are here

hAP AC Lite won't flash .bin

36 posts / 0 new
Last post
kd2hzg
hAP AC Lite won't flash .bin

I recently purchased a few mikrotik boards to start building a local (and not so local) AREDN network. I ran through the first 3 (2x baseboards 1x hap ac lite) without issues. Grabbed the second hAP and it took the .elf without issue, but when I upload the .bin to either via the webUI or via the CLI it won't flash and it reverts back to RouterOS 6.7 something. I've tried with the force and no repartition flags with no avail, anyone else run into this? I've factory reset the RouterOS as well. It seems to me like there is write protection somewhere on the RouterOS config but I'm unable to find anything.
Thanks


EDIT: I think a point that is being missed here, is that I successfully updated two hAP's and two routerboards with the exact same method as I'm using for the locked hAP. Just wanted to make sure I emphasized that.
 

nc8q
nc8q's picture
webUI or via the CLI it won't

"webUI or via the CLI it won't flash and it reverts back to RouterOS 6.7 something. I've tried with the force and no repartition flags"

To be sure...is your device is a RB952Ui-5ac2nD ?

I am not familiar with your terms 'webUI, 'CLI', 'force', and 'no repartition' in the installation.
I mean...I know what they mean. but I don't remember seeing them in the installation instructions here:
https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html#mikrotik-first-install-process

'force' is mentioned once in the Ubiquiti installation instructions.

If you are following instructions from another site, perhaps you should ask for assistance there. ?
If you follow the instructions on arednmesh.org and fail, please re-post here.

I hope this helps,
Chuck

kd2hzg
Chuck, thanks for the reply.

Chuck, thanks for the reply.
Yep pulled the board out of the case to verify (at least the sticker on the board) and when I boot in the .elf it shows the RB952 as well.

So webUI is in reference to the standard "sysupgrade firmware" update process of logging into the webUI of the aredn booted on the .elf and uploading the .bin file through the "Firmware Upgrade Section" as referenced in the doc you linked. Just below that it references a method of copying the .bin file over via SCP and sshing into the AREDN node booted on the .elf and running "sysupgrade" as a utility from the CLI. There are a couple flags that I tried in addtion to the prescribed method there with no luck.

TL;DR I followed the instructions on the link you posted (initially) and it failed. I'm dead in the water with this board.

-Joe Kalfa
 

K6AH
K6AH's picture
It takes a long time to reboot
These particular devices take a long time to reboot and they reboot 2 or 3 times after this sysupgrade.  Be sure to give it at least 10 minutes before trying to reboot it manually or reconnecting to it.

Andre, K6AH
 
kd2hzg
I'll give it another shot,
I'll give it another shot, but I had 2 of the exact same device work perfectly. This one has been powered on continuously since the last attempt and is still on RouterOS.
kd2hzg
So here's a tshark output

So here's a tshark output from the last attempt (after your wait a full 10 minutes advice)
basically at 46 seconds it goes down for reboot with the new firmware, and at 84 seconds the hAP lite comes back online then at 129 seconds you see it identify as running RouterOS.



 6090 44.948751493 74:4d:28:37:9c:28 → ff:ff:ff:ff:ff:ff ARP 60 Who has 192.168.1.10? Tell 192.168.1.1
 6091 44.948808330 d0:67:e5:4d:cd:b9 → 74:4d:28:37:9c:28 ARP 42 192.168.1.10 is at d0:67:e5:4d:cd:b9
 6092 44.949070863  192.168.1.1 → 192.168.1.10 TCP 66 [TCP Keep-Alive] 80 → 45802 [ACK] Seq=73739 Ack=7148689 Win=139648 Len=0 TSval=4294948784 TSecr=3134219395
 6093 44.949124993 192.168.1.10 → 192.168.1.1  TCP 66 [TCP Keep-Alive ACK] 45802 → 80 [ACK] Seq=7148689 Ack=73740 Win=179072 Len=0 TSval=3134224436 TSecr=4294948105
 6094 45.188606848  192.168.1.1 → 192.168.1.10 TCP 66 [TCP Keep-Alive] 80 → 45800 [ACK] Seq=14150 Ack=2651 Win=37536 Len=0 TSval=4294948808 TSecr=3134219635
 6095 45.188670658 192.168.1.10 → 192.168.1.1  TCP 66 [TCP Keep-Alive ACK] 45800 → 80 [ACK] Seq=2651 Ack=14151 Win=64128 Len=0 TSval=3134224675 TSecr=4294948106
 6096 46.481753855  192.168.1.1 → 192.168.1.10 TCP 66 80 → 45802 [FIN, ACK] Seq=73740 Ack=7148689 Win=139648 Len=0 TSval=4294948937 TSecr=3134224436
 6097 46.482009564  192.168.1.1 → 192.168.1.10 TCP 66 80 → 45800 [FIN, ACK] Seq=14151 Ack=2651 Win=37536 Len=0 TSval=4294948937 TSecr=3134224675
 6098 46.482118430 192.168.1.10 → 192.168.1.1  TCP 66 45802 → 80 [FIN, ACK] Seq=7148689 Ack=73741 Win=179072 Len=0 TSval=3134225969 TSecr=4294948937
 6099 46.482219648 192.168.1.10 → 192.168.1.1  TCP 66 45800 → 80 [FIN, ACK] Seq=2651 Ack=14152 Win=64128 Len=0 TSval=3134225969 TSecr=4294948937
 6100 46.482626621  192.168.1.1 → 192.168.1.10 TCP 66 80 → 45802 [ACK] Seq=73741 Ack=7148690 Win=139648 Len=0 TSval=4294948937 TSecr=3134225969
 6101 46.482626671  192.168.1.1 → 192.168.1.10 TCP 66 80 → 45800 [ACK] Seq=14152 Ack=2652 Win=37536 Len=0 TSval=4294948937 TSecr=3134225969
 6102 50.135582127 d0:67:e5:4d:cd:b9 → 74:4d:28:37:9c:28 ARP 42 Who has 192.168.1.1? Tell 192.168.1.10
 6103 50.135851794 74:4d:28:37:9c:28 → d0:67:e5:4d:cd:b9 ARP 60 192.168.1.1 is at 74:4d:28:37:9c:28
 6104 53.371668474 fe80::d267:e5ff:fe4d:cdb9 → ff02::16     ICMPv6 130 Multicast Listener Report Message v2
 6105 54.103651091 fe80::d267:e5ff:fe4d:cdb9 → ff02::16     ICMPv6 130 Multicast Listener Report Message v2
 6106 82.335665423 fe80::d267:e5ff:fe4d:cdb9 → ff02::16     ICMPv6 130 Multicast Listener Report Message v2
 6107 82.383064764 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6108 82.435651847 fe80::d267:e5ff:fe4d:cdb9 → ff02::16     ICMPv6 130 Multicast Listener Report Message v2
 6109 84.110084568 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6110 86.108611448 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6111 88.119597651 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6112 90.121818707 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6113 92.124034150 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6114 94.125316237 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6115 96.127450865 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6116 98.129677145 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6117 100.132571135 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6118 102.134804824 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6119 104.136576649 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6120 106.138760789 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6121 108.140962990 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6122 110.143164745 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6123 112.145326514 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6124 114.146569905 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6125 116.148742615 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6126 118.150882755 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6127 120.153241915 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6128 122.155410319 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6129 124.167304106 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6130 126.169928531 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6131 128.172035775 74:4d:28:36:9c:24 → 01:80:c2:00:00:00 STP 60 RST. Root = 32768/0/74:4d:28:36:9c:23  Cost = 0  Port = 0x8004
 6132 129.387431767 192.168.88.1 → 255.255.255.255 MNDP 168 5678 → 5678 Len=126
 6133 129.387431972 74:4d:28:36:9c:24 → 01:00:0c:cc:cc:cc CDP 111 Device ID: MikroTik  Port ID: bridge/ether3  
 6134 129.387432088 74:4d:28:36:9c:24 → 01:80:c2:00:00:0e LLDP 125 MA/74:4d:28:36:9c:24 IN/bridge/ether3 120 SysN=MikroTik SysD=MikroTik RouterOS 6.47.1 (stable) RB952Ui-5ac2nD

nc8q
nc8q's picture
It takes a long time to reboot after an image upload, upgrade,.
+1
I usually set an 8 minute timer and don't rush to return to check status after the timer expires. ;-)
Alas, this does not seems to fix the issue with Joe's  hAP #3. :-(




 
KD1HA
KD1HA's picture
Maybe I"m missing something
Maybe I"m missing something here but shouldn't you be using factory upgrade for the new device?

Denis
kd2hzg
.elf is the factory upgrade, that boots fine.
So for a "new device" aka one that is running RouterOS, requires bootp to load the .elf file (factory upgrade) before loading the sysupgrade file via either the webUI or scp and running the command from the terminal.
kd2hzg
Bump
Just flashed two more RB912UAGs this morning wtihout issue. Anyone have any ideas?
AB7PA
Sure it's not an hap?

I assume you're certain the device isn't an hAP rather than hAP ac lite?  They are identical from the case, but the hAP is not supported.

kd2hzg
Yep, verified by pulling the
Yep, verified by pulling the board out of the case. Also when it boots from the .elf it identifies as the 952ui-5XX2XX model, so I don't think that's the issue. Good call tho.
KD1HA
KD1HA's picture
You have stumped us all.
You have stumped us all. Maybe you should return it if you can for a new one at this point. 
KB9OIV
I had a hAP AC lite take a

I had a hAP AC lite take a dump on me yesterday.  

Went to reboot, and it never came back.

I re-flashed from scratch with AREDN firmware, and got as far as saving the permanent firmware, but on the final reboot, became unresponsive.

I tried a few more times, but the only time it 'worked' was with the temp firmware at 192.168.1.1.

I then tried reflashing stock Mikrotik, which appeared to flash completely, but that never booted up or responded to 192.168.88.1 stock IP either.

In a last ditch try, I flashed OpenWRT (basicall uses the same method as AREDN), and that did work!

From there, I flashed the 'final' AREDN firmware from within OpenWRT.

When that booted up, the device had really strange IP addresses assigned by AREDN (10.0.0.1/8) or something like that.

Anyway, I then 'reflashed' AREDN again from the AREDN GUI, chosing to not save settings.

Device came back with proper IP's after that.


So, maybe try flashing OpenWRT at least, first?

https://openwrt.org/toh/mikrotik/rb952ui-5ac2nd_hap_ac_lite
 

kd2hzg
Interesting work around
Still no joy. Boots into the bootp .bin file without issue, then uploads the sysupgrade.bin and says everything is good to go. Reboots.....whomp whomp, defaults to mikrotik firmware. I think this is the universe telling me I need to learn RouterOS.
KB9OIV
i.e.:
i.e.:

Use this file in place of the 'elf'
https://downloads.openwrt.org/releases/19.07.8/targets/ar71xx/mikrotik/o...

And this file as the 'final' that you flash within openwrt:

https://downloads.openwrt.org/releases/19.07.8/targets/ar71xx/mikrotik/o...

and then finally, flash the AREDN 'sysupgrade' within OpenWRT.



 
km4eug
Flashing HAP

I tried for 11 hrs testerday to flash the areden  firmware to the hap ac lite the PXE server method and can not get it to load  

bigest issue i see is i change ip[ address of computer to 192.168.88.50 and the PXE should pick up that address  most of the time it would not  reboot and try agian   
a few times i did get the ip address to match but then the HAP  ip address after the upload would still be 192.168.88.1 so i know the aAREDEN tit not take 

what am i missing?  

km4eug@gmail.com
 

AB7PA
Try following these steps in

Try following these steps in the install checklist. No need to change the IP to 192.168.88.x

km4eug
if the haps address is 192
if the haps address is 192.168.88.1 would i not need an ip address in that range?

Yes followed thos instructions it says  row 4 set your computer interface to static in same range of your device.
 
km4eug
this is one set of
this is one set of instructions i am following
AB7PA
You do not need to set your

You do not need to set your computer to an address of 192.168.88.x because your computer is running a PXE server which will automatically provide the hAP ac lite with an IP address in whatever range you choose.  No matter what it was set to before, the hAP ac lite will get a new IP address from your computer's PXE server during the PXEboot process.  The online AREDN install instructions suggest that you use an IP address range of 192.168.1.x because that is the IP segment which the AREDN firmware will eventually require during its NOCALL configuration process immediately after the firmware has been installed.  Using 192.168.1.x simply eliminates the need to change your computer's IP address twice during the install process.  I hope this helps.

K6CCC
K6CCC's picture
Much better instructions for
Much better instructions for initial flashing of Mikrotik devices.  I have done many, and NEVER had this fail.
km4eug
this is the oter set of
this is the oter set of instructions i have tried 
nc8q
nc8q's picture
what am i missing?
It seems that you are missing the AREDN instructions for installing AREDN firmware.
I you want help in this forum, please use the instructions in the documentation on this site.
73, Chuck

 
km4eug
It seems that you are missing
It seems that you are missing the AREDN instructions for installing AREDN firmware.
I you want help in this forum, please use the instructions in the documentation on this site.
73, Chuck

Tell me how to interpret the following step besides (change the ip address to 192.168.88.50 the range the router is in)
This is the check list
this is STEP 4

I did come her looking for help  I came here for some one to fill me in on what i don't understand .
If i knew what I am doing wrong i would not need to ask.
 I have gone thru theses steps  and it has not worked.  X 50 times or more with reboots and ip changes and many other attempts. 

I will follow the instructions and help some of the above post have mentioned 

MY DEVICE is 192.168.88.1 that is the only thing I KNOW ! 

km4eug
 my Settings
 my Settings
Image Attachments: 
K6CCC
K6CCC's picture
Did you set RFC951=1
Did you set RFC951=1 (page 16 of the powerpoint I linked earlier)?
As I recall, it will not work unless you set that.
 
km4eug
This setting was set to
This setting was set to RFC951=1 when i checked it 

 
Did you set RFC951=1

Did you set RFC951=1 (page 16 of the powerpoint I linked earlier)?
As I recall, it will not work unless you set that.

AB7PA
Does your computer static IP match the DHCP addr?

Terry, based on the online AREDN install instructions your PXE server config should look like below, with your computer's static IP address matching the DHCP Server address shown in the first highlighted row.

km4eug
I agree with your statement. 
I agree with your statement.  My PXE does not match, i turn off wireless  set static  reboot. verify static ip address  launch PXE and it dont match 

I am trying with diffrent computer today. 
km4eug
It was already there
It was already there

K6AH
K6AH's picture
Perhaps one of you would be
Perhaps one of you would be willing to zoom call with Bill. Andre
K6CCC
K6CCC's picture
I can do a Zoom or TeamViewer
I can do a Zoom or TeamViewer call with him.
Also note that if you have more than one network connection (for example wired and WiFi), turn OFF any that are not being used for this operation.

 
km4eug
Team Viewer  
Team Viewer  

828 619 514
ve7f6pnf

Ham Shack Hotline 6100000423



ve7f6pnf
km4eug
email if you need to send me
email if you need to send me a link   km4eug@gmail.com
Cell 7313942028
KI5OOH
zero memory
I just wanted to throw this out there.  I bought four of these devices from an Ebay seller last month.  Three of them flashed fine, the other will not.

That being said, I believe it has a hardware issue.  When I boot into the .elf firmware it shows there is no available flash memory.  I'm thinking the chip itself is defective.

Throwing this out there for the original poster.  Sometimes pieces and parts go bad.

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer