Custom 128 UUID and Service Data = unknown error

RE: Custom 128 UUID and Service Data = unknown error

zeusminos — Thu, 09 Oct 2014 13:11:16 GMT

Thanks for your help Petter :-). You guys ROCK

RE: Custom 128 UUID and Service Data = unknown error

Petter Myhre — Thu, 09 Oct 2014 12:56:51 GMT

I experience the same thing. The advertisment packet becomes too big, by changing it you increase it from 30 to 33 bytes. I used the debugger and checked the len_advdata in

sd_ble_gap_adv_data_set(p_encoded_advdata, len_advdata, p_encoded_srdata, len_srdata);

If you have more questions, please ask them separately, and link to this one if it's relevant.

RE: Custom 128 UUID and Service Data = unknown error

zeusminos — Thu, 09 Oct 2014 12:42:46 GMT

Peter,

Seems like the root of my headaches was Luna. I switch to Kepler and the latest GNU ARM toolchanis + latest Jlink (firmware/software) and your code ble_app_template_128UUID.rar seems to work. I can see the 128 UUID, but something kind of strange is that as soon as I switch from:

advdata.name_type               = BLE_ADVDATA_NO_NAME;

To:

advdata.name_type               = BLE_ADVDATA_SHORT_NAME;

advdata.name_type               = BLE_ADVDATA_FULL_NAME;

The system does not broadcast anymore. I am using a 1 character string under device name

#define DEVICE_NAME                     "N"

Any idea why?

P.S I have not debug this issue yet.

Thanks for your help.

Cheers Dan

RE: Custom 128 UUID and Service Data = unknown error

zeusminos — Thu, 09 Oct 2014 11:18:34 GMT

Hi Petter,

Well that narrows my search to: eclipse/jlink software/firmware.

Thanks,

I'll keep you posted with the latest news.

RE: Custom 128 UUID and Service Data = unknown error

Petter Myhre — Thu, 09 Oct 2014 06:54:48 GMT

I'm using Keil, Windows 7, J-Link V4.86. But that doesn't affect the hex file, try it.

RE: Custom 128 UUID and Service Data = unknown error

zeusminos — Thu, 09 Oct 2014 06:50:36 GMT

Hi Petter,

I am going to use Kepler 4.3 SR2 instead with the latest GNU toolchains.

Could you please let me know the versions that you have in your system:

Segger jlink (PC and firmware version)
GNU ARM toolchain version
Eclipse version
OS version

Are you using the GNU ARM Eclipse plugin if yes what version?

Thanks again for your help.

Cheers

RE: Custom 128 UUID and Service Data = unknown error

Petter Myhre — Tue, 07 Oct 2014 13:25:34 GMT

I suspect your advertisement packet is simply too big. You should be able to find a more meaningful error code if you turn off Optimization (set it to Level 0) under C/C++ tab in Options for target.

Is the device advertising (no error) if you set the name type to it BLE_ADVDATA_NO_NAME? Obviously you can't identify your device with the name anymore, use the address or your UUID instead.

I tested this quickly with an example; you can find my dirty code below. I used SDK 6.1.0 and S110 7.0.0.

ble_app_template_128UUID.rar

Edit: I have tested your hex files.

ble_app_template_128UUID_s110_xxaa.hex works fine.

ble_app_lbs_s110_xxaa.hex doesn't work.

Are you sure err_code = sd_ble_gap_ppcp_set(&gap_conn_params); gives an error? I find that very strange.

Could you just do the following in nRFgo Studio:

Erase all
Click the Program SoftDevice tab and select s110_nrf51822_7.0.0_softdevice.hex
Click the Program Application tab and select ble_app_template_128UUID_s110_xxaa.hex