forked from openwrt/openwrt
Devices and testers #4
Open
opened 2026-04-15 01:40:54 +00:00 by Sirherobrine23
·
24 comments
No Branch/Tag Specified
airoha_en7523
main
v23.05.6
v24.10.2
v24.10.1
v24.10.0
v24.10.0-rc7
v24.10.0-rc6
v24.10.0-rc5
v24.10.0-rc4
v24.10.0-rc3
v24.10.0-rc2
v24.10.0-rc1
v23.05.5
v22.03.7
v23.05.4
v23.05.3
v22.03.6
v23.05.2
v23.05.1
v23.05.0
v23.05.0-rc4
v23.05.0-rc3
v23.05.0-rc2
v23.05.0-rc1
v21.02.7
v22.03.5
v21.02.6
v22.03.4
v22.03.3
v21.02.5
v22.03.2
v22.03.1
v21.02.4
v22.03.0
v22.03.0-rc6
v22.03.0-rc5
v22.03.0-rc4
v22.03.0-rc3
v22.03.0-rc2
v22.03.0-rc1
v21.02.3
v19.07.10
v19.07.9
v21.02.2
v21.02.1
v21.02.0
v21.02.0-rc4
v19.07.8
v21.02.0-rc3
v21.02.0-rc2
v21.02.0-rc1
v19.07.7
v19.07.6
v19.07.5
v18.06.9
v19.07.4
v19.07.3
v19.07.2
v18.06.8
v18.06.7
v19.07.1
v19.07.0
v18.06.6
v19.07.0-rc2
v18.06.5
v19.07.0-rc1
v18.06.4
v18.06.3
v17.01.7
v18.06.2
v17.01.6
v18.06.1
v18.06.0
v17.01.5
v18.06.0-rc2
v18.06.0-rc1
v17.01.4
v17.01.3
v17.01.2
v17.01.1
v17.01.0
v17.01.0-rc2
v17.01.0-rc1
reboot
Labels
Clear labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Breaking change that won't be backward compatible
Something is not working
Documentation changes
Improve existing functionality
New functionality
This is security issue
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No labels
Milestone
No items
No Milestone
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: airoha_en7523/openwrt#4
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
@Sirherobrine23 and @kvn193:
custom board for Brazilian ISP) (same device xx230v but wireless chip is different)@lilmayofuksu:
@Gemnon
EN7523:
EN7529
Genexis arcee CX20
Genexis laxy "Unknown model"
Genexis rodimus HX40
I think CX30 has EN7523 and HX30 has EN7529. But it doesnt reallt matter as it is the same architecture just different pinout.
@merbanan, @Gemnon, and @lilmayofuksu, should we merge the
firmware{1, 2}partitions into one partition, keeping onlyenv{1, 2},art, andfirmware?I would vote for merge, for more free space. (but then heimgard boxes have easy access serial ;))
I will perform the merge on the xx230v and xx530v devices, but I need to know if the other devices will want it
Knowing this, rolling back to the vendor version will depend on the person having made a stock backup of the entire nand/nor before restoring it.
Will do that for the other boxes too only did for CX30. But to be honest not even sure Heimgard connect app still work (the mobile app peoples supposed to set the things up) and if it is still working how long it will, so not much chance i ever want to go back anyway plus last ota dates to end of 2024 (so think updates just stopped when Genexis acquired them)
Keep art as it has relative offsets for wifi calibration. Art will be needed for laser driver calibration also. If art is wiped wifi and optical will not be advisable to use. The other partitions have other stuff in them that might be good to have but can probably be merged.
The partitions that will not be merged are
firmware,art, anduboot+atf; the rest will be relocated and/or merged.for
artthere will be no change, and for the tplinks it will be a copy of themiscpartition wheremt76 eeprom,pon bobandtplink configare located.@merbanan should I keep the prefix an7523, or should I change it to en7523?
en7523 is what is written on the SoC, and it is used in all materials I have access to
I'm asking because the an7581 was renamed, wouldn't it be good if we could rename it on the en7523 as well?
en7523 is the official name used for this soc, it makes sense to use it.
okay
@merbanan
Will the Aura E650 also be added, since we are currently adding 6 devices?
It is the plan but I am working all over the Econet/Airoha hardware space. I dont want to do a half-arsed implementation of it. Right now I am actually making good progress on the NPU. I just need to focus on one thing at the time and real (or is fake?) life eats time also.
I think you will be quite happy if what I am working on pans out.
okay, I'm seeing that some NPU features were recently implemented upstream, which the SDK files I have don't contain, so I'm also lost. I'm also messing around a bit with the EN7523's PPE, it doesn't seem to be working, as the tuples aren't being written, so I still have a lot to do.
Tests between the router and the laptop are showing okay speeds (750-900Mbps up and 709-809Mbps down), but when it comes from one network interface to another, things get very slow. Even with hardware offload enabled, so I'll still be looking into that.
having the Ethernet partially working already makes me happy, and some of the things I'm adding are also making me happy. What's bringing me down is my attempts to get pcs/hsgmii working on the EN7523, but they're all failing, and for now I've kind of given up on that part. It's a shame the EN8801 and SFP aren't ready for this Airoha family yet.
What PCs ?
Ahh PCS ok I get it.
I also noticed that the NPU initialization is very unstable on the EN7523, sometimes it starts correctly, and other times it freezes during the entire boot process. This usually happens when the network cables are connected to the network switch and there is some network traffic
Yeah, it might be that the NPU needs to start up like the SDK does. We'll see what we can do about that.
this in order enable kernel modules from this file:
@merbanan should we start using kernel 6.18 for testing?
We need to follow openwrt so yes. There will not be any port to 6.12.
so I will be integrating the openwrt/openwrt#21019 file into the repository and migrating the patches