absolute script path in debug/run launch configuration
In stored debug/run configuration file the openocd scipt file is stored as aboslute file path
that make the configuration machine/user/os instalation type dependant what is anoying.
Opencocd manage script relative path very well so relative path solution should be posible
In confguration the key is
stringAttribute key=”fr.ac6.mcu.ide.OPENOCD_SCRIPT”
and value are
“C:\Users\xxxx\AppData\Roaming\Ac6\SW4STM32\openocd\scripts\st_board\nucleo_f401re.cfg”
“lilkley a window package install” with all file in user directory
“K:\eclipse-luna\plugins\fr.ac6.mcu.debug_1.1.0.201503121115\resources\openocd\scripts\st_board\nucleo_f401re.cfg”/”
An eclipse install from update site
idealy it should bed one using internal pulgin install relative path like :
stringAttribute key=”....openocd.gdbServerOther” value=”-f board/stm32f4discovery.cfg”
stringAttribute key=”...openocd.gdbServerExecutable” value=”${openocd_path}/${openocd_executable}”
;){kind=link}