Closed ilg-ul closed 7 years ago
The SVD files and description strings are handwritten or generated using vendor tool exports. Unfortunately we have a lot of SVD files around without a common usage of the description field.
Instead of adding a bunch of messages (many SVDs are leading to thousands of them already) we decided to overrule the formatting within our generators. Thus SVDConv for instance simply removes multiple white-spaces. Forcing a line-break can be achieved using a escaped linefeed (\n).
I have appended a description of the current usage to the CMSIS-SVD documentation, see commit 5a5e78e08dc55d0c9497a0e0fca352472d692655.
Closed due to inactivity.
While using the SVD files, I noticed that sometimes the
<description>
text is arbitrarily split on two lines.For example the following lines from the STM32F40x.svd:
According to normal XML rules, when parsing such a syntax, the result includes explicit line terminations and spaces:
This syntax leads to unusual displays in a debugger window.
Identifying and fixing these strings at application level is possible, but requires some efforts.
Questions: