Two Button function coverage problem

RE: Two Button function coverage problem

Naeem Maroof — Wed, 26 Jun 2024 11:44:37 GMT

Hello,

Apologies for the delayed response.

Is there any update at your end?

[quote user="cheiron"]I tried copying a new "BLE central UART" example without making any modifications, and after flashing it , I couldn't see the Bluetooth using nRF Connect[/quote]

Please follow the instruction given on the Testing section of the sample. You would require a peripheral (step 6) to connect with.

RE: Two Button function coverage problem

ITEK — Wed, 12 Jun 2024 03:25:30 GMT

I didn't make any changes to the BLE-related subroutines, except for turning off Uarte in the original example program. After receiving your message, I tried copying a new "BLE central UART" example without making any modifications, and after flashing it , I couldn't see the Bluetooth using nRF Connect.

Could you please test it for me to see if there's an issue?

Here's the link to the example program: [insert link]

RE: Two Button function coverage problem

Naeem Maroof — Tue, 11 Jun 2024 10:29:45 GMT

Hi,

I downloaded the code from your repo, and button1 is working before and after the connection.

However, when I send those characters (80 03...) through ble, it results into hard-fault

it is caused in line 857 (uart_tx)

RE: Two Button function coverage problem

ITEK — Thu, 06 Jun 2024 08:35:09 GMT

I've tried a method that seems to work in testing, but I still have some concerns and would like to confirm a few things before proceeding.

First, I'd like to ask if your data is being sent and received via Bluetooth or through UART or UARTE. In the example program, the Bluetooth functionality hasn't been modified, nor does it include the issue demonstration code.

Here's the approach I took: I combined the button code from the "Button Sample" and "BLE LED Button Service" examples.

1.After resetting the DK, the "CapReadyPinInit" function initializes the button, and I test it to ensure it works. This part of the code comes from the Button Sample.

2.When I send "80 03 02 35 23 81" via UARTE, it directly initializes the buttons from the "BLE LED Button Service" example.

err = dk_buttons_init(button_changed);
if (err) {
    LOG_ERR("Cannot init buttons (err: %d)", err);
}

The button actions are handled in the "button_changed" function. This setup meets the project's requirements during testing.

3. When I send "80 03 02 35 23 81" via UARTE again, I first disable the buttons with:

err = dk_buttons_init(NULL);
if (err) {
    LOG_ERR("Cannot init buttons (err: %d)", err);
}

4. Then, I reinitialize "CapReadyPinInit". This approach works in testing,

but I have some doubts. Although both parts come from example programs, could there be stability issues when combining them? Or is it likely stable since both are from example programs?

And I've updated the code on GitHub. Sorry for the inconvenience. Could you please take another look at it? Thanks!

RE: Two Button function coverage problem

ITEK — Mon, 03 Jun 2024 03:33:45 GMT

I might not have been very clear in my previous description. Here's the ideal behavior I'm aiming for:

1.When I reset the DK, LED1 starts blinking, indicating that the chip is working properly.
2.Button1 should toggle LED4, while Button2 does nothing.
When I connect to the device and send the HEX data "80 03 02 35 23 81", 3.Button1 should still control LED4, and now Button2 should toggle LED3.
4.Sending the same HEX data "80 03 02 35 23 81" again should revert to Button1 controlling LED4, and Button2 doing nothing.
5This should cycle between steps 2 and 4.

However, during my testing, here's what I observed:

1.When I reset the DK, LED1 starts blinking, indicating that the chip is working properly.
2.Button1 toggles LED4, while Button2 does nothing.
When I connect to the device and send the HEX data "80 03 02 35 23 81", 3.Button1 stops working, and Button2 toggles LED3.
4.Sending the HEX data "80 03 02 35 23 81" again results in both Button1 and Button2 not working.
5.Sending the HEX data "80 03 02 35 23 81" again makes Button2 toggle LED3, but Button1 remains non-functional.
6.Sending the HEX data "80 03 02 35 23 81" again returns to step 4, cycling through steps 4 to 6.

This process does not cause the device to reset, and I couldn't reproduce the reset issue after multiple attempts.

To check the code for the two buttons, search for "deButtonFunction" within the #if #endif section (lines 76 to 174). You'll notice that CapReadyPinInit (lines 97 to 124) and RxButtonEn (lines 147 to 174) have almost identical content. This code is derived from the Button Sample example. Button actions can be seen in CapRdyButtonInterrupt (lines 83 to 96) and RxButtonInterrupt (lines 83 to 96). UART functionality is within the #if deMCU_URFunc section (lines 178 to 348), with data handling in lines 263 to 303 and actions in lines 178 to 221. The reset might be caused here, though I couldn't reproduce it to confirm.

If the issue is with button debugging, I want to use the declarations and debugging from the "BLE LED Button service" example. How can I disable the Button functionality? Which parts should I modify or disable, given that my project needs to switch between Rx and Button modes on the same pin?

By the way, I'm using the nRF52840-DK board for testing.

Please assist with this. Thank you.

RE: Two Button function coverage problem

Naeem Maroof — Tue, 28 May 2024 14:53:53 GMT

Hi,

I have tried to go through your code, but I cannot review your whole code, it is not a short code.

Also, when I flashed, I see different behavior than what you have described:

When I reset the DK,

LED4 is ON

LED1 starts blinking

if I press Button1 then LED4 toggles

(meaning Button1 is working and in the callback we are toggling LED4)

if I press Button2 in this state, it does nothing,

next,

when I connect with the device, LED2 turns ON,

I can still use BUTTON1 to toggle LED4

Button2 still does nothing,

next,

when I send that data "80 03 02 35 23 81" through RX characteristic, the device resets.

You should probably debug your code by seeing how things go on.

Also, maybe your Button2 is not configured properly.

Can you first just test your buttons. Can you just show the sample code for buttons that produce that issue?

RE: Two Button function coverage problem

ITEK — Fri, 24 May 2024 01:00:07 GMT

Thank you for your response. The issue with the chip reset has been resolved. Unfortunately, when testing the required functionality with version 2.6.1, I’m still encountering the same problems as with 2.5.2.

Using the nrf52840 development board, after powering it on and pressing Button1, LED4 lights up. After sending the command 80 03 02 35 23 81, LED2 lights up, and when Button2 is pressed, LED3 lights up. However, Button1 stops working and doesn’t respond. In the project, both buttons are supposed to work simultaneously.

Could you please assist with this? I’ve updated and uploaded the code.

Here’s the link:https://github.com/ItekRD/TwoButtonProblem

RE: Two Button function coverage problem

Naeem Maroof — Tue, 21 May 2024 13:32:59 GMT

Hi,

Apologies for the delayed response.

The issue is coming from configure_gpio() function that calls dk_buttons_init()

This function would initialize buttons as on the DK.

As you can see that on the DK (nrf52840dk), pins 11, 12, 24 and 25 are used for the four buttons.

When you are calling the configure_gpio() function, three of the DK buttons are initialized while initializing the 4th one which you have defined gives error; of course this is not as on the DK, this is your definition.

Error is also "Unsupported pin" that is pin 8.

Hope if provides you direction in your debugging.

Regards,

Naeem

RE: Two Button function coverage problem

ITEK — Fri, 17 May 2024 05:04:09 GMT

it's been a while, and I haven't received a reply yet. Can you give me an update on the current status? Is there any additional information or materials you need from me?

RE: Two Button function coverage problem

ITEK — Tue, 07 May 2024 05:12:44 GMT

Hi there! Sorry for the delayed response; work's been keeping me busy. After seeing your reply, I made several attempts to create a new project and use NCS 2.5.2 to present the issues I mentioned. However, after selecting "create a new application" -> "Copy a sample" -> "BLE UART service," the project I created couldn't include three files: "uart_async_adapter.h," "zephyr/usb/usb_device.h," and "<soc.h>." I tried to troubleshoot this on my own, but the problem persisted.

So, I decided to upgrade to NCS version 2.6.1 to see if I could resolve the issues. However, I encountered a new problem. After burning the code into the MCU, it kept resetting itself continuously, and I received a UR message:

1: *** Booting nRF Connect SDK 3758bcbfa5cd ***\r\n

ASSERTION FAIL [(cfg->port_pin_mask & (gpio_port_pins_t)(1UL << (pin))) != 0U] @ WEST_TOPDIR/zephyr/include/zephyr/drivers/gpio.h:1001\r\n

Unsupported pin\r\n [16:17:54.2484378]

Since I need to switch between Rx and Button modes to complete the project, I'm in need of assistance.

Here's the complete project for NCS 2.6.1. If you still need the project for NCS 2.5.2, just let me know.

RE: Two Button function coverage problem

Naeem Maroof — Mon, 15 Apr 2024 11:24:25 GMT

Hello,

Could it be due to some value you assign in the CapSwReadyPin(), or due to initialization of global variables? I am not sure.

Can you provide a minimally complete project that I can compile in NCS 2.5.2 and flash on the DK and test?

RE: Two Button function coverage problem

Hieu — Fri, 12 Apr 2024 13:37:50 GMT

Hello ITEK,

One of our engineers will look into this and follow up with you soon.