Re: Respond to a write characteristic

On Mon, May 23, 2016 at 09:22:42PM -0700, James Howarth wrote: > Hi Chris, > > Looking at the LightBlue app on my iPhone, it tells me the response is 'null'. Hmm... I am not sure. A write response does not contain any data of its own; all write responses are alike. Is it possible lightblue

Re: Respond to a write characteristic

Hi Chris, Looking at the LightBlue app on my iPhone, it tells me the response is 'null'. Cheers James > On May 23, 2016, at 9:19 PM, Christopher Collins wrote: > > Hi James, > >> On Mon, May 23, 2016 at 02:24:15PM -0700, James Howarth wrote: >> Hi, >> >> I am looking

Re: Respond to a write characteristic

Hi James, On Mon, May 23, 2016 at 02:24:15PM -0700, James Howarth wrote: > Hi, > > I am looking to issue a response to a write characteristic, and seem to be > just getting a null response. > [...] > static int > gatt_svr_p_command_cb(uint16_t conn_handle, uint16_t attr_handle, uint8_t > op, >

Respond to a write characteristic

Hi, I am looking to issue a response to a write characteristic, and seem to be just getting a null response. Is there anything I need to do special with the write data, before writing back some data. Here's my code, it's based off the peripheral tutorial from 0.80. Inside static const struct

RE: Language Reference

Nice!! I pinged a question to my Green Hills compiler friend about that abstruse for(int X=0; ... thingie. I'll let you know what I hear back. d -Original Message- From: Sterling Hughes [mailto:sterl...@apache.org] Sent: Monday, May 23, 2016 12:56 PM To:

Re: Language Reference

Hi David, Compiler options are in the compiler directory: $ more compiler/arm-none-eabi-m4/compiler.yml compiler.path.cc: arm-none-eabi-gcc compiler.path.archive: arm-none-eabi-ar compiler.path.as: arm-none-eabi-gcc -x assembler-with-cpp compiler.path.objdump: arm-none-eabi-objdump

Re: Language Reference

Apparently I’m not running with C99 options for my compiles, as the error thrown says it is only allowed with C99. I’m still trying to figure out the structure of a build so I can change build options, etc. Thanks, dg > On May 23, 2016, at 1:27 PM, David Baker wrote: >

RE: Language Reference

Do you run with C99 options for your compiles? I thought this for(int x = 0; x < 8; x++) should have been valid too. Is this a MISRA restriction? -Original Message- From: David G. Simmons [mailto:santa...@mac.com] Sent: Monday, May 23, 2016 12:14 PM To:

Re: Language Reference

Standard C stuff should be acceptable. What's not working -- note: we do compile with -Wall -Werror as the default setting. Sterling On 5/23/16 9:27 AM, David G. Simmons wrote: Another N00B question … Is there a language reference for mynewt? I’m seeing that standard C stuff is not

Language Reference

Another N00B question … Is there a language reference for mynewt? I’m seeing that standard C stuff is not acceptable, so I’m wondering if there is a language reference for how to do stuff in mynewt. specifically things like arrays, initializing arrays, for lops, etc. I’m playing around with