Upcoming Maintenance Alert:

The UBNT Community will be upgraded at 5pm MDT on April 25th. During this time the community forums will be set to read-only status.

Learn more

×
Reply
Highlighted
New Member
Posts: 20
Registered: ‎10-31-2012
Kudos: 1

Problem with U-Boot BAD DATA CRC

One of our Unifi device has failed on firmware upgrade.

 

I tried to fixed with urescue using the newest unfi firmware but I just can't get rid off BAD DATA CRC message:

 

Is there any way to fix this ?

 

see below:

 

ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: checksum bad
checksum bad
-
Receiving file from 192.168.1.22:53745
Received 5025705 bytes
Firmware Version: BZ.ar7240.v3.1.2.2175.130529.1047
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:
        erasing range 0x9F050000..0x9F13FFFF: ............... done
Erased 15 sectors
        writing to address 0x9f050000, length 0x000f0000 ...
write addr: 9f050000
Copying partition 'rootfs' to flash memory:
        erasing range 0x9F150000..0x9F52FFFF: .............................................................. done
Erased 62 sectors
        writing to address 0x9f150000, length 0x003e0000 ...
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-gb7ed2513 (Sep  8 2011 - 13:54:33)

Board: Ubiquiti Networks AR7241 board (e502.0101.002e)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.32.33
   Created:      2013-05-29  17:54:18 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    962001 Bytes = 939.5 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...Bad Data CRC
ar7240>

 

 

Ubiquiti Employee
Posts: 299
Registered: ‎01-18-2011
Kudos: 105
Solutions: 21

Re: Problem with U-Boot BAD DATA CRC

Hi, 

 

If you tried it several times and got same CRC error message, that means something's wrong on flash IO from u-boot.

That may come from some hardware issue, can't be fixed from software side.

 

-KM

New Member
Posts: 20
Registered: ‎10-31-2012
Kudos: 1

Re: Problem with U-Boot BAD DATA CRC

Hi !

 

I saw later in this topic

 

http://community.ubnt.com/t5/UniFi/RESOLVED-UniFi-AP-Firmware-1-3-3-Won-t-Upgrade/m-p/265757#M14186

 

That there was some problem with U-Boot checksum calculation.

 

I thought the problem is the same.

 

Are you absolutely sure that this is HW related error ?

 

 

 

Ubiquiti Employee
Posts: 299
Registered: ‎01-18-2011
Kudos: 105
Solutions: 21

Re: Problem with U-Boot BAD DATA CRC

Hi,

That link shows CRC error on u-boot environment partition, yours is CRC error on Linux kernel.
They are not the same issue.

-KM
New Member
Posts: 1
Registered: ‎09-19-2013

Re: Problem with U-Boot BAD DATA CRC

I'm also with this problem. Any idea? Thanks to all.

U-Boot unifi-v1.2.1.71-g529c499d (Dec 21 2012 - 12:50:21)

Board: Ubiquiti Networks AR7241 board (e512-6.0101.002e)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.15-5.2
   Created:      2012-12-21  21:40:43 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    729741 Bytes = 712.6 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...Bad Data CRC
ar7240>

 

Emerging Member
Posts: 48
Registered: ‎03-09-2014
Kudos: 14

Re: Problem with U-Boot BAD DATA CRC


shunt wrote:

I'm also with this problem. Any idea? Thanks to all.

U-Boot unifi-v1.2.1.71-g529c499d (Dec 21 2012 - 12:50:21)

Board: Ubiquiti Networks AR7241 board (e512-6.0101.002e)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.15-5.2
   Created:      2012-12-21  21:40:43 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    729741 Bytes = 712.6 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...Bad Data CRC
ar7240>

 


I realise this is an old post, but I've had success in bringing these back from that error; Using the TFTP recovery process described here in my post.

 

Reply