Expanded and revised list of chips #1145
Conversation
- Updated CHANGELOG.md - Updated GitHub security policy - [doc] Updated steps for release procedure - [doc] Updated list of supported OS - Removed old clang_analyze script - Minor fix in travis build script
|
@Ant-ON I switched this to the testing branch, because I had updated the names and also unified the chip-id defines as part of the chip-config separation from the source code (#1129). So one has to resolve the differences: Use of the changed defines + additional changes to the descriptions from your side. Both is useful, but conflicts need to be resolved. |
|
As I have noticed, some defines need to be updated as well. As currently proposed (see testing branch) I'd prefer to use a small "x" for placeholders in MCU names/types to distinguish from the capital "X" used by ST Microelectronics in some MCU part names. |
|
@Nightwalker-87 In the |
|
@Nightwalker-87 In most codding standards the enum names naming according to the rule: "Labels All Upper Case with '_' Word Separators". Using the "x" char is not entirely correct. |
|
One may also use another symbol as a placeholder like $ etc. as well as long as it is part of the ASCII character set. |
|
@Nightwalker-87 Everything is ready here and nothing needs to be changed. In the test branch is lack previous corrections by other authors (it's produced conflict). "X" is not used in the names of MСU. "X" is used in enum names and this follows their naming standards. |
|
@Ant-ON No, there were some renamed defines that have already been replaced in other source files. These changes are in testing already. Thus this has to be reviewed with care. There are relevant / useful changes from both versions. |
|
Merged manually preserving the defines from the current branch. |
The list of chips is expanded with missing ones in accordance with the ST documentation
All the names of the chips are brought to the same style
Fixed incorrect size of SRAM of the G0 chips (not critical, but it would be better if it would correspond to the documentation)