Hardware/ARMEBS/4/Troubleshooting
(Difference between revisions)
(→Problem occured : 'Launching XXX') |
(typo) |
||
| Line 38: | Line 38: | ||
* 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 | + | === Problem occurred : 'Start GDB Server Job' === |
eclipse error window | eclipse error window | ||
<pre> | <pre> | ||
| Line 48: | Line 48: | ||
* 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. | * 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. | ||
| − | === Problem | + | === Problem occurred : 'Launching XXX' === |
eclipse error window | eclipse error window | ||
<pre> | <pre> | ||
Revision as of 11:29, 21 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 occurred : '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.
Problem occurred : 'Launching XXX'
eclipse error window
'Launching XXX' has encoutered a problem. Error in services launch sequence Error while launching command /openocd -c gdb_port 3333 -c telnet_port 4444 -f ...\libheivs_stm32\armebs4.cfg Error while launching command /openocd -c gdb_port 3333 -c telnet_port 4444 -f ...\workspace\libheivs_stm32\armebs4.cfg Cannot run program "/openocd": Launching failed
Solution:
- openocd not found, set the openocd_path variable to the openocd path
CreateProcess: No such file or directory
eclipse build console
arm-none-eabi-gcc.exe: error: CreateProcess: No such file or directory
Solution:
- Windows can't handle command lines longer than 32767, try to reduce the command line size.
