Adding accelerometer value to own service

RE: Adding accelerometer value to own service

Karthiknk — Wed, 30 Dec 2020 10:31:54 GMT

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

RE: Adding accelerometer value to own service

Karthiknk — Tue, 29 Dec 2020 11:53:36 GMT

If I enable the accelerometer read function, I can not connect the device with the nrf connect app. The device stays in advertising mode. The program does not enter the timer_timout_handler where the accelerometer function is called.

I think my twi configuration is interrupting softdevice. I changed the interrupt priority from high to low and medium. Nothing works. Do you have any suggestions? I can share my code if necessary.

RE: Adding accelerometer value to own service

Daniel Chisholm — Mon, 28 Dec 2020 19:45:27 GMT

With a debugger, set a breakpoint after your call to MPU6050_ReadAcc() and see if it is hit (or not; if you are in "DEBUG" mode the program will enter a loop).

Or, put an NRF_LOG_INFO() trace message before and after your call to MPU6050_ReadAcc(), to confirm your program flow... does your routine return, or do you fall into a crash-loop?

My "GPIO line" suggestion is moot, since you can run a debugger and see log outputs (if you couldn't, I was suggesting that you could control a GPIO pin, and watch it with an oscilloscope or logic analyzer, to determine whether or not your code was hit, and if there was a reasonably short or unreasonably long time taken to run your accelerometer reading routine)

RE: Adding accelerometer value to own service

Karthiknk — Mon, 28 Dec 2020 13:37:06 GMT

I can run a debugger. RTT on debugger terminal shows this,

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

Nothing after this.

[quote userid="92730" url="~/f/nordic-q-a/69847/adding-accelerometer-value-to-own-service/286688#286688"]If you can't run a debugger, could you raise a GPIO line before calling it, and lower that line upon return?[/quote]

I don't understand what you are trying to say. Can you please explain a little more elaborately?

RE: Adding accelerometer value to own service

Daniel Chisholm — Mon, 28 Dec 2020 11:19:46 GMT

If MPU6050_ReadAcc(AccValue) crashes, or if it takes too much time to perform, that could explain why your device disconnects.

If you can't run a debugger, could you raise a GPIO line before calling it, and lower that line upon return?

RE: Adding accelerometer value to own service

Karthiknk — Mon, 28 Dec 2020 10:18:33 GMT

I'm using SDK 17.0.2. I'm trying to send accelerometer data through BLE. I followed BLE characteristics tutorial to develop my project. The code works fine, the problem occurs when I include the accelerometer read function in the code.To verify the problem, instead of sending accelerometer data, I sent dummy data. The data received without a problem. When I include my sensor read function into the code, the problem occurs. I have included the sniffer packets below, please have a look at them.

devzone.nordicsemi.com/.../sniffer1.pcapng

RE: Adding accelerometer value to own service

Øyvind — Mon, 28 Dec 2020 10:03:38 GMT

Hello,

The technical support team is currently low staffed due to Christmas holidays and the response time is therefor much longer than usual.

Please provide more information on what SDK you are using, and what application you are running.

Thank you!

Kind regards,
Øyvind