I'd suggest putting toolchain setup etc. into wiki pages like:
FAMILY:-arm, FAMILY:-msp etc.
If BOARDS:-msba2 points to FAMILY:-arm and RIOT-Platforms points to
both the family and the board, then I think this information is on the
best of all possible paths.
I'd suggest putting toolchain setup etc. into wiki pages like:
FAMILY:-arm, FAMILY:-msp etc.
If BOARDS:-msba2 points to FAMILY:-arm and RIOT-Platforms points to
both the family and the board, then I think this information is on the
best of all possible paths.
I think having a collection of information about the different toolchains on
separate pages is a very good idea. However, I think I haven't completely
understood how you envision the concrete implementation. Could you provide a
sample wiki page of your idea?
That would definitely help to make this page much neater.
Any thoughts on this?
We should also include information about which toolchain and version is known
to work well with which platform and feature and which is known to cause
trouble.
I further created a page for the STM32F3dicovery ( ) on the plane on Friday. It has a slightly different structure, but I think it would go together well with Ludwigs idea of creating separate Wiki pages for toolchains, which could in fact just be referenced to from the board-pages. cheers, Hauke
I further created a page for the STM32F3dicovery (
https://github.com/RIOT-OS/RIOT/wiki/Board:-STM32F3discovery) on the
plane on Friday. It has a slightly different structure, but I think it
would go together well with Ludwigs idea of creating separate Wiki pages
for toolchains, which could in fact just be referenced to from the
board-pages.
Looks good to me, just one issue: ARM7 is not equal to ARM Cortex, there
are different issues and not all Arm toolchains work for both
architectures... But I guess we just need to differentiate a little
better here...