BLE accelerometer

RE: BLE accelerometer

Karthiknk — Wed, 30 Dec 2020 10:30:32 GMT

Im happy to say that the project is complete. Thank you for your support. You may close this ticked.

RE: BLE accelerometer

Karthiknk — Wed, 23 Dec 2020 12:16:59 GMT

Hi, I found the problem. The device is advertising, When I connect to the nRF Connect application, I can not see my service, the status says disconnected.

This is the timer event handler I use in the program

static void timer_timeout_handler(void * p_context)
{
// Acquire accelerometer data
MPU6050_ReadAcc(AccValue); // accelerometer read
acc[0] = AccValue[0];
acc[1] = AccValue[1];
acc[2] = AccValue[2];

characteristic_accel_update(&m_our_service, acc);
}

If I line comment my accelerometer read function, The app works fine, I can see the service and its characters at the nrf connect(without accel. values). How can I include my accelerometer read function into my program without crashing the app?

RE: BLE accelerometer

Karthiknk — Mon, 21 Dec 2020 22:23:30 GMT

Hi Jorgen. While setting up sniffer, programming my nRF52 DK, I accidentally put my DK in bootloader mode. How can I bring it back to normal? I can not see the device in nrf connect.

RE: BLE accelerometer

Jørgen Holmefjord — Mon, 21 Dec 2020 19:08:34 GMT

[quote user="Karthiknk"]

Are you checking error codes from all softdevice APIs you are calling in your application?

Yes I guess, I didn't change anything in the app_template example regarding error check.

[/quote]

I was thinking more about the code that you added from the tutorial, that you have remembered to store the return code from all function calls, and pass this along to APP_ERROR_CHECK() macro.

[quote user="Karthiknk"]

And in nRF connect log. I get error 133 (0x85): GATT ERROR

didn't this log information helps in any way?

[/quote]

Unfortunately, this is a very generic error code. It can be caused by a lot of things. Can you post the full log output from nRF Connect? A sniffer trace will also tell if the peripheral did not respond to packets, etc.

RE: BLE accelerometer

Karthiknk — Mon, 21 Dec 2020 18:51:22 GMT

Are you checking error codes from all softdevice APIs you are calling in your application?

Yes I guess, I didn't change anything in the app_template example regarding error check.

And in nRF connect log. I get error 133 (0x85): GATT ERROR

didn't this log information helps in any way?

RE: BLE accelerometer

Jørgen Holmefjord — Mon, 21 Dec 2020 18:40:58 GMT

Are you checking error codes from all softdevice APIs you are calling in your application?

If you could provide a sniffer trace of the communication between the two devices, that could also help determining where the issue occurs.

RE: BLE accelerometer

Karthiknk — Mon, 21 Dec 2020 18:31:07 GMT

This is what I see in the debugger terminal.

<info> app_timer: RTC: initialized.
<debug> nrf_sdh: State request: 0x00000000
<debug> nrf_sdh: Notify observer 0x0003095C => ready
<debug> nrf_sdh: State change: 0x00000000
<debug> nrf_sdh: State change: 0x00000001
<debug> nrf_sdh_ble: RAM starts at 0x20002260
<info> app: Template example started.
<info> app: Fast advertising.

And in nRF connect log. I get error 133 (0x85): GATT ERROR

RE: BLE accelerometer

Jørgen Holmefjord — Mon, 21 Dec 2020 18:27:01 GMT

Try dragging the empty client window towards the right side of the screen, that should reveal the log terminal. It may be that something crashes on the peripheral side during connection, leading to a reset or something. Does the log on the peripheral side not give any output regarding what happens?

RE: BLE accelerometer

Karthiknk — Mon, 21 Dec 2020 18:23:10 GMT

The device is shown in scanner. I give connect. It opens up Nordic_template. I can not see anything in the client.

RE: BLE accelerometer

Jørgen Holmefjord — Mon, 21 Dec 2020 18:17:52 GMT

"Not bonded" and "not connected" are two different things. Do the phone try to connect, but fails? Are you seeing anything in the logs of nRF Connect application, or the peripheral device that indicates what goes wrong?

RE: BLE accelerometer

Karthiknk — Mon, 21 Dec 2020 17:57:42 GMT

I fixed the RAM issue. The device is advertising. But it is not connecting. In nRF Connect app, I see not bonded. How can I fix it?

RE: BLE accelerometer

Karthiknk — Sat, 19 Dec 2020 13:48:03 GMT

I made the Debug terminal to work. I changed the RAM start address as recommended. Still, I get Fatal error. unsigned int error_code=0x00000004. This is what I get in the Debug Terminal.

RE: BLE accelerometer

Jørgen Holmefjord — Fri, 18 Dec 2020 18:29:59 GMT

You need to adjust the size to match the size of the RAM available in the chip you are using. If you increase the RAM start address, you need to decrease the size accordingly.

RE: BLE accelerometer

Karthiknk — Fri, 18 Dec 2020 18:10:10 GMT

Thank you, sure I will go through the material. I followed this tutorial about the adjustment of flash and RAM memory. When I change to debugger recommended RAM start, then the RAM_START + RAM_SIZE is larger than RAM_PH_START + RAM_PH_SIZE.

What should I do now? I'm stuck.

RE: BLE accelerometer

Jørgen Holmefjord — Fri, 18 Dec 2020 17:04:36 GMT

Hi,

Try increasing NRF_SDH_BLE_VS_UUID_COUNT in your sdk_config.h file. Regarding logging, have you enabled the logger module through NRF_LOG_ENABLED config in your sdk_config.h file?

You also have to call the init macro in main(): NRF_LOG_INIT(NULL);, and you may have to call NRF_LOG_DEFAULT_BACKENDS_INIT(). More details can be found in the Logger module documentation.

Best regards,
Jørgen

RE: BLE accelerometer

Karthiknk — Thu, 17 Dec 2020 22:29:03 GMT

Hi, Sorry for the late update. I followed this tutorial and created a program. It compiles without error. But the device is not advertising. In the debug, I found this error, eror_code=0x00000004

I saw it as a memory error from this video. I enabled the nrf_log_enabled and nrf_log_backed_rtt to see the debug terminal. But I can't see anything in the terminal. How can I fix this issue? If you want additional information, please let me know.

RE: BLE accelerometer

Jørgen Holmefjord — Tue, 15 Dec 2020 10:58:09 GMT

Do you get any error codes when calling ble_nus_data_send? Also, make sure that twim_handler does not run at a interrupt priority higher than 4, as this will prevent you from calling softdevice APIs.

RE: BLE accelerometer

Karthiknk — Mon, 14 Dec 2020 16:43:41 GMT

Thank you for your information. I fixed the driver issue. As per your advice, I'm trying to use app_ble_uart to send my TWI sensor data. Can I just use the NUS function to send the data or should I program the ble services and events to function properly? Because I called the function ble_nus_data_send into my sensor read and it didn't work.

void twim_handler(nrfx_twim_evt_t const * p_event, void * p_context)
{

static uint8_t data_array[BLE_NUS_MAX_DATA_LEN];
static uint8_t index = 0;
uint32_t err_code;

switch (p_event->type)
{
case NRFX_TWIM_EVT_DONE:
UNUSED_VARIABLE(MPU6050_ReadAcc( &data_array[index]));
index++;

if ((data_array[index - 1] == '\n') ||
(data_array[index - 1] == '\r') ||
(index >= m_ble_nus_max_data_len))
{
if (index > 1)
{
NRF_LOG_DEBUG("Ready to send data over BLE NUS");
NRF_LOG_HEXDUMP_DEBUG(data_array, index);

do
{
uint16_t length = (uint16_t)index;
err_code = ble_nus_data_send(&m_nus, data_array, &length, m_conn_handle);
if ((err_code != NRF_ERROR_INVALID_STATE) &&
(err_code != NRF_ERROR_RESOURCES) &&
(err_code != NRF_ERROR_NOT_FOUND))
{
APP_ERROR_CHECK(err_code);
}
} while (err_code == NRF_ERROR_RESOURCES);
}

index = 0;
}
break;

m_xfer_done = true;
break;
default:
break;
}
}

RE: BLE accelerometer

Jørgen Holmefjord — Mon, 14 Dec 2020 16:33:26 GMT

I assume you mean NRFX_TWIM_XFER_DESC_TX? These are also present in the legacy driver: Advanced usage.

There is not much advantage of migrating to the NRFX driver, most of it is just redefinitions of the old API, both APIs use the NRFX driver in the bottom layer anyway.

RE: BLE accelerometer

Karthiknk — Sat, 12 Dec 2020 19:18:01 GMT

Hi,

I tried the BLE UART example to send my TWI sensor data. I'm having trouble with sdk_config. In my TWI program, im using the nrf_drv_twi legacy driver. I think it is creating some compatibility problems. So as per the article in devzone, I'm migrating from nrf_drv_twi to nrfx_twim driver. I have a doubt in it. What is this NRFX_TWIM_DESC_TX macro? I don't understand what is this descriptor means. I searched for other functions in nrfx_twim, but the functions are not advised to use. Please help me to understand this, I'm a t lost here. What are the functions or macros I need to migrate to this new nrfx_twim driver? For your information, I'm reading 3axis accelerometer LIS3DH using I2C communication. Please let me know my approach is correct.

RE: BLE accelerometer

Karthiknk — Wed, 09 Dec 2020 14:43:20 GMT

Thank you for the quick response. I will go through your materials.

RE: BLE accelerometer

Jørgen Holmefjord — Wed, 09 Dec 2020 13:44:49 GMT

Hi,

It is possible to send the values as a string using Nordic UART Service (NUS). There is an example available in the SDK: UART/Serial Port Emulation over BLE

If you want to create your own custom service for sending accelerometer data, please have a look at the BLE tutorials. These should be most useful:

Best regards,
Jørgen