valinor - generate debugger project files, and launch a debugger, to debug an ELF file

       This  manual  page  is  based  on  the  valinor documentation.  It was created by Nick Morrott <nickm@de‐
       bian.org> for the Debian GNU/Linux system, but may be used by others

       Copyright (c) 2014-2015 ARM Limited

valinor is designed to be used as a proxy debug command for yotta targets to provide as their scripts.de‐
       bug command.

valinor - generate debugger project files, and launch a debugger, to debug an ELF file

       -t, --tool TOOL
              debug tool (IDE) to generate for (if omitted, a debug project will be generated for an IDE detect‐
              ed on your system, defaulting to opening a GDB debug session, if no known IDEs are detected)

       -d, --project-dir PROJECT_DIR
              directory  in  which to generate any necessary project files (default: directory of the executable
              argument)

       -n, --no-open
              do not open debug session (generate the necessary files to enable debugging and print  command  to
              proceed)

       -–target TARGET
              target  board to generate project file for (e.g. K64F) (this name is passed to project_generator -
              any name it accepts will work)

       --version
              print version and exit

       Upstream bug tracker: https://github.com/ARMmbed/valinor/issues

yotta(1), progen(1), progendef(1)

1.1.4+ds                                            May 2019                                          VALINOR(1)

valinor [--toolTOOL] [--project-dirPROJECT_DIR] [--no-open] -–targetTARGETexecutablevalinor–-version

       To use valinor to add debug support to a yotta target description, add the following to your  target.json
       file (replacing K64F with the project_generator target ID for the chip/board on your target):

              "scripts":{
                  "debug": ["valinor", "--target", "frdm-k64f", "$program"]
              }