5 ms·
AFAIK SVD files are an ARM thing.
by dbcurtis 9y ago
AFAIK SVD files are an ARM thing.
- timerol 9y agoYeah, they are ARM specific, at least according to https://siliconlabs.github.io/Gecko_SDK_Doc/CMSIS/SVD/html/index.html https://siliconlabs.github.io/Gecko_SDK_Doc/CMSIS/SVD/html/i.... "The CMSIS System View Description format(CMSIS-SVD) formalizes the description of the system contained in ARM Cortex-M processor-based microcontrollers, in particular, the memory mapped registers of peripherals."
- twic 9y agoIs it that it would be impossible to write an SVD file for another architecture, or just that vendors don't do it? If it's possible, and this tooling makes SVDs a really powerful tool for porting, then perhaps it would be easier for the community to write SVDs for non-ARM chips than code.
- jdub 9y agoDeviceTree is the standard / tooling you'll see outside ARM micro-controllers. Started on Power, then found a place in Linux's ARM tree, and is now spreading further.
- kbumsik 9y agoProbably, but companies wouldn’t do it since they have their own tooling. And I don’t think the community would like to write it neither. Look at a SVD file for a single MCU. https://github.com/posborne/cmsis-svd/blob/master/data/STMicro/STM32F100xx.svd https://github.com/posborne/cmsis-svd/blob/master/data/STMic... It’s a more than 10k loc XML file. It is too much effort for the community to do that and verify it. And as an embedded system engineer, I wouldn’t trust the community-driven register definition because even vendors have some bug on it and it is almost impossible for the community to write a better register definitions than the vendors themselves. This is a vendors’ job, not the community's.