Re: newNewt

2017-01-26 Thread marko kiiskila
Try running pyocd-flashtool manually with the arguments newt would pass to it. If that works, then at least you have the jtag communications working ok. Or just try changing the download script to use absolute path. Obviously the shell running trying to execute pyocd-flashtool does not have the

Re: Higher priority interrupts and nimble stack

2017-01-26 Thread WangJiacheng
Thanks Will, My high interrupt is event driving and the time can not be predicted, it must be served because it is related to power supply. I’m trying to make the Nimble connections are not dropped when the high interrupt event is served. If I’m lucky there will be no Nimble and Mynewt

Re: newNewt

2017-01-26 Thread Christopher Collins
Sorry, there's something else I forgot to mention. You'll need to put the boot loader on your board as well. You can do this before or after uploading blinky. newt target create boot-frdm-k64f && newt target set boot-frdm-k64f app=@apache-mynewt-core/apps/boot\

Re: newNewt

2017-01-26 Thread Christopher Collins
On Thu, Jan 26, 2017 at 09:14:02AM -0800, Christopher Collins wrote: > Plug your board in and attach a debugger if necessary, and try running > blinky on your board: > > newt run blinky-frdm-k64f That should be: newt run blinky-frdm-k64f 0 (append a zero!) Chris

Re: os_time_delay in milliseconds / microseconds

2017-01-26 Thread will sanfilippo
os_cputime_delay_ticks does not put the task to sleep; it was meant for short blocking delays. The nrf_delay_ms() function doesnt put the task to sleep either so I am not sure why you are seeing a difference between the two. > On Jan 26, 2017, at 6:03 AM, then yon wrote:

[RFC] Using BLE device address in API

2017-01-26 Thread Andrzej Kaczmarek
Hi, I think it would be nice to do one more API refactoring before 1.0 release and simplify using BLE device address in API. The current state here is similar to what we had with UUIDs in ATT code, i.e. addresses are passed as pair of address type and address value and there is no common way to

Re: os_time_delay in milliseconds / microseconds

2017-01-26 Thread then yon
Dear Jiacheng, Thanks for your reply. When i used os_cputime_delay_ticks() function it will cause my app hang and it will never goes into idle stat. I found the solution by using the nrf_delay_ms from nordic sdk. Thank you. Regards, Then Yoong Ze On 26/1/2017 7:41 PM, WangJiacheng

os_time_delay in milliseconds / microseconds

2017-01-26 Thread then yon
Dear Support, I'm working on a timing critical app; but the os_time_delay didn't gave me a precise timing. Currently the min delay i can get is more than 2ms with os_time_delay function. Somehow i notice that the clock time have up to microsecond precision; but how do i make a delay with