Re: [RFC v2] nimble/l2cap: Add LE L2CAP COC API

HI Chris, On 18 January 2017 at 05:39, Christopher Collins wrote: > Hi Łukasz, > > I like it. I just have one comment: > > > > +struct ble_l2cap_chan *ble_l2cap_connect(uint16_t conn_handle, > uint16_t psm, > > > + uint16_t mtu, > > > +

Re: Firmware update with MyNewt

Youll find another thread (now poorly) titled "Single Bank firmware update (ie nordic vendor style dfu)" where Im getting a bunch of support on firmware updating on the nordic 16kbram target specifically. Split image is probably a really good link to read https://mynewt.apache.org/latest/os/module

Re: Firmware update with MyNewt

Then, Have you taken a look at https://mynewt.apache.org/latest/os/modules/bootloader/bootloader/ ? thanks, aditi > On Jan 17, 2017, at 10:00 PM, then yon wrote: > > Dear Support, > > I wish to workout with firmware update

Firmware update with MyNewt

Dear Support, I wish to workout with firmware update in mynewt platform. If i understand correctly the bootloader should able to do this, but i cant found any documentation on this. While i looking into bootloader coding, can you help to give me a hint/guide to start with? Appreciate on yo

IDE used for Mynewt Development

Hi, Before moving to mynewt platform, I worked with Nordic SDK using Eclipse IDE and uses CDT Parser to parse the makefile output to display useful information in Eclipse. And was able to use the GDB to perform debugging in Eclipse. (https://devzone.nordicsemi.com/tutorials/7/) Tutorials - No

Re: [RFC v2] nimble/l2cap: Add LE L2CAP COC API

Hi Łukasz, I like it. I just have one comment: > > +struct ble_l2cap_chan *ble_l2cap_connect(uint16_t conn_handle, uint16_t > > psm, > > + uint16_t mtu, > > + struct os_mbuf *sdu_rx, > > +

Re: Single Bank firmware update (ie nordic vendor style dfu)

Used your settings to be sure were the same (cool override in the target) JLinkExe -if SWD -device nRF51822 -speed 1000 erase all q newt size shows were under 112238 110532 1276 10664 122472 1de68 /Users/jacobrosenthal/Downloads/mynewt-hr-observer/bin/targets/split-nrf51dk/loader/apps/bleprp

Re: Single Bank firmware update (ie nordic vendor style dfu)

On Tue, Jan 17, 2017 at 05:47:49PM -0700, Jacob Rosenthal wrote: > Thanks Chris! Tried some more with the new upstreamed code but a few > more issues... > > > Still had to add the serial transport to bleprph, not sure if you left > that out of there on purpose for code size.. - > mgmt/newtmgr/t

Re: sys/stats and sys/log

Ok, (mostly) done. I named the full implementation and stub similarly to console. I.e. sys/log is now under sys/log/full. And stats sys/stats/full. Unfortunate side-effect of this is that the app dependencies will have to adjusted. Previously, app might not have even needed to explicitly list sys

Re: Single Bank firmware update (ie nordic vendor style dfu)

Thanks Chris! Tried some more with the new upstreamed code but a few more issues... Still had to add the serial transport to bleprph, not sure if you left that out of there on purpose for code size.. - mgmt/newtmgr/transport/nmgr_shell newt run split-nrf51dk 0 and it responds to newtmgr se

Re: sys/stats and sys/log

I think the stub approach is fine as well. > On Jan 17, 2017, at 1:43 PM, Kevin Townsend wrote: > > I don't have any issues with the stub approach myself, and it's easy to > switch back and forth (no more work than changing syscfg.yml) > > > On 17/01/17 22:07, marko kiiskila wrote: >> Hi, >>

Re: sys/stats and sys/log

I don't have any issues with the stub approach myself, and it's easy to switch back and forth (no more work than changing syscfg.yml) On 17/01/17 22:07, marko kiiskila wrote: Hi, at the moment it is not very easy to get rid of all code related to logging and/or statistics. I ran across this w

sys/stats and sys/log

Hi, at the moment it is not very easy to get rid of all code related to logging and/or statistics. I ran across this when trying to see how small I can make an image while keeping BLE and OIC. Therefore, I was going to create stub packages for sys/stats and sys/log. Then, within the app you can

Re: Bluetooth specification question after seeing Android 7.1.1 disconnect

It was not a phone I was using. I think it was a Nexus 6P. And yeah, I shouldnt’t have said “Android” when I was mentioning the bug. I have used other Android phones and they dont have this issue. Well, I have used one other Android Phone (I think it was a Nexus 5x) and there was no issue. Rega

Re: SPI/I2C on Arduino Primo

You can look at the LSM303DLHC driver I implemented here as a starting point for I2C ... that should cover the basics like the I2C transactions, which is 1/2 the work already: https://github.com/apache/incubator-mynewt-core/tree/sensors_branch/hw/drivers/sensors/lsm303dlhc You have to look in

SPI/I2C on Arduino Primo

Devs, Has anyone used the SPI or I2C on Arduino Primo? Anyone have any sample code? Kevin Townsend wrote the Adafruit_BME280_Library in C++ and this is the part I'm working with right now, so I do have a starting point from that end, but from the MyNewt end? TIA, dg -- David G. Simmons (919)

Re: [RFC v2] nimble/l2cap: Add LE L2CAP COC API

Hi, On 17 January 2017 at 14:28, Łukasz Rymanowski < lukasz.rymanow...@codecoup.pl> wrote: > This patch adds API for LE Connection Oriented Channels. > Note that implementation is hided behind BLE_L2CAP_COC_MAX_NUM flag > which defines maximum number of supported dynamic channels > > Overview: >

[RFC v2] nimble/l2cap: Add LE L2CAP COC API

This patch adds API for LE Connection Oriented Channels. Note that implementation is hided behind BLE_L2CAP_COC_MAX_NUM flag which defines maximum number of supported dynamic channels Overview: Idea is that credits are hidden from the user and controlled by the stack. User creates its own memory p

Re: [RFC] Refactor UUID handling in Nimble

Hi Chris, I squashed code into a single commit (so bisect is not broken) and created a pull request: https://github.com/apache/incubator-mynewt-core/pull/160 If there are comments about the code I think we can continue there. BR, Andrzej On Fri, Jan 13, 2017 at 11:13 PM, Christopher Collins w

Re: Bluetooth specification question after seeing Android 7.1.1 disconnect

Hi Will, On Tue, Jan 17, 2017 at 5:48 AM, will sanfilippo wrote: > Hello: > > Was wondering if there were any folks out there that could comment on > something regarding a disconnect issue with an Android Phone running 7.1.1 > and our bluetooth stack (the controller). > Which phone do you use?