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 project for the discovery 
board. If you send out the patch I can enhance the docs. Or you could create a 
new example app and submit a pull request. 

thanks,
aditi

> On Jun 6, 2016, at 9:07 AM, David G. Simmons <[email protected]> wrote:
> 
> 
> I’ve modified the Blinky demo for STM32F3Discovery to use all the LEDs 
> on-board. I thought it looked nicer than having a single LED blink on and off 
> every second. :-) 
> 
> I made the following changes to the hw/bsp/stm32f3discovery/include/bsp/bsp.h 
> in mynewt_stm32f3:
> 
> 35: - #define LED_BLINK_PIN   (72)
> 35: + #define LED_BLINK_PIN_1   (72)
> 36: + #define LED_BLINK_PIN_2   (73)
> 36: + #define LED_BLINK_PIN_3   (74)
> 38: + #define LED_BLINK_PIN_4   (75)
> 39: + #define LED_BLINK_PIN_5   (76)
> 40: + #define LED_BLINK_PIN_6   (77)
> 41: + #define LED_BLINK_PIN_7   (78)
> 42: + #define LED_BLINK_PIN_8   (79)
> 
> That enables all the LEDs on the Board. 
> 
> I then modified main.c in the mynewt_blinky app to initialize all the pins 
> (in an array) and then turn them on/off in a round-robin pinwheel fashion. 
> 
> I’ll submit pull requests for it all. 
> 
> Best regards,
> dg
> --
> David G. Simmons
> (919) 534-5099
> Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • 
> Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter 
> <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs>
> /** Message digitally signed for security and authenticity.  
> * If you cannot read the PGP.sig attachment, please go to 
> * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!!
> * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/>
> **/
> ♺ This email uses 100% recycled electrons. Don't blow it by printing!
> 
> There are only 2 hard things in computer science: Cache invalidation, naming 
> things, and off-by-one errors.
> 
> 

Reply via email to