1.0.0-b1 BLE testing

Hello all, I did some BLE testing for the upcoming release (test plan is here: https://cwiki.apache.org/confluence/display/MYNEWT/Apache+Mynewt+Test+Plan). Everything seems to be good. There were a few issues that were identified and fixed during testing; the below results correspond to what is

Re: OS Event Queue errors in blinky

Hi David, Is there a reason you want/need to replace the bootloader while an app is running on a device? This is a pretty atypical scenario, in my opinion. thanks, aditi > On Nov 11, 2016, at 11:16 AM, David G. Simmons wrote: > > Interesting side-effect: > > If the blinky

Re: OS Event Queue errors in blinky

Interesting side-effect: If the blinky app is running, and I attempt to re-load a new version of the bootloader I'm back to: DSimmons-Pro:arduino_zero dsimmons$ newt load arduino_boot Loading bootloader Error: Downloading

Re: OS Event Queue errors in blinky

Hi Chris, Thanks for the insight on this. Yes, that's an interesting side effect. I'm inclined to agree with you that we leave blinky as-is for the release. I'll think about some possible wording for the Tutorials pages around blinky to indicate that it is, indeed, a "hello world" and that we

Re: OS Event Queue errors in blinky

Hi David, That is an interesting find. The problem is that blinky does not set a default eventq for taskless packages to use. If a package requires an event queue, and none has been designated, it triggers a crash with a failed assert. Blinky in its original state doesn't crash because it

Re: Smoke testing latest release

I think adding the erase command to newt is/was a great idea. This way there can be a standard way of erasing the supported board flash contents. I think the newt erase command should be able to erase the entire flash as well as portions of the flash. > On Nov 11, 2016, at 9:19 AM, Kevin

Re: Smoke testing latest release

We have a ticket for the erase command; it will get done soon. I just wanted to add my 1 cent regarding what the erase command should do (have the ability to erase the entire flash or portions of it). > On Nov 11, 2016, at 9:44 AM, Vipul Rahane wrote: > > +1 as well for the

Re: Smoke testing latest release

At the risk of repeating myself .. > On Nov 11, 2016, at 12:36 PM, will sanfilippo wrote: > > I think adding the erase command to newt is/was a great idea. This way there > can be a standard way of erasing the supported board flash contents. I think > the newt erase command

Re: Smoke testing latest release

+1 as well for the erase command. As for the smoke tests, I smoke tested the following boards using the same process Will mentioned: - Red Bear Nano 1 - Red Bear Nano 2 Looks good. Regards, Vipul Rahane > On Nov 11, 2016, at 9:37 AM, David G. Simmons wrote: > > At the

Re: Smoke testing latest release

You'll need to change the chip ID (there is a list available on Segger's website), but if you are using a JLink you can also try this and then send the '*erase*' command once you're connected, just as a FYI: $ jlinkexe -device nrf52832_xxaa -if swd -speed auto -autoconnect 1 On 11/11/16

Re: Smoke testing latest release

This was the bit I was missing ... All good now! I guess I should add this to the tutorial. dg > On Nov 11, 2016, at 11:55 AM, will sanfilippo wrote: > > # Erase the flash > newt debug arduino_zero_blinky > > (gdb) mon at91samd chip-erase > chip erased > chip erased >

Re: Smoke testing latest release

Hello David: As I said in my email, the smoke test consists of erasing the flash, loading the bootloader then loading the image. The steps are (using my target names): # Clean and buiild all the images. newt clean arduino_zero_boot newt clean arduino_zero_blinky newt build arduino_zero_boot