The specification (such as it is) is here:
http://www.keil.com/pack/doc/CMSIS/SVD/html/index.html
Stephen
--
Stephen Pelc, stephen@mpeforth.com
MicroProcessor Engineering Ltd - More Real, Less Time
133 Hill Lane, Southampton SO15 5AF, England
tel: +44 (0)23 8063 1441, +44 (0)78 0390 3612
web: http://www.mpeforth.com - free VFX Forth downloads
Reply by Stef●April 10, 20202020-04-10
On 2020-04-08 Tauno Voipio wrote in comp.arch.embedded:
>
> At least Atmel and ST made the mistake by attempting to
> cover all the processors types with one set of sources.
>
> This led to a sorry mess of conditional code, which is
> undecipherable even for a seasoned programmer. (me:
> over 50 years of embedded code).
Does anyone have experience with Renesas and their Synergy
stuff? Did a workshop a while ago and this all seemed to
work quite good. But ofcourse this was a prepared workshop
example that was bound to work. Did not have a chance to
try it on a project of our own. We nowadays mostly use ST,
so using something else must have huge advantages before we
give it a try. ;-)
--
Stef (remove caps, dashes and .invalid from e-mail address to reply by mail)
FORCE YOURSELF TO RELAX!
Reply by Clifford Heath●April 9, 20202020-04-09
On 9/4/20 10:31 pm, Stephen Pelc wrote:
> On Thu, 9 Apr 2020 09:39:01 +1000, Clifford Heath <no.spam@please.net>
> wrote:
>
>>>> Had a look at the ST code examples and their obscure header file
>>>> mess for cortex years ago. Our way or the highway and unusable
>>>> as presented. Code examples were rubbish as well. May be better
>>>> now, but still useless if you have a house standard for form and function...
>>>
>>> We agree. In the end we wrote a (sort of) parser for ARM's SVD file
>>> format to produce our header file equivalents. Several others have
>>> gone down this route too.
>>
>>
>> Tell me more. what are these SVD files and where can I get some?
>
> SVD is a format promoted by ARM for CPU description. It's an XML
> format. AFAIR ARM keeps a collection of these files, and ST usually
> provide them. See:
>
> https://community.st.com/s/question/0D50X00009XkWDkSAN/how-does-st-manage-svd-files
Thanks. Something to reach for when I'm back in this ball-park again.
CH
Reply by Tauno Voipio●April 9, 20202020-04-09
On 9.4.20 15:31, Stephen Pelc wrote:
> On Thu, 9 Apr 2020 09:39:01 +1000, Clifford Heath <no.spam@please.net>
> wrote:
>
>>>> Had a look at the ST code examples and their obscure header file
>>>> mess for cortex years ago. Our way or the highway and unusable
>>>> as presented. Code examples were rubbish as well. May be better
>>>> now, but still useless if you have a house standard for form and function...
>>>
>>> We agree. In the end we wrote a (sort of) parser for ARM's SVD file
>>> format to produce our header file equivalents. Several others have
>>> gone down this route too.
>>
>>
>> Tell me more. what are these SVD files and where can I get some?
>
> SVD is a format promoted by ARM for CPU description. It's an XML
> format. AFAIR ARM keeps a collection of these files, and ST usually
> provide them. See:
>
> https://community.st.com/s/question/0D50X00009XkWDkSAN/how-does-st-manage-svd-files
>
> Stephen
>
>
The ARM files are only the smaller half of the whole story:
on the chips there are also the manufacturer-provided peripherals,
which, IMHO, are the more complicated to make the header files for.
Anyway, I did it by hand.
--
-TV
>>> Had a look at the ST code examples and their obscure header file
>>> mess for cortex years ago. Our way or the highway and unusable
>>> as presented. Code examples were rubbish as well. May be better
>>> now, but still useless if you have a house standard for form and function...
>>
>> We agree. In the end we wrote a (sort of) parser for ARM's SVD file
>> format to produce our header file equivalents. Several others have
>> gone down this route too.
>
>
>Tell me more. what are these SVD files and where can I get some?
SVD is a format promoted by ARM for CPU description. It's an XML
format. AFAIR ARM keeps a collection of these files, and ST usually
provide them. See:
https://community.st.com/s/question/0D50X00009XkWDkSAN/how-does-st-manage-svd-files
Stephen
--
Stephen Pelc, stephen@mpeforth.com
MicroProcessor Engineering Ltd - More Real, Less Time
133 Hill Lane, Southampton SO15 5AF, England
tel: +44 (0)23 8063 1441, +44 (0)78 0390 3612
web: http://www.mpeforth.com - free VFX Forth downloads
Reply by Clifford Heath●April 8, 20202020-04-08
On 9/4/20 10:59 am, Dave Nadler wrote:
> On Wednesday, April 8, 2020 at 7:39:05 PM UTC-4, Clifford Heath wrote:
>> On 9/4/20 6:49 am, Stephen Pelc wrote:
>>> We agree. In the end we wrote a (sort of) parser for ARM's SVD file
>>> format to produce our header file equivalents. Several others have
>>> gone down this route too.
>>
>>
>> Tell me more. what are these SVD files and where can I get some?
>>
>> Clifford Heath.
>
> What's it worth to you Cliff?
:)
Well, I've done a lot of parsing and code generation, and I also hate
the manufacturer libraries and header files. I haven't yet launched into
building my own ARM infrastructure libraries, but I've often considered
doing that. I hadn't come across these SVD files before. Of course, I
wrote the above message *before* using Google :)
CH
Reply by Dave Nadler●April 8, 20202020-04-08
On Wednesday, April 8, 2020 at 7:39:05 PM UTC-4, Clifford Heath wrote:
> On 9/4/20 6:49 am, Stephen Pelc wrote:
> > We agree. In the end we wrote a (sort of) parser for ARM's SVD file
> > format to produce our header file equivalents. Several others have
> > gone down this route too.
>
>
> Tell me more. what are these SVD files and where can I get some?
>
> Clifford Heath.
What's it worth to you Cliff?
Reply by Clifford Heath●April 8, 20202020-04-08
On 9/4/20 6:49 am, Stephen Pelc wrote:
> On Wed, 08 Apr 2020 14:58:08 +0100, Chris <xxx.syseng.yyy@gfsys.co.uk>
> wrote:
>
>> Had a look at the ST code examples and their obscure header file
>> mess for cortex years ago. Our way or the highway and unusable
>> as presented. Code examples were rubbish as well. May be better
>> now, but still useless if you have a house standard for form and function...
>
> We agree. In the end we wrote a (sort of) parser for ARM's SVD file
> format to produce our header file equivalents. Several others have
> gone down this route too.
Tell me more. what are these SVD files and where can I get some?
Clifford Heath.
Reply by Stephen Pelc●April 8, 20202020-04-08
On Wed, 08 Apr 2020 14:58:08 +0100, Chris <xxx.syseng.yyy@gfsys.co.uk>
wrote:
>Had a look at the ST code examples and their obscure header file
>mess for cortex years ago. Our way or the highway and unusable
>as presented. Code examples were rubbish as well. May be better
>now, but still useless if you have a house standard for form and function...
We agree. In the end we wrote a (sort of) parser for ARM's SVD file
format to produce our header file equivalents. Several others have
gone down this route too.
Stephen
--
Stephen Pelc, stephen@mpeforth.com
MicroProcessor Engineering Ltd - More Real, Less Time
133 Hill Lane, Southampton SO15 5AF, England
tel: +44 (0)23 8063 1441, +44 (0)78 0390 3612
web: http://www.mpeforth.com - free VFX Forth downloads
Reply by Tauno Voipio●April 8, 20202020-04-08
On 8.4.20 16:58, Chris wrote:
> On 04/06/20 15:14, Dave Nadler wrote:
>> On Monday, April 6, 2020 at 3:05:47 AM UTC-4, Tauno Voipio wrote:
>>> Just stay away from the hardware guys' software, write your own.
>>
>> Yup, I had to write my own drivers for ST DMA, timer, SPI.
>>
>> But it gets quite impractical to write one's own drivers for every
>> ethernet and USB peripheral set etc... And lots of the vendor
>> stuff absolutely does not work (ST for example).
>>
>> Now if I could only figure out why my release build works,
>> but not the debug build (reverse of the usual puzzle!)...
>> Off to check the timing on the scope!
>
> Always write separate header files for the cpu and each of the on chip
> peripherals as a first task for every new processor. It's a good
> way to get a top level overview of the machine and capabilities.
>
> Had a look at the ST code examples and their obscure header file
> mess for cortex years ago. Our way or the highway and unusable
> as presented. Code examples were rubbish as well. May be better
> now, but still useless if you have a house standard for form and
> function...
At least Atmel and ST made the mistake by attempting to
cover all the processors types with one set of sources.
This led to a sorry mess of conditional code, which is
undecipherable even for a seasoned programmer. (me:
over 50 years of embedded code).
--
-TV