# SCHEMATIC REVIEW for MM8108-MF15457 Halow

**URL:** <https://community.morsemicro.com/t/schematic-review-for-mm8108-mf15457-halow/1990>\
**Category:** Hardware\
**Created:** [September 5, 2026, 4:43am UTC](https://community.morsemicro.com/t/schematic-review-for-mm8108-mf15457-halow/1990 "2026-09-05T04:43:43Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [September 9, 2026, 7:14am UTC](https://community.morsemicro.com/t/schematic-review-for-mm8108-mf15457-halow/1990/7 "2026-09-09T07:14:47Z")

</div>

The chip firmware and driver are different, but we deliver both of those, and swapping between should be as simple as changing the `MMHAL_CHIP_TYPE` and `FW_MBIN`.

The `mmhal_wlan` abstraction layer for interfacing with the chip over SPI is agnostic to the chip and shouldn’t need to change.

For accessing the busy (and wake!) pin, I think your best bet is to use the test points around the chip - see here where I discussed this with another user: ["mm8108-ekh05 v2" + esp32-p4 - #2 by ldennis](https://community.morsemicro.com/t/mm8108-ekh05-v2-esp32-p4/1920/2)

---

_[View the full topic](https://community.morsemicro.com/t/schematic-review-for-mm8108-mf15457-halow/1990)._