On Tue, Aug 30, 2016 at 12:35:31AM +, p...@wrada.com wrote:
> Would you expect that everyone that writes a new core package, would add
> their init code to sys/sysinit package and include their package in the
> dependencies for sys/sysinit? Would that mean that if I include
> sys/sysinit as a
On Mon, Aug 29, 2016 at 04:53:12PM -0700, marko kiiskila wrote:
> Hi,
>
> for bootloader I’d like to have different set of devices than the app.
> What did you have in mind for that? Different bsp_init() routines?
> Or would bsp_init() have conditional parts depending on syscfg.h says?
I know
Thanks Chris,
I think this is a great step in the right direction. I¹m looking forward
to seeing it.
Just a few quick questions/comments about sysinit.
Would you expect that everyone that writes a new core package, would add
their init code to sys/sysinit package and include their package in
All,
I have been adding split image to ble-nano.
What I found what that there is something happening with MK20 USB daughter
board. When I have the BLE module plugged into the daughter module, I am not
able to use newtmgr commands with slinky.
However, when I unplug the module and wire
On Mon, Aug 29, 2016 at 10:32:25AM -0600, Cody Smith wrote:
> Hey Everybody,
>
> I'm trying to build the ble tiny example in Ubuntu 16.04 using the Newt
> 0.8.0. I've done a newt upgrade, and still get this same error. The error
> on a newt build is:
>
> Building target targets/bleFuzzTiny_tgt
