Filter results by

Recovery over USB

When something happens where your ARTIK 530 or 710 module image is corrupted, and you can't use a microSD card to recover, it is possible to recover using USB. The procedure involves:

  • Building replacement partition images

  • Loading the Android fastboot tool on your Linux development system

  • Loading a USB recovery utility to the module

  • Using the utility in conjunction with the fastboot tool to load a functioning image, partition-by-partition.

Preparation

You'll use your Linux-based development system for this procedure.

  1. Attach a USB cable from your PC to the USB OTG port on your ARTIK board. If using an ARTIK development board, you can refer to the Update by Partition article for port location.

  2. Set USB Boot Mode as shown. These settings will cause the ARTIK module USB OTG port to identify as a bulk transfer device (the USB recovery port) after reset.

    On your development board
    For your custom design
  3. Install driver.

  1. Download the Nexell USB driver
  2. Open Device Manager.
  3. Power up and reset the board; an unknown USB device will appear.
  4. Update the device drivers to use the Nexell driver.
  5. Unplug and reattach your ARTIK board USB cable, and check that the device appears in Device Manager under "libusb" as NEXELL_BULK_USB.
  1. Download the Nexell USB driver
  2. You must disable Windows 10 driver signature enforcement before you can install the Nexell driver. It is unsigned, as it is only intended for development purposes.
    1. Start Command Prompt as administrator.
    2. Enter
      bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
      bcdedit.exe -set TESTSIGNING ON
    3. Restart the system.
  3. Open Device Manager.
  4. Power up and reset the board; an unknown USB device will appear.
  5. Update the device drivers to use the Nexell driver.
    When the security message box pops up, select "Install" as shown.
  6. Unplug and reattach your ARTIK board USB cable, and check that the device appears in Device Manager under "libusb" as NEXELL_BULK_USB.

Power up and reset your ARTIK board, and check using lsusb that the device appears as "Samsung Electronics Co., Ltd."

If you have the USB debug port connected, you won't see anything on the debug terminal interface at this time.

VirtualBox

For Linux running on a Windows machine under VirtualBox, you'll need to take control of the "Samsung Electronics Co., Ltd." device, the name of the USB recovery port on your ARTIK board.

  1. Click Settings.
  2. Select USB.
  3. Choose USB 3.0.
  4. Click the second icon on the right side, bringing up a list of available USB devices.
  5. Select the "Samsung Electronics Co., Ltd." device and click OK.

Load Recovery Tool

  1. Change to your output build directory. For example:
    cd build-artik/output/images/artik530s/1.0/20171115.19/

  2. Open the usb_recoveery.sh script. If you find
    sleep 1
    between sections, replace it with
    echo "Press Enter to continue to the second part...
    read -n 1

  3. Power up and reset your ARTIK board, and make sure your USB cable is connected.

  4. Run the script to transfer the necessary recovery files for your module type.
    ./usb_recovery.sh artik530
    ./usb_recovery.sh artik530s
    ./usb_recovery.sh artik710
    ./usb_recovery.sh artik710s
    The script runs the usb-downloader program twice, pausing in between.

  5. Before hitting Enter to continue, unplug and then reconnect the USB cable.

  6. Hit Enter to continue.

You should see "Success" noted for both transfers. If not, repeat the procedure.

Load Partitions

With the USB recovery tool in place, you'll use the Android fastboot tools to load one partition at a time using the flash_all_by_fastboot.sh script.

Note: Using OTA? You may need to manually change partmap_emmc.txt to partmap_emmc_ota.txt if the script does not already handle this.

Go now to the Update by Partition article and follow the instructions to set up, then run
./flash_all_by_fastboot.sh

Remember to restore your boot mode settings for normal operation. Otherwise, the USB OTG device will be the wrong one for fastboot.

Last updated on: