Fwd: [riot-devel] About porting RIOT to platforms based on STM32.
61 views
Skip to first unread message
DangNhat PhamHuu
Feb 28, 2014, 1:52:54 AM2/28/14
to ss...@googlegroups.com
1 chut tin vu ve RIOT. :D
* Class: MT10KTTN
* Ho Chi Minh University of Technology
* Mobile: 0164.968.2716
***********************************************/
/***********************************************
* Phạm Hữu Đăng Nhật
* StudentID: 51002279* Phạm Hữu Đăng Nhật
***********************************************/
---------- Forwarded message ----------
From: Hauke Petersen <hauke.p...@fu-berlin.de>
Date: 27 February 2014 13:06
Subject: Re: [riot-devel] About porting RIOT to platforms based on STM32.
To: DangNhat PhamHuu <phamhuu...@gmail.com>
Hello Nhat,
sorry for the delayed reply and welcome to the RIOT community!
RIOTs STM32 port is currently work in progress - it is working for the
most parts, but we are still working on the best way to integrate it
into RIOTs main repository. The main problems here are some very
restrictive licenses in the STM standard library, which you are probably
also using?!
For getting RIOT running on the your STM platforms, the best way to
start is to look into the thirdparty_cpu [1] and thirdparty_boards [2]
repositories, as they contain rudimentary working implementations for
the stm32f4discovery board. You can build the default application for
the stm32f4discovery by uncommenting the RIOTCPU and RIOTBOARD variables
in the Makefile of the example project (RIOT/examples/default/Makefile)
and setting the BOARD to stm32f4discovery. This is of course most useful,
if you have an stm32f4discovery board available... Might I ask anyway,
which STM controllers you are using specificly?
If you want to contribute to RIOT (which we would highly welcome!) you
could for example debug and test the task-switching more thoroughly, as
we suspect there might be still some issues with it.
For further correspondence, I would like to encourage you to register to
the RIOT devel mailing-list. The people in the RIOT community are very
friendly and will answer your questions relatively fast.
Let me know if you need any help!
cheers,
Hauke
[1] https://github.com/RIOT-OS/thirdparty_cpu
[2] https://github.com/RIOT-OS/thirdparty_boards
From: Hauke Petersen <hauke.p...@fu-berlin.de>
Date: 27 February 2014 13:06
Subject: Re: [riot-devel] About porting RIOT to platforms based on STM32.
To: DangNhat PhamHuu <phamhuu...@gmail.com>
Hello Nhat,
sorry for the delayed reply and welcome to the RIOT community!
RIOTs STM32 port is currently work in progress - it is working for the
most parts, but we are still working on the best way to integrate it
into RIOTs main repository. The main problems here are some very
restrictive licenses in the STM standard library, which you are probably
also using?!
For getting RIOT running on the your STM platforms, the best way to
start is to look into the thirdparty_cpu [1] and thirdparty_boards [2]
repositories, as they contain rudimentary working implementations for
the stm32f4discovery board. You can build the default application for
the stm32f4discovery by uncommenting the RIOTCPU and RIOTBOARD variables
in the Makefile of the example project (RIOT/examples/default/Makefile)
and setting the BOARD to stm32f4discovery. This is of course most useful,
if you have an stm32f4discovery board available... Might I ask anyway,
which STM controllers you are using specificly?
If you want to contribute to RIOT (which we would highly welcome!) you
could for example debug and test the task-switching more thoroughly, as
we suspect there might be still some issues with it.
For further correspondence, I would like to encourage you to register to
the RIOT devel mailing-list. The people in the RIOT community are very
friendly and will answer your questions relatively fast.
Let me know if you need any help!
cheers,
Hauke
[1] https://github.com/RIOT-OS/thirdparty_cpu
[2] https://github.com/RIOT-OS/thirdparty_boards
Reply all
Reply to author
Forward
0 new messages