Every time I post with a problem, I cringe because there's a > 0 probability 
that it is caused by me being somehow out of sync with the latest develop 
branch. That being said, I'm pretty sure that I am, indeed, on the latest of 
all said repos. 

DSimmons-Pro:apache-mynewt-core dsimmons$ git log
commit 0c51338ed56eee51d3c1b76f90db842eae1cac44
Author: Marko Kiiskila <[email protected]>
Date:   Tue Nov 8 23:29:14 2016 -0800

    boot; don't start OS even when boot_serial is not defined.

commit 41e4670a896ce2087e4e5ae1354dc40c74a0e4ce
Author: Marko Kiiskila <[email protected]>
Date:   Tue Nov 8 23:27:50 2016 -0800

    imgmgr; fix use of incorrect cbor encoder.

...

So it looks like I have the latest version of the apache-mynewt-core repo. The 
mynewt repo is another story entirely. Somehow I think I managed to get 
sidetracked onto 'origin/0_10_0_dev' which is, apparently, not the same as 
'origin/develop' 

This, however, brings up another issue. Since I'm now up to date on newt, I 
figured I should also make sure I was up to date on newtmgr. It's actually not 
possible to tell what version of newtmgr I have, since 'newtmgr version' isn't 
a valid command. (I've created a JIRA tocket o nhis, as I think newtmgr should 
be able to tell you what version you're using)

Now that I've gotten THAT issue cleared up, and I've rebuilt/installed newt 
again, it seems to work. Have I mentioned recently how git is black magic? 

Back to work ... 

dg


> On Nov 9, 2016, at 12:26 PM, will sanfilippo <[email protected]> wrote:
> 
> I dont like saying this, because I dont like it when folks say it to me, but 
> I have the latest newt tool and the latest from develop (at least I think I 
> do) and I have no issue with loading an arduino_zero board (either the 
> bootloader or the image).
> 
> I need to look at the go code in more detail to provide a better answer, but 
> CORE_PATH is set here: builder/load.go.
> 
> If you turn on debug when you load with -lDEBUG it shows the CORE_PATH 
> setting. Not that that will help much, but at least it will show what it 
> thinks it is.
> 
> 
>> On Nov 9, 2016, at 7:46 AM, David G. Simmons <[email protected]> wrote:
>> 
>> 
>> On the latest develop branch, there seems to be an issue with loading ... 
>> 
>> newt load arduino_boot
>> Loading bootloader
>> + . /hw/scripts/openocd.sh
>> /Users/dsimmons/dev/myproj/repos/mynewt_arduino_zero/hw/bsp/arduino_zero/arduino_zero_download.sh:
>>  line 31: /hw/scripts/openocd.sh: No such file or directory
>> 
>> It appears that $CORE_PATH is not properly set before 
>> arduino_zero_download.sh is called. I've yet to discover where this is 
>> supposed to be set in newt.
>> 
>> dg
>> --
>> 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.
>> 
>> 
> 

--
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.


Reply via email to