...
- Ozone (for debugging) - download here (pick V2.62g!!!!!)
- platform-io 4.0.0+ (for building firmware) - download ($ pip install platformio) or upgrade (
$ platformio upgrade) - Drivers (details here)
- Note: to force JLink installation, run "platformio run -e teensy35_debug --target=upload"
You do not need the programmer, as the JLink probe is capable of programming the board. For the Jlink adapter, the text must be facing the processor. However, you must power the Pyxida, recommended through the programming port.
...
$ platformio run -e teensy35_debug
Or, you can build/run the pio_build_debug configuration in CLion. That is equivalent to running make pio_build_debug in the directory in which you created the Makefile with cmake.
Note: there are two platformio environments, teensy35 and teensy35_debug. Only the second one will produce DWARF debug information, which is necessary for debugging.
...
Open Ozone and create a new project with the File > New > New Project Wizard.
We are using the MK64fx512vll12 microprocessor. In the first step, select the MK64fx512xxx12 chip family, and leave peripherals blank.
In the next one, select JTAG, 1MHz, USB, and leave Serial No blank - all of this should be the default anyway.
In the third one, browse to find the .elf file you have just compiled.
Debugging
Now you are all set to debug like you would any other chip with SEGGER! If all the debug information was compiled with the code, Ozone should be able to open up the correct files. If you want to set a breakpoint in a particular C++ file, just open it in Ozone (Ctrl-O or File > Open).
The most important commands are in the top left corner - to upload, pause, resume and restart execution. There, you can also find Step Into/Over/Out while debugging.
Ozone also allows you to see Global data, Local data, set watches, see function addresses, raw memory and a lot more - pretty much all you need
...