Flashing Yocto on Genio 1200 is stuck or fails

Hi,

Hope someone has an idea what is going on here. I am following the instructions on this page: Genio 1200 EVK Demo Requirements — IoT Yocto documentation

Unfortunately it worked once, and then never again!

Here some additional information:

$ uname -a
Linux vuwall-DH610 6.17.0-14-generic #14~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 15 15:52:10 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
$ python3 --version
Python 3.12.3
$ genio-flash --version
1.7.0

$ sudo dmesg | grep tty
[sudo] password for vuwall:
[ 0.113760] printk: legacy console [tty0] enabled
[ 0.407365] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 0.432035] 00:02: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[15469.033372] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0

download and unpacking the following:
scarthgap_k6.6_v25.1_genio-1200-evk_private_251230072807.tar.gz

genio-flash
Genio Tools: v1.7.0
Yocto Image:
name: Rity Demo Image (rity-demo-image)
distro: Rity Demo Layer 25.1-release (rity-demo)
codename: scarthgap
machine: genio-1200-evk
overlays: [‘display-dsi.dtbo’, ‘display-hdmi.dtbo’, ‘video.dtbo’, ‘apusys.dtbo’]

WARNING:aiot:[Errno 22] Invalid argument
WARNING:aiot:Board control failed. Possible causes are:

  1. This is not a Genio 350/700 EVK, nor a Pumpkin board.
  2. The board port UART0 is not connected.
  3. The UART0 port is being opened by another tool, such as TeraTerm on Windows.
    You can now manually reset the board into DOWNLOAD mode.

INFO:aiot:Continue flashing…
Looking for MediaTek SoC matching USB device 0e8d:0003
Opening /dev/ttyACM0 using baudrate=115200
Connected to MediaTek SoC: hw_code[0x8195]
Sending bootstrap to address: 0x201000
Jumping to bootstrap at address 0x201000 in AArch64 mode
erasing mmc0
< waiting for any device >

stuck at this point indefinetively

other times I get a little bit further:
$ genio-flash
Genio Tools: v1.7.0
Yocto Image:
name: Rity Demo Image (rity-demo-image)
distro: Rity Demo Layer 25.1-release (rity-demo)
codename: scarthgap
machine: genio-1200-evk
overlays: [‘display-dsi.dtbo’, ‘display-hdmi.dtbo’, ‘apusys.dtbo’, ‘video.dtbo’]

WARNING:aiot:[Errno 22] Invalid argument
WARNING:aiot:Board control failed. Possible causes are:

  1. This is not a Genio 350/700 EVK, nor a Pumpkin board.
  2. The board port UART0 is not connected.
  3. The UART0 port is being opened by another tool, such as TeraTerm on Windows.
    You can now manually reset the board into DOWNLOAD mode.

INFO:aiot:Continue flashing…
Looking for MediaTek SoC matching USB device 0e8d:0003
Opening /dev/ttyACM0 using baudrate=115200
Connected to MediaTek SoC: hw_code[0x8195]
Sending bootstrap to address: 0x201000
Jumping to bootstrap at address 0x201000 in AArch64 mode
erasing mmc0
< waiting for any device >
Erasing ‘mmc0’ (bootloader) request sz: 0xece000000, real erase len: 0x0
OKAY [ 0.217s]
Finished. Total time: 0.220s
erasing mmc0boot0
Erasing ‘mmc0boot0’ (bootloader) request sz: 0x400000, real erase len: 0x400000
OKAY [ 0.138s]
Finished. Total time: 0.142s
erasing mmc0boot1
Erasing ‘mmc0boot1’ (bootloader) request sz: 0x400000, real erase len: 0x400000
OKAY [ 0.015s]
Finished. Total time: 0.019s
flashing mmc0=rity-demo-image-genio-1200-evk.rootfs.wic.img
Warning: skip copying mmc0 image avb footer (mmc0 partition size: 0, mmc0 image size: 140736921043912).
Sending sparse ‘mmc0’ 1/16 (262140 KB) OKAY [ 7.004s]
Writing ‘mmc0’ FAILED (remote: ‘flash write failure’)
fastboot: error: Command failed
flashing mmc0boot0=bl2.img
Warning: skip copying mmc0boot0 image avb footer (mmc0boot0 partition size: 0, mmc0boot0 image size: 235264).
Sending ‘mmc0boot0’ (229 KB) OKAY [ 0.008s]
Writing ‘mmc0boot0’ FAILED (remote: ‘Flash write failure.’)
fastboot: error: Command failed
Detected U-Boot env size: 4096
flashing mmc0boot1=u-boot-env.bin
Warning: skip copying mmc0boot1 image avb footer (mmc0boot1 partition size: 0, mmc0boot1 image size: 4096).
Sending ‘mmc0boot1’ (4 KB) OKAY [ 0.002s]
Writing ‘mmc0boot1’ FAILED (remote: ‘Flash write failure.’)
fastboot: error: Command failed
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.052s

either way: the board will not boot!

Thanks.

Hi Enno,

From the console messages you posted, I’m not sure, but it looks like you’re using a bad quality USB-C cable. Because an USB-C cable is used for flashing Genio 1200 EVK, bad cable sometimes may cause random failure to the flashing process. Can you use another one and see if it can improve?

Spend some time today again and tried it on a complete differntn machine. This time withe Windows 11 instead of Ubuntu 24.04.

Same result:

Thanks. I replaced all cables and also tried a different machine (see post below). Always with the same result.