Re: newtmgr over Serial

Ok, there’s a bug there, caused by debug printfs. Probably my fault. There is a call to console_printf() in bootloader. apps/boot/boot.c, lines 120-121. Those should not be there. And they will crash nrf52 when building with BOOT_SERIAL set. Remove them, and you should be ok. > On Sep 23, 2016,

Re: newtmgr over Serial

> On Sep 23, 2016, at 12:15 PM, Kevin Townsend wrote: > > Hi Marko, > > Thanks for the reply ... I wasn't sure what to do with the console/stub > dependency though ... where should this be set? You should remove the console/stub from apps/boot/pkg.yml. libs/boot_serial

Re: hal watchdog

I also worry (slightly) that the default time between sanity waking up and the watchdog firing may not be enough. It is configurable so that is all good, but maybe the default should be a bit longer as sanity is checked in the idle task and if a system has lots of tasks the idle task may not

Notify with more than 20 bytes

Hi Everyone, I am doing throughput testing specifically with notification characteristics for sending sensor data from nrf52dk to mobile. I use ble_gattc_notify_custom(buffer, size) without any issues, except when the buffer is > 20 bytes, it seems to be truncated

RE: Notify with more than 20 bytes

Hi Chris, Thank you very much, that is the perfect explanation. I got MTU exchanged work with Adafruit Bluefruit app and doing statistics of tx time for several combination of now :) Best regards, Ha Thach > -Original Message- > From: Christopher Collins [mailto:ccoll...@apache.org]

Re: newtmgr over Serial

Hi Marko, Thanks for the reply ... I wasn't sure what to do with the console/stub dependency though ... where should this be set? # # Define BOOT_SERIAL in target features to include serial downloader. # And uncomment 'libs/console/stub' from pkg.deps. # This builds properly but when I flash

Re: hal watchdog

Well, I have worked on systems where 200 or even 500 msecs would definitely have caused the code to crash. For example, you have to do lots of crypto processing and you dont have HW support. That being said, I think this is a moot point as it is configurable so all good. I just like to hear

Re: newtmgr over Serial

Hi Sterling, I saw the note on the dependency, but is the target the right place to be adding the dep entry as follows: $ newt target set bootloader deps="@apache-mynewt-core/libs/console/stub" Adding the two missing defines at the BSP level for BOOT_SERIAL gets this building at least

Re: hal watchdog

Oh yeah, sorry. I dont know why I said 200 when it is clearly 500 :-) Thanks for pointing that out. All good about the msec v sec thing. > On Sep 23, 2016, at 11:02 AM, Sterling Hughes wrote: > > 2 reasons: > > - most (all) chips provide that granularity that i’ve seen,

Re: hal watchdog

2 reasons: - most (all) chips provide that granularity that i’ve seen, so why not? IMO, it’s not up for us to decide what people set watchdog interval to in the HAL if it’s portable. - as you point out, it’s convenient to have a consistent timebase between sanity and watchdog, given how

Re: hal watchdog

Why is the interval defined in milliseconds btw? Is there a particular reason for it? Is it because you wanted to be able to separate the sanity interval and the watchdog interval by less than one second? Or are you worried that some watchdogs may have very small timeouts and milliseconds would

Re: Notify with more than 20 bytes

On Fri, Sep 23, 2016 at 10:02:32AM -0700, Christopher Collins wrote: [...] > If your application needs to send larger ATT packets, it needs to > negotiate a greater MTU with its peer. This is accomplished by calling > ble_gattc_exchange_mtu() >

Re: Notify with more than 20 bytes

Hello Ha, On Fri, Sep 23, 2016 at 11:00:32PM +0700, hathach wrote: > Hi Everyone, > > I am doing throughput testing specifically with notification characteristics > for sending sensor data from nrf52dk to mobile. I use > ble_gattc_notify_custom(buffer, size) without any issues, except when the >

Re: newtmgr over Serial

No worries: try setting the feature vs CFLAGS. (Note: all good efforts learning about features will be unfortunately useless, as we’ve changed to sys config in develop :-( ). # clear cflags newt target set bootloader cflags= # set feature newt target set bootloader features=BOOT_SERIAL That

Re: newtmgr over Serial

Hi Sterling, Thanks for the heads up. I added the cflag via '$ newt target set bootloader cflags=-DBOOT_SERIAL' and I can see that it exists in '/repos/apache-mynewt-core/libs/boot_serial', though when I try to build I'm getting: $ newt build bootloader Building target

Notify with more than 20 bytes

Hi Everyone, I am doing throughput testing specifically with notification characteristics for sending sensor data from nrf52dk to mobile. I use ble_gattc_notify_custom(buffer, size) without any issues, except when the buffer is > 20 bytes, it seems to be truncated

Re: newtmgr over Serial

Hi Kevin, I think (and I’ll let Marko chime in here), you can use the boot_serial package to achieve this (apache-mynewt-core/libs/boot_serial.) It speaks the newtmgr protocol, but doesn’t require the shell task or an image to be programmed. I think it will slightly explode the size of

Re: newtmgr over Serial

+1 for bootloader-only serial programming All the best Wayne On 23 September 2016 at 10:46, Kevin Townsend wrote: > Hi Will (and company), > > Sorry to recycle an old thread, but I was just doing some testing with the > bootloader on the latest release, and wanted to come