Skip to main content

Python interface to SVD files through GDB

Project description

Talk to microcontrollers through a debug probe.

Example 1

We have an nRF51822 on a Black Magic Probe. Let’s see its unique device ID:

>>> from svd_gdb.drivers.nrf5x import NRF51
>>> d = NRF51()
>>> d.FICR.DEVICEID
[nrf51.FICR.DEVICEID[0] = 0xb5b527cd, nrf51.FICR.DEVICEID[1] = 0x15896259]

The nRF51 has a random number generator. Let’s collect some random numbers with it:

>>> d.RNG.TASKS_START=1
>>> bytes(d.RNG.VALUE for _ in range(15))
b'\xa8qS\x0e\x86\xacw\xfb\x7fP\xb2\x02a9X'

Let’s see why the last reset happened:

>>> d.POWER.RESETREAS._dump()
            nrf51.POWER.RESETREAS
            | Reset reason.
0x40000400: 0x   0   0   0   0   0   0   0   4
            0b00000000000000000000000000000100
                           ^^^            ^^^^
                           |||            |||+ RESETPIN = 0x0 (NotDetected) | Reset from pin-reset detected.
                           |||            ||+- DOG = 0x0 (NotDetected) | Reset from watchdog detected.
                           |||            |+-- SREQ = 0x1 (Detected) | Reset from AIRCR.SYSRESETREQ detected.
                           |||            +--- LOCKUP = 0x0 (NotDetected) | Reset from CPU lock-up detected.
                           ||+---------------- OFF = 0x0 (NotDetected) | Reset from wake-up from OFF mode detected by the use of DETECT signal from GPIO.
                           |+----------------- LPCOMP = 0x0 (NotDetected) | Reset from wake-up from OFF mode detected by the use of ANADETECT signal from LPCOMP.
                           +------------------ DIF = 0x0 (NotDetected) | Reset from wake-up from OFF mode detected by entering into debug interface mode.

Example 2

We have a Bluepill board on the probe. A Bluepill has an STM32F103 processor, with an LED on pin C13. Let’s toggle it on:

>>> from svd_gdb.drivers.stm32 import STM32F103
>>> d = STM32F103()
>>> d.PC_13.o ^= 1

Let’s see if pin C12 is floating:

>>> d.PC_12.hiz
False

It is not. Is it pulled high or low?

>>> d.PC_12.i
0

That means it is pulled low.

Rationale

What is a Python library like this useful for?

  • Production test scripting.

    In a production test of a microcontroller system, you are already connected to a debugger, to program the application code.

    Using this library, in addition to programming code, you can do basic tests on connectivity. If your script can measure supply current, you can verify that LEDs are installed correctly. You can take readings from sensors on the board under test, and store calibration parameters.

    For comparison to alternative approaches to production testing, see Appendix A.

  • Development

    For a typically poorly-specified sensor like a commercial accelerometer, there is a fair amount of trying-and-tuning different register settings to find an optimal configuration. Using this library (perhaps with a wireless debugger), the settings can be determined in the actual circuit, before writing any firmware code.

    The same is even true for microcontroller peripherals – sometimes it is easier to prototype their operation in a scripting environment.

    I have used the library to prototype LED blinking behavior in actual hardware, for the approval of product management. We iterated through a handful of different blinking patterns in a few minutes, much faster than an approach that involves compilation cycles, or an approach that requires designing and implementing a “blink specification protocol” to control firmware at run time.

Implementation

This script uses gdb.py from the Black Magic Probe project, and extends it with register definitions from the SVD (“system view description”) file provided by the microcontroller’s vendor.

It is no accident that the SVD file happens to contain exactly the correct information to make an ergonomic Python interface to the microcontroller functionality. This kind of thing is what SVD was invented to do.

This package gets the SVD files on demand from the cmsis-svd project. But it uses its own parser.

Other projects

To use SVD files for more convenient debugging within the gdb’s shell, see https://github.com/bnahill/PyCortexMDebug

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

svd_gdb-0.0.13.tar.gz (104.2 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

svd_gdb-0.0.13-py3-none-any.whl (103.8 kB view details)

Uploaded Python 3

File details

Details for the file svd_gdb-0.0.13.tar.gz.

File metadata

  • Download URL: svd_gdb-0.0.13.tar.gz
  • Upload date:
  • Size: 104.2 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.4

File hashes

Hashes for svd_gdb-0.0.13.tar.gz
Algorithm Hash digest
SHA256 bdae60c8a486b2ad00f22178ce6115f1a732028af30d2b4622c4dc309927c741
MD5 450193778b4a4dc658f9f0f03051f7bd
BLAKE2b-256 82ebce418af8ed73838efa06c7eecf1246b622d4b767ba2dec8e4e8766899e83

See more details on using hashes here.

File details

Details for the file svd_gdb-0.0.13-py3-none-any.whl.

File metadata

  • Download URL: svd_gdb-0.0.13-py3-none-any.whl
  • Upload date:
  • Size: 103.8 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.12.4

File hashes

Hashes for svd_gdb-0.0.13-py3-none-any.whl
Algorithm Hash digest
SHA256 de9756cd21457487c36123e674e171270372ebdd363adc1b0c362bcbf7367a6d
MD5 0497884588b5c9c00f74f4d51b7d4158
BLAKE2b-256 51a91e1e66b4de6a07fe6098e02d196cfc01383b5823e38cff412ed689153e73

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page