Hi Wayne,
As you suspected, the latest changes go into a development branch.
They'll be in the next release, but if you want to try them out ahead of
time, you can configure your project to download packages from the
development branch.
To use the development branch, change your project.yml as follows:
FROM:
repository.apache-mynewt-core:
type: github
vers: 0-latest
user: apache
repo: incubator-mynewt-core
TO:
repository.apache-mynewt-core:
type: github
vers: 0-dev
user: apache
repo: incubator-mynewt-core
(change the "vers" field).
Then upgrade your packages with "newt upgrade", e.g.,
[ccollins@iori:~/tmp/myproj]$ newt upgrade
apache-mynewt-core
Would you like to upgrade repository apache-mynewt-core from 0.7.9-none to
0.0.0-none ? [Yn] y
Naturally, this branch is quite unstable.
Chris
On Sat, Apr 23, 2016 at 05:39:22AM +0100, Wayne Keenan wrote:
> Hi,
>
> Thanks or this.
>
> Please could you let me know what else needs to be run / updated /
> downloaded prior to those commands in order to update the repo and obtain
> the bsp package?
>
> I tried `newt upgrade` on an existing project and also tried creating a
> project from scratch but there is no
> repos/papache-mynewt-core/hw/bsp/nrf52dk folder
>
> Do I need to move from using the release build of newt and switch to a dev
> version ?
>
>
> All the best
> Wayne
>
> On Sat, Apr 23, 2016 at 2:00 AM, will sanfilippo <[email protected]> wrote:
>
> > Hello:
> >
> > Just wanted to let folks know that we added support for the new nrf52 DK.
> > The BSP is in hw/bsp/nrf52dk. If you have exisiting targets using either
> > the nrf51dk or nrf52pdk it should be easy to copy them and replace the bsp
> > with the nrf52dk:
> >
> > newt target copy my_old_nrf52pdk_target my_new_nrf52dk_target
> > newt target set my_new_nrf52dk_target bsp=hw/bsp/nrf52dk
> >
> > Aside from fixing a number of errata, one of the big fixes was that now it
> > is possible to address all of the RAM as data ram. The nrf52 chips on the
> > Preview Development kits could only access 32K of the 64K as data ram; the
> > other 32K was code ram. This was not a big deal unless you want to DMA from
> > memory; you can only use data ram.
> >
> > Anyway, please give it a spin. If there are any issues please let me know.
> >
> > Enjoy!
