Devices and testers #4

Open
opened 2026-04-15 01:40:54 +00:00 by Sirherobrine23 · 24 comments
Owner

@Sirherobrine23 and @kvn193:

  • EN7562CT:
    • Mikrotik hEX S 2025
  • EN7529CT:
    • TP-Link xx230v v1 (v1.0 and v1.9)
    • TP-Link xx530v v1 (v1 and v1 Algar Telecom custom board for Brazilian ISP) (same device xx230v but wireless chip is different)

@lilmayofuksu:

  • EN7562CT: TP-Link ex530v v1

@Gemnon

  • EN7523:

    • Genexis pixly CX30
  • EN7529

    • Genexis zephyr HX30
  • Genexis arcee CX20

  • Genexis laxy "Unknown model"

  • Genexis rodimus HX40

@Sirherobrine23 and @kvn193: - EN7562CT: - Mikrotik hEX S 2025 - EN7529CT: - TP-Link xx230v v1 (v1.0 and v1.9) - TP-Link xx530v v1 (v1 and v1 Algar Telecom `custom board for Brazilian ISP`) (same device xx230v but wireless chip is different) ---- @lilmayofuksu: - EN7562CT: TP-Link ex530v v1 ----- @Gemnon - EN7523: - Genexis pixly CX30 - EN7529 - Genexis zephyr HX30 - Genexis arcee CX20 - Genexis laxy "Unknown model" - Genexis rodimus HX40
Sirherobrine23 pinned this 2026-04-15 01:41:02 +00:00
Owner

I think CX30 has EN7523 and HX30 has EN7529. But it doesnt reallt matter as it is the same architecture just different pinout.

I think CX30 has EN7523 and HX30 has EN7529. But it doesnt reallt matter as it is the same architecture just different pinout.
Author
Owner

@merbanan, @Gemnon, and @lilmayofuksu, should we merge the firmware{1, 2} partitions into one partition, keeping only env{1, 2}, art, and firmware?

@merbanan, @Gemnon, and @lilmayofuksu, should we merge the `firmware{1, 2}` partitions into one partition, keeping only `env{1, 2}`, `art`, and `firmware`?
Owner

I would vote for merge, for more free space. (but then heimgard boxes have easy access serial ;))

I would vote for merge, for more free space. (but then heimgard boxes have easy access serial ;))
Author
Owner

I will perform the merge on the xx230v and xx530v devices, but I need to know if the other devices will want it

I will perform the merge on the xx230v and xx530v devices, but I need to know if the other devices will want it
Author
Owner

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.

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.
Owner

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)

> 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)
Owner

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.

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.
Author
Owner

The partitions that will not be merged are firmware, art, and uboot+atf; the rest will be relocated and/or merged.
for art there will be no change, and for the tplinks it will be a copy of the misc partition where mt76 eeprom, pon bob and tplink config are located.

The partitions that will not be merged are `firmware`, `art`, and `uboot+atf`; the rest will be relocated and/or merged. for `art` there will be no change, and for the tplinks it will be a copy of the `misc` partition where `mt76 eeprom`, `pon bob` and `tplink config` are located.
Author
Owner

@merbanan should I keep the prefix an7523, or should I change it to en7523?

@merbanan should I keep the prefix an7523, or should I change it to en7523?
Owner

en7523 is what is written on the SoC, and it is used in all materials I have access to

en7523 is what is written on the SoC, and it is used in all materials I have access to
Author
Owner

I'm asking because the an7581 was renamed, wouldn't it be good if we could rename it on the en7523 as well?

I'm asking because the an7581 was renamed, wouldn't it be good if we could rename it on the en7523 as well?
Owner

en7523 is the official name used for this soc, it makes sense to use it.

en7523 is the official name used for this soc, it makes sense to use it.
Author
Owner

okay

okay
Author
Owner

@merbanan

Will the Aura E650 also be added, since we are currently adding 6 devices?

@merbanan Will the Aura E650 also be added, since we are currently adding 6 devices?
Owner

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.

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.
Author
Owner

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.

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.

I think you will be quite happy if what I am working on pans out.

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.

> 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. 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. > I think you will be quite happy if what I am working on pans out. 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.
Owner

What PCs ?

What PCs ?
Owner

Ahh PCS ok I get it.

Ahh PCS ok I get it.
Author
Owner

Right now I am actually making good progress on the NPU

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

> Right now I am actually making good progress on the NPU 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
Owner

Yeah, it might be that the NPU needs to start up like the SDK does. We'll see what we can do about that.

Yeah, it might be that the NPU needs to start up like the SDK does. We'll see what we can do about that.
Author
Owner

this in order enable kernel modules from this file:

  1. FE
  2. IFC
  3. NPU
    • NPU Host adapter
  4. eth
  5. eth_ephy
    • set eth0 up
  6. qdma_wan
  7. Wireless
  8. mt_whnat
  9. tso2
this in order enable kernel modules from [this file](https://sirherobrine23.com.br/tplink_gpl/xgb830v_v1/src/commit/35cb20be30678b93ab94d3b0d18d35c2b54dc5eb/sdk/an7551/openwrt-21.02/openwrt-21.02.1_dev/feeds/airoha/airoha_build/profile/Kernel_Api/en7523/target/linux/airoha/en7523/base-files/etc/preinit): 1. FE 2. IFC 3. NPU * NPU Host adapter 4. eth 5. eth_ephy * set eth0 up 6. qdma_wan 7. Wireless 8. mt_whnat 9. tso2
Author
Owner

@merbanan should we start using kernel 6.18 for testing?

@merbanan should we start using kernel 6.18 for testing?
Owner

We need to follow openwrt so yes. There will not be any port to 6.12.

We need to follow openwrt so yes. There will not be any port to 6.12.
Author
Owner

so I will be integrating the openwrt/openwrt#21019 file into the repository and migrating the patches

so I will be integrating the openwrt/openwrt#21019 file into the repository and migrating the patches
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: airoha_en7523/openwrt#4