OpenWrt Forum Archive

Topic: Arcor EasyBox 803A Astoria ARV752DPW22

The content of this topic has been archived between 23 Mar 2017 and 13 Apr 2018. Unfortunately there are posts – most likely complete pages – missing.

Ahh, right. Can you write the following on the command line and reboot:

dd if=/dev/mtdblock3 of=/lib/firmware/RT2860.eeprom bs=2 skip=520 count=256 conv=swab
[   16.460000] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'RT2860.eeprom'.
[   16.512000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
[   16.520000] ieee80211 phy0: rt2800_init_eeprom: Error - Invalid RF chipset 0x000a detected
[   16.528000] ieee80211 phy0: rt2x00lib_probe_dev: Error - Failed to allocate device

Ok, now I'm confused. Can you show me the outputs of

dd if=/lib/firmware/RT2860.eeprom bs=2 count=7 | hexdump

and

dd if=/dev/mtdblock3 skip=520 bs=2 count=7 | hexdump
dd if=/lib/firmware/RT2860.eeprom bs=2 count=7 | hexdump

gives

7+0 records in
7+0 records out
0000000 faf0 49bc b77a 5edd b694 a00a 5c4c     
000000e

and

dd if=/dev/mtdblock3 skip=520 bs=2 count=7 | hexdump

gives

0000000 f0fa bc49 7ab7 dd5e 94b6 0aa0 4c5c     
000000e
7+0 records in
7+0 records out

What should be in the eeprom on this place? The PCI-ID ? Could it be, that a accidentaly overwrote it during flashing the box?

(Last edited by kai4065 on 22 Jan 2014, 18:23)

Of course, after the automatically generated partitions board_config is partition 5 and not 3! Try this

dd if=/dev/mtdblock5 of=/lib/firmware/RT2860.eeprom bs=2 skip=520 count=256 conv=swab
[   16.392000] PCI: Enabling device 0000:00:0e.0 (0000 -> 0002)
[   16.396000] rt2800pci 0000:00:0e.0: failed to load eeprom property
[   16.400000] ieee80211 phy0: rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'RT2860.eeprom'.
[   16.456000] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
[   16.464000] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0001 detected

Interesting. So now it's the same as with my earlier build which also should've worked, but didn't. Can you again post the output of the two dd-hexumps (with mtdblock3 replaced by mtdblock5 in the second command)? I'll then try to figure out what the driver is actually seeing...

dd if=/lib/firmware/RT2860.eeprom bs=2 count=7 | hexdump
7+0 records in
7+0 records out
0000000 ffff ffff ffff ffff ffff ffff ffff
000000e

dd if=/dev/mtdblock5 skip=520 bs=2 count=7 | hexdump
7+0 records in
7+0 records out
0000000 ffff ffff ffff ffff ffff ffff ffff
000000e

Are you sure you have not erased that part of the flash (0xb07f0000 to 0xb07fffff) by accident when you installed OpenWrt? Your bootlog does complain also about an invalid mac-address, which is also located in the same region. If you don't have it backed up anywhere, I can provide you with a backup of mine.

(Last edited by snk on 22 Jan 2014, 19:30)

No, i'm not sure. That's why i asked to posts above. I have a backup, so i will flash it first and then try again.

Oh, sorry, I didn't notice your edit. I updated the image, so download it again. It should work straight away without any commands once you restore the last part of the flash.

Works. Tested as AP and Client. Thanks snk !

Great! I've also sent the patches to the mailing list.

Hi!
I've managed to execute my router, but I've got an other one.
On the weekend I'll will try out these images. All I have to do is flashing snk's image from 0x40000? How could I set the bootloader to point this address?
Is there any solution to keep the original bootlader, which point to u-boot, which point to this address? Or it makes no sense? I'm not so brave now to replace the original bootloader and brick my device again. smile
And finally, how stable this version? It is ready for everyday use? Does this image contain LuCi or other web-based admin ui?

Thank you for your efforts!

Cheers, qwercu

(Last edited by qwercu on 24 Jan 2014, 09:58)

Unfortunately you need to replace the original bootloader, as the "brnboot"-variant (which chainloads from the original bootloader) of U-Boot is not available anymore. The image contains luci and quite a lot of other packages.

Thank you very much!
Sorry for my incompetency, but for sure a step-by-step procedure would be something like this:

0. backup th whole flash with brnboot
1. 3 space at boot to enter command mode, than '!' to enter admin mode
2. \[U\] Upload to Flash at 0xB0000000 the http://downloads.openwrt.org/snapshots/ … u-boot.img
3. wait....wait...wait
4.  \[U\] Upload to Flash at 0x40000 the http://downloads.openwrt.org/snapshots/ … shfs.image
5. wait....wait...wait...wait...wait...wait
6. reboot and happy ever after?

Thank you in advance!

Yes, although I would reboot after flashing U-Boot and upload the squashfs image with TFTP from the freshly installed U-Boot. TFTP is a lot faster than serial line. I'm also not sure if you even can upload to 0xb0040000 in the original bootloader, since the original layout doesn't coincide with the new one.

ok, thanks.
So, I don't need to erase flash (to protect WLAN), simply overwrite flash?

You do need to erase areas 0 and 1 from the original bootloader before flashing U-Boot, and then in the U-Boot you must do

erase 0xb0040000 0xb07f0000

before writing the squashfs image to flash.

Edit: actually, I don't remember if flashing to area 5 will also erase that entirely (including the WLAN EEPROM). In any case, you can restore the EEPROM later from backup with U-Boot if that is the case.

(Last edited by snk on 24 Jan 2014, 15:59)

snk wrote:
erase 0xb0040000 0xb07f0000

before writing the squashfs image to flash.

Edit: actually, I don't remember if flashing to area 5 will also erase that entirely (including the WLAN EEPROM). In any case, you can restore the EEPROM later from backup with U-Boot if that is the case.

That's what i did first and it erased the eeprom. I transfered the image via loady, which displays the exact size of the image after the transfer is complete. So i erased exactly this area with:

erase 0xb0040000 +0x640004 

"+0x640004" is the size of the image.

If you flash another image, the correct size must be inserted after the "+".

(Last edited by kai4065 on 24 Jan 2014, 17:52)

I've download this image: http://downloads.openwrt.org/snapshots/ … u-boot.img and uploaded to the memory, but when I press 'Go to memory" it does nothing but

[DANUBE Boot]:y

Go to Memory Address: (default:0x80002000) : 0x
Jump to address 0x80002000 ...

So, I'm afraid of overwrite the bootloader with this...or this is how it works, and I sould take a deep breath and flash?

OK, I've erased partition 0 and 1.
Then I [ U ] Upload to Flash at 0xb0000000 http://downloads.openwrt.org/snapshots/ … u-boot.img

>>>  sx openwrt-lantiq-arv7518pw_nor-u-boot.img < /dev/ttyUSB0 > /dev/ttyUSB0  
Sending openwrt-lantiq-arv7518pw_nor-u-boot.img, 1414 blocks: Give your local XMODEM receive command now.
Bytes Sent: 181120   BPS:9637                             

and can't boot
What I've missed? Any ideas?

Thank you in advance!

(Last edited by qwercu on 24 Jan 2014, 23:23)

qwercu wrote:

OK, I've erased partition 0 and 1.
Then I [ U ] Upload to Flash at 0xb0000000 http://downloads.openwrt.org/snapshots/ … u-boot.img
and cant boot
What I've missed? Any ideas?

Thank you in advance!

Did you flash to partition 5?

(Last edited by snk on 24 Jan 2014, 23:25)

[0] Boot            0xB0000000     128K
[1] Configuration   0xB0020000     512K

I've flashed to 0.
Is this was the error? But partition 5 starts from 0xB0000000 as well. Or I don't understabd something...

Or I've flashed only the first 128K of my image?
It seems I need a stupid-safe description. big_smile

(Last edited by qwercu on 24 Jan 2014, 23:35)

Sorry, posts 51 to 50 are missing from our archive.