Loading...
 
Skip to main content

System Workbench for STM32

Forum List Topic List

Forums » System Workbench for STM32 » absolute script path in debug/run launch configuration
 
Thread actions
Print this page
  • Print all pages

    • absolute script path in debug/run launch configuration

    Posted by diabolo38 on 2015-06-10 10:49

    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}"

    Reads: 12329
    Posted by fcgehrke on 2015-07-31 03:59

    You can use the -s parameter to specify the scripts directory to OPENOCD the it will find the files when you put -f "interface/stlink-v2.cfg".

    Example: -s "C:\openocd\scripts"