# Esp-halow with ESP32-P4 and MM8108-MF15457

**URL:** <https://community.morsemicro.com/t/esp-halow-with-esp32-p4-and-mm8108-mf15457/1808>\
**Category:** Software\
**Created:** [July 7, 2026, 2:41pm UTC](https://community.morsemicro.com/t/esp-halow-with-esp32-p4-and-mm8108-mf15457/1808 "2026-07-07T14:41:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmartauz](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@dmartauz](https://community.morsemicro.com/u/dmartauz)\
**Post date:** [July 7, 2026, 2:41pm UTC](https://community.morsemicro.com/t/esp-halow-with-esp32-p4-and-mm8108-mf15457/1808/1 "2026-07-07T14:41:57Z")

</div>

Are all of these signals mandatory for esp-halow?

 ![image](https://us1.discourse-cdn.com/flex001/uploads/morsemicro/original/1X/c645e2f31ee45194dcfe6be5841ed821e7fa5fc5.png)

In our application we are having issues with free GPIOs on the ESP32-P4, IO extender is already used for some slower signals. Now we would like to add **MM8108-MF15457** into the hardware design as additional IP interface.

Another question: with current status of esp-halow, is it already fully integrated into esp-idf IP stack?

---

<div class="post-metadata">

**Author:** ![ldennis](https://avatars.discourse-cdn.com/v4/letter/l/3ab097/32.png) [@ldennis](https://community.morsemicro.com/u/ldennis)\
**Post date:** [July 8, 2026, 4:22am UTC](https://community.morsemicro.com/t/esp-halow-with-esp32-p4-and-mm8108-mf15457/1808/2 "2026-07-08T04:22:57Z")

</div>

Hi @dmartauz,

All the signals except CONFIG\_MM\_WAKE and CONFIG\_MM\_BUSY are mandatory.

CONFIG\_MM\_WAKE and CONFIG\_MM\_BUSY are required if you would like the MM HaLow chip to support power-save. If you are ok with an always-on configuration, you can skip these two pins.

See page 18 of the module datasheet “Figure 8: SPI host interface circuit for always-on applications”

> **[MM8108-MF15457\_Data\_Sheet.pdf](https://www.morsemicro.com/resources/datasheets/modules/MM8108-MF15457_Data_Sheet.pdf)**

You’ll need to ensure you set the chip powersave state to disabled with `mmwlan_set_power_save_mode(MMWLAN_PS_DISABLED);`

---

<div class="post-metadata">

**Author:** ![dmartauz](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@dmartauz](https://community.morsemicro.com/u/dmartauz)\
**Post date:** [July 8, 2026, 5:11am UTC](https://community.morsemicro.com/t/esp-halow-with-esp32-p4-and-mm8108-mf15457/1808/3 "2026-07-08T05:11:34Z")

</div>

@ldennis thank you. Few more questions:

1. Is esp-halow fully integrated into esp-idf IP stack? Can existing application layer libraries be used out of the box? E.g. esp\_http\_client, esp\_mqtt\_client.
2. Would you consider implementing USB transport for MM8108?

---

<div class="post-metadata">

**Author:** ![ldennis](https://avatars.discourse-cdn.com/v4/letter/l/3ab097/32.png) [@ldennis](https://community.morsemicro.com/u/ldennis)\
**Post date:** [July 8, 2026, 5:34am UTC](https://community.morsemicro.com/t/esp-halow-with-esp32-p4-and-mm8108-mf15457/1808/4 "2026-07-08T05:34:47Z")

</div>

I’ll have to defer to my colleagues on the esp-idf question, but as for implementing support for MCU communicating to the MM chip over USB, we don’t have any plans to do this.

---

<div class="post-metadata">

**Author:** ![michael.mccandless](https://avatars.discourse-cdn.com/v4/letter/m/c5a1d2/32.png) [@michael.mccandless](https://community.morsemicro.com/u/michael.mccandless)\
**Post date:** [July 8, 2026, 7:18am UTC](https://community.morsemicro.com/t/esp-halow-with-esp32-p4-and-mm8108-mf15457/1808/5 "2026-07-08T07:18:21Z")

</div>

The esp-idf IP stack should be fully supported. There are [examples out in the wild](https://github.com/camthink-ai/lowpower_camera), that one specifically uses MQTT so it may be a good reference for your use case.