Getting scanned device names: p_typedata includes junk/previous data in adv_report_parse

RE: Getting scanned device names: p_typedata includes junk/previous data in adv_report_parse

Stian Røed Hafskjold — Mon, 03 Nov 2014 10:38:25 GMT

Please click the "accept answer" button if you feel your question has been answered.

RE: Getting scanned device names: p_typedata includes junk/previous data in adv_report_parse

Carson — Mon, 03 Nov 2014 02:18:18 GMT

Vebjornr!!! Your awesome, worked like a charm thank you so much, I'll keep the null-char advice in mind from now own thank you!!

RE: Getting scanned device names: p_typedata includes junk/previous data in adv_report_parse

Vebjørn — Sun, 02 Nov 2014 21:50:12 GMT

p_typedata->p_data only points to where the string starts within p_advdata->p_data, and it isn't null-terminated. Naturally, when you try to print it with simple_uart_putstring it just keeps printing random characters from memory until it reaches a null-char, or MAX-size. Try this:

uint8_t * result = p_typedata->p_data;
result[p_typedata->data_len] = 0; // add a null-char
simple_uart_putstring (result);

or this, if you dont want to actually change the p_data:

uint8_t result[BLE_GAP_DEVNAME_MAX_LEN] = {0}; // array big enough to fit your device name
memcpy(result, p_typedata->p_data, p_typedata->data_len);
simple_uart_putstring (result);