Thanks for the quick response Will! I’m brand new to mynewt, so I'm not sure that dealing with this is necessarily the first thing I should tackle. The STM32F3DISCOVERY board was only $12 at DigiKey, so I just ordered one. I have a more pressing goal with mynewt first, but once I get that underway and am more comfortable with it, I will probably tackle this board. Ultimately I’m looking to get it running on a (currently non-existent in the wild, but coming soon) M0-based SoC, so creating a bsps for that chip will have to be done, but … baby steps!
Thanks! dg > On May 19, 2016, at 1:41 PM, will sanfilippo <[email protected]> wrote: > > Hello David: > > I took a peek at the evaluation board you mentioned. We dont have that eval > board in house nor do we have that flavor of st chip in house, but getting > mynewt up and running on this would certainly be possible. It appears that > this is the 256K Flash/32KB RAM version on that eval board. Is that correct? > If so, that should be plenty of space for mynewt and a really killer app! > > What you would need to do is to create a bsp for this board and add MCU > support for it. I am not a huge fan of STM32Cube but that is the SDK that ST > points to for this eval board so using that code for the HAL would be the > quickest route if you wanted HAL for it. Of course, you dont need to support > the HAL in the first cut (just pieces you needed). > > We have tutorials on creating bsps and adding mcu support on the mynewt page > so if you wanted to take a crack at adding support that would be great. We > love feedback on the tutorials and we are always around to help if you have > questions. > > >> On May 19, 2016, at 9:56 AM, David G. Simmons <[email protected]> wrote: >> >> Is this something that is supported/possible? I don’t happen to have an >> STM32F3DISCOVERY board, but I do happen to have one of these lying around. >> If anyone has used this board, or knows haow to get it up and running with >> mynewt, I’d appreciate some pointers/help. >> >> 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. >> >> > -- David G. Simmons (919) 534-5099 Web • Blog • Linkedin • Twitter • GitHub /** Message digitally signed for security and authenticity. * If you cannot read the PGP.sig attachment, please go to * http://www.gnupg.com/ Secure your email!!! * Public key available at 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
