You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mynewt.apache.org by "David G. Simmons" <sa...@mac.com> on 2016/10/24 13:51:59 UTC
Develop branch issues
Seems that things on the develop branch are not working as expected ... I'm tryin g build for the STMf32F3Discovery board using the develop branch of both apache-mynewt-core and mynewt_stm32f3 and neither the bootloader will nor the blinky app will build.
DSimmons-Pro:air_quality dsimmons$ newt target show
targets/blink_f3
app=apps/blinky
bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
build_profile=debug
targets/boot_f3
app=@apache-mynewt-core/apps/boot
bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
build_profile=optimized
targets/my_blinky_sim
app=apps/blinky
bsp=@apache-mynewt-core/hw/bsp/native
build_profile=debug
DSimmons-Pro:air_quality dsimmons$ newt build boot_f3
...
Linking boot.elf
Error: /Users/dsimmons/dev/air_quality/bin/boot_f3/apps/boot/boot.a(boot.o): In function `main':
/Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/apps/boot/src/boot.c:73: undefined reference to `bsp_init'
/Users/dsimmons/dev/air_quality/bin/boot_f3/libs/os/os.a(os_fault.o): In function `__assert_func':
/Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_fault.c:121: undefined reference to `system_debugger_connected'
collect2: error: ld returned 1 exit status
DSimmons-Pro:air_quality dsimmons$ newt build blink_f3
...
Linking blinky.elf
Error: /Users/dsimmons/dev/air_quality/bin/blink_f3/libs/os/os.a(os_arch_arm.o): In function `os_arch_os_init':
/Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_arch_arm.c:214: undefined reference to `bsp_init'
/Users/dsimmons/dev/air_quality/bin/blink_f3/libs/os/os.a(os_fault.o): In function `__assert_func':
/Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_fault.c:121: undefined reference to `system_debugger_connected'
collect2: error: ld returned 1 exit status
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.
Re: Develop branch issues
Posted by will sanfilippo <wi...@runtime.io>.
Let me take a look at that one. I was using the nrf52dk with a different app to do i2c testing. Hope I didnt break anything in bletiny! :-)
> On Oct 24, 2016, at 9:48 AM, David G. Simmons <sa...@mac.com> 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.
>
> dg
>
>> On Oct 24, 2016, at 12:28 PM, will sanfilippo <wi...@runtime.io> wrote:
>>
>> I am not sure if the stm32f3 directories have been updated for the new system configuration code. Develop is still not quite there yet (as you can see) so we will take a look at this and get it worked out. Sorry about the inconvenience.
>>
>>
>>> On Oct 24, 2016, at 6:51 AM, David G. Simmons <sa...@mac.com> wrote:
>>>
>>>
>>> Seems that things on the develop branch are not working as expected ... I'm tryin g build for the STMf32F3Discovery board using the develop branch of both apache-mynewt-core and mynewt_stm32f3 and neither the bootloader will nor the blinky app will build.
>>>
>>> DSimmons-Pro:air_quality dsimmons$ newt target show
>>> targets/blink_f3
>>> app=apps/blinky
>>> bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
>>> build_profile=debug
>>> targets/boot_f3
>>> app=@apache-mynewt-core/apps/boot
>>> bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
>>> build_profile=optimized
>>> targets/my_blinky_sim
>>> app=apps/blinky
>>> bsp=@apache-mynewt-core/hw/bsp/native
>>> build_profile=debug
>>> DSimmons-Pro:air_quality dsimmons$ newt build boot_f3
>>> ...
>>> Linking boot.elf
>>> Error: /Users/dsimmons/dev/air_quality/bin/boot_f3/apps/boot/boot.a(boot.o): In function `main':
>>> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/apps/boot/src/boot.c:73: undefined reference to `bsp_init'
>>> /Users/dsimmons/dev/air_quality/bin/boot_f3/libs/os/os.a(os_fault.o): In function `__assert_func':
>>> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_fault.c:121: undefined reference to `system_debugger_connected'
>>> collect2: error: ld returned 1 exit status
>>>
>>> DSimmons-Pro:air_quality dsimmons$ newt build blink_f3
>>> ...
>>> Linking blinky.elf
>>> Error: /Users/dsimmons/dev/air_quality/bin/blink_f3/libs/os/os.a(os_arch_arm.o): In function `os_arch_os_init':
>>> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_arch_arm.c:214: undefined reference to `bsp_init'
>>> /Users/dsimmons/dev/air_quality/bin/blink_f3/libs/os/os.a(os_fault.o): In function `__assert_func':
>>> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_fault.c:121: undefined reference to `system_debugger_connected'
>>> collect2: error: ld returned 1 exit status
>>>
>>> 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.
>
>
Re: Develop branch issues
Posted by Christopher Collins <cc...@apache.org>.
On Wed, Oct 26, 2016 at 09:26:38AM -0400, David G. Simmons wrote:
> Fixed ... GIT is some serious black-magic.
>
> I was somehow on branch 0.10.0-dev, so I reset my HEAD to
> origin/develop and it all worked. Can now biuild and load ble_tiny.
That is a relief to hear. I was out of ideas!
And yes, I can't argue with the comment about git :).
Chris
Re: Develop branch issues
Posted by "David G. Simmons" <sa...@mac.com>.
Fixed ... GIT is some serious black-magic.
I was somehow on branch 0.10.0-dev, so I reset my HEAD to origin/develop and it all worked. Can now biuild and load ble_tiny.
dg
> On Oct 25, 2016, at 6:50 PM, Adam <ad...@gmail.com> wrote:
>
> Strangely, that specific error: "Compiler Package not specified by BSP" was
> deleted from targetbuild.go in this commit:
>
>> git log -S"Compiler package"
> commit dd715c24b20d18fd77e52c02cab1a9f860ed329f
> Author: Christopher Collins <cc...@apache.org>
> Date: Wed Sep 28 16:29:24 2016 -0700
>
> It had been moved from build.go earlier. That error message shouldn't even
> be possible with latest develop. Very curious.
>
> Adam
>
>
> On Tue, Oct 25, 2016 at 2:16 PM, David G. Simmons <sa...@mac.com> wrote:
>
>>
>>> On Oct 25, 2016, at 4:52 PM, Christopher Collins <cc...@apache.org>
>> wrote:
>>>
>>> Hi David,
>>>
>>> On Tue, Oct 25, 2016 at 09:41:04AM -0400, David G. Simmons wrote:
>>> [...]
>>>> DSimmons-Pro:newt dsimmons$ ./build.sh
>>>> Building newt. This may take a minute...
>>>> Successfully built executable: /Users/dsimmons/dev/go/src/myn
>> ewt.apache.org/newt/newt/newt
>>>> DSimmons-Pro:newt dsimmons$ /Users/dsimmons/dev/go/src/myn
>> ewt.apache.org/newt/newt/newt version
>>>> Apache Newt (incubating) version: 0.9.0
>>>> DSimmons-Pro:newt dsimmons$ which newt
>>>> /Users/dsimmons/dev/go/bin/newt
>>>
>>> I think this might be the issue. The build.sh script doesn't copy the
>>> newt binary to your $GOPATH/bin directory. Instead, it builds it in
>>> your current directory. I would recomment not using the build.sh script
>>> at all. Instead, just run "go install" from the newt/newt directory.
>>> This command will put the built executable at $GOPATH/bin/newt
>>
>> DSimmons-Pro:mynewt.apache.org dsimmons$ cd newt/
>> DSimmons-Pro:newt dsimmons$ git branch
>> * develop
>> master
>>
>> So I'm definitely on the develop branch.
>>
>> I edited newtutil.go and changed
>> var NewtVersionStr string = "Apache Newt (incubating) version: 1.0.0-dev"
>>
>> and then
>> DSimmons-Pro:newt dsimmons$ go clean
>> DSimmons-Pro:newt dsimmons$ go install
>> DSimmons-Pro:newt dsimmons$ which newt
>> /Users/dsimmons/dev/go/bin/newt
>> DSimmons-Pro:newt dsimmons$ newt version
>> Apache Newt (incubating) version: 1.0.0-dev
>>
>> So I have what should be the most recent version of newt installed.
>>
>> Now, from the repo in the project:
>>
>> DSimmons-Pro:apache-mynewt-core dsimmons$ git branch
>> * develop
>> master
>> DSimmons-Pro:apache-mynewt-core dsimmons$ git checkout
>> Your branch is up-to-date with 'origin/develop'.
>> DSimmons-Pro:apache-mynewt-core dsimmons$
>>
>> So my repo in the project is up to date on the develop branch.
>>
>> DSimmons-Pro:nrf52dk dsimmons$ newt clean nrf52_boot
>> DSimmons-Pro:nrf52dk dsimmons$ newt build nrf52_boot
>> Building target targets/nrf52_boot
>> Error: Compiler package not specified by BSP
>> DSimmons-Pro:nrf52dk dsimmons$
>>
>> So there is some failure somewhere. Could be a PEBKAC, and I'm happy to
>> have it pointed out to me if so. :-)
>>
>> dg
>>
>>>
>>>> DSimmons-Pro:newt dsimmons$ newt version
>>>> Apache Newt (incubating) version: 0.9.0
>>>
>>> Yikes, this is indeed a problem. We should have updated the version
>>> string immediately after releasing 0.9.0.
>>>
>>> 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.
>>
>>
>>
--
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.
Re: Develop branch issues
Posted by Adam <ad...@gmail.com>.
Strangely, that specific error: "Compiler Package not specified by BSP" was
deleted from targetbuild.go in this commit:
> git log -S"Compiler package"
commit dd715c24b20d18fd77e52c02cab1a9f860ed329f
Author: Christopher Collins <cc...@apache.org>
Date: Wed Sep 28 16:29:24 2016 -0700
It had been moved from build.go earlier. That error message shouldn't even
be possible with latest develop. Very curious.
Adam
On Tue, Oct 25, 2016 at 2:16 PM, David G. Simmons <sa...@mac.com> wrote:
>
> > On Oct 25, 2016, at 4:52 PM, Christopher Collins <cc...@apache.org>
> wrote:
> >
> > Hi David,
> >
> > On Tue, Oct 25, 2016 at 09:41:04AM -0400, David G. Simmons wrote:
> > [...]
> >> DSimmons-Pro:newt dsimmons$ ./build.sh
> >> Building newt. This may take a minute...
> >> Successfully built executable: /Users/dsimmons/dev/go/src/myn
> ewt.apache.org/newt/newt/newt
> >> DSimmons-Pro:newt dsimmons$ /Users/dsimmons/dev/go/src/myn
> ewt.apache.org/newt/newt/newt version
> >> Apache Newt (incubating) version: 0.9.0
> >> DSimmons-Pro:newt dsimmons$ which newt
> >> /Users/dsimmons/dev/go/bin/newt
> >
> > I think this might be the issue. The build.sh script doesn't copy the
> > newt binary to your $GOPATH/bin directory. Instead, it builds it in
> > your current directory. I would recomment not using the build.sh script
> > at all. Instead, just run "go install" from the newt/newt directory.
> > This command will put the built executable at $GOPATH/bin/newt
>
> DSimmons-Pro:mynewt.apache.org dsimmons$ cd newt/
> DSimmons-Pro:newt dsimmons$ git branch
> * develop
> master
>
> So I'm definitely on the develop branch.
>
> I edited newtutil.go and changed
> var NewtVersionStr string = "Apache Newt (incubating) version: 1.0.0-dev"
>
> and then
> DSimmons-Pro:newt dsimmons$ go clean
> DSimmons-Pro:newt dsimmons$ go install
> DSimmons-Pro:newt dsimmons$ which newt
> /Users/dsimmons/dev/go/bin/newt
> DSimmons-Pro:newt dsimmons$ newt version
> Apache Newt (incubating) version: 1.0.0-dev
>
> So I have what should be the most recent version of newt installed.
>
> Now, from the repo in the project:
>
> DSimmons-Pro:apache-mynewt-core dsimmons$ git branch
> * develop
> master
> DSimmons-Pro:apache-mynewt-core dsimmons$ git checkout
> Your branch is up-to-date with 'origin/develop'.
> DSimmons-Pro:apache-mynewt-core dsimmons$
>
> So my repo in the project is up to date on the develop branch.
>
> DSimmons-Pro:nrf52dk dsimmons$ newt clean nrf52_boot
> DSimmons-Pro:nrf52dk dsimmons$ newt build nrf52_boot
> Building target targets/nrf52_boot
> Error: Compiler package not specified by BSP
> DSimmons-Pro:nrf52dk dsimmons$
>
> So there is some failure somewhere. Could be a PEBKAC, and I'm happy to
> have it pointed out to me if so. :-)
>
> dg
>
> >
> >> DSimmons-Pro:newt dsimmons$ newt version
> >> Apache Newt (incubating) version: 0.9.0
> >
> > Yikes, this is indeed a problem. We should have updated the version
> > string immediately after releasing 0.9.0.
> >
> > 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.
>
>
>
Re: Develop branch issues
Posted by "David G. Simmons" <sa...@mac.com>.
> On Oct 25, 2016, at 4:52 PM, Christopher Collins <cc...@apache.org> wrote:
>
> Hi David,
>
> On Tue, Oct 25, 2016 at 09:41:04AM -0400, David G. Simmons wrote:
> [...]
>> DSimmons-Pro:newt dsimmons$ ./build.sh
>> Building newt. This may take a minute...
>> Successfully built executable: /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt
>> DSimmons-Pro:newt dsimmons$ /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt version
>> Apache Newt (incubating) version: 0.9.0
>> DSimmons-Pro:newt dsimmons$ which newt
>> /Users/dsimmons/dev/go/bin/newt
>
> I think this might be the issue. The build.sh script doesn't copy the
> newt binary to your $GOPATH/bin directory. Instead, it builds it in
> your current directory. I would recomment not using the build.sh script
> at all. Instead, just run "go install" from the newt/newt directory.
> This command will put the built executable at $GOPATH/bin/newt
DSimmons-Pro:mynewt.apache.org dsimmons$ cd newt/
DSimmons-Pro:newt dsimmons$ git branch
* develop
master
So I'm definitely on the develop branch.
I edited newtutil.go and changed
var NewtVersionStr string = "Apache Newt (incubating) version: 1.0.0-dev"
and then
DSimmons-Pro:newt dsimmons$ go clean
DSimmons-Pro:newt dsimmons$ go install
DSimmons-Pro:newt dsimmons$ which newt
/Users/dsimmons/dev/go/bin/newt
DSimmons-Pro:newt dsimmons$ newt version
Apache Newt (incubating) version: 1.0.0-dev
So I have what should be the most recent version of newt installed.
Now, from the repo in the project:
DSimmons-Pro:apache-mynewt-core dsimmons$ git branch
* develop
master
DSimmons-Pro:apache-mynewt-core dsimmons$ git checkout
Your branch is up-to-date with 'origin/develop'.
DSimmons-Pro:apache-mynewt-core dsimmons$
So my repo in the project is up to date on the develop branch.
DSimmons-Pro:nrf52dk dsimmons$ newt clean nrf52_boot
DSimmons-Pro:nrf52dk dsimmons$ newt build nrf52_boot
Building target targets/nrf52_boot
Error: Compiler package not specified by BSP
DSimmons-Pro:nrf52dk dsimmons$
So there is some failure somewhere. Could be a PEBKAC, and I'm happy to have it pointed out to me if so. :-)
dg
>
>> DSimmons-Pro:newt dsimmons$ newt version
>> Apache Newt (incubating) version: 0.9.0
>
> Yikes, this is indeed a problem. We should have updated the version
> string immediately after releasing 0.9.0.
>
> 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.
Re: Develop branch issues
Posted by Christopher Collins <cc...@apache.org>.
Hi David,
On Tue, Oct 25, 2016 at 09:41:04AM -0400, David G. Simmons wrote:
[...]
> DSimmons-Pro:newt dsimmons$ ./build.sh
> Building newt. This may take a minute...
> Successfully built executable: /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt
> DSimmons-Pro:newt dsimmons$ /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt version
> Apache Newt (incubating) version: 0.9.0
> DSimmons-Pro:newt dsimmons$ which newt
> /Users/dsimmons/dev/go/bin/newt
I think this might be the issue. The build.sh script doesn't copy the
newt binary to your $GOPATH/bin directory. Instead, it builds it in
your current directory. I would recomment not using the build.sh script
at all. Instead, just run "go install" from the newt/newt directory.
This command will put the built executable at $GOPATH/bin/newt
> DSimmons-Pro:newt dsimmons$ newt version
> Apache Newt (incubating) version: 0.9.0
Yikes, this is indeed a problem. We should have updated the version
string immediately after releasing 0.9.0.
Thanks,
Chris
Re: Develop branch issues
Posted by "David G. Simmons" <sa...@mac.com>.
Hi Chris,
I'm pretty sure I have the latest version of newt, but it's difficult to tell.
DSimmons-Pro:newt dsimmons$ pwd
/Users/dsimmons/dev/go/src/mynewt.apache.org/newt
DSimmons-Pro:newt dsimmons$ git branch
* develop
master
DSimmons-Pro:newt dsimmons$ git pull
remote: Counting objects: 588, done.
remote: Compressing objects: 100% (396/396), done.
remote: Total 435 (delta 299), reused 0 (delta 0)
Receiving objects: 100% (435/435), 102.36 KiB | 110.00 KiB/s, done.
Resolving deltas: 100% (299/299), completed with 102 local objects.
From https://git-wip-us.apache.org/repos/asf/incubator-mynewt-newt
fed90aa..7177ff6 develop -> origin/develop
Already up-to-date.
DSimmons-Pro:newt dsimmons$ ./build.sh
Building newt. This may take a minute...
Successfully built executable: /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt
DSimmons-Pro:newt dsimmons$ /Users/dsimmons/dev/go/src/mynewt.apache.org/newt/newt/newt version
Apache Newt (incubating) version: 0.9.0
DSimmons-Pro:newt dsimmons$ which newt
/Users/dsimmons/dev/go/bin/newt
DSimmons-Pro:newt dsimmons$ newt version
Apache Newt (incubating) version: 0.9.0
So it appears that there's no way to tell if I have the most recent version or not, as the version strings have not been updated.
That being said, I have taken that brand new freshly build version of newt, and attempted to build the nrf52_boot loader with it, and still get the compiler package error message.
It appears that I have the most recent (develop branch) versions of both newt and the -core repos.
dg
>
> On Oct 24, 2016, at 5:29 PM, Christopher Collins <cc...@apache.org> wrote:
>
> On Mon, Oct 24, 2016 at 03:49:51PM -0400, David G. Simmons wrote:
>> 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.
>
> Recently, many BSP settings were moved out of the BSP's pkg.yml file and
> into a new file: bsp.yml. Among these settings is the compiler package
> that should be used to build projects for the BSP.
>
> Is it possible that you don't have the latest newt tool? An older
> version won't know to look for the bsp.yml file, so it won't find the
> compiler reference. Similarly, if you have a new newt tool but an older
> core repo, the newt tool will be looking for a bsp.yml file that doesn't
> exist.
>
> Let me know if these don't sound like reasonable possiblities and I'll
> dig deeper!
>
> 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.
Re: Develop branch issues
Posted by Christopher Collins <cc...@apache.org>.
On Mon, Oct 24, 2016 at 03:49:51PM -0400, David G. Simmons wrote:
> 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.
Recently, many BSP settings were moved out of the BSP's pkg.yml file and
into a new file: bsp.yml. Among these settings is the compiler package
that should be used to build projects for the BSP.
Is it possible that you don't have the latest newt tool? An older
version won't know to look for the bsp.yml file, so it won't find the
compiler reference. Similarly, if you have a new newt tool but an older
core repo, the newt tool will be looking for a bsp.yml file that doesn't
exist.
Let me know if these don't sound like reasonable possiblities and I'll
dig deeper!
Chris
Re: Develop branch issues
Posted by "David G. Simmons" <sa...@mac.com>.
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 <cc...@apache.org> 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.
Re: Develop branch issues
Posted by Christopher Collins <cc...@apache.org>.
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
Re: Develop branch issues
Posted by "David G. Simmons" <sa...@mac.com>.
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.
dg
> On Oct 24, 2016, at 12:28 PM, will sanfilippo <wi...@runtime.io> wrote:
>
> I am not sure if the stm32f3 directories have been updated for the new system configuration code. Develop is still not quite there yet (as you can see) so we will take a look at this and get it worked out. Sorry about the inconvenience.
>
>
>> On Oct 24, 2016, at 6:51 AM, David G. Simmons <sa...@mac.com> wrote:
>>
>>
>> Seems that things on the develop branch are not working as expected ... I'm tryin g build for the STMf32F3Discovery board using the develop branch of both apache-mynewt-core and mynewt_stm32f3 and neither the bootloader will nor the blinky app will build.
>>
>> DSimmons-Pro:air_quality dsimmons$ newt target show
>> targets/blink_f3
>> app=apps/blinky
>> bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
>> build_profile=debug
>> targets/boot_f3
>> app=@apache-mynewt-core/apps/boot
>> bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
>> build_profile=optimized
>> targets/my_blinky_sim
>> app=apps/blinky
>> bsp=@apache-mynewt-core/hw/bsp/native
>> build_profile=debug
>> DSimmons-Pro:air_quality dsimmons$ newt build boot_f3
>> ...
>> Linking boot.elf
>> Error: /Users/dsimmons/dev/air_quality/bin/boot_f3/apps/boot/boot.a(boot.o): In function `main':
>> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/apps/boot/src/boot.c:73: undefined reference to `bsp_init'
>> /Users/dsimmons/dev/air_quality/bin/boot_f3/libs/os/os.a(os_fault.o): In function `__assert_func':
>> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_fault.c:121: undefined reference to `system_debugger_connected'
>> collect2: error: ld returned 1 exit status
>>
>> DSimmons-Pro:air_quality dsimmons$ newt build blink_f3
>> ...
>> Linking blinky.elf
>> Error: /Users/dsimmons/dev/air_quality/bin/blink_f3/libs/os/os.a(os_arch_arm.o): In function `os_arch_os_init':
>> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_arch_arm.c:214: undefined reference to `bsp_init'
>> /Users/dsimmons/dev/air_quality/bin/blink_f3/libs/os/os.a(os_fault.o): In function `__assert_func':
>> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_fault.c:121: undefined reference to `system_debugger_connected'
>> collect2: error: ld returned 1 exit status
>>
>> 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.
Re: Develop branch issues
Posted by will sanfilippo <wi...@runtime.io>.
I am not sure if the stm32f3 directories have been updated for the new system configuration code. Develop is still not quite there yet (as you can see) so we will take a look at this and get it worked out. Sorry about the inconvenience.
> On Oct 24, 2016, at 6:51 AM, David G. Simmons <sa...@mac.com> wrote:
>
>
> Seems that things on the develop branch are not working as expected ... I'm tryin g build for the STMf32F3Discovery board using the develop branch of both apache-mynewt-core and mynewt_stm32f3 and neither the bootloader will nor the blinky app will build.
>
> DSimmons-Pro:air_quality dsimmons$ newt target show
> targets/blink_f3
> app=apps/blinky
> bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
> build_profile=debug
> targets/boot_f3
> app=@apache-mynewt-core/apps/boot
> bsp=@mynewt_stm32f3/hw/bsp/stm32f3discovery
> build_profile=optimized
> targets/my_blinky_sim
> app=apps/blinky
> bsp=@apache-mynewt-core/hw/bsp/native
> build_profile=debug
> DSimmons-Pro:air_quality dsimmons$ newt build boot_f3
> ...
> Linking boot.elf
> Error: /Users/dsimmons/dev/air_quality/bin/boot_f3/apps/boot/boot.a(boot.o): In function `main':
> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/apps/boot/src/boot.c:73: undefined reference to `bsp_init'
> /Users/dsimmons/dev/air_quality/bin/boot_f3/libs/os/os.a(os_fault.o): In function `__assert_func':
> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_fault.c:121: undefined reference to `system_debugger_connected'
> collect2: error: ld returned 1 exit status
>
> DSimmons-Pro:air_quality dsimmons$ newt build blink_f3
> ...
> Linking blinky.elf
> Error: /Users/dsimmons/dev/air_quality/bin/blink_f3/libs/os/os.a(os_arch_arm.o): In function `os_arch_os_init':
> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_arch_arm.c:214: undefined reference to `bsp_init'
> /Users/dsimmons/dev/air_quality/bin/blink_f3/libs/os/os.a(os_fault.o): In function `__assert_func':
> /Users/dsimmons/dev/air_quality/repos/apache-mynewt-core/libs/os/src/arch/cortex_m4/os_fault.c:121: undefined reference to `system_debugger_connected'
> collect2: error: ld returned 1 exit status
>
> 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.
>
>