Hi Chris, I'm pretty sure I have the latest version of newt, but it's difficult to tell.
DSimmons-Pro:newt dsimmons$ pwd /Users/dsimmons/dev/go/src/mynewt.apache.org/newt DSimmons-Pro:newt dsimmons$ git branch * develop master DSimmons-Pro:newt dsimmons$ git pull remote: Counting objects: 588, done. remote: Compressing objects: 100% (396/396), done. remote: Total 435 (delta 299), reused 0 (delta 0) Receiving objects: 100% (435/435), 102.36 KiB | 110.00 KiB/s, done. Resolving deltas: 100% (299/299), completed with 102 local objects. From https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt fed90aa..7177ff6 develop -> origin/develop Already up-to-date. DSimmons-Pro:newt dsimmons$ ./build.sh Building newt. This may take a minute... Successfully built executable: /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt DSimmons-Pro:newt dsimmons$ /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt version Apache Newt (incubating) version: 0.9.0 DSimmons-Pro:newt dsimmons$ which newt /Users/dsimmons/dev/go/bin/newt DSimmons-Pro:newt dsimmons$ newt version Apache Newt (incubating) version: 0.9.0 So it appears that there's no way to tell if I have the most recent version or not, as the version strings have not been updated. That being said, I have taken that brand new freshly build version of newt, and attempted to build the nrf52_boot loader with it, and still get the compiler package error message. It appears that I have the most recent (develop branch) versions of both newt and the -core repos. dg > > On Oct 24, 2016, at 5:29 PM, Christopher Collins <[email protected]> wrote: > > On Mon, Oct 24, 2016 at 03:49:51PM -0400, David G. Simmons wrote: >> Thanks Chris, >> >> I'm using develop as I'm working on updating all the docs for the >> 1.0Beta release, and it's rough going in places. :-) >> >> I've taken your suggestions and erased the NRF52 device using J-Link >> and that was successful. >> >> I've made sure that the repos are on the develop branch >> >> DSimmons-Pro:apache-mynewt-core dsimmons$ git branch >> * develop >> master >> >> I have targets all set: >> DSimmons-Pro:nrf52dk dsimmons$ newt target show >> targets/blink_nordic >> app=apps/blinky >> bsp=@apache-mynewt-core/hw/bsp/nrf52dk >> build_profile=debug >> targets/my_blinky_sim >> app=apps/blinky >> bsp=@apache-mynewt-core/hw/bsp/native >> build_profile=debug >> targets/myble >> app=@apache-mynewt-core/apps/bletiny >> bsp=@apache-mynewt-core/hw/bsp/nrf52dk >> build_profile=optimized >> cflags=-DSTATS_NAME_ENABLE >> targets/nrf52_boot >> app=@apache-mynewt-core/apps/boot >> bsp=@apache-mynewt-core/hw/bsp/nrf52dk >> build_profile=optimized >> >> And they look correct (to me) >> >> newt build nrf52_boot >> Building target targets/nrf52_boot >> Error: Compiler package not specified by BSP >> >> So, the earlier errors were no doubt caused by something else, and >> something NOT in the develop branch. That being said, there's clearly >> a new step involved in setting the "compiler package" that I'm not >> aware of. > > Recently, many BSP settings were moved out of the BSP's pkg.yml file and > into a new file: bsp.yml. Among these settings is the compiler package > that should be used to build projects for the BSP. > > Is it possible that you don't have the latest newt tool? An older > version won't know to look for the bsp.yml file, so it won't find the > compiler reference. Similarly, if you have a new newt tool but an older > core repo, the newt tool will be looking for a bsp.yml file that doesn't > exist. > > Let me know if these don't sound like reasonable possiblities and I'll > dig deeper! > > Chris -- 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.
