Re: [xpcc-dev] Schema for XML device files
Hi Niklas, Is there a documentation available what the different attributes mean? Especially for the attributes marked as optional the use differs quite a lot between the different architectures. Do you mean the `type` vs. `pin-id` difference between AVR and STM32? E.g. "pcint", "extint", "func", "bits" and "define" in the tag. The only documentation we have on the device files is this here: https://github.com/salkinium/xpcc/blob/develop/src/xpcc/architecture/platform/devices/Readme.md#device-identifier (linkerscript element is deprecated now) Great, that helps a lot! Cheers, Fabian PS: HexadezimalType with a z? Um, you saw nothing... *pushes* ...what are you talking about? ___ xpcc-dev mailing list xpcc-dev@lists.rwth-aachen.de http://mailman.rwth-aachen.de/mailman/listinfo/xpcc-dev
Re: [xpcc-dev] Schema for XML device files
Hi, > in an effort to make xpcc build system independent I had a look at the > platform generation and therefore the XML device files. To understand how > they are set up I wrote a schema against all of them can be validated: > > https://github.com/dergraaf/modm-platform/blob/master/tools/device/device/resources/schema/device.xsd > > The schema could be refined a bit more (not only string type for attributes) > but should be good starting point. Awesome! > Is there a documentation available what the different attributes mean? > Especially for the attributes marked as optional the use differs quite a lot > between the different architectures. Do you mean the `type` vs. `pin-id` difference between AVR and STM32? The only documentation we have on the device files is this here: https://github.com/salkinium/xpcc/blob/develop/src/xpcc/architecture/platform/devices/Readme.md#device-identifier (linkerscript element is deprecated now) Cheers, Niklas PS: HexadezimalType with a z? ___ xpcc-dev mailing list xpcc-dev@lists.rwth-aachen.de http://mailman.rwth-aachen.de/mailman/listinfo/xpcc-dev
