Unable to flash Android pre-build image on windows

General Discussion
1

I’m following the blow document page to setup my win10 environment:

and according to this page:

I’m preparing to flash the Android pre-build image.

However, my genio-flash --version is 1.4.2, while Genio 720 requires 1.7.0a2 version or later.

I tried to upgrade my genio-tool version and encountered the following error:

ERROR: Could not find a version that satisfies the requirement windows-curses; platform_system == “Windows” (from genio-tools) (from versions: none)
ERROR: No matching distribution found for windows-curses; platform_system == “Windows”

How can I fix the issue?

Thanks very much.

2

Dear odin_lin,

Welcome to the Genio community! We’re excited to have you on board.

To help you get started, could you please let us know which version of Python you’re using?

You can download Genio Tool directly from:
https://pypi.org/project/genio-tools/

If you’d like to make sure you’re running the latest version, just use this command:

pip install -U --pre genio-tools

Please let me know if this takes care of the issue—or if you run into any trouble, feel free to ask!

Thanks,
Santosh

3

Dear Santosh,

Here is my python version:

D:>python --version
Python 3.14.2

D:>pip --version
pip 25.3 from C:\Users\odin\AppData\Local\Programs\Python\Python314\Lib\site-packages\pip (python 3.14)

D:>pip3 --version
pip 25.3 from C:\Users\odin\AppData\Local\Programs\Python\Python314\Lib\site-packages\pip (python 3.14)

I think they should be the latest version.

Thanks,

Odin

4

Dear Odin,

Thanks for reaching out!

When you get a chance, could you try using Python version 3.12?

You can download Genio Tool directly from:

After downloading, please run the following command to install Genio Tool:

pip install genio-tools==1.7.0a5

Let me know how it goes, and if you run into any trouble, I’m here to help!

Thanks so much,
Santosh

5

OK, I will try it and let you know the latest status update.

Thanks very much.

Odin

6

Dear Santosh,

Thank you for your support. I can now flash the Android image to eMMC correctly.

The following messages are from my DOS prompt:

D:\aiot8391p2>genio-flash
Genio Tools: v1.7.0a5
Raw Image:
name: UFS Disk Image (Sparse Image)
machine: Unspecified

WARNING:aiot:Cannot find any FTDI device
WARNING:aiot:Unable to find and reset the board. 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 COM6 using baudrate=115200
Connected to MediaTek SoC: hw_code[0x8189]
Sending bootstrap to address: 0x2001000
Jumping to bootstrap at address 0x2001000 in AArch64 mode
erasing mmc0
< waiting for any device >
Erasing ‘mmc0’ (bootloader) request sz: 0xed2000000, real erase len: 0x0
OKAY [ 0.283s]
Finished. Total time: 0.294s
erasing mmc0boot0
Erasing ‘mmc0boot0’ (bootloader) request sz: 0x1f80000, real erase len: 0x1f80000
OKAY [ 0.013s]
Finished. Total time: 0.020s
erasing mmc0boot1
Erasing ‘mmc0boot1’ (bootloader) request sz: 0x1f80000, real erase len: 0x1f80000
OKAY [ 0.009s]
Finished. Total time: 0.018s
flashing mmc0=ufs_lu2.bin
Sending sparse ‘mmc0’ 1/7 (262141 KB) OKAY [ 6.332s]
Writing ‘mmc0’ OKAY [ 7.971s]
Sending sparse ‘mmc0’ 2/7 (262140 KB) OKAY [ 6.286s]
Writing ‘mmc0’ OKAY [ 7.638s]
Sending sparse ‘mmc0’ 3/7 (262140 KB) OKAY [ 6.289s]
Writing ‘mmc0’ OKAY [ 7.649s]
Sending sparse ‘mmc0’ 4/7 (262140 KB) OKAY [ 6.283s]
Writing ‘mmc0’ OKAY [ 7.629s]
Sending sparse ‘mmc0’ 5/7 (262140 KB) OKAY [ 6.285s]
Writing ‘mmc0’ OKAY [ 7.638s]
Sending sparse ‘mmc0’ 6/7 (262140 KB) OKAY [ 6.294s]
Writing ‘mmc0’ OKAY [ 7.648s]
Sending sparse ‘mmc0’ 7/7 (208524 KB) OKAY [ 5.006s]
Writing ‘mmc0’ OKAY [ 7.212s]
Finished. Total time: 128.572s
flashing mmc0boot0=ufs_lu0_lu1.bin
Warning: skip copying mmc0boot0 image avb footer (mmc0boot0 partition size: 0, mmc0boot0 image size: 2097152).
Sending ‘mmc0boot0’ (2048 KB) OKAY [ 0.085s]
Writing ‘mmc0boot0’ OKAY [ 0.529s]
Finished. Total time: 0.671s
flashing mmc0boot1=ufs_lu0_lu1.bin
Warning: skip copying mmc0boot1 image avb footer (mmc0boot1 partition size: 0, mmc0boot1 image size: 2097152).
Sending ‘mmc0boot1’ (2048 KB) OKAY [ 0.051s]
Writing ‘mmc0boot1’ OKAY [ 0.519s]
Finished. Total time: 0.599s
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.004s

It seems the flashing process has completed.

However, my Genio 720 EVK cannot boot.

When I pressed the power button, the screen remained completely black and there was no response.

Thanks very much.

Odin

7

Dear Odin,

The logs show that flashing was successful.
Could you please try erasing and re-flashing the image, then confirm?

Thanks,
Santosh

8

Dear Odin,

Could you double-check that the USB-C cable is connected to the Download port? Please try rebooting the box as well, and let me know what happens.

Thanks so much,
Santosh

9

Dear Santosh,

I have tried to erase the emmc, the following are my DOS message:

// ------------------------------------------------------------------------
D:\aiot8391p2>genio-flash erase-mmc
Genio Tools: v1.7.0a5
Raw Image:
name: UFS Disk Image (Sparse Image)
machine: Unspecified

WARNING:aiot:Cannot find any FTDI device
WARNING:aiot:Unable to find and reset the board. 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 COM6 using baudrate=115200
Connected to MediaTek SoC: hw_code[0x8189]
Sending bootstrap to address: 0x2001000
Jumping to bootstrap at address 0x2001000 in AArch64 mode
erasing mmc0
Erasing ‘mmc0’ (bootloader) request sz: 0xed2000000, real erase len: 0x0
OKAY [ 0.293s]
Finished. Total time: 0.504s
erasing mmc0boot0
Erasing ‘mmc0boot0’ (bootloader) request sz: 0x1f80000, real erase len: 0x1f80000
OKAY [ 0.010s]
Finished. Total time: 0.015s
erasing mmc0boot1
Erasing ‘mmc0boot1’ (bootloader) request sz: 0x1f80000, real erase len: 0x1f80000
OKAY [ 0.010s]
Finished. Total time: 0.016s
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.004s

// ------------------------------------------------------------------------
D:\aiot8391p2>genio-flash
Genio Tools: v1.7.0a5
Raw Image:
name: UFS Disk Image (Sparse Image)
machine: Unspecified

WARNING:aiot:Cannot find any FTDI device
WARNING:aiot:Unable to find and reset the board. 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 COM6 using baudrate=115200
Connected to MediaTek SoC: hw_code[0x8189]
Sending bootstrap to address: 0x2001000
Jumping to bootstrap at address 0x2001000 in AArch64 mode
erasing mmc0
< waiting for any device >
Erasing ‘mmc0’ (bootloader) request sz: 0xed2000000, real erase len: 0x0
OKAY [ 0.097s]
Finished. Total time: 0.105s
erasing mmc0boot0
Erasing ‘mmc0boot0’ (bootloader) request sz: 0x1f80000, real erase len: 0x1f80000
OKAY [ 0.008s]
Finished. Total time: 0.015s
erasing mmc0boot1
Erasing ‘mmc0boot1’ (bootloader) request sz: 0x1f80000, real erase len: 0x1f80000
OKAY [ 0.008s]
Finished. Total time: 0.014s
flashing mmc0=ufs_lu2.bin
Sending sparse ‘mmc0’ 1/7 (262141 KB) OKAY [ 6.272s]
Writing ‘mmc0’ OKAY [ 7.958s]
Sending sparse ‘mmc0’ 2/7 (262140 KB) OKAY [ 6.242s]
Writing ‘mmc0’ OKAY [ 7.643s]
Sending sparse ‘mmc0’ 3/7 (262140 KB) OKAY [ 6.260s]
Writing ‘mmc0’ OKAY [ 7.629s]
Sending sparse ‘mmc0’ 4/7 (262140 KB) OKAY [ 6.218s]
Writing ‘mmc0’ OKAY [ 7.637s]
Sending sparse ‘mmc0’ 5/7 (262140 KB) OKAY [ 6.261s]
Writing ‘mmc0’ OKAY [ 7.644s]
Sending sparse ‘mmc0’ 6/7 (262140 KB) OKAY [ 6.288s]
Writing ‘mmc0’ OKAY [ 7.643s]
Sending sparse ‘mmc0’ 7/7 (208524 KB) OKAY [ 4.977s]
Writing ‘mmc0’ OKAY [ 7.195s]
Finished. Total time: 128.441s
flashing mmc0boot0=ufs_lu0_lu1.bin
Warning: skip copying mmc0boot0 image avb footer (mmc0boot0 partition size: 0, mmc0boot0 image size: 2097152).
Sending ‘mmc0boot0’ (2048 KB) OKAY [ 0.074s]
Writing ‘mmc0boot0’ OKAY [ 0.527s]
Finished. Total time: 0.674s
flashing mmc0boot1=ufs_lu0_lu1.bin
Warning: skip copying mmc0boot1 image avb footer (mmc0boot1 partition size: 0, mmc0boot1 image size: 2097152).
Sending ‘mmc0boot1’ (2048 KB) OKAY [ 0.050s]
Writing ‘mmc0boot1’ OKAY [ 0.518s]
Finished. Total time: 0.590s
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.004s

I’m pretty sure the USB-C cable is connected to the Download port, and the result was the same as before.

I have some things i’d like confirm with you:

  1. When we first received the Genio-720 EVK, the devault storage is ufs.
  2. Then we switch the jumper according to Build Genio 720/520 EVK Images from Latest IoT Yocto v25.1-dev (UFS and eMMC Boot), select the system boot from eMMC. Because the pre-build image “aiot8391p2_64_bsp_alps-vf-mp-u0.mp5-mp-v0.mp5-V7.48.V4.47_user_raw“ cannot be flashed to ufs.
  3. Finally, we follow the steps in the document to flash the Android image.

Is there any thing wrong with any of the above?

Thanks,

Odin

10

Hi Odin,

Note:
The prebuilt Android image aiot8391p2_64_bsp_alps-vf-mp-u0.mp5-mp-v0.mp5-V7.48.V4.47_user_raw is ONLY applicable to UFS boot .
The image is incompatible with eMMC. Therefore, the board won’t boot if you flash the prebuilt UFS image to the board when configured as eMMC boot.

Steps to Try

  1. Set the board to UFS boot according to the EVK user guide/Jumper settings.
  2. Flash aiot8391p2_64_bsp_alps-vf-mp-u0.mp5-mp-v0.mp5-V7.48.V4.47_user_raw to UFS.
  3. Check if the board boots successfully.

If the Problem Persists

  1. Connect to the UART0 port
  2. Set baudrate to 921600
  3. Manually reset & put the board into DOWNLOAD mode.
    This is because genio-flash cannot automatically put the board into download mode if the UART0 port is being occupied by other Windows applications.
11

Hi, Santosh,

We have tried flashing the image the UFS, the flowing messages are from my DOS prompt:

D:\aiot8391p2>genio-flash
Genio Tools: v1.7.0a5
Raw Image:
name: UFS Disk Image (Sparse Image)
machine: Unspecified

WARNING:aiot:DEVICE_NOT_OPENED
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 COM6 using baudrate=115200
Connected to MediaTek SoC: hw_code[0x8189]
Sending bootstrap to address: 0x2001000
Jumping to bootstrap at address 0x2001000 in AArch64 mode
erasing mmc0
< waiting for any device >
Erasing ‘mmc0’ FAILED (remote: ‘Partition does not exist.’)
fastboot: error: Command failed
Traceback (most recent call last):
File “”, line 198, in _run_module_as_main
File “”, line 88, in run_code
File "C:\Users\odin\AppData\Local\Programs\Python\Python312\Scripts\genio-flash.exe_main.py", line 7, in
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flashtool.py”, line 149, in main
tool.execute()
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flashtool.py”, line 115, in execute
self.run_worker(image, args)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flashtool.py”, line 144, in run_worker
flasher.flash_worker(image=image, args=args)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flash.py”, line 196, in flash_worker
self.flash(args.targets)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flash.py”, line 148, in flash
self.flash_group(target)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flash.py”, line 97, in flash_group
self.erase_partition(partition)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flash.py”, line 63, in erase_partition
self.fastboot.erase(partition)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\fastboot.py”, line 128, in erase
return self._run_command(command)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\fastboot.py”, line 31, in _run_command
subprocess.run(command, check=True)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\subprocess.py”, line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command ‘[‘fastboot’, ‘erase’, ‘mmc0’]’ returned non-zero exit status 1.

//———————————————————

And there are some errors in the UART0 console messages:

===============================================================================

Dram Type= LPDDR5, Freq= 1544, FreqGroup= 1600, CH_1, rank 1
fsp= 0, odt_onoff= 0, Byte mode= 662448, Lat mode= 306452, DivMode= 0, ByteSwap=0

[3200][CH1][RK1][RX] Bit0 Center 85 (35 ~ 135) 662560
[3200][CH1][RK1][RX] Bit1 Center 87 (35 ~ 139) 662560
[3200][CH1][RK1][RX] Bit2 Center 93 (39 ~ 147) 662560
[3200][CH1][RK1][RX] Bit3 Center 99 (47 ~ 151) 662560
[3200][CH1][RK1][RX] Bit4 Center 111 (59 ~ 163) 662560
[3200][CH1][RK1][RX] Bit5 Center 111 (59 ~ 163) 662560
[3200][CH1][RK1][RX] Bit6 Center 103 (55 ~ 151) 662560
[3200][CH1][RK1][RX] Bit7 Center 101 (47 ~ 155) 662560
[3200][CH1][RK1][RX] Bit8 Center 101 (47 ~ 155) 662560
[3200][CH1][RK1][RX] Bit9 Center 91 (39 ~ 143) 662560
[3200][CH1][RK1][RX] Bit10 Center 103 (51 ~ 155) 662560
[3200][CH1][RK1][RX] Bit11 Center 97 (51 ~ 143) 662560
[3200][CH1][RK1][RX] Bit12 Center 87 (35 ~ 139) 662560
[3200][CH1][RK1][RX] Bit13 Center 87 (35 ~ 139) 662560
[3200][CH1][RK1][RX] Bit14 Center 89 (39 ~ 139) 6MI] Dram manu id is 255
[EMI] (16+16)+(16+16) setting, CONA=0xf053f154
[EMI] Vcore -1, Vmddr -1
[Dramc_Top] dramc_set_vcore_voltage :725000
Restore Vcore = -1
check_dramc_voltage_after_k: Read voltage: Vdd1 = -1, Vcore = -1, Vddq = -1, Vmddr = -1, Vdd2H = -1, Vdd2L = 0
[MEM] Memory size: 0x200000000
[MEM] mt_mem_init(): done
[DA] gpio_trap_value : 0x0
[DA] storage_tpye: UFS
device descriptor length = 0x59
power descriptor length = 0x62
interconnect descriptor length = 0x6
configuration descriptor length = 0xe6
unit descriptor length = 0x2d
geometry descriptor length = 0x57
[UFS] UFS version 3.10
[UFS] ufs_get_device_info: Device Desc:
59 0 0 0 0 0 3 4 1 1 1 7f 0 1 f 0
3 10 4 31 0 1 3 4 1 45 16 1a 2 0 0 b3
7 20 b2 fd 20 0 96 a1 e0 17 2 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2 3 b3 1 0 0 0 0 0
[UFS] Unipro version= 5
TW Reduction = 1, TW Type = 0
Shared WB Buffer AU = 0x0
ud0_base_offset = 22, ud_config_len = 26
[UFS] get unit serial number string len 0x18
[UFS] vendor id : 0x145
[UFS] ufs id : SDINFDO4-128G
[UFS] ufs fwver: 2218
[UFS] ufs serial number: f1a0103341d28320af249621
[UFS] dev_quirk = 0x0
opcode 0x1 for idn 1 failed, err = 251
[UFS] failed reading ufshcd_read_desc_param. desc_id 1 param_offset 0 desc_len 230 ret 251
[UFS] err: ufs_check_lu_cfg: read config descr error: 251
hba->dev_info.bootable: 0x1
[UFS] info: LU Configuration Check OK. Bootable UFS
[UFS] info: Boot LU Configuration Check OK. Active Boot LU: LU0
opcode 0x1 for idn 1 failed, err = 251
[UFS] failed reading ufshcd_read_desc_param. desc_id 1 param_offset 0 desc_len 230 ret 251
[UFS] err: ufs_check_lu_cfg: read config descr error: 251
bug: active_num_lu shall not be 0[UFS] info: HS-G1-2
[UFS] Sense Data: ASC=29, ASCQ=3
[UFS] err: task response error = 1
[UFS] err: ufs_get_lu_size: ufshcd_queuecommand err
[UFS] err: ufs_get_lu_size(0) fail, ret -5
starting app fitboot
block devices:
fastboot_init()
[USB] U2 pullup D+
[USB] HS (2) is detected
[USB] usb_online: 1
fastboot: processing commands
fastboot: getvar:has-slot:mmc0[len:20]
fastboot:[download_base:0xffff000300000000][download_size:0x0]
fastboot:[cmd:getvar:]-[arg:has-slot:mmc0]
fastboot: getvar:partition-type:mmc0[len:26]
fastboot:[download_base:0xffff000300000000][download_size:0x0]
fastboot:[cmd:getvar:]-[arg:partition-type:mmc0]
fastboot: erase:mmc0[len:10]
fastboot:[download_base:0xffff000300000000][download_size:0x0]
fastboot:[cmd:erase:]-[arg:mmc0]
cmd_erase mmc0
Partition does not exist.

How can I fix that?

Thanks.

Odin.

12

Hi, Santosh,

We have tried flashing the image the UFS, the flowing messages are from my DOS prompt:

D:\aiot8391p2>genio-flash
Genio Tools: v1.7.0a5
Raw Image:
name: UFS Disk Image (Sparse Image)
machine: Unspecified

WARNING:aiot:DEVICE_NOT_OPENED
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 COM6 using baudrate=115200
Connected to MediaTek SoC: hw_code[0x8189]
Sending bootstrap to address: 0x2001000
Jumping to bootstrap at address 0x2001000 in AArch64 mode
erasing mmc0
< waiting for any device >
Erasing ‘mmc0’ FAILED (remote: ‘Partition does not exist.’)
fastboot: error: Command failed
Traceback (most recent call last):
File “”, line 198, in _run_module_as_main
File “”, line 88, in run_code
File "C:\Users\odin\AppData\Local\Programs\Python\Python312\Scripts\genio-flash.exe_main.py", line 7, in
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flashtool.py”, line 149, in main
tool.execute()
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flashtool.py”, line 115, in execute
self.run_worker(image, args)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flashtool.py”, line 144, in run_worker
flasher.flash_worker(image=image, args=args)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flash.py”, line 196, in flash_worker
self.flash(args.targets)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flash.py”, line 148, in flash
self.flash_group(target)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flash.py”, line 97, in flash_group
self.erase_partition(partition)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\flash.py”, line 63, in erase_partition
self.fastboot.erase(partition)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\fastboot.py”, line 128, in erase
return self._run_command(command)
^^^^^^^^^^^^^^^^^^^^^^^^^^
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\site-packages\aiot\fastboot.py”, line 31, in _run_command
subprocess.run(command, check=True)
File “C:\Users\odin\AppData\Local\Programs\Python\Python312\Lib\subprocess.py”, line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command ‘[‘fastboot’, ‘erase’, ‘mmc0’]’ returned non-zero exit status 1.

//———————————————————

And there are some errors in the UART0 console messages:

===============================================================================

Dram Type= LPDDR5, Freq= 1544, FreqGroup= 1600, CH_1, rank 1
fsp= 0, odt_onoff= 0, Byte mode= 662448, Lat mode= 306452, DivMode= 0, ByteSwap=0

[3200][CH1][RK1][RX] Bit0 Center 85 (35 ~ 135) 662560
[3200][CH1][RK1][RX] Bit1 Center 87 (35 ~ 139) 662560
[3200][CH1][RK1][RX] Bit2 Center 93 (39 ~ 147) 662560
[3200][CH1][RK1][RX] Bit3 Center 99 (47 ~ 151) 662560
[3200][CH1][RK1][RX] Bit4 Center 111 (59 ~ 163) 662560
[3200][CH1][RK1][RX] Bit5 Center 111 (59 ~ 163) 662560
[3200][CH1][RK1][RX] Bit6 Center 103 (55 ~ 151) 662560
[3200][CH1][RK1][RX] Bit7 Center 101 (47 ~ 155) 662560
[3200][CH1][RK1][RX] Bit8 Center 101 (47 ~ 155) 662560
[3200][CH1][RK1][RX] Bit9 Center 91 (39 ~ 143) 662560
[3200][CH1][RK1][RX] Bit10 Center 103 (51 ~ 155) 662560
[3200][CH1][RK1][RX] Bit11 Center 97 (51 ~ 143) 662560
[3200][CH1][RK1][RX] Bit12 Center 87 (35 ~ 139) 662560
[3200][CH1][RK1][RX] Bit13 Center 87 (35 ~ 139) 662560
[3200][CH1][RK1][RX] Bit14 Center 89 (39 ~ 139) 6MI] Dram manu id is 255
[EMI] (16+16)+(16+16) setting, CONA=0xf053f154
[EMI] Vcore -1, Vmddr -1
[Dramc_Top] dramc_set_vcore_voltage :725000
Restore Vcore = -1
check_dramc_voltage_after_k: Read voltage: Vdd1 = -1, Vcore = -1, Vddq = -1, Vmddr = -1, Vdd2H = -1, Vdd2L = 0
[MEM] Memory size: 0x200000000
[MEM] mt_mem_init(): done
[DA] gpio_trap_value : 0x0
[DA] storage_tpye: UFS
device descriptor length = 0x59
power descriptor length = 0x62
interconnect descriptor length = 0x6
configuration descriptor length = 0xe6
unit descriptor length = 0x2d
geometry descriptor length = 0x57
[UFS] UFS version 3.10
[UFS] ufs_get_device_info: Device Desc:
59 0 0 0 0 0 3 4 1 1 1 7f 0 1 f 0
3 10 4 31 0 1 3 4 1 45 16 1a 2 0 0 b3
7 20 b2 fd 20 0 96 a1 e0 17 2 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2 3 b3 1 0 0 0 0 0
[UFS] Unipro version= 5
TW Reduction = 1, TW Type = 0
Shared WB Buffer AU = 0x0
ud0_base_offset = 22, ud_config_len = 26
[UFS] get unit serial number string len 0x18
[UFS] vendor id : 0x145
[UFS] ufs id : SDINFDO4-128G
[UFS] ufs fwver: 2218
[UFS] ufs serial number: f1a0103341d28320af249621
[UFS] dev_quirk = 0x0
opcode 0x1 for idn 1 failed, err = 251
[UFS] failed reading ufshcd_read_desc_param. desc_id 1 param_offset 0 desc_len 230 ret 251
[UFS] err: ufs_check_lu_cfg: read config descr error: 251
hba->dev_info.bootable: 0x1
[UFS] info: LU Configuration Check OK. Bootable UFS
[UFS] info: Boot LU Configuration Check OK. Active Boot LU: LU0
opcode 0x1 for idn 1 failed, err = 251
[UFS] failed reading ufshcd_read_desc_param. desc_id 1 param_offset 0 desc_len 230 ret 251
[UFS] err: ufs_check_lu_cfg: read config descr error: 251
bug: active_num_lu shall not be 0[UFS] info: HS-G1-2
[UFS] Sense Data: ASC=29, ASCQ=3
[UFS] err: task response error = 1
[UFS] err: ufs_get_lu_size: ufshcd_queuecommand err
[UFS] err: ufs_get_lu_size(0) fail, ret -5
starting app fitboot
block devices:
fastboot_init()
[USB] U2 pullup D+
[USB] HS (2) is detected
[USB] usb_online: 1
fastboot: processing commands
fastboot: getvar:has-slot:mmc0[len:20]
fastboot:[download_base:0xffff000300000000][download_size:0x0]
fastboot:[cmd:getvar:]-[arg:has-slot:mmc0]
fastboot: getvar:partition-type:mmc0[len:26]
fastboot:[download_base:0xffff000300000000][download_size:0x0]
fastboot:[cmd:getvar:]-[arg:partition-type:mmc0]
fastboot: erase:mmc0[len:10]
fastboot:[download_base:0xffff000300000000][download_size:0x0]
fastboot:[cmd:erase:]-[arg:mmc0]
cmd_erase mmc0
Partition does not exist.

How can I fix that?

Thanks.

Odin.

In additional, here are the jumper settings on our board.

53304
533041195×423 114 KB

13

Hi, Santosh,

I mentioned this issue to another engineer, and he suggested that it may be due to we flashing the device with Yocto Linux 25.1-dev (scarthgap_k6.6_v25.1_genio-720-evk-ufs_private_251026184708_dev.tar.gz) when we first received the EVK, resulting in a partition or preloader error.

If so, how can we solve this problem?

Thanks,

Odion

14

Dear Odin,

We are currently checking this internally and will revert back to you soon.

Thank you,
Santosh

15

Hi Odin,

The ufs:SDINFDO4-128G is not supported until Yocto 25.1-dev PR4. So please try to utilize PR4 or PR5 SW package to flash your EVK.