Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/stlink-org/stlink/pull/237 below:

[refactoring] Configurations are in the sources and not in a separate file · Issue #237 · stlink-org/stlink · GitHub

Things like the memory map, and the stuff to send to GDB are included in the source. This means that when a new chip comes out, you have to edit the source to be able to work with it. I had that yesterday when I needed to patch the source for my 030F chip (and I didn't notice until later that "git pull" would've worked).
Issue #218 is the same: new chip, slightly different -> needs source code patch.

Suggestion:

• Like AVRDUDE move the chip descriptions to a config file. Actually, having a config directory is better: Then it is much easier for people to share "Here, take my STM32F429 definition file!".
• optional: If an unknown chip is found, offer to update the "database" of known chips over the internet. Have an "version" identifier in the chip-description-files that gets updated when a higher version of the source becomes necessary. (but know that the chip matches before checking the version: "This chip requires an update of the program"

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4