nrf52832 cannot control a PWM(servo motor) via Bluetooth

RE: nrf52832 cannot control a PWM(servo motor) via Bluetooth

Kautham — Wed, 06 Jun 2018 07:29:51 GMT

Thanks for your tip buddy. I will try out the UART logging as you suggest. If it isn't working then i have to do it with the leds. I will try it out and let you know. Again thanks a lot. It is a drag to not own a J-Link or any of nordics DK's.

RE: nrf52832 cannot control a PWM(servo motor) via Bluetooth

Edvin — Wed, 06 Jun 2018 07:08:23 GMT

Ok. I understand. Then I suggest that you try to get some logging information via UART, since RTT is not available, and debugging is not an option.

Actually, this makes it a bit hard to develop software on your device. Do you have access to any of the nRF DKs? Either nRF51DK or nRF52DK? If not, then you have to get the logging information from the UART, but you would need an external UART->USB device. Try to google "uart to usb".

If you don't have any of these, I guess you can try to toggle a led after every before APP_ERROR_CHECK(err_code) if err_code != 0 (NRF_SUCCESS)

But you would also have to stop your device after these, because an APP_ERROR_CHECK(err_code) with an err_code != 0 will reset the device. So maybe you can go into some infinite loop, instead of APP_ERROR_CHECK().

You will have to do this once for every APP_ERROR_CHECK() you want to check. Change the code, compile, upload and see.

I am sorry. It is a bit hard to do app development if you can't see what is actually going on in the software.

Best regards,

Edvin

RE: nrf52832 cannot control a PWM(servo motor) via Bluetooth

Kautham — Tue, 05 Jun 2018 13:50:55 GMT

Sorry for the delayed information I don't own a J-Link device. I use Bumpy to load my code. Also for all the ble examples i have to merge the s132_softdevice.hex and the app.hex files using the nRF5x-command-line-tools mergehex command and then load this merged hex file. The problem is this merged hex file does not contain any debug symbols so i cannot debug it at the runtime and also no log comes to the GDB console. Hence i am stuck in this debugging. So could you please point me if i am missing anything or any alternative.

RE: nrf52832 cannot control a PWM(servo motor) via Bluetooth

Edvin — Tue, 05 Jun 2018 12:46:56 GMT

Ok. So it sounds like the application is stopping somewhere. Try out the debugging tip ,or RTT log, because if you are able to program the chip, then it uses the same wires for the RTT log. Just define RTT_LOG_BACKEND_ENABLE 1 and NRF_LOG_ENABLE 1 in SDK config, open JLINK RTT Viewer and run the application.

The log module in SDK15 should print all relevant debug info.

Best regards,

Edvin

RE: nrf52832 cannot control a PWM(servo motor) via Bluetooth

Kautham — Tue, 05 Jun 2018 11:53:55 GMT

Thanks for your time. Sorry if my texts "the program crashes at run time" were misleading. What i meant is, the ble_blinky has a flow that if it is not connected or disconnected from the device(iOS app) the red LED would light up and the BLE would advertise again. But after Running PWM, even if i disconnect from my iOS app the BLE won't advertise and no red LED. Also after the sending the command (case 4 and 5) for the PWM, the commands for the external LEDs(case 0 and 1) and buzzer(case 2 and 3) doesn't toggles them.I have to reset the kit with the reset button on the kit to start the program from the beginning.

But thanks for the debugging tip. I will try them and reply to you.

RE: nrf52832 cannot control a PWM(servo motor) via Bluetooth

Edvin — Tue, 05 Jun 2018 09:46:31 GMT

Hello,

When you say that "the program crashes at run time", can you please explain what happens?

I assume that it is one of the calls for APP_ERROR_CHECK(err_code) that receives an err_code != 0 (NRF_SUCCESS). Have you checked your log? I am not familiar with the hackable kit, but you can either enable the UART logging backend, or the RTT logging backend. I assume that you program the kit via SWDIO pin. This means that you can use the RTT backend, which will send the logging information via this pin. You can view the log in JLINK RTT Viewer.

You can also enable the UART log backend, and use one of the pins as the UART TX pin. All of these settings are set in sdk_config.h.

Alternatively, you can debug to find out which call that returned the err_code != 0. add the define DEBUG in your preprocessor defines (and you probably need to turn off optimization as well. Set it to -O0). Then set a breakpoint on line 91 in app_error_weak.c. this is where the error is sent to the log, so you can see here what id, the file name and line code where the error occured.

Best regards,

Edvin