EKH05 MCU-Host Questions for Peer-to-Peer Soft TDMA Use Case

Software
1

Hi, we are trying to setup EKH05 with MM-IOT-SDK-2.10.4 for a peer-to-peer soft TDMA use case.

From the public SDK, our understanding is that EKH05 uses an MCU-host architecture, where an external STM32U585 host MCU interfaces over SPI or SDIO to an MM6108 or MM8108 transceiver. We also understand that Linux-host deployments appear to expose richer public mesh support than the MCU-host SDK path.

From the public MCU-host SDK, we could see normal STA/AP support, packet RX/TX callbacks, some MAC tuning, and scan-time fields such as RSSI, noise, and TSF. However, we could not confirm whether the following are supported in the MCU-host path, available through internal/private APIs, or possible through custom firmware:

  • absolute-time or TSF-based scheduled TX for TDMA-like operation

  • low-level contention control such as reduced backoff, EDCA override, or CCA override

  • per-packet RX/TX metadata such as timestamp/TSF, RSSI, SNR, MCS, CRC/FCS, and TX completion status

  • TSF get/set support in MCU-host mode

  • direct peer-to-peer communication or AP-free multi-hop forwarding

We would appreciate your guidance on which of these are currently:

  • supported in the public MCU-host SDK

  • available through internal/private APIs

  • or possible through firmware customization

We also saw the public note that Linux platforms support 802.11s / EasyMesh, while the microcontroller offering does not currently support mesh, so we would especially appreciate guidance on the best-supported path for this type of EKH05 use case.

Thank you

2

+1 to questions about mesh for mcu-host based projects.

3

Hi @user44

From the public MCU-host SDK, we could see normal STA/AP support, packet RX/TX callbacks, some MAC tuning, and scan-time fields such as RSSI, noise, and TSF. However, we could not confirm whether the following are supported in the MCU-host path, available through internal/private APIs, or possible through custom firmware:

  • absolute-time or TSF-based scheduled TX for TDMA-like operation

  • low-level contention control such as reduced backoff, EDCA override, or CCA override

  • per-packet RX/TX metadata such as timestamp/TSF, RSSI, SNR, MCS, CRC/FCS, and TX completion status

  • TSF get/set support in MCU-host mode

Unfortunately none of these are supported, and therefore would not be available through any APIs.

We are currently working on Relay support, so watch this space :slight_smile: