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.
Thanks,
dg
> On Oct 24, 2016, at 1:53 PM, Christopher Collins <[email protected]> wrote:
>
> On Mon, Oct 24, 2016 at 12:48:26PM -0400, David G. Simmons wrote:
>> Thanks for looking into this Will. I'm also seeing some misbehavior on the
>> NRF52DK board and the bletiny app.
>>
>> 0:Unhandled interrupt (3), exception sp 0x20007f38
>> 0: r0:0x00000000 r1:0x00000000 r2:0xdeadbeef r3:0x00000000
>> 0: r4:0x20001538 r5:0x08000008 r6:0x00000200 r7:0x20001558
>> 0: r8:0xffffffff r9:0x00022792 r10:0x0000db19 r11:0x00000000
>> 0:r12:0x200009ec lr:0x0000d75b pc:0x0000d3b6 psr:0x81000000
>> 0:ICSR:0x00000803 HFSR:0x40000000 CFSR:0x00008200
>> 0:BFAR:0x08000008 MMFAR:0x08000008
>>
>> Which causes the board to reset, and repeat ad infinitum.
>
> Hi David,
>
> There have been a number of changes to develop lately which might cause
> problems if some parts are out of sync. In particular, I recommend
> doing all of the following:
>
> * Update newt to the latest in 'develop'
> * Erase the entire flash on your device
> * Build and upload a new boot loader
>
> These actions are necesary to account for some changes to the flash map
> and boot loader code. I have been negligent in keeping the dev list up
> to date with some backwards-compatibility breaking changes. I wasn't
> sure if anyone was still using the develop branch, and I wanted to wait
> until all the changes were in. That said, I think it is great that you
> are using develop. It is a relief to hear that someone is trying out
> the latest! I plan on sending out some more detailed updates later
> today.
>
> Please let us know if this doesn't solve the issue, or if you have any
> other questions.
>
> (For the record, I am able to run bletiny on the nrf52dk without issue.)
>
> Thanks,
> 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.
