You are here

Bullet M5 XM TFTP stops when trying to upload firmware

20 posts / 0 new
Last post
N4RT
N4RT's picture
Bullet M5 XM TFTP stops when trying to upload firmware
Need some help to figure out what I'm doing wrong.

I have successfully flashed other M5 devices including those with XW chip sets.  This is a Bullet M5 with XM chip set running AirOS 6.1.9.

I can put the Bullet in TFTP mode with alternating LEDs as expected and I am using the Windows 10 TFTP client to transfer the 3.18.9.0 firmware.  As soon as I hit the enter key after typing in the TFTP command string, the alternating LEDs on the Bullet STOP and it just sits there.

I can remove power by disconnecting the Ethernet cable from the POE and then reconnect the Ethernet cable and the Bullet boots up again just fine with the AirOS intact and I can again put it in TFTP mode but the same thing happens each time I attempt to load the firmware using TFTP.

Has anyone run into this before and how did you fix it?

73,

Ron  N4RT
 
AE6XE
AE6XE's picture
Place a dumb switch in the
Place a dumb switch in the middle can make symptoms like this go away.   Make sure the bullet is ping'able at 192.168.1.20 before starting the tftp command.  If not, something is wrong. 
N4RT
N4RT's picture
Bullet M5 TFTP Issue

I can put the Bullet M5 in TFTP mode and can ping it from the CMD screen on the host computer.  But when I execute the TFTP command, the Bullet acts like it is trying to load (rapidly flashing green LED) for about a half second then it stops and appears to be locked up.  At that point, after a few seconds, the TFTP command times out on the host computer and I get a prompt back again.  The TFTP alternating light pattern starts up again and I can still ping 192.168.1.20.  Try it again and again and the same thing happens.

I'll try the dumb switch idea and see what happens.

73,

Ron N4RT
AE6XE
AE6XE's picture
There should be tftp client
There should be tftp client options to "trace" and "-v" verbose mode to see a lot more details of what is happening -- can point in the right direction.  Triple check the binary option is set.  I use the linux tftp command line, so not as familiar with the windows clients. 
N4RT
N4RT's picture
Bullet M5 TFTP Issues
Well, I'll be doggoned... the dumb switch idea worked!!!  Who was the mastermind that originally came up with that idea?  I don't understand why it made a difference but I was successful getting the node flashed by putting a switch between the computer and the LAN port on the POE adapter.  Amazing!

But now, when I try to configure the NO CALL screen and save changes, it reverts right back to the NO CALL configuration.

I think I've seen other folk's messages in the forums with that same situation but not sure what they did to fix it.  Any help with that problem would be appreciated but I'll also do some research in the forums.

Thanks for the dumb switch idea... crazy that it worked!

73,

Ron N4RT
K6CCC
K6CCC's picture
Not as crazy as it sounds.  I
Not as crazy as it sounds.  I think the logic is that with a direct connection the computer sees interruptions of the LAN port and it can’t handle it.  With a dumb switch in between, the port never goes away to the computer because it is live between the computer and the switch.
 
N4RT
N4RT's picture
Now Bullet M5 won't keep configuration
Ok, now I have successfully flashed this Bullet M5 XM with the 3.19.9.0 firmware and I get the NOCALL configuration screen.  However, when I configure it with my Call and other settings and hit the SAVE button, it reboots but never comes back to the node status page in the browser.  Also, the Ethernet port seems to stop working after the reboot cycle.  If I power cycle the Bullet, it comes up again in the NOCALL condition... did not save any new configuration. 

I've tried the dumb switch trick, and four different browsers all with the same result.  Help!!  I've run out of ideas.  This has been a problem node from the beginning.

73,

Ron
N4RT
N4RT's picture
I meant 3.18.9.0 firmware...
I meant 3.18.9.0 firmware... sorry.
AE6XE
AE6XE's picture
The computer has a 192.168.1
The computer has a 192.168.1.x address when loading the firmware and going into setup.  After the save and reboot, be sure to change the computer back to dhcp mode and look for it to get a 10.x.x.x address.   
N4RT
N4RT's picture
Yes, I am aware of that. 
Yes, I am aware of that.  Computer is set to obtain an IP address automatically and gets an IP address from the node.  But, it's not getting a 10.X.X.X address, it is still getting a 192.168.1.X address (.21 to be exact).  The node seems to have 192.168.1.1 even though the setup screen shows me 10.X.X.X addresses.  The DHCP seems to be screwed up.

Makes no difference which browser I use or if the dumb switch is between the computer and the LAN port on the POE adapter.  I've never run into this before and I've flashed a lot of nodes.

73,
Ron
AE6XE
AE6XE's picture
From setup->Administration,
From setup->Administration, can you grab a support download?   Connect via DtDlink, RF, or on LAN?
K6AH
K6AH's picture
Same thing happened to me...
I saw the same thing happen while AI6BX and I were installing San Marcos Pk this past Sunday.  We never could get it going until Keith got it down off the mountain and TFTP reloaded it.

Andre
N4RT
N4RT's picture
Hi Andre,
Hi Andre,

I tried another TFTP attempt to reload the factory bin but still get the same result.  It seems to be coming up with an IP address of 192.168.1.1 and my computer takes an address of 192.168.1.21 when the node is in the NOCALL condition.  So, even though the bullet is flashed with the AREDN firmware, DHCP is not issuing addresses in the 10.x.x.x block.  I can ping 192.168.1.1 and it responds.

For Joe:  I sent you the support data downloaded when the node is in this condition.

Ron
N4RT
N4RT's picture
Here's the support data file,
Here's the support data file, Joe:
Support File Attachments: 
AE6XE
AE6XE's picture
I'm not finding a smoking gun
I'm not finding a smoking gun in the support data file yet.  It looks like a typical firstboot situation.  The Bullet M5 is expected to boot up with 192.168.1.1 address and give your computer a 192.168.1.x address.   It is expected when looking in basic setup to see the (proposed) IP address of 10.x.x.x for the wifi.    After typing in your callsign, channel #, channel width, and other settings...  when you "save settings", what happens?   What is displayed or is it an empty browser window with white screen and eventually times out?    I'm looking to confirm there was a message that says it is rebooting, wait a few minutes, renew your IP address, etc.  Did this happen?

Joe AE6XE
N4RT
N4RT's picture
Yes, Joe... all that happens.
Yes, Joe... all that happens.  After I configure the node with callsign, etc, I "save changes" and I immediately get the screen that says the changes are being saved and the node is rebooting.  But, it sits there forever.  After more than three minutes, I click on the link to local node and it comes up and says that the site can't be found.  So, I type in the browser http://localnode:8080 and up comes the NOCALL page with all the same information as I started with.  It does not take the configuration changes.

Again, it seems that the DHCP is never issuing a 10.x.x.x address even though it tells me on the setup page what those address are.  I've tried pinging the 10.33.82.81 address that the node says it's using but it times out and can't be reached.  If I ping 192.168.1.1 I get good responses.

Ron
w6bi
w6bi's picture
IP address change.
The node won't issue DHCP 10.x.x.x addresses until AFTER it's been configured and that configuration has been saved.  So you're still on a 192.168.x.x address and it stands to reason you can't ping the 10.33.82.81 address.   Don't know if that helps any; you still need to find out why you Save Changes, reboot and it doesn't save them.

Orv W6BI
N4RT
N4RT's picture
Well, yes, I know that.  Of
Well, yes, I know that.  Of course, I understand that I can't ping the 10.x.x.x address because it never saves the configuration changes.  The whole issue now is why doesn't it "Save Changes?"

I have no clue.  Maybe someone can take this issue beyond that step?  I've spent a lot of time getting this far but, so far, no one has offered any real solutions.  Surely, I am not the only one who has run into this problem.

I've ordered another Bullet M5, so can put this on the back burner.  But, am still concerned that the advertised firmware doesn't appear to work on all hardware.  To me, that is the bigger concern!

73,

Ron
AE6XE
AE6XE's picture
Yea, it sure sounds like the
Yea, it sure sounds like the save settings is failing to write the settings to flash.     Unfortunately, the symptoms are not being seen elsewhere, or otherwise reproduced, so not sure how to assist at this point.   If you want, mail the device to my QRZ address, I could further investigate.

Joe AE6XE   






 
N4RT
N4RT's picture
Joe,
Joe,

I appreciate your offer to look at this one and I'll get it in the mail to you ASAP.  It is not doing me any good as it is and maybe you can figure out why the settings aren't being saved.  That might help someone else out down the road.

73,

Ron

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer