# How to determine eFuse settings on previously used iMX6 SOM

**URL:** <https://community.solid-run.com/t/how-to-determine-efuse-settings-on-previously-used-imx6-som/230>\
**Category:** I.MX6\
**Created:** [January 28, 2022, 2:32am UTC](https://community.solid-run.com/t/how-to-determine-efuse-settings-on-previously-used-imx6-som/230 "2022-01-28T02:32:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rayk](https://avatars.discourse-cdn.com/v4/letter/r/f17d59/32.png) [@rayk](https://community.solid-run.com/u/rayk)\
**Post date:** [January 28, 2022, 2:32am UTC](https://community.solid-run.com/t/how-to-determine-efuse-settings-on-previously-used-imx6-som/230/1 "2022-01-28T02:32:03Z")

</div>

I recently acquired a couple of used HummingBoard 2 devices (a Gate Rev 1.2 no eMMC and an Edge Rev 1.2 w/ 4GB eMMC). These came with 3 different SOM Modules

1. i2EX-3C sticker on bottom. IMX6-uSOM 1.3 silkscreened on top. Appears to be 1GB RAM, no eMMC
2. I4P 1.5.0 sticker on bottom. REV 1.5 silkscreened on top. Appears to be 2GB RAM, 8GB eMMC
3. S6QN28C15 1.5.0 sticker on bottom, REV 1.5 silkscreened on top. Sticker w/ Model i4P-3C-310-D MAC and a MAC address, another sticker with S6QN28

Neither of the devices will boot from SD with any of the SOM Modules.

How do I determine what if any eFuses have already been blown on the SOM Modules. Is there some way to do this without the MFGTool which seems to require MS Windows which I don’t currently have!

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [January 28, 2022, 6:16am UTC](https://community.solid-run.com/t/how-to-determine-efuse-settings-on-previously-used-imx6-som/230/2 "2022-01-28T06:16:11Z")

</div>

To read the fused settings you will need to boot the device. If the SOC won’t boot from the configured medium it should fall back to USB recovery mode. There are instructions on [developer.solid-run.com](http://developer.solid-run.com) for making a recovery cable, the other option if you have a USB-C to USB-A cable is to get a USB-C to USB-A male adapter. Generally these adapters come with resistor already on VCC so this configuration is safe to use for board to board recovery.

On Linux you can either use NXP’s utility, [GitHub - NXPmicro/mfgtools: Freescale/NXP I.MX Chip image deploy tools.](https://github.com/NXPmicro/mfgtools) or Boundary Devices imxusbloader, [GitHub - boundarydevices/imx\_usb\_loader: USB & UART loader for i.MX5/6/7/8 series](https://github.com/boundarydevices/imx_usb_loader)

There is documentation on [developer.solid-run.com](http://developer.solid-run.com) regarding decoding the sku on the sticker to understand the hardware you have.