# Morse\_sdio\_reg32\_write failed

**URL:** https://community.morsemicro.com/t/morse-sdio-reg32-write-failed/207
**Category:** Linux
**Created:** [December 18, 2024, 12:47am UTC](https://community.morsemicro.com/t/morse-sdio-reg32-write-failed/207 "2024-12-18T00:47:05Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)
#### Post date: [December 18, 2024, 1:14pm UTC](https://community.morsemicro.com/t/morse-sdio-reg32-write-failed/207/9 "2024-12-18T13:14:29Z")

</div>

I’ll continue to check what I can on the hardware side, but this looks very similar to [Mmc2: error -110 whilst initialising SDIO card - #19 by ajudge](https://community.morsemicro.com/t/mmc2-error-110-whilst-initialising-sdio-card/149/19).

While the MM6108 can support a 1.8V I/O voltage for the SDIO lines, the RESET line needs to operate in the “VBAT” domain, 3.3V.

Unfortunately at this stage the solution may require a pull-up resistor to be inserted on the RESET line to 3.3V, as well as some device tree adjustment to configure the SD2\_RESET pin as an open drain GPIO, and finally adding an mm6108 specific child node in the `usdhc2` controller to provide a reset-gpios to the Morse driver so it can control that GPIO.

Are you in a position where you can add a hardware pullup to that RESET line? Does the bootloader allow you to load an alternative device tree binary?

---

_[View the full topic](https://community.morsemicro.com/t/morse-sdio-reg32-write-failed/207)._
