Reply
New Member
Posts: 19
Registered: ‎07-27-2015
Kudos: 12

5.6.2 TFTP ERROR

[ Edited ]

I have been uploading Gargoyle firmware onto AirOS versions 5.5.8 and 5.5.10.  With the new version of AirOS 5.6.2 I uploaded Gargoyle version 1.6.2, but the webpages looked very strange and settings were not being saved.  So I put the Bullet M2 into recovery mode and TFTP'ed the AirOS 5.6.2 image and the transfer was successful.  However, the unit now just keeps resetting itself. 

 

So I put the unit in recovery mode again and attempted to TFTP the AirOS 5.5.8 image.  However, I got some error saying that firmware check failed.

 

How can I successfully re-load an AirOS firmware image onto a Bullet M2???

New Member
Posts: 19
Registered: ‎07-27-2015
Kudos: 12

Re: 5.6.2 TFTP ERROR

Are any Bullet M2's / Pico Station M2's being shipped from the factory with this verson of firmware?

 

I recently bought some more devices and they all came with XM version v5.5.8.

 

 

New Member
Posts: 2
Registered: ‎07-28-2015
Kudos: 1

Re: 5.6.2 TFTP ERROR

I have the same error in the tftp recovery mode..this is after i try to flash openwrt  over airos gui.

i try differnt images no possible flash airos or openwrt. Only dd-wrt image is possible to flash.

 

what ca i do ?

New Member
Posts: 19
Registered: ‎07-27-2015
Kudos: 12

Re: 5.6.2 TFTP ERROR

I plugged in a serial cable and the device just keeps resetting itself. After it goes to booting... it just keeps starting over.  Does any one know any diagnostics I can try to find the root of the problem?

 

 

Its just keeps repeating this sequence:

 

U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50)

DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Board: Ubiquiti Networks XM board (rev 1.0 e202)
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS Ubiquiti Linux-2.6.32.65
Created: 2015-07-16 9:01:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1004345 Bytes = 980.8 kB
Load Address: 80002000
Entry Point: 80002000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK

Starting kernel ...

Booting...

New Member
Posts: 19
Registered: ‎07-27-2015
Kudos: 12

Re: 5.6.2 TFTP ERROR

Here's the result of the iminfo command, which says --- print header information for application image

 

ar7240> iminfo

## Checking Image at 81000000 ...
Bad Magic Number

New Member
Posts: 19
Registered: ‎07-27-2015
Kudos: 12

Re: 5.6.2 TFTP ERROR

I'm guessing this issue has to do with the new version of U-Boot being loaded with the 5.6.2 firmware version.

 

For firmware versions 5.5.8 and 5.5.10 the U-Boot is: U-Boot 1.1.4.2-s594 (Dec  5 2012 - 15:23:07)

 

Here is the mtdparts command result for 5.5.8 and 5.5.10

 

U-Boot 1.1.4.2-s594 (Dec  5 2012 - 15:23:07)

device nor0 <ar7240-nor0>, # parts = 6
#: name                 size                       offset      mask_flags
0: u-boot          0x00040000             0x00000000      0
1: u-boot-env    0x00010000             0x00040000      0
2: kernel          0x00100000             0x00050000      0
3: rootfs          0x00660000              0x00150000      0
4: cfg              0x00040000             0x007b0000      0
5: EEPROM    0x00010000             0x007f0000       0

active partition: nor0,0 - (u-boot) 0x00040000 @ 0x00000000

 

Now for the 5.6.2 firmware version the U-Boot version is: U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50)

 

Here is the mtdparts command result for 5.6.2

 

U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50)

device nor0 <ar7240-nor0>, # parts = 6
#: name              size                    offset          mask_flags
0: u-boot         0x00040000         0x00000000           0
1: u-boot-env   0x00010000         0x00040000           0
2: kernel         0x00100000         0x00050000           0
3: rootfs         0x005a0000         0x00150000          0
4: cfg             0x00040000         0x006f0000           0
5: EEPROM   0x00010000         0x00730000           0

active partition: nor0,0 - (u-boot) 0x00040000 @ 0x00000000

 

The Red and Bold indicates that these partitions are different.  I'm guessing this is the cause of all my problems.  Does anyone have any comments on how to get gargoyle / openwrt loaded successfully on this device?

New Member
Posts: 19
Registered: ‎07-27-2015
Kudos: 12

Re: 5.6.2 TFTP ERROR

SOLUTION:   DO NOT UPLOAD OPENWRT TO FIRMWARE VERSION 5.6.2.  INSTEAD, FIRST LOAD AN OLDER VERSION OF FIRMWARE, ex: 5.5.10, AND THEN UPLOAD OPENWRT.

New Member
Posts: 2
Registered: ‎07-28-2015
Kudos: 1

Re: 5.6.2 TFTP ERROR

but for me, its to late.

 

I have try flash openwrt from 5.6.2 !!! Now isnt possible flash any airos!! the u-boot is the new one.

It's a way to bring back to the old u-boot ?

 

with a serial-ttl console, can flash an new openwrt image, but is'nt possible save any configuration...

 

Any idea's

New Member
Posts: 3
Registered: ‎08-07-2015

Re: 5.6.2 TFTP ERROR

From console type "mtdparts default"

 

type urescue

 

tftp of versions 5.6.2 succeed but it was still in a boot loop. the older firmwares failed to flash

I tried openwrt and it worked.

I used "openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin" for Picostation M2-HP

 

I'm still trying to get the stock firmware back on mine but that gets you unbricked

 

 

 

New Member
Posts: 19
Registered: ‎07-27-2015
Kudos: 12

Re: 5.6.2 TFTP ERROR

Revek, is the openwrt firmware stable? I was successfully able to load gargoyle firmware via urescue from 5.6.2 , but whenever I turned off the device it didn't remember any of my settings. Everything would go back to default. I believe this was due to the different address location of the cfg section.
New Member
Posts: 3
Registered: ‎08-07-2015

Re: 5.6.2 TFTP ERROR

I don't know how stable it is but we are going to deploy three of them in local city parks.  AirOS doesn't have the ability to schdule access so it wouldn't work as is for our deployment.  We needed something with content filtering and would automatally shutoff access at night. 

New Member
Posts: 3
Registered: ‎08-07-2015

Re: 5.6.2 TFTP ERROR

[ Edited ]

Oh and it doesn't retain settings.

I used this version of openwrt "OpenWrt Barrier Breaker 14.07 / LuCI Trunk (0.12+svn-r10530)"

What i have discovered is that mtdpart default changes the environment variable to

mtdparts=mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),1024k(kernel),6528k(rootfs),256k(cfg),64k(EEPROM)

This matches the old uboot settings.  I tried to saveenv command but its is changed back at the next reboot

mtdparts=mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),1024k(kernel),5760k(rootfs),256k(cfg),64k(EEPROM)

 

New Member
Posts: 19
Registered: ‎07-27-2015
Kudos: 12

Re: 5.6.2 TFTP ERROR

Revek, I guess that's what I meant by "stable."  If openwrt reverts back to its default settings upon reboot I would classify that as un-stable, but I may be incorrect in my definition.  

 

My guess for getting this to work properly is to overwrite that newer 2015 U-Boot version with the 2012 U-Boot version.  Even though you are changing the partitions, I think when it loads that 2015 U-Boot version it reverts back.

 

The v5.5.10 AirOS can overwrite the U-Boot sector with the older version. If you try the "urescue" command and upload the v5.5.10 AirOS image and THEN upload the OpenWRT image, will that work?

New Member
Posts: 5
Registered: ‎09-07-2015

Re: 5.6.2 TFTP ERROR

on my Loco M2 unit this would not work, as the flash procedure would complain that there is no partition after rootfs.

 

As described in my other post the flash layout has been changed with the new u-boot version and the new version also has a bug that prevents it from keeping settings; also the upgrade procedure does not seem to correctly copy the cfg and EEPROM partitions and that causes additional issues.

 

Does anybody have a custom firmware (Ubnt, Openwrt etc. does not matter) ready that makes the u-boot partition writeable? I would load that firmware just to downgrade the u-boot bootloader again (from u-boot itself it is not possible; from within AirOS after having upgraded the u-boot it is also not possible as it complains about the missing partition after rootfs).

New Member
Posts: 16
Registered: ‎01-26-2015

Re: 5.6.2 TFTP ERROR

Try to transfer fw 5.6.2, use tftp recovery mode.

It will automatically connect to AP when ssid=ubnt as default. So you will need another device, configure it as AP bridge.

Probable through the wireless interface you can access GUI/webinterface of your device and you can downgrade it to 5.5.10.

Good luck! Please read this post 

New Member
Posts: 19
Registered: ‎07-27-2015
Kudos: 12

Re: 5.6.2 TFTP ERROR

Attee,

 

I have transferred fw 5.6.2 after uploading Gargoyle 1.6.2.  Now, the device is in a reboot-loop. However, I can get the device in a tftp-recovery mode.  I have another UBNT bullet m2 setup as an AP in bridge mode.  The SSID is ubnt, but my other bullet won't connect to it even when I put that broken bullet in the TFTP recovery mode.

 

Is there a step I'm missing?

 

New Member
Posts: 8
Registered: ‎08-12-2013

Re: 5.6.2 TFTP ERROR

[ Edited ]
 
New Member
Posts: 6
Registered: ‎04-14-2015
Solutions: 1

Re: 5.6.2 TFTP ERROR

Anyone know where the location of GND, TX, RX pin in BM2-Ti.

My BM2-Ti brick after

I install latest OpenWrt from AirOS 5.6.3. The OS running but I can't access GUI.

It said not enough memory.

I think maybe if I downgrade using older OpenWrt, it would run.

I try to downgrade using tftp.

Here the problem happen. It can't get ip at all

I try to convert to AirOS 5.6.3 and 5.6.2. It success but no ip at all

Try to convert to 5.5 will give error firmware check failed

 

Based on my research, I think I need serial connection to my BM2-Ti, but I don't where the pin location is.

 

tq

New Member
Posts: 8
Registered: ‎08-12-2013

Re: 5.6.2 TFTP ERROR

you most open your device case and use USB TTL cable for recovery........

 

anyway after boot to u-boot and force downgrade bootloader with this command:

urescue -f -e

now you'r device going to tftp recovery mode 

transfare v5.5.11 with tftp client to your device

Good luck and sorry for bad english

Member
Posts: 214
Registered: ‎01-20-2012
Kudos: 33
Solutions: 2

Re: 5.6.2 TFTP ERROR

I had this problem on a couple Nanostation M2 and in the end to be able to acces the ubnt browser gui I had to use a USB TTL as sajadm posted but I had do it in this order.

 

stop boot at uboot

urescue -f -e
tftp v 5.5.11 to 192.168.1.20
reboot

 

stop boot at uboot
urescue -f -e
tftp v 5.6.3.2 to 192.168.1.20
reboot

 

You should then be able to access the browser gui
gui flash back to 5.5.11

 

Anything below 5.11 won't tftp or browser gui flash

 

What I need is an exact list of specific unknown problems we might encounter.
Reply