Re: Changes to HAL/BSP/Drivers

> On Jun 2, 2016, at 5:07 PM, Sterling Hughes wrote: ... > My suggestions on how to change this API, and the general design philosophy > are as follows: > > * A #define should be added HAL_ADC_MAX which indicates the number of > peripherals enabled on a given board > >

Re: New Demo for stm32F3Discovery Based on Blinky

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

Re: New Demo for stm32F3Discovery Based on Blinky

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

Re: Changes to HAL/BSP/Drivers

On 6 Jun 2016, at 12:56, marko kiiskila wrote: On Jun 2, 2016, at 5:07 PM, Sterling Hughes wrote: ... :) Right now, we don’t have a drivers interface, and the HAL is dual-purposing both. The ADC is a good example of this, so I’ll focus in on that API. … :)

Re: New Demo for stm32F3Discovery Based on Blinky

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

Fwd: incubator-mynewt-core git commit: slinky, bootloader; make trying out config storage in NFFS vs FCB easier. If NFFS is included in build, use that. If that's not there, then expect FCB. Need to f

Hi, this is a continuation of the plan to make building apps which don’t need/want NFFS easier. Now you can build slinky and matching bootloader which use FCB instead of NFFS. This has been possible even before, but I thought I’d make it easier for ppl to try this out. What you would do is

Re: Board Support Tutorial

Hi David, sorry for belated response, I’ve been off-grid for a bit now. > On Jun 3, 2016, at 10:07 AM, David G. Simmons wrote: > > > Is there a tutorial, or some detailed docs on how to go about adding support > for a new board? I’ve been trying to figure it out just going

Re: New Demo for stm32F3Discovery Based on Blinky

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,

Re: New Demo for stm32F3Discovery Based on Blinky

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