boot_serial support

[Kevin Townsend <ke...@adafruit.com>]

Hi Marko,

Thanks for getting this into the development branch! ... I was just 
setting things up to test it out, and I had a look at the code directly 
on github in the 'develop' branch, but despite my project being on 
'0-dev' it doesn't pull the changes locally when I run 'newt upgrade'. 
My project.yml is shown below:

    # Use github's distribution mechanism for core ASF libraries.
    # This provides mirroring automatically for us.
    #
    repository.apache-mynewt-core:
         type: github
         vers: 0-dev
         user: apache
         repo: incubator-mynewt-core

Is that still the correct 'vers' field, or should it be changed to 
something else? I thought this particular name mapped to 'develop' in 
the repo.

I can pull the remote changes via git easily enough, but I'd like to 
stick to using 'upgrade' if possible simply to avoid issues moving forward?

I assume these should be defined at the BSP level as well? 
https://github.com/apache/incubator-mynewt-core/blob/develop/apps/boot/src/boot.c#L184

K.


On 18/06/16 01:44, marko kiiskila wrote:
> Hi,
>
> I checked in a package that can be included in bootloader, and
> it will accept image upgrades over serial port.
>
> It expects that the image upgrade is done using the newtmgr
> protocol. Command set that it supports is limited; it can list images,
> accept an image upload command (stores it to slot 0), and also reset.
>
> For testing, I added a snippet of code to apps/boot which can
> be conditionally compiled in by defining target features for boot loader
> to include BOOT_SERIAL.
> The code monitors a GPIO pin, and if it\u2019s set to specific state during
> bootup, it\u2019ll enter the serial downloader, awaiting these commands.
> Again for testing, I added the pin config to use for Arduino MKR1000
> BSP.
>
> Here\u2019s my target definition for using this, in case you want to try this
> out:
> [marko@IsMyLaptop:~/src/incubator-mynewt-blinky]$ newt target show boot_mkr1000
> targets/boot_mkr1000
>      app=@apache-mynewt-core/apps/boot
>      bsp=@mynewt-arduino-zero/hw/bsp/arduino_mkr1000
>      build_profile=optimized
>      features=BOOT_SERIAL
>
> Feedback appreciated,
> M
>
>> On Jun 17, 2016, at 4:26 PM, marko@apache.org wrote:
>>
>> boot; conditionally check whether to expect image download commands
>> over serial. Whether code gets built in depends on target features.
>>
>>

Re: boot_serial support

[Christopher Collins <cc...@apache.org>]

On Sat, Jun 18, 2016 at 11:38:02AM +0200, Kevin Townsend wrote:
> Hi Marko,
> 
> Thanks for getting this into the development branch! ... I was just 
> setting things up to test it out, and I had a look at the code directly 
> on github in the 'develop' branch, but despite my project being on 
> '0-dev' it doesn't pull the changes locally when I run 'newt upgrade'. 

Unfortunately, pulling from git manually (as you did) is currently the
only way to get the latest changes.  This is a known shortcoming, and
there is a fix planned (https://issues.apache.org/jira/browse/MYNEWT-307).

Thanks,
Chris