[riot-notifications] [RIOT-OS/RIOT] Introduce Atmel XMEGA CPU (#15703)

Gerson Fernando Budke notifications at github.com
Sat Jan 2 20:22:44 CET 2021

#### Description
I noted that current RIOT-OS doesn't have support for XMEGA CPUs. After some research I found a 2018 version from @Josar, which seams as a good start point.

I adjusted the code and made some rework on **atmega_**. With that, I could share the fundamental code for both CPUs. These means, **ATmega** and **ATxmega** will follow different paths for drivers and configurations but can have the same core, which I named **avr8_**.

I opened this Feature Request to centralize and collect all missing parts to introduce Xmega support on RIOT-OS.

### Useful links
The below link is a proposal to split **atmega_** into **atmega_** and **avr8_** to pave the path to introduce **atxmega_**.

The following add on top of _split-mega-into-mega-avr8_ a current prove of concept using ATxmega256A3U MCU.

#### How to evaluate
To evaluate user must inspect below files to enable proper LEDs and Serial port.

├── include
│   ├── board.h
│   └── periph_conf.h
├── led_init.c

└── periph
    └── uart.c

The user must select the proper DEBUGPROTO (default PDI), debug/flash tool AVRDUDE_PROGRAMMER (default atmelice_pdi) and the linker script LDSCRIPT_COMPAT_NAME (default avrxmega6.xn).
└── Makefile.include
└── Makefile.include
└── Makefile.include

The port was tested using Tutorials/task-01 executing below command:
BOARD=wm200-xmegaa3 make all flash term

I hope this could be good for the project. I had boards with xmega and rf2xx 2.4 and sub-giga radios and would like introduce that boards soon.

CC: @benpicco 

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20210102/9d662859/attachment.htm>

More information about the notifications mailing list