Re: Compile and build time, any way to speed up?

Hi Cris, On Fri, Jan 06, 2017 at 12:54:03PM -0500, Cris Frusina wrote: > Fixed the TCP issue by restarting Virtualbox, did an newt upgrade and a > newt install with the 0-dev in the project file. > > Still missing something as -j is not recognized. The -j option is only supported in the

Re: Compile and build time, any way to speed up?

Fixed the TCP issue by restarting Virtualbox, did an newt upgrade and a newt install with the 0-dev in the project file. Still missing something as -j is not recognized. ~/newt version Apache Newt (incubating) version: 1.0.0-b1 ~/newt build -j 5 ble_usb Error: unknown shorthand flag: 'j' in

Re: Compile and build time, any way to speed up?

That looks like your network isn't working from your Docker instance. If that's actually the case, it could also (possibly) explain the torturously long compile times. Maybe. dg > On Jan 6, 2017, at 12:24 PM, Cris Frusina wrote: > > David, > > I've tried what you suggested

Re: Compile and build time, any way to speed up?

David, I've tried what you suggested I'm getting this error: *apache-mynewt-core** **Error: Get https://api.github.com/repos/apache/incubator-mynewt-core/contents/repository.yml?ref=master: dial tcp: lookup api.github.com on 10.0.2.3:53: read udp 172.17.0.2:38728->10.0.2.3:53: i/o timeout*

Re: Compile and build time, any way to speed up?

You could do that, but if you don't want to remake the whole Docker instance, you should be able to simply edit the project.yml file and change the vers strin for repository.apache-mynewt-core to 0-dev and then run newt install Best regards, dg > On Jan 6, 2017, at 5:23 AM, Fabio Utzig

Re: Compile and build time, any way to speed up?

I'm not using the docker version myself, but I think you could try rebuilding the docker image: https://github.com/runtimeinc/newt-docker Inside the Makefile, change the branch that is checked out from "-b mynewt_1_0_0_b1_tag" to "-b develop":

Re: Getting Unhandled interrupt (17)

Hi, The unhandled exception is most probably caused by missing to define a handler function. Before enabling the IRQ, try adding something like (assuming the IRQ you want to handle is SWI0_EGU0_IRQ): NVIC_SetVector(SWI0_EGU0_IRQn, (uint32_t) my_swi0_handler); Att, Fabio Utzig On Fri, Jan 6,