If you need any measurements from a working board, I'm happy to help. Mine has Micron NAND tho
I think ADAM2/EVA is on the flash chip too though, but you're looking at an even earlier bootloader.
Thank you for your offer. I was away for a few days. I'll let you know what info I will need (e.g. voltage on a test-point)
I might try a few things with this router in the future but try not to spend a lot of time on it.
The original memories on the one I have are:
Micron - NAND Flash
Winbond - NOR Flash
I can confirm this. What would be the next step for OpenWRT regarding this HW?
The next step would be to implement a system to configure remote (wifi) SoCs, that have no Flash. And then to build images that contain additional OpenWRT images for such SoCs
So the way i see it this is done with the remoteproc kernel module in the
for the 3390 for example, no?
The remoteproc kernel module only boots the WiFi SoC. But there is no way to really configure it from the Lantiq SoC. It is a whole second openwrt instance. You can configure it via it's own LuCI, but once you reboot, everything is lost, because the WiFi SoC has no flash. So some kind of remote configuration system is needed
1 Like
I have understood that there is no way to save the config. I have a 3390 at home as well, which has the same wasp, but i have 5G WiFi. So i though it had the wasp driver enabled.
But it seems like the 3390 does not have the WASP enabled by default.
So andy might have partley solved it as descrived on the blog
Basically, I added MDIO support to the Lantiq switch driver, created a userspace stage 1 and stage 2 uploader and created a second OpenWrt instance for the Atheros target.
But what I don't understand what he got the information: Using freetz, I could compile a firmware that dumps MDIO packets and got an MDIO trace.
5 GHz is apparently on the Lantiq and 2.4 GHz is on the WASP SoC. I can try adding 3390 support, too. If you are willing to go the Local Startup Script Config route
I used Freetz to compile a version of the AVM firmware that dumps all MDIO reads/writes, so I basically sniffed the communication between the Lantiq and the WASP. Took me some time to figure out the details.
Then I also sniffed the raw Ethernet frames between the devices to get the firmware upload right.
Please keep in mind that these tools most probably won't work with the remoteproc version or are not needed at all.
5 Likes
Would you like to elaborate on that?
I assume your 2 stages boot the WASP image and configs it in the same time.
Where as with the remote proc, boots the WASP kernel blank no config before?
OK, let's take one step back:
This thread is about the 7490, but we are talking about the 3390 now. There are fundamental differences between them, most notably:
- The 3390 has a 5GHz WiFi chip connected to the Lantiq target, the WASP is only needed for 2.4GHz WiFi
- The 7490 has quite a few more telephony features (all unsupported), and both WiFi chipsets are handled by the WASP
My original implementation allowed the configuration to be stored on the Lantiq target somewhere under /opt and it would be restored during boot. The wasp_downloader is run on the WASP and waits for a connection by the Lantiq. The wasp_uploader runs on the lantiq, consisting of a stage1 and a stage2 uploader. The stage1 uploader uploads the ath_tgt_fw1.fw file which is nowadays uploaded by the remoteproc kernel module. The stage2 uploader uploads OpenWrt along with the configuration file.
Since I sold all these devices a few years ago, I do not remember all details. Please dig through my website and the PRs on github for the discussions.
Hey guys, i hope you are doing fine.
I am trying to pass-through my DSL connection i have, using the 7490 as DSL modem only.
So i've added the dsl0 interface to the br-lan, and everything works well, VLAN 10 and 20 from my ISPs are bridged to the devices behind, and i can do the PPPoE login there.
But the connection even between the LAN interfaces of the 7490 and my switch is capped to 100mbps.
Maybe caused by the slowest interface, which is the dsl0?
But whenever i use my 7490 with stock Fritz OS i am able to get my dsl connection running on 107/43 mbps, but this way only with OpenWrt 97/43. Using PPPoE passthrough on FritzOS i can also achieve those speeds on devices behind the 7490. But on OpenWrt i am limited to almost 100mbps.
Is there a way to get around this?
First, SSH into the 7490 and run top while testing. If either/both of the CPUs are hitting 100%, you could try enabling "software flow offloading" and/or setting "receive packet steering" to Enabled (All CPUs).