You are here

Home » Forums » General discussion

Nightly Build Clarification

7 posts / 0 new
Log in or register to post comments
Last post
Tue, 08/07/2018 - 13:51
#1
KI6CVM
Nightly Build Clarification

I have a new NanoStation loco M2 (XW) running v5.6.15. I understand it can't be downgrade to v5.5 and thus I can't use the stable release. My understanding is I must install a nightly build using the TFTP method.

I have located the TFTP instructions here https://www.arednmesh.org/content/uploading-firmware-ubiquiti

There are two different paths to nightly builds and I am unclear on the proper build to use.

Path 1
"Software" --> "Nightly Builds" --> "Ubiquiti" brings me here http://downloads.arednmesh.org/snapshots/trunk/targets/ar71xx/generic/
This path has a number of "factory" or "sysupgrade" bin files. 

Path 2
"Software" --> "Downloads" --> "Click here for downloads" --> "Nightly Builds" brings me here http://downloads.arednmesh.org/snapshots/trunk/
This is simply a directly structure.

Can I get clarification on the proper path I should be using?

Thanks in advance.

-JP
 

Top
Tue, 08/07/2018 - 14:35
K6AH
K6AH's picture
Follow the instructions detailed on the web site...

Follow the instructions detailed on the web site menu at Software/Nightly Builds
(​https://www.arednmesh.org/content/nightly-builds).

Be sure to read the README file (http://downloads.arednmesh.org/snapshots/trunk/readme.md) to determine which load is intended for your device.  They are often not intuitive.

Andre

 

Top
Tue, 08/07/2018 - 15:31
AE6XE
AE6XE's picture
JP,  what is the "test date"
JP,  what is the "test date" on the packaging of the loco M2 XW you recently received?    There are some changes that will appear in the README of the next nightlybuild for a new hardware revision of this device.    We've discovered Ubiquiti started shipping this new revision with test dates as early as Nov 2017.   If you have one of these devices, then you'll need to load the "rocket-m-xw" factory image with tftp to get started.   If this is the older hardware version, then you'll need to tftp load the "loco-m-xw" factory image.     The model #, etc. is all the same, only known way to determine which hardware version in advance is by opening the cover and inspecting the chips or by inspecting linux log files under AirOS from the command line. 

Joe AE6XE
Top
Tue, 08/07/2018 - 16:17
(Reply to #3)
KI6CVM
Test date is 05/09/18. 

Test date is 05/09/18. 

I did see the note about using the Rocket image. 

To confirm I should TFTP "

aredn-120-22e4557-4f30825-ubnt-rocket-m-xw-factory.bin
 

" to the root of the device using the TFTP instructions?

Thanks,
-JP

Top
Tue, 08/07/2018 - 16:47
(Reply to #4)
AE6XE
AE6XE's picture
Yes, that is correct.
Yes, that is correct.

Joe AE6XE
Top
Tue, 08/07/2018 - 19:53
(Reply to #5)
KI6CVM
I wanted to share an update.
I wanted to share an update. The "rocket XW" firmware as suggested did NOT work. I tried the "loco XW" and it is working.

The symptom when using the "rocket XW" FW was no Ethernet. The PC directly attached showed no link. It would not grab an address from DHCP and with a static address I could not ping .22 or .1. 

To confirm my test date is 05/09/18 so possibly UBNT reverted back to the previous hardware or there is something unique to the late 2017 M2 loco devices. 
Top
Tue, 08/07/2018 - 21:33
(Reply to #6)
AE6XE
AE6XE's picture
The prior work with AREDN
The prior work with AREDN firmware was on a loco M5 XW with test date of Nov 2017.  This device succeeded with the Rocket-m-xw image.   The idea that the same hardware change has occurred on the loco M2 XW comes from an openwrt post.  The ethernet did not work with the loco-m-xw image for a newer device.   It had not been confirmed that the M2 has the same hardware revision and your results now confirm that something else was going on with the loco M2 XW, it still has the AR8032 ethernet chip and does not have a hardware revision.     

Do keep an eye out on both M2 and M5 XW loco, AirGrid M5 XW model, and maybe other XW models with the AR8032 chip for the ethernet port to stop working at some point (after working for hours or days).  Basically, any model using the loco-m-xw image.   The release notes of  the ~Aug 1st release of Openwrt 18.06.0, which we are based upon, indicated that a fix had accidentally been left out.  This is probably what was occurring with that openwrt post.   

It's unclear at what point this fix was not carried forward and dropped from our nightly builds, but we'll manually add that in the nightly build in the next few days (probably this weekend when I arrive back home).

Joe AE6XE
Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer