Hardware/ARMEBS/4/Troubleshooting

From UIT
Revision as of 09:44, 9 July 2014 by Pim (Talk | contribs)
Jump to: navigation, search

Contents

ARMEBS4 Troubleshooting and common problems

Connection problems

When the programming fails, go to the openocd console, searching for "Error:" messages

Wrong driver

openocd console

...
Error: failed to reset FTDI device: -1
Error: unable to open ftdi device with vid 08ee, pid 3100, description '*' and serial '*'

Solution: The driver is wrong, run zadig.exe, "options -> list all devices", select "armebs4 interface 0", select "WinUSB" driver -> Replace driver

Board not connected

openocd console

...
Error: no device found
Error: unable to open ftdi device with vid 08ee, pid 3100, description '*' and serial '*'

Solution:

  • Verify the USB debug connector is connected
  • Verify the PWR led, it should be on (green)

Another openocd is running

openocd console

...
Error: libusb_open() failed with LIBUSB_ERROR_ACCESS
Error: no device found
Error: unable to open ftdi device with vid 08ee, pid 3100, description '*' and serial '*'

Solution:

  • A debug session is probably running. It must be stopped (Terminate) before starting another one
Personal tools
Namespaces
Variants
Actions
Navigation
Browse
Toolbox