Esp-halow with ESP32-P4 and MM8108-MF15457

Software
1

Are all of these signals mandatory for esp-halow?

image
image803×326 15 KB

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?

2

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”

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

3

@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?
4

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.

5

The esp-idf IP stack should be fully supported. There are examples out in the wild, that one specifically uses MQTT so it may be a good reference for your use case.

1 Like