Re: Mynewt Local BSP Instance Location

2016-05-11 Thread Kevin Townsend
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: Mynewt Local BSP Instance Location

2016-05-11 Thread Sterling Hughes
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

2016-05-11 Thread microBuilder.eu
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

2016-05-11 Thread Christopher Collins
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, >

Mynewt Local BSP Instance Location

2016-05-11 Thread Kevin Townsend
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