Re: i2c HAL API

Ah yes. Sorry, I forgot that every transaction starts with an address. Not just after start condition. Yes, I think the API is OK as is. > On Apr 19, 2016, at 12:46 PM, p...@wrada.com wrote: > > Thanks Marko. > > Regarding the address, that is what I was originally thinking, but the > protocol

Re: i2c HAL API

Thanks Marko. Regarding the address, that is what I was originally thinking, but the protocol sends the address in every read or write, so I would have to ³store² it in the driver state. Its just another byte, but I suspect the application is already storing it anyway. If you don¹t mind the

i2c HAL API

All, Please take a look at the i2c HAL api in https://github.com/apache/incubator-mynewt-core/pull/44 I chose a simple blocking API for now to get some I2C functionality fast. Its mostly just read/write, with a few other functions. 1. probe - I found that immediately after writing this

Re: MYNEWT-262 Log module needs split in logging and reporting

Hi Vipul, On Mon, Apr 18, 2016 at 11:53:28PM -0700, Vipul Rahane wrote: > - Make changes to the log_register() function to take LOG_MODULE_X as > an argument. This module ID is present as a field in the log structure > and can be used anytime an entry is logged in the specific log. There > was a

MYNEWT-262 Log module needs split in logging and reporting

Hello, I am currently looking at: MYNEWT-262 Log module needs split in logging and reporting My understanding of the problem is as follows: - We do not have a way to re-register a log(Change handlers of modules) currently. The application