Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STM8 port #5557

Closed
spth opened this issue Jun 18, 2016 · 5 comments
Closed

STM8 port #5557

spth opened this issue Jun 18, 2016 · 5 comments
Assignees
Labels
Platform: ARM Platform: This PR/issue effects ARM-based platforms State: stale State: The issue / PR has no activity for >185 days Type: new feature The issue requests / The PR implemements a new feature for RIOT

Comments

@spth
Copy link

spth commented Jun 18, 2016

How about porting RIOT to STM8? It already has an STM32 port, and AFAIK, the peripherals are quite similar.

Philipp

@OlegHahm OlegHahm added Feature Request Platform: ARM Platform: This PR/issue effects ARM-based platforms labels Jun 20, 2016
@jnohlgard
Copy link
Member

I have never used any STM8 but from what I gather from the web it has similar specs as the ATmegas (avr) which puts it in the lower end of the spectrum of devices capable of running RIOT. The biggest issue may be that there is no GCC port, and we have not tested building RIOT on any compilers other than GCC and Clang AFAIK. I have never used SDCC or IAR so I wouldn't know how big the required effort is, but I'm guessing it is likely quite a bit more than just changing CC= in the Makefile.
Feel free to start your own port and open a PR against the RIOT repository when you have something you want feedback on. You can open a PR even when it is work in progress, it doesn't have to be a completely finished port.

@spth
Copy link
Author

spth commented Jun 21, 2016

There are four important C implementations for the STM8: http://colecovision.eu/stm8/compilers.shtml
Their standard-support is at different levels, but in general, I'd say IAR and SDCC are the most advanced. The SDCC regression test suite includes most of the tests that GCC uses (excluding in particular those that rely on GCC extensions). AFAIK neither IAR nor SDCC aim for GCC-compability the way Clang does.

Philipp

@jnohlgard jnohlgard removed their assignment Jul 4, 2016
@n-eq
Copy link

n-eq commented Sep 12, 2018

Any update on this issue?

ST seems to produce 8 bit MCUs (e.g.: https://www.st.com/en/evaluation-tools/nucleo-8l152r8.html)

@spth
Copy link
Author

spth commented Sep 17, 2018

I do not know of any progress, and currently do not have time to initiate work on this myself. But if someone wants to work on it, I will help (I do not have much experience with RIOT, but know SDCC, and the STM8 reasonably well).

Philipp

@miri64 miri64 added Type: new feature The issue requests / The PR implemements a new feature for RIOT and removed Feature Request labels Sep 30, 2018
@stale
Copy link

stale bot commented Aug 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Aug 10, 2019
@stale stale bot closed this as completed Sep 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Platform: ARM Platform: This PR/issue effects ARM-based platforms State: stale State: The issue / PR has no activity for >185 days Type: new feature The issue requests / The PR implemements a new feature for RIOT
Projects
None yet
Development

No branches or pull requests

6 participants