Modify

Opened 3 years ago

Last modified 20 months ago

#20280 assigned defect

The Linksys EA6300v1/EA6400

Reported by: ewtoombs Owned by: hauke
Priority: normal Milestone:
Component: kernel Version: Trunk
Keywords: ea6400, bcm4708, bcm53xx Cc:

Description

I've added preliminary support for the Linksys EA6300v1/EA6400. The power LED and the WPS button aren't configured yet, but the RAM is correctly configured and the 2.4GHz wireless works mostly.

There are problems. This router has partitions in its flash memory for a main image and a backup image. This is the default partition table:

00000000: boot
00080000: nvram
00180000: devinfo
00200000: firmware

00200000: header
0020001c: kernel
00436430: / squashfs

01f00000: firmware2

01f00000: header
01f0001c: kernel
020d364c: / squashfs

03c00000: /var/config jffs2
08000000: END OF MEMORY

On the first flash, openwrt accidentally ignores its root filesystem and instead mounts the root filesystem of the backup image on /, effectively forcing the Linksys userspace to use the OpenWRT kernel. That only lasts one boot though. OpenWRT erases everything after 0x01f00000 during the first boot, replacing it with the UBIFS overlay so on the next boot, openwrt's kernel does manage to find its root filesystem. Nothing happened this time, but running the Linksys userspace with the openwrt kernel is dangerous and shouldn't even happen once.

Also, I'm pretty sure the wireless b/g/n interface doesn't work in Managed mode. Master mode works fine, though. Any reason why that might be? Is it hardware or software? The hardware was only meant to work in Master mode, after all.

The files I used to build my image are attached.

Attachments (3)

902-Add-DT-for-linksys-ea6400.patch (1.8 KB) - added by ewtoombs 3 years ago.
Makefile-add-ea6400.patch (1.2 KB) - added by ewtoombs 3 years ago.
ea6400.diffconfig (86 bytes) - added by ewtoombs 2 years ago.
scripts/diffconfig.sh output. (move to .config and run make defconfig to use.)

Download all attachments as: .zip

Change History (11)

Changed 3 years ago by ewtoombs

Changed 3 years ago by ewtoombs

comment:1 Changed 2 years ago by anonymous

Bump.

Well hopefully the router donation to dd-wrt may shed some light in the future.

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=172389

comment:2 Changed 2 years ago by anonymous

It appears that DD-WRT builds have been released for the EA6400; can any further work be done for OpenWRT from that?

comment:3 Changed 2 years ago by hauke

  • Owner changed from developers to hauke
  • Status changed from new to assigned

Could you please send the patches to the mailing list and follow SubmittingPatches.

When you flash the image where is the kernel and where is the rootfs written to? Do you have any more details on how the boot process works, like based on which variable to boot loader chooses from where to boot?

comment:4 Changed 2 years ago by ewtoombs

The Linksys bootloader boots the kernel and rootfs at the offset "firmware" by default. If that fails, it boots the kernel and rootfs at firmware2. These bootloader settings seemed fine by default, so I never bothered learning more about where the bootloader stores its settings. This is the complete default boot log: https://forum.openwrt.org/viewtopic.php?id=58041

When I flash the OpenWRT image, I flash the whole thing starting at the offset "firmware". I use the target image type called "squashfs" in make menuconfig.

I'd put all this information in a wiki article for the ea6400, but I don't have the permissions to start a new article.

Changed 2 years ago by ewtoombs

scripts/diffconfig.sh output. (move to .config and run make defconfig to use.)

comment:5 Changed 2 years ago by anonymous-Henri

" OpenWRT erases everything after 0x01f00000 during the first boot " - yep, this issue is also occurring with DD-Wrt after three reboots. I don't know what is the cause but after reseting the router by pushing the button for 30 seconds in this state it reloads DD-Wrt with factory settings.

There is some form of blame game going on, developers are slaming Linksys for their cfe whilst there has been some changesets to make the partialboots counter go up to three.

Checkout this cfe for a modified version of XVortex CFE's complied for the EA6400, this has dropped temperatures on the router whilst running DD-WRT and remove the nvram bug of 32k :)

Source:

-> cfe post

variables identified as partialboots taken from my router -->
nvram get maxpartialboots
nvram get partialboots
nvram get bootpartition

-Output-

3
0
0

comment:6 Changed 2 years ago by anonymous-Henri

Yep, bug with 3 reboots gone after using this cfe.

You should try the firmware on that to see if the bug still occurs for your build of openwrt

comment:7 Changed 20 months ago by anonymous

Any progress on this device with OpenWRT? Are the dev builds stable enough to use the router?

comment:8 Changed 20 months ago by anonymous

Any progress on this device with OpenWRT? Are the dev builds stable enough to use the router?

Add Comment

Modify Ticket

Action
as assigned .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.