Unable to Flash the Co-Processor

Seems to say nothing @bucknalla :

[97101.310025] systemd-udevd[28]: Starting version 241
[97101.979662] kauditd_printk_skb: 8 callbacks suppressed
[97101.979671] audit: type=1111 audit(1640106582.076:1055): pid=14488 uid=0 auid=4294967295 ses=4294967295 msg='op=change-system-time exe="/sbin/hwclock" hostname=? addr=? terminal=? res=failed'
[97102.078675] audit: type=1111 audit(1640106582.009:1056): pid=14498 uid=0 auid=4294967295 ses=4294967295 msg='op=change-system-time exe="/sbin/hwclock" hostname=? addr=? terminal=? res=failed'

Then it reboots.

The full log as it boots:

crbn60_fin_dmesg_01.txt (31.3 KB)

Hello @crbn60

We’ve been looking at the logs and it doesn’t seem to be standard behavior, which might indicate some HW failure. For that reason we’d like to get our hands on your device and run more intensive tests. Would you be able to send an email to store@balena.io with a link to this thread so we can get you a replacement?


I can certainly do that.

This is a production device, is there a smart way to copy the data directory and host keys into the replacement?

Thanks @ntzovanis ,


@crbn60 do you have physical access to the device or would you require to do the backup remotely?

If you do have access to it, we can ship the replacement device before retrieving the problematic one. That way you could use etcher’s clone function to clone them.
This is assuming you want the data and keys from that device copied to the replacement. Let me know if that isn’t the case.


I can get access, no problem. And yes, I’d like a full clone.

I guess I didn’t realize that the onboard eMMC was going to be accessible via USB, so that sounds much easier.



For future readers: you can not access the eMMC on a balenaFin board without a CM4 module installed.

1 Like

Sorry, you’re right and thanks for adding this.
What happens (as far as I understand, but I am not an expert on this :wink: ) - etcher is bootstrapping a variant of rpi-boot ( GitHub - raspberrypi/usbboot: Raspberry Pi USB booting code, moved from tools repository ) into the CM3 module - the CM3 is basically booting the code provided by etcher from your computers USB - which is a mini program only having one purpose: Mounting the eMMC memory as a flash drive to your computer and making it accessible. The eMMC is hardwired via the SODIMM slot to the CM3 and is not available via USB or other means, so the CM3 is just providing it to your PC as an emulated harddrive. Without the CM3 as the “converter bridge” inbetween USB and eMMC, this is not possible :slight_smile: .

1 Like

The “bad” board should be arriving today.

@crbn60 were you able to clone the device?