Etcher: Problems detecting and intialising CM3 on balenaFin

[markcorbinuk]

• Etcher version: 1.5.96
• Operating system and architecture: Kubuntu 20.04 x86_64
• Image flashed: image_Raspbian-Fin-full.zip v0.1.0
• Do you see any meaningful error information in the DevTools? No

Etcher needs to be run twice to detect the Compute Module on the balenaFin (v1.0).
The first time Etcher runs it gets stuck initialising the device (as shown below):

If you quit and start Etcher again the Compute Module automatically appears as the target (as shown below):

At this point you can continue and program the device successfully.

Steps to reproduce are as follows:
1) Insert debug cable into balenaFin.
2) Power up balenaFin.
3) Run Etcher as root.
4) Select 'Flash from File'.
5) Select 'image_Raspbian-Fin-full.zip'.
6) The 'Select target' button is now available, so click it.
7) The 'Select a Drive' dialog shows 'Compute Module - Initializing device'. When the progress bar is almost complete (maybe 90%) it doesn't move any further.
8) If you exit from Etcher and immediately restart it the Compute Module automatically appears as the target.
9) You can then select 'Flash from file' and program the device.
10) Once the flashing process has completed the board can be booted into Raspbian.

[thundron]

Interesting, I'll try once more on my ubuntu VM, I can see it being slow (requiring up to a few minutes depending on the system) but not stuck

[markcorbinuk]

It seems that once it has reached the progress shown in the screenshot it is actually 'ready' because when you restart Etcher it is detected immediately. Up until now I've left it to run for about 15 minutes before giving up. I'll let it run longer and see if it completes. Let me know if there is anything I can do to help debug this.

[markcorbinuk]

It's been running for 2.5 hours this morning and is still stuck.

[thundron]

@markcorbinuk I can confirm we reproduced the issue and are investigating the cause

[thundron]

I shall correct myself - I wasn't able to reproduce this specific issue anymore, but there are multiple instances of the compute module appearing as "initialising" when just one is connected