Based on all the comments, etc. (thanks!) here’s what I’ve done:
I’ve submitted a pull request against the STM32F repository to add the
LED_BLINK_PIN_X defines, and then #define LED_BLINK_PIN LED_BLINK_PIN_1 which
solves for leaving the blinky as-is as the “hello world” of MyNewt while still
On Mon, Jun 06, 2016 at 12:42:38PM -0700, marko kiiskila wrote:
> I would leave blinky as is. It is beneficial to have a sample that
> shows that you can have applications which don’t need any platform
> specific changes.
I agree. Blinky is Mynewt's "hello world" applications.hhC, and I think
it
Hi David,
I would leave blinky as is. It is beneficial to have a sample that shows that
you can
have applications which don’t need any platform specific changes.
As for the mynewt_pinwheel demo, you could check that into mynewt-stm32f3
repository
as a separate app. The particular layout of
I thought about creating a new demo app, and the required pages to go with it
for the documentation.
That being said, if the pull request for the mynewt_stm32f3 is accepted, the
standard blinky app will have to be modified slightly. As you can see, I
numbered all the pins, and in the original,
Hi David,
Thank you for the modified demo - a pinwheel is far more exciting than a single
blinking LED :)
Thanks for the pull request on the remote mynewt_stm32f3 repo.
As for the mynewt_blinky app changes, we could simply describe the main.c
modifications in a mini-tutorial under the Blinky
