[riot-devel] msp430 thoughts
hauke.petersen at fu-berlin.de
Mon Sep 7 13:53:56 CEST 2015
currently it seems like we do not have any 'main' msp430 developers,
though there are some who have spend some time on these boards. I have
just last week implemented our low-level peripheral interfaces for UART,
timers, SPI, and GPIO for the msp430 - stumbling on exactly the painful
inconsistencies in the msp430 family you describe below...
To cope with some of them, I actually re-wrote parts of the msp430
header files in a more modern, ARM CMSIS style. This makes it much
easier, to implement register based code in a configurable fashion.
Although we do now have first periph driver implementation, there is a
lot of cleanup of the msp code to be done. Some steps include (i) moving
and generalization of the clock initialization code from the boards into
the cpu (as done for cortex based CPUs), (ii) implementation of missing
periph drivers (e.g. I2C, cpuid, adc, pwm), and switching to the CORE_NG
interface (implementing the interfaces in `core/include/arch/..`).
So your help would be much appreciated!
On 07.09.2015 02:46, Eric Decker wrote:as430 chips on TinyOS. It was a
pain. The TI architecture across different models of the cpu is let us
just say not very consistent.
> I've looked quickly at the approach taken in the RIOT code and there
> are some issues which run into the TI issues.
> I'd liked to possibly help you folks to avoid the same crap I ran into.
> who are the main msp430 developers?
> also take a look at my documentation (I actually documented the issues
> as I ran into them) at
> Eric B. Decker
> Senior (over 50 :-) Researcher
> devel mailing list
> devel at riot-os.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the devel