.. include:: /keyword.rst

=========================
Troubleshooting (Windows)
=========================

.. warning::

   This section applies to Windows only.

.. contents::
    :local:
    :depth: 1

Missing Image or Binary
=======================

This issue might happen to compressed image archive in *.zip* or *.tar.gz* format.
You might encounter the following error on Windows after executing ``genio-flash``:

.. code:: text

    Traceback (most recent call last):
    ...
    with open(f"{path}/{name}-{machine}.testdata.json", 'r') as fp:
    FileNotFoundError: [Errno 2] No such file or directory: './rity-demo-image-genio-350-evk.testdata.json'

This is usually caused by incompletely extracted file archives. In this case, try the following:

1. Rename the image archive to a short name, such as ``image.tar.gz``.
2. Extract the images to root directory, such as ``D:\\`` on Windows.


.. _missing-yocto-driver:

Missing "Yocto" Device Driver
=============================

If you are connecting the board and switching it to Download Mode for the first time, you might find that

1. There is an unrecognized ``Yocto`` device, and 
2. ``genio-flash`` keeps waiting for the device after ``Jumping to bootstrap``:

.. prompt:: batch > auto
    
    > genio-flash
    Genio Tools: v1.4.a4
    Yocto Image:
            name:     Rity Demo Image (rity-demo-image)
            distro:   Rity Demo Layer 23.2-dev (rity-demo)
            codename: kirkstone
            machine:  genio-1200-evk
            overlays: ['video.dtbo', 'gpu-mali.dtbo']

    Looking for MediaTek SoC matching USB device 0e8d:0003
    Opening COM14 using baudate=115200
    Connected to MediaTek MT8168 SoC
    Sending bootstrap to address: 0x201000
    Jumping to bootstrap at address 0x201000 in AArch64 mode
    erasing mmc0
    < waiting for any device >

This is likely caused by an unrecognized device driver. To confirm if this is exactly the issue:

1. Press ``Windows+R`` and type ``devmgmt.msc`` then press ``ENTER``.
2. Check the Device Manager dialog and see if it has a **Other devices > Yocto** device that is not recognized:
   
   .. figure:: /_asset/sw_rity_get-started_flash_unrecog_dev.png
    :align: center
    :width: 640

    Unrecognized "Yocto" device in Windows Device Manager

To install driver for the unrecognized device, please follow steps below:

1. Right-click on the **Yocto** device, and select **Update Driver Software**.
2. Click **Browse my computer for driver software**.
3. Click **Let me pick from a list of device drivers on my computer**.
4. Choose **Android Device**.
5. Choose **Android Bootloader Interface**.
6. Click **Yes** if a "Update Driver Warning" dialog pops.

.. figure:: /_asset/sw_yocto_get-started_flash_update-yocto-device-driver-on-windows.gif
    :align: center
    :width: 55%


After updating the Android Bootloader Interface driver, ``genio-flash`` should be able to detect the device and start the flashing procedure.


Windows Device Drivers
======================

Different ports on Genio EVK require different Windows drivers when connected to your windows host PC. Here is a list of the drivers and the corresponding location in the Windows Device Manager:


* UART-to-USB-Serial

   .. figure:: /_asset/sw_yocto_get-started_flash_flash-troubleshoot-windows_UART-to-USB-Serial.jpg
    :align: center
    :width: 640
    
* FastBoot (for `genio-flash`)

   .. figure:: /_asset/sw_yocto_get-started_flash_flash-troubleshoot-windows_FastBoot-for-genio-flash.jpg
    :align: center
    :width: 640

* RNDIS (After boot into Yocto and connected to Windows via USB port)

   .. figure:: /_asset/sw_yocto_get-started_flash_flash-troubleshoot-windows_RNDIS.jpg
    :align: center
    :width: 640

* ADB (After boot into Yocto and connected to Windows via USB port)
    
   .. figure:: /_asset/sw_yocto_get-started_flash_flash-troubleshoot-windows_ADB.jpg
    :align: center
    :width: 640


Flash Process Paused
====================

You might find that the flashing process is "paused" during writing operation:

.. figure:: /_asset/sw_yocto_get-started_flash_windows_pause.png
    :width: 55%


And the flash process can be resumed by pressing **ENTER** in the console window.

To remedy this problem, please follow these steps:

* Click the console icon in the upper-left corner of the console window, and select **Defaults**

  .. figure:: /_asset/sw_yocto_get-started_flash_windows_open_console_setting.png
      :width: 35%

* In the Console Window Properties window:
  
  1. Click **Options** tab.
  2. Uncheck **QuickEdit** Mode in Edit Options
  3. Click **OK**

  .. figure:: /_asset/sw_yocto_get-started_flash_windows_disable-quick-edit.png
      :width: 35%

This should prevent the flashing process being paused in the future console sessions.