one interesting consequence of using a peripheral/register/bitfield model is that it allows to partly automate the creation of a new MCU.
the natural source for peripheral registers and bitfields are the SVD files, while the natural source for MCU families/subfamilies/devices are the CMSIS PACK .pdsc files. for my next release I plan to restructure the existing peripheral/register/bitfield in my branch, and make them CMSIS centric. as such, the definition of a new MCU will include a set of Info structures, including details like flash/ram areas (automatically generated as .c source files, one for each CMSIS PACK family), and a set of JSON files, also automatically generated from the SVD files (one JSON for each SVD). in addition, a large set of callback functions, manually written, will handle the functionality for register that require such functionality. the specifications for this new model are advanced, but there are still some decisions to be made. any suggestions are welcome. regards, Liviu
