When debugging comm lines with embedded linux, you can often use a library called i2c-tools that allow you to do things like send an I2C transaction over the CLI, or dump the contents of a device's registers, or probe for any devices that might be on the network. It would be super cool if we could implement something similar with GDB and STM32, where you like start GDB and then call a function that automatically probes for all devices on a bus
Reason for Spike
Board bringup is hard, and verifying comm lines are one of the more frustrating parts of it. This would streamline the bringup process to make debug a lot easier.
Spike Type
Functional
Goal
When debugging comm lines with embedded linux, you can often use a library called i2c-tools that allow you to do things like send an I2C transaction over the CLI, or dump the contents of a device's registers, or probe for any devices that might be on the network. It would be super cool if we could implement something similar with GDB and STM32, where you like start GDB and then call a function that automatically probes for all devices on a bus
Reason for Spike
Board bringup is hard, and verifying comm lines are one of the more frustrating parts of it. This would streamline the bringup process to make debug a lot easier.
Additional notes
No response