Has anyone else struggled with the MX3080/M1400 Wi‑Fi modules?

[islavv]

Honestly, this choice feels like a trap.

STM keeps promoting it as a “solution,” but compared to Murata, ESP32, or Broadcom it looks outdated:

– Legacy M4 core, original MXCHIP code from 2017

– Closed software, very little documentation

– Hard to debug (no sequence diagrams, no clear dedicated examples)

– Rare, unpolished firmware updates

– No Nucleo board for hands‑on exploration

– Doesn’t seem seriously supported by MXCHIP anymore (similar by STM)

This isn’t a shallow impression — I spent three weeks with console access and a logic analyzer writing and debugging code on the B‑U585I‑IOT2A board, and the friction was constant.

Curious if others see the same issues, or if there’s a hidden advantage I’m missing?

[Andrew Neil]

Prompted by this ?

[islavv]

I was eventually able to get the MX3080 Wi‑Fi running properly, but only after working through a number of issues that really should have been better explained and documented by ST and not explored with logical analyzer and soldering console port to chip. From what I’ve seen, ST’s policy is to take no responsibility for non‑ST parts, even when they’re included on ST demo boards, and MXCHIP itself doesn’t appear to be very actively maintained anymore.

Because I had to dig into clock settings, pin modes, SPI, and interrupt configurations step by step, I can appreciate how challenging this path could be for others approaching it for the first time.

[Andrew Neil]

---

@islavv wrote:

From what I’ve seen, ST’s policy is to take no responsibility for non‑ST parts, even when they’re included on ST demo boards

---

Even when they're promoted as "Partners":

https://community.st.com/t5/stm32-mcus-products/new-madeforstm32-what-does-it-actually-mean/m-p/131466