i.MX ProcessorsのトピックRe: Fuse write error in imx95 boards

Fuse write error in imx95 boards

CrazyDeveloper — Mon, 29 Sep 2025 15:18:58 GMT

Hello Everyone,

I am working on imx96 verdin development kit and I have generated keys and fuses for AHAB using CST4.0.1. However, when I try to write fuses in u-boot via fuse command, I am getting the below error


=> fuse prog 16 0 0x36C10F0D



Programming bank 16 word 0x00000000 to 0x36c10f0d...
Warning: Programming fuses is an irreversible operation!
         This may brick your system.
         Use this command only if you are sure of what you are doing!




Really perform this fuse programming? <y/N>
y
Error: ele_write_fuse: ret -5, fuse_id 0x80, response 0xd38dff29
ahab write fuse failed -5, 0xd38dff29
ERROR

The address for writing fuses in imx95 also looking right to me as given in this article https://github.com/varigit/uboot-imx/blob/lf_v2024.04_6.6.52-2.2.0_var01/doc/imx/ahab/guides/mx8ulp_9x_secure_boot.txt

I have fused otp for several imx6 and imx8 based already but never got this error. Anyone have idea why these fuse commands are not working in imx95? Any type of support/information will be very helpful. Thanks!

Re: Fuse write error in imx95 boards

JosephAtNXP — Mon, 29 Sep 2025 18:36:44 GMT

Hi,

Thank you for your interest in NXP Semiconductor products,

Do you still read unfused values in your processor?

Could you quickly try replacing the vowels with lowercase vowels?

If you make to this checkpoint, we need to confirm the top marking in your processor, the BSP/U-boot and ELE FW version flashed to the processor.

Regards

Re: Fuse write error in imx95 boards

CrazyDeveloper — Tue, 30 Sep 2025 08:11:22 GMT

Normal Case

u-boot=> fuse prog -y 16 0 0x36C10F0D
Programming bank 16 word 0x00000000 to 0x36c10f0d...
Error: ele_write_fuse: ret -5, fuse_id 0x80, response 0xd38dff29
ahab

replacing the vowels with lowercase vowel

u-boot=> fuse prog 16 0 0x36c10f0d
Programming bank 16 word 0x00000000 to 0x36c10f0d...
Warning: Programming fuses is an irreversible operation!
         This may brick your system.
         Use this command only if you are sure of what you are doing!

Really perform this fuse programming? <y/N>
y
Error: ele_write_fuse: ret -5, fuse_id 0x80, response 0xd38dff29
ahab write fuse failed -5, 0x

Fuse Read

u-boot=> fuse read 16 0
Reading bank 16:

Word 0x00000000: 00000000
u-boot=> fuse read 16 1
Reading bank 16:

Word 0x00000001: 00000000

AHAB STATUS

u-boot=> ahab_status 
Lifecycle: 0x00000010, OEM Open


        0x0087eed6
        IPC = INVALID
        CMD = ELE_OEM_CNTN_AUTH_REQ (0x87)
        IND = ELE_NO_AUTHENTICATION_FAILURE_IND (0xEE)
        STA = ELE_SUCCESS_IND (0xD6

I have applied the things that you asked and I got the same results. What do you think the further steps to debug and approach this problem?

Re: Fuse write error in imx95 boards

JosephAtNXP — Tue, 30 Sep 2025 17:33:43 GMT

Hi @CrazyDeveloper

Thanks for sharing the results, then we will move to confirm your setup.

Could you share how did you generate your images? Did you use Yocto or standalone?

Share the top marking of your i.MX 95 part.

Share the U-boot and ELE FW version, or the whole U-boot prompt.

Regards

Re: Fuse write error in imx95 boards

CrazyDeveloper — Tue, 30 Sep 2025 18:24:21 GMT

I am building the system in yocto with meta-imx as bsp have u-boot-imx as bootloader. The branch of meta-imx is scarthgap and the commit of meta-imx is 89c4d98c236ac1a2fbfcc92e5adf6571e41bd2da

The u-boot-imx SRC_branch and commit is here

SRC_URI = "${UBOOT_SRC};branch=${SRCBRANCH}"
UBOOT_SRC ?= "git://github.com/nxp-imx/uboot-imx.git;protocol=https"
SRCBRANCH = "lf_v2024.04_6.6.52_2.2.x"
LOCALVERSION ?= "-${SRCBRANCH}"
SRCREV = "82d4220bc6b832128454b09814a52e674943bd9a"

The uboot logs till loading is here

```

U-Boot SPL 2024.04-lf_v2024.04_6.6.52_2.2.x+g82d4220bc6b+p0 (Jul 11 2025 - 05:04:16 +0000)
SOC: 0xa1009500
LC: 0x40010
SYS Boot reason: unused, origin: -1, errid: -1
SYS shutdown reason: unused, origin: -1, errid: -1
DDRMIX is powered UP
Normal Boot
Trying to boot from MMC2
Primary set selected
Load image from MMC/SD 0xe8c00
NOTICE: BL31: v2.10.0 (release):lf-6.6.52-2.2.1
NOTICE: BL31: Built : 06:40:36, Jul 7 2025

U-Boot 2024.04-lf_v2024.04_6.6.52_2.2.x+g82d4220bc6b+p0 (Jul 11 2025 - 05:04:16 +0000)

CPU: i.MX95 rev1.1 at 1800MHz
CPU: Automotive temperature grade (-40C to 125C) at 51C
LM Boot reason: sw, origin: 2, errid: 1
LM shutdown reason: sw, origin: 2, errid: 1
Model: NXP i.MX95 19X19 board
DRAM: 15.8 GiB
setup_typec: tcpc init failed, err=-62
pca953x i2c3-gpio-expander@20: Error reading output register
pca953x i2c4-gpio-expander@21: Error reading output register
pca953x i2c5-gpio-expander@21: Error reading output register
pca953x i2c6-gpio-expander@21: Error reading output register
pca953x i2c7-gpio@22: Error reading output register
netc_phy_rst lookup i2c5_io@21_2 failed ret = -22
pca953x i2c5-gpio-expander@21: Error reading output register
Get regulator-aqr-stby regulator failed 3
pca953x i2c7-gpio@22: Error reading output register
Get regulator-mac-stby regulator failed 7
pca953x i2c5-gpio-expander@21: Error reading output register
Get regulator-aqr-en regulator failed 3
pca953x i2c5-gpio-expander@21: Error reading output register
Get regulator-mac-en regulator failed 3
pca953x i2c5-gpio-expander@21: Error reading output register
Get regulator-aqr-stby regulator failed 3
pca953x i2c7-gpio@22: Error reading output register
Get regulator-mac-stby regulator failed 7
pca953x i2c5-gpio-expander@21: Error reading output register
Get regulator-aqr-en regulator failed 3
pca953x i2c5-gpio-expander@21: Error reading output register
Get regulator-mac-en regulator failed 3
pca953x i2c5-gpio-expander@21: Error reading output register
Get regulator-aqr-stby regulator failed 3
pca953x i2c7-gpio@22: Error reading output register
Get regulator-mac-stby regulator failed 7
cfg name not match mx95alt:mx95evk, ignore
Core: 294 devices, 37 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
Loading Environment from MMC... *** Warning - bad CRC, using default environment

[*]-Video Link 0clk disp1pix already disabled
idle-states (1920 x 1080)
[0] display-controller@4b400000, video
[1] channel@0, video_bridge
[2] bridge@8, video_bridge
[3] dsi@4acf0000, video_bridge
[4] hdmi@3d, panel
In: serial
Out: serial
Err: serial

BuildInfo:
- SM firmware Build 646, Commit 707569f4, Aug 19 2025 09:45:49
- ELE firmware version 2.0.2-4e395675

switch to partitions #0, OK
mmc1 is current device
UID: a66adecd89624fdd84cb912a00387c23
flash target is MMC:1
Net: pca953x i2c5-gpio-expander@21: Error reading output register
enetc_mdio_probe: device_get_supply_regulator failed: 3
pca953x i2c5-gpio-expander@21: Error reading output register
enetc_mdio_probe: device_get_supply_regulator failed: 3
pca953x i2c5-gpio-expander@21: Error reading output register
enetc_probe: device_get_supply_regulator failed: 3
pca953x i2c5-gpio-expander@21: Error reading output register
enetc_probe: device_get_supply_regulator failed: 3
No ethernet found.

Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0

```

Re: Fuse write error in imx95 boards

JosephAtNXP — Tue, 30 Sep 2025 21:08:08 GMT

Share (also) a processor top view image, please

Re: Fuse write error in imx95 boards

CrazyDeveloper — Tue, 30 Sep 2025 21:15:59 GMT

Currently, I have only this image. Please tell me if it will work or not. Otherwise, I can send a more clear image in few hours when I will back in the workspace

Re: Fuse write error in imx95 boards

JosephAtNXP — Tue, 30 Sep 2025 23:22:01 GMT

Hi @CrazyDeveloper,

I thought that SOM exposed the processor, I want to confirm the silicon revision, could you confirm with Verdin what silicon revision you have and if your silicon revision is compatible with the branch you built in Yocto?

Thanks for your quick responses,

Regards,

Re: Fuse write error in imx95 boards

CrazyDeveloper — Wed, 05 Nov 2025 12:18:11 GMT

The error was resolved by changing the ELE version