any word on when a flash might be available for the XW?
It's getting increasingly difficult to find these new (and even used) that are XM.
Tim
It's getting increasingly difficult to find these new (and even used) that are XM.
Tim
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
According to that bountysource link, this problem does not affect
"M5 High-Power XW devices"
which I suppose means the Rocket M5 XW
or is that incorrect?
Thanks.
So yep still there, just only so much of me to go around :)
PS: Sorry haven't acknowledged some of your emails been a hectic month for me.
Thanks,
Keith - AI6BX
Thank you,
Ken
We have been putting in some debug code to help validate what we think we know. We are finding variations in the chipset configuration between different XW devices. One of the issues is that the symptom on the Rocket XW does not show up very often, like days and weeks timeframe to appear. On the NS Loco M5 XW it can show up in hours.
Hence if you have easy access (on your roof), you might only need to power cycle it every few weeks when the port locks up to use the Rocket XW. Not a good idea at a remote tower site. The image is located with the nightly builds recently made available.
We may be soliciting everyone's help at some point to zero in on a fix and scale up to get debug data or test the fix. Waiting weeks for the symptom to trigger is problematic.
Joe AE6XE
Let me know, David
KE6UPI
David
Joe AE6XE
Left click - return to home unit in same window/tab. Right click - open up new Tab with "home" node.
Trying to flash a Rocket M5 and got the firmware image check failed code -6 error. Looking at this thread, haven't seen any update since January 2017. SSH'ing into the node the prompt shows XW.v5.5.10-u2. If I use the nightly build version of code and things go south, can I revert the version?
BTW, I did use the utility, backed up the partition, backleveled the software and got the error trying to load the AREN software for AREDN-3.16.1.1-ubnt-nano-m-squashfs-factory.bin.
The error is expected loading the nono-m-squashfs-factory.bin image. The AREDN firmware for the Rocket M5 XW device is included in the current 3.17.1.0RC1 (Release candidate):
Factory image (to upload from AirOS UI) or tftp method: http://downloads.aredn.org/firmware/ubnt/AREDN-3.17.1.0RC1-ubnt-rocket-m...
Joe AE6XE
Thank you Gentlemen! I loaded the release candidate and it's all configured. Comm testing comes next, but the node itself is flashed and configured.
I'm guessing there is no sysupgrade firmware version to load as I did with the other three nodes, correct?
Thanks again! I really appreciate the help!
You need the rocketxw sysupgrade code. It should go like a champ with 3.17.1.0RC1
I'm guessing there is no sysupgrade firmware version to load as I did with the other three nodes, correct?
Thanks again! I really appreciate the help!
I tried to update my Rocket XW from ORC1 factory to ORC1 sysupgrade and ran into a problem. First, the update doesn't behave at the UI like the others I've flashed to 3.16.1.1 in that one picks the firmware to upload, uploads it, then tells the node to apply it. In this case it uploaded it and immediately started to apply it and bricked. I ended up with light 1 green, light 3 red, and unable to ping the node. Powering off and back on didn't help.
The good thing that happened is that I learned how to use tftp to recover the node. I have to say that holding a paper clip on the reset button with one hand while plugging in an RJ-54 into the POE port of the power injector with the other is an interesting exercise!
Figuring that I must have done something wrong I did it again, got the same behavior and it's bricked again so now I have to recover it. Again.
Am I indeed doing something wrong or is there a bug in the sysupgrade ORC1?
I also got carried away flashing an airRouter and forgot to run the test program first. Oops! I'm going to try to apply the 5.5 AirOS to it, but if you have any additional information on that I'd love to hear it.
OK, off to recovering my Rocket XW!
Rich
KC7ZDM
Start from AirOS: upload and only use the 'factory' image of the AREDN firmware.
Start from AREDN: upload and only use the 'sysupgrade' image
tftp: only use the 'factory' image
If you are running AREDN 3.17.1.0RC1 and uploaded the sysupgrade image, it should work, but the end result would be the same as the starting point (with keep settings).
Joe AE6XE
Here are the steps I used to upgrade and recover:
I flashed the Rocket XW node last week with AREDN-3.17.1.0RC1-ubnt-rocket-m-xw-squashfs-factory.bin. Realized this week that I hadn't applied the sysupgrade software (hadn't checked last week to see if it existed as I took the link from a post to me in this thread). Since it did, last night I applied AREDN-3.17.1.0RC1-ubnt-rocket-m-squashfs-sysupgrade.bin and it bricked. That's where things were different.
Normally one uploads the bin file and get's a prompt to apply it. If it fails to upload then you don't apply it. Must be a change to the UI with the ORC1 release.
When recovering the node, which I have now done for the second time, I executed:
tftp -i 192.168.1.20 put AREDN-3.17.1.0RC1-ubnt-rocket-m-xw-squashfs-factory.bin and the node was recovered. I've now reconfigured. Didn't lose much because I really hadn't done anything with the node yet.
I'm unclear on a point: are you saying the sysupgrade isn't needed? That doesn't seem right or AREDN wouldn't have put it out there, right?
Cheers!
You correctly loaded the ...rocket-m-xw-squash-factory.bin when loading from AirOS. (You were done after that.)
FROM THIS POINT ON, for this node... USE the "sysupgrade" version for any future update.
if you decide to apply another version of AREDN, (which there is no later one from the one you just loaded, btw), you need to use the ...rocket-m-xw-squash
fs-sysupgrade.bin. It appears that you loaded the non-xw version, which, obviously, would not work on an XW device.
hope that clears it up.
After reading your comment I went back to the download page, clicked the ORC1 link, and scrolled up tio the row that calls out PowerBeam and Rocket M5 (XW). That shows a sysupgrade version. I copied the link: http://downloads.aredn.org/firmware/ubnt/AREDN-3.17.1.0RC1-ubnt-rocket-m-xw-squashfs-sysupgrade.bin. If that's an incorrect version then shouldn't it be taken down off the page? I'm having trouble figuring out where I went wrong.
I very much appreciate all the help you guys have given me on this.
Do you have any ideas on my AirRouter HP? I most definatly messed up on that. I got carried away and flashed it before checking it with the U-Boot test program. Oops! I've successfully tftp'd AirOS 6 to it, but the DHCP server isn't working. I tried tftp-ing the XM 5.5 firmware but never got a successful completion message.
For the AirRouter, tftp the AirOS firmware. If it is not functional, and you are sure the right AirOS frimware was uploaded, then it may be bricked to the point it requires a special procedure. This procedure has been tested on an AirRouter: http://bloodhound.aredn.org/products/AREDN/wiki/HowTo/Unbrick
Joe AE6XE
Thanks for the link! I'm wondering if this shouldn't be moved to another thread, but I'll ask my question here anyhow. I don't have all I need for this yet, but do you think this AdaFruit cable will do the trick? I do have some Pi's and have been longing for a reason to buy the cute little 7" touchscreen and display case (plus another Pi wouldn't come amiss!). Not that I need another one but this might be just the excuse I needed. Here's the link:
https://www.adafruit.com/product/954
Besides, I love AdaFruit. I've never had better customer service anywhere and their tutorials are top-notch. I also have a couple of Windows 10 laptops including a Surface Pro 4 that I could "make do" with if I just had to. :) All kidding aside, I love my Surface! It boots Windows 10 so fast I never use sleep or hibernate. I just shut down and boot up when I want to use it next. 15 seconds max. The SSD and I7 combination doesn't hurt a bit.
Joe AE6XE