Re: STM32F3-Discovery problems

2016-11-03 Thread marko kiiskila
Cool. I want this revived as well, I just have been missing time to work on it. Lemme know if you get stuck somewhere, I’ll help. > On Nov 3, 2016, at 8:15 AM, David G. Simmons wrote: > > Thanks Marko! I'll take a look at this today. I need to look at code for a > few hours

Re: STM32F3-Discovery problems

2016-11-03 Thread David G. Simmons
Thanks Marko! I'll take a look at this today. I need to look at code for a few hours anyway, as looking for stray commas and errant cApiTaliZation is making my eyes hru. :-) dg > On Nov 3, 2016, at 11:05 AM, marko kiiskila wrote: > > Hi David, > > there are few things;

Re: STM32F3-Discovery problems

2016-11-03 Thread marko kiiskila
Hi David, there are few things; hal_uart() interface has changed, now there is a init routine which gets called from the bp_init(). This call must now have the platform specific HW config in it. This changed from before, as then the driver would make a call to BSP to ask for the config.

Re: STM32F3-Discovery problems

2016-11-02 Thread David G. Simmons
Hi Chris, I guess then yay it's not me being daft again but boo that it doesn't work. Have you got an outline of what needs to be done to bring it up to speed? I'm happy to work on it as part of my work to get the demos/docs ready for 1.0 if I know what needs to be done. dg > On Nov 2,

Re: STM32F3-Discovery problems

2016-11-02 Thread Christopher Collins
Hi David, On Wed, Nov 02, 2016 at 11:51:36AM -0400, David G. Simmons wrote: > > I'm hoping that this isn't just more of my git-idiocy, but ... trying to get > the STM32F3-Discovery board to load the blinky app, and keep getting: > > DSimmons-Pro:myproj dsimmons$ newt build stmf3_boot >