# RPi CM4 with Zymkey 4i - no boot

**URL:** <https://community.zymbit.com/t/rpi-cm4-with-zymkey-4i-no-boot/1627>\
**Category:** Uncategorized\
**Created:** [February 2, 2024, 3:00pm UTC](https://community.zymbit.com/t/rpi-cm4-with-zymkey-4i-no-boot/1627 "2024-02-02T15:00:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![cobalt2435](https://avatars.discourse-cdn.com/v4/letter/c/e99b99/32.png) [@cobalt2435](https://community.zymbit.com/u/cobalt2435)\
**Post date:** [February 2, 2024, 3:00pm UTC](https://community.zymbit.com/t/rpi-cm4-with-zymkey-4i-no-boot/1627/1 "2024-02-02T15:00:48Z")

</div>

Hi guys!  
I got the trouble with my CM4 module, witch stands on Waveshare NANO-C shield and wired with Zymkey 4i module.  
It worked before I did rpiboot recovery.  
Now it has not video signal on HDMI, no boot, except the message from the UART port:

Failed to validate bootconf.txt  
FATAL error-code 24

This is the brand new device, without useful info on it, and I have 2 flashdisks with keys.  
It can boot only from eMMC memory.

How can I bring CM4 back to the life?

---

<div class="post-metadata">

**Author:** ![Bob\_of\_Zymbit](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@Bob\_of\_Zymbit](https://community.zymbit.com/u/Bob_of_Zymbit)\
**Post date:** [February 2, 2024, 4:14pm UTC](https://community.zymbit.com/t/rpi-cm4-with-zymkey-4i-no-boot/1627/2 "2024-02-02T16:14:29Z")

</div>

@cobalt2435 - Sounds like your bootloader/EEPROM code isn’t correct after your rpiboot recovery. You will need to get your Waveshare board and CM4 booting again following Waveshare’s instructions before adding the Zymkey. Once you have your CM4 running, if you need help with the Zymkey, post back here.

---

<div class="post-metadata">

**Author:** ![cobalt2435](https://avatars.discourse-cdn.com/v4/letter/c/e99b99/32.png) [@cobalt2435](https://community.zymbit.com/u/cobalt2435)\
**Post date:** [February 2, 2024, 5:11pm UTC](https://community.zymbit.com/t/rpi-cm4-with-zymkey-4i-no-boot/1627/3 "2024-02-02T17:11:43Z")

</div>

Hi Bob!  
I was on RPi forum few days, and no decision.  
Here is an idea that the problem linked with secure boot and Zymkey module.  
My Zymkey was without a battery and always blinked blue, also USB flashdrive has a key. As I read, the indication shows unconfigured device.  
But is it possible the Zymkey module locked the boot?

---

<div class="post-metadata">

**Author:** ![Bob\_of\_Zymbit](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@Bob\_of\_Zymbit](https://community.zymbit.com/u/Bob_of_Zymbit)\
**Post date:** [February 2, 2024, 7:32pm UTC](https://community.zymbit.com/t/rpi-cm4-with-zymkey-4i-no-boot/1627/4 "2024-02-02T19:32:41Z")

</div>

@cobalt2435 - The Zymkey does not do any locking of the boot. Any references to Zymbit Supervised Boot are only applicable to our SCM product. What the Zymkey can do is lock your encrypted root partition.

Is your setup working without a Zymkey? What exactly is the USB flashdrive key used for?

---

<div class="post-metadata">

**Author:** ![cobalt2435](https://avatars.discourse-cdn.com/v4/letter/c/e99b99/32.png) [@cobalt2435](https://community.zymbit.com/u/cobalt2435)\
**Post date:** [February 2, 2024, 8:42pm UTC](https://community.zymbit.com/t/rpi-cm4-with-zymkey-4i-no-boot/1627/5 "2024-02-02T20:42:13Z")

</div>

Ok, thank you. Perhaps it is really problem with boot, and if you say that Zymkey doesn’t edit the boot, so problem with another side.  
On RPi forum they said “It is not possible to disable secure-boot once enabled or use a different code signing key.” So it is problem with original pem key for boot.img

---

<div class="post-metadata">

**Author:** ![Bob\_of\_Zymbit](https://avatars.discourse-cdn.com/v4/letter/b/82dd89/32.png) [@Bob\_of\_Zymbit](https://community.zymbit.com/u/Bob_of_Zymbit)\
**Post date:** [February 2, 2024, 9:26pm UTC](https://community.zymbit.com/t/rpi-cm4-with-zymkey-4i-no-boot/1627/6 "2024-02-02T21:26:54Z")

</div>

That is true of PI’s secure boot. Once you set the OTP bits, you cannot go back. That would not involve the Zymkey.
