NRF54L15 DFU The image does not have a valid mcu header

[bevis]

My steps:

1. Generate KEY using ed25519   py ../../bootloader/mcuboot/scripts/imgtool.py keygen -t ed25519 -k ./sysbuild/privateKey/private_key.pem
2. Compilation is complete, no errors, dfu_xxx.zip is generated
3. Placed on phone, used the latest version of nrf connect to load and send
4. Triggered APP error "Invalid file: The image does not have a valid mcu header"
   

---

Tried efforts - all unsuccessful

1. Local environment encryption on computer? -- Changed to another computer
2. APP version too low? Does not support NRF54? -- Already the latest from the GitHub repository
3. Searched for answers on forums? -- No relevant issues found

[Vidar Berg]

Hello, 

you can run "imgtool dumpinfo" on the signed *.bin file to check if it has a valid mcuboot header or not. But Are you signing the image yourself from the command line, or are you using the dfu_application.zip file from the build folder?

Best regards,

Vidar

[bevis]

I use the git bash command line run it, finaly use p256 work

My current configuration is as shown in the following figure.

However, in the previous configuration, I used a single definition and did not explicitly disable other signature methods. I suspect that other signatures were also enabled, causing the problem

SB_CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y