Hi,

is there already a consensus how we are going to deal with all those
different uC and on top of this all those different boards (featuring the
same or very similar controller)?

Once there was the discussion how to make sure that people do not start to
copy over (possibly old and never updated) code into a new folder and work
redundant on the same feature sets.
I would suggest to add something to the dev-wiki as soon as we have an
consensus here.

On one hand its nice to have (at least the most popular boards) in once
place (one repro different folders). On the other hand git is made for
forking and branching. We could have a micropython-base which gets forked
by micropython-stm (and regular resynced) which gets branches like
pyboard, discovery, netduino, etc.
However, that would require people to deal with git, forking and branches
which many may don't like.

Other projects separate into core/stable, testing, experimental but I it
would need some tweak to fit into the micropython environment.

Any ideas?

On 18 February 2014 03:11, Dave Hylands notifications@github.com wrote:

This commit also introduces board directories and moves board
specific config into the appropriate board directory.

boards/stm32f4xx-af.csv was extracted from the STM32F4xx datasheet
and hand-tweaked.

make-pins.py takes boards/stm32f4xx-af.csv, boards/stm32f4xx-prefix.c,
and boards/BOARD-NAME/pins.csv as input and generates the file
build/pins_BOARD_NAME.c

The generated pin file for PYBOARD4 looks like this:
https://gist.github.com/dhylands/9063231

The generated pins file includes all of the supported alternate
functions, and includes upsupported alternate functions as comments.

See the commnet block at the top of stm/pin_map.c for details on
how to use the pin mapper.

I also went ahead and modified stm/gpio.c to use the pin mapper.

You can merge this Pull Request by running

git pull https://github.com/dhylands/micropython pin_map

Or view, comment on, or merge it at:

#310
Commit Summary

• Add pin mapping code.

File Changes

• M py/objfun.chttps://github.com/Add pin mapping code. #310/files#diff-0(20)
• M py/runtime.hhttps://github.com/Add pin mapping code. #310/files#diff-1(2)
• M stm/Makefilehttps://github.com/Add pin mapping code. #310/files#diff-2(19)
• A stm/boards/NETDUINO_PLUS_2/mpconfigboard.hhttps://github.com/Add pin mapping code. #310/files#diff-3(48)
• A stm/boards/NETDUINO_PLUS_2/pins.csvhttps://github.com/Add pin mapping code. #310/files#diff-4(28)
• A stm/boards/PYBOARD3/mpconfigboard.hhttps://github.com/Add pin mapping code. #310/files#diff-5(42)
• A stm/boards/PYBOARD3/pins.csvhttps://github.com/Add pin mapping code. #310/files#diff-6(37)
• A stm/boards/PYBOARD4/mpconfigboard.hhttps://github.com/Add pin mapping code. #310/files#diff-7(42)
• A stm/boards/PYBOARD4/pins.csvhttps://github.com/Add pin mapping code. #310/files#diff-8(45)
• A stm/boards/STM32F4DISC/mpconfigboard.hhttps://github.com/Add pin mapping code. #310/files#diff-9(43)
• A stm/boards/STM32F4DISC/pins.csvhttps://github.com/Add pin mapping code. #310/files#diff-10(85)
• A stm/boards/make-pins.pyhttps://github.com/Add pin mapping code. #310/files#diff-11(241)
• A stm/boards/stm32f4xx-af.csvhttps://github.com/Add pin mapping code. #310/files#diff-12(142)
• A stm/boards/stm32f4xx-prefix.chttps://github.com/Add pin mapping code. #310/files#diff-13(34)
• M stm/gpio.chttps://github.com/Add pin mapping code. #310/files#diff-14(59)
• M stm/main.chttps://github.com/Add pin mapping code. #310/files#diff-15(2)
• M stm/mpconfigport.hhttps://github.com/Add pin mapping code. #310/files#diff-16(181)
• A stm/pin.chttps://github.com/Add pin mapping code. #310/files#diff-17(62)
• A stm/pin.hhttps://github.com/Add pin mapping code. #310/files#diff-18(115)
• A stm/pin_map.chttps://github.com/Add pin mapping code. #310/files#diff-19(221)
• A stm/pin_named_pins.chttps://github.com/Add pin mapping code. #310/files#diff-20(67)
• M stm/qstrdefsport.hhttps://github.com/Add pin mapping code. #310/files#diff-21(4)

Patch Links:

• https://github.com/micropython/micropython/pull/310.patch
• https://github.com/micropython/micropython/pull/310.diff

Reply to this email directly or view it on GitHubhttps://github.com//pull/310
.

Oooh @dhylands, this is a biggie! Good job for getting it done.

@torwag I do believe this topic has been discussed in the following two threads:

• Initial Support for the STM32F4DISCOVERY Board #83
• Code sharing #187

This thread is also relevant:

• How to name pins and peripherals #265

Kudos! Thank you @dhylands.