Posted on May 17, 2011 at 12:35hi ST,
many people already voiced their desire for this in a previous thread, we even discussed generating headers by translating the config files in the Ride7 simulator.
if you go through with this, may I suggest that you create (and publish) an xml description of the register set instead. you can generate c and asm headers from it. plus, most registers will require bit fields, and there are lots of ways to express them. with xml the user can choose: identifier styles, macros vs consts, masks vs bit positions, c/c++ bit fields vs inline getter/setters vs macros or consts, etc.
you can define an xml transform that will shadow every register definition with 32 word definitions in the bitband region, thus gaining correct bitbanding for everything for free in all languages you support.
going further, you can generate the complete register definition tables in the reference manual from the xml file by replacing the tables with register references in the document source. that way you don't have to maintain duplicate data sets.
you could get a head start by extracting a good part of the xml from the tables of the current manual (and automatically replacing with references). you could sanity-check by comparing with Ride7 files.
lanchon
