Re: Smoke testing latest release

Also FYI I am working on an iPhone app to connect to MyNewt devices (currently the NRF52DK) and read sensor data. dg > On Nov 14, 2016, at 8:08 PM, Christopher Collins wrote: > > FYI- I have added a 1.0.0-b1 test results page to the wiki: >

Re: Smoke testing latest release

FYI- I have added a 1.0.0-b1 test results page to the wiki: https://cwiki.apache.org/confluence/display/MYNEWT/1.0.0-b1+Test+Results Hopefully this will make it easier to coordinate testing efforts. Thanks, Chris On Fri, Nov 11, 2016 at 08:55:40AM -0800, will sanfilippo wrote: > Hello David: >

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

Re: Smoke testing latest release

olimex and arduino zero good too. > On Nov 10, 2016, at 6:01 PM, will sanfilippo wrote: > > All: > > Just wanted to note I smoke tested the following boards/bps. The smoke test > is basically erasing the flash, loading the bootloader and blinky (and making > sure it

Smoke testing latest release

All: Just wanted to note I smoke tested the following boards/bps. The smoke test is basically erasing the flash, loading the bootloader and blinky (and making sure it blinks!) nrf52dk nrf51dk nrf51dk-16kb bmd300 arduino mkr1000 nucleo-f401 We had a snafu with the arduino zero if the flash was