Hardware/ARMEBS/4/Troubleshooting
(Difference between revisions)
(→Wrong driver) |
|||
| Line 37: | Line 37: | ||
'''''Solution:''''' | '''''Solution:''''' | ||
* A debug session is probably running. It must be stopped (Terminate) before starting another one | * A debug session is probably running. It must be stopped (Terminate) before starting another one | ||
| + | |||
| + | === Problem occured : 'Start GDB Server Job' === | ||
| + | eclipse error window | ||
| + | <pre> | ||
| + | 'Start GDB Server Job' has encoutered a problem. | ||
| + | An internal error occurred during: "Start GDB Server Job". | ||
| + | java.lang.NullPointerException | ||
| + | </pre> | ||
| + | '''''Solution:''''' | ||
| + | * Verify in the "Debug configuration..", "Debugger tab" that all eclipse variable used are valid. This is typically a ${wockspace_loc:/} depending on a closed project. | ||
Revision as of 09:52, 9 July 2014
|
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
Problem occured : 'Start GDB Server Job'
eclipse error window
'Start GDB Server Job' has encoutered a problem. An internal error occurred during: "Start GDB Server Job". java.lang.NullPointerException
Solution:
- Verify in the "Debug configuration..", "Debugger tab" that all eclipse variable used are valid. This is typically a ${wockspace_loc:/} depending on a closed project.
