djsundog/circuitpython
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Address code review feedback.

Browse Source
This commit is contained in:
Roy Hooper 2019-12-17 09:48:55 -05:00
parent a46adb6175
commit a7f8a0afd7
1 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
BUILDING.md
View File

@ -44,10 +44,6 @@ Examples:
If you aren't sure what boards exist, have a peek in the boards subdirectory of your port. 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 # Testing
If you are working on changes to the core language, you might find it useful to run the test suite. 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 # 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 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: Example:
JLinkGDBServer -if SWD -device ATSAMD51J19 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"