diff options
| author | Roy Hooper <rhooper@toybox.ca> | 2019-12-17 09:48:55 -0500 |
|---|---|---|
| committer | Roy Hooper <rhooper@toybox.ca> | 2019-12-17 09:48:55 -0500 |
| commit | a7f8a0afd7239a51062ebff12d239b80de358cec (patch) | |
| tree | c888f6f7bb48ca10734ac20878481e2d009814b6 /BUILDING.md | |
| parent | a46adb6175d479870960a38b47f9bf27e0e5ccc3 (diff) | |
Address code review feedback.
Diffstat (limited to 'BUILDING.md')
| -rw-r--r-- | BUILDING.md | 10 |
1 files changed, 3 insertions, 7 deletions
diff --git a/BUILDING.md b/BUILDING.md index 794d5409a..9513f7145 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -44,10 +44,6 @@ Examples: If you aren't sure what boards exist, have a peek in the boards subdirectory of your port. -Useful make arguments or targets: - - make BOARD=circuitplayground_express clean - # Testing If you are working on changes to the core language, you might find it useful to run the test suite. @@ -70,14 +66,14 @@ A successful run will say something like # Debugging -The easiest way to debug CircuitPython on hardware is with a JLink device, JLinkGDBServer, and `gcc-arm-embedded`. +The easiest way to debug CircuitPython on hardware is with a JLink device, JLinkGDBServer, and an appropriate GDB. Instructions can be found at https://learn.adafruit.com/debugging-the-samd21-with-gdb -If using JLink, you'll need both the `JLinkGDBServer` and `arm-non-eabi-gdb-py` running. +If using JLink, you'll need both the `JLinkGDBServer` and `arm-none-eabi-gdb` running. Example: JLinkGDBServer -if SWD -device ATSAMD51J19 - arm-none-eabi-gdb-py build-metro_m4_express/firmware.elf -iex "target extended-remote :2331" + arm-none-eabi-gdb build-metro_m4_express/firmware.elf -iex "target extended-remote :2331"
\ No newline at end of file |