# Compex WLE200NX / Atheros AR9280

**URL:** <https://forum.mikrotik.com/t/compex-wle200nx-atheros-ar9280/166217>\
**Category:** General\
**Created:** [April 25, 2023, 3:57pm UTC](https://forum.mikrotik.com/t/compex-wle200nx-atheros-ar9280/166217 "2023-04-25T15:57:08Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![r00t](https://forum.mikrotik.com/letter_avatar/r00t/32/6_449c533f586939b6e5f246632a46421f.png) [@r00t](https://forum.mikrotik.com/u/r00t)\
**Post date:** [April 25, 2023, 7:10pm UTC](https://forum.mikrotik.com/t/compex-wle200nx-atheros-ar9280/166217/2 "2023-04-25T19:10:19Z")

</div>

AR9280 seems to be problematic, another older thread about it: [http://forum.mikrotik.com/t/ar9280-low-speed/62030/1](http://forum.mikrotik.com/t/ar9280-low-speed/62030/1)  
I think it may be down to radio EEPROM contents, the ROS wireless implementation is rather specific to work just with Mikrotik hardware and it may need some extra data/fields in there.  
Best would be to compare EEPROM dumps from radio that works and one that doesn’t using [https://github.com/rsa9000/atheepmgr](https://github.com/rsa9000/atheepmgr)

Update:  
I just checked rb711-5hn board that does have AR9280 radio on it and there is NO EEPROM connected to it at all. Maybe WLE200NX would run without it?  
If you are feeling adventurous just shorting clock/data pins should make it unreadable…  
Here is FCC report for WLE200NX including schematics: [https://fcc.report/FCC-ID/TK4-10-WLE200NX](https://fcc.report/FCC-ID/TK4-10-WLE200NX)

---

_[View the full topic](https://forum.mikrotik.com/t/compex-wle200nx-atheros-ar9280/166217)._
