You are here

Home » Forums » Hardware » Nodes

BULLET BM2 FIRMWARE DOWNGRADE

5 posts / 0 new
Log in or register to post comments
Last post
Fri, 04/03/2020 - 17:40
#1
VA3QT
BULLET BM2 FIRMWARE DOWNGRADE

I've an "old" Bullet BM2-HP  that I converted some 4 years ago.  It's since been in storage for quite awhile.  I connected it to a Win7 laptop, logged into "localnode ..." and up came the GUI as expected.  Trusting neophyte that I am, and having successfully updated a pair of AirRouters, I tried to update the Bullet.  It failed and gave every appearance of being locked up.  Of course I failed to write down the
AREDN firmware version number I had put on it.

Put the laptop Ethernet port into static IP 192.168.1.20.  No joy.  Could one of the more expert hams offer guidance on how to proceed forward?

73

Ian VA3QT
   
 

Top
Fri, 04/03/2020 - 17:52
K6CCC
K6CCC's picture
Use the AR71xx version

Follow the TFTP procedure as if it was a brand new node.  Make sure you use the AR71XX version and not the ATH79 version.  I have found that on a pair of NanoBridges (which also use the Bullet firmware) that they will get bricked 100% of the time if using the ATH79 version of the firmware.
 

Top
Fri, 04/03/2020 - 18:10
(Reply to #2)
K6AH
K6AH's picture
Definition of "Bricked"
The term "bricked" is used loosely here.  Normally the term is used to describe a device that has become completely unable to function, on a permanent basis.  Historically, this occurs only in a very small number of these cases... and I don't believe is the case here.
Top
Fri, 04/03/2020 - 18:54
(Reply to #3)
K5DLQ
K5DLQ's picture
CORRECTION: the Bullet M2 is
CORRECTION: the Bullet M2 is supported on the ath79 architecture.
the Nanobridge is supported on the ar71xx architecure
Always check the downloads page for your device.
Top
Sun, 04/05/2020 - 20:45
VA3QT
Bullet M2 IP
Thank-you for the comments.  Have gone back through the steps but still a little confused.  Major stumbling block at this point is I can't "talk" to the Bullet using IP 192.168.1.20.  Could someone verify that that is the right IP to use as the adapter static address.  I'm using 255.255.255.0 for the subnet.  I'm using the same IP address for the Default Gateway and Preferred DNS server.  I'm finding conflicting instructions which IP to use on the browser.  Please don't assume I know what I'm doing, you don't need to be gentle ;-)

73,

Ian VA3QT
Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer