Re: Mynewt Local BSP Instance Location

Hi Sterling, Thanks for the quick reply and solution. You're correct, the compiler was missing the reference to the repo and I can build local BSPs with the following changes from the source BSP: pkg.compiler: "@apache-mynewt-core/compiler/arm-none-eabi-m0" pkg.deps: -

Re: Migrate clock source or PLL setup to the BSP level

Hi, > On May 11, 2016, at 10:02 AM, Kevin Townsend wrote: > > Hi Will, > > I'll be happy to throw my opinions in on the PLL or clock changes at the BSP > level. > > This also touches on some important issues with power management if you start > thinking about an API

Re: Mynewt Local BSP Instance Location

Hi Kevin, I was able to reproduce the issue, it looks like you didn't update the repository descriptor for the pkg.compiler -- that should point to a package in the @apache-mynewt-core repository as well. If you do that, you should get past that error. I was able to get your target to

Re: Re: Mynewt Local BSP Instance Location

This is slightly modified since it now points to the repo folder but the structure and files are basically identical: targets/adablink app=@apache-mynewt-core/apps/blinky bsp=@apache-mynewt-core/hw/bsp/blefriend32 build_profile=debug targets/bleper_nrf51

Re: Mynewt Local BSP Instance Location

Hi Kevin, On Wed, May 11, 2016 at 01:32:14PM +0200, Kevin Townsend wrote: > I'm trying to document the process of creating a custom BSP based on an > existing model from apache-newt-core, and copied the model into the > local `projectroot/hw/bsp/boardname` folder, updated the `pkg.yml` file, >

Re: Migrate clock source or PLL setup to the BSP level

Hello Kevin: Well, I just woke up and havent had my coffee yet, so if this response makes no sense you know why :-) I certainly agree that what you have run across here is an issue that we will have to deal with. Certainly the clock source and/or its availability needs to be dictated by the

Mynewt Local BSP Instance Location

I'm trying to document the process of creating a custom BSP based on an existing model from apache-newt-core, and copied the model into the local `projectroot/hw/bsp/boardname` folder, updated the `pkg.yml` file, and modified the filenames/content accordingly. I then referenced this BSP in the

Migrate clock source or PLL setup to the BSP level

While working on a BSP based on the nRF51 SoC, I noticed what may be an issue with the current division of config data between the 'bsp' and the 'mcu' code. For the nRF51 (and likely the nRF52, I haven't looked yet) the LF clock source is defined in 'mcu/nordic/nrf51xxx/src/hal_os_tick.c':