[riot-devel] Need some orientation about using vendor SDK when porting MCU

Hauke Petersen hauke.petersen at fu-berlin.de
Mon Oct 30 10:25:49 CET 2017

Hi Cristiano,

I think in general, the inclusion of at least the vendor/firmware 
headers for those CPUs should probably be done in a similar fashion than 
the inclusion of the stellaris ware (cpu/stellaris_common). But 
dependent on the amount of headers (or even library source files), it 
would be definately worth a thought to consider adding the vendor 
libraries as packages. This way there would be no need for keeping all 
these files in the RIOT source tree directly, and code duplication would 
not be an issue. Further, it would be simple to update the libraries. 
Drawback here is, that we/someone would need to provide a public 
available repository containing these libraries - I guess TI is not 
doing this, right?


On 28.10.2017 13:47, Cristiano GaviĆ£o wrote:
> Hello Riot Devs,
> As I have written before, I would like to use Riot in my 6lowPan 
> project that is using CC1310 and CC1350 MCU.
> No long ago, Texas Instruments have separated its common provided SDK 
> into CC13XXWARE and CC26XXWARE. Currently there are many code that are 
> still equals, but I did a file to file compare using Meld and found 
> significant differences between some of them (9 files).
> What I heard was that in the next MCUs versions (CC1312 and CC1352) 
> more differences will come...
> Besides that, those MCU have written in they ROM the most used SDK's 
> driverlib binaries. So using the binaries instead flash them can give 
> us more space for the applications.
> So I would like to use headers and driverlib from CC13XXWARE in a best 
> way that would fit in Riot and also facilitate maintenance when new 
> updated come.
> Would like to hear suggestion about what would be the best approach to 
> work on this.
> thanks for any comment,
> Cristiano
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel

More information about the devel mailing list