I just pushed it to my repo as it is, so you can have a look. https://github.com/Josar/RIOT_XMEGA
I would suggest to implement the common functionality in the atxmega_common folder. I have done the gpio, timer anf the uart but spi is still hard coded to my platform. Von: devel [mailto:[email protected]] Im Auftrag von Arndt, Josua Gesendet: Dienstag, 12. Dezember 2017 11:00 An: RIOT OS kernel developers <[email protected]> Betreff: Re: [riot-devel] Atxmega Port with RIOT OS - Where to put abundance of new driver features? I have a working port of an atxmega256a3u I started to port it to a common folder maybe we could work something out Von: devel [mailto:[email protected]] Im Auftrag von Madison McCarthy Gesendet: Montag, 11. Dezember 2017 22:04 An: [email protected]<mailto:[email protected]> Betreff: [riot-devel] Atxmega Port with RIOT OS - Where to put abundance of new driver features? Hi Everyone, I'm nearing completion of a port for RIOT OS to the ATxmega family of devices (targeting the atxmega128). The Atxmega is feature rich when contrasted against the Atmega counterpart which I am using as a porting guideline. 1) Since I would like to contribute my port to the git repository, how should I go about implementing new CPU features not found in the core RIOT OS functionality (enhanced TWI, USART, etc.)? 2) How should I implement the addition of both Master and Slave functionality to my peripheral interfaces? 3) How should I go about adding interrupt functionality for these peripherals? Currently I am just smashing these extra features right into the driver's .C files as I am trying to preserve the OS-Core files. Any suggestions would be appreciated! Madison McCarthy
_______________________________________________ devel mailing list [email protected] https://lists.riot-os.org/mailman/listinfo/devel
