nRF5340 Audio application - moving button5 to gpio1 instead of gpio0

RE: nRF5340 Audio application - moving button5 to gpio1 instead of gpio0

Naeem Maroof — Tue, 25 Jun 2024 13:48:01 GMT

Hi Daniel,

Susheel is away and I will be communicating with you regarding this ticket.

I have gone through the sample, your changes, and building / programming on the DK.

I could see what you are getting. I could exactly see the same behavior and the error / logs.

However, upon searching about the issue and looking more into the code, we could see that the audio-application button-handler module indeed uses only the gpio0.

That was also the finding of this case, and probably you would need to make changes at your own if you want to use another gpio port.

Best regards,

Naeem

RE: nRF5340 Audio application - moving button5 to gpio1 instead of gpio0

d.nguyen — Tue, 18 Jun 2024 20:39:16 GMT

Hello Susheel,

My apologies for the delay. Here is the project i am using. It is basically the SDK v2.6.1 nRF5340 Audio application with a modification in the project CMake to use the included overlay. The overlay is used to re-route P1.07 that is usually used for UART to button5. and i just used a "random" gpio for the UART. I chose P1.07 specifically because it shows the issue.
Unzip and flash Headset Left.
Usually, Headset Left has a BLUE color, but you'll notice that it's Magenta. This is because RGB LED1 RED is being triggered. While I asked for P1.07 to be used for button5, it is using P0.07 instead which is RGB LED1 RED, hence the magenta instead of blue.

In the original app, when we press and release button5, the audio will mute. If you flash a gateway as well and pair them, you can test this. Then, flash with my code. You will see that button5 no longer works, so i know the overlay is working as intended. If you bring ground to P1.07 by the header, nothing will happen. But, if you bring ground to P0.07, the audio will mute at the Headset.

Please let me know if your findings are the same and what can be done to fix this.

Cheers.

devzone.nordicsemi.com/.../3173.nrf5340_5F00_audio.zip

RE: nRF5340 Audio application - moving button5 to gpio1 instead of gpio0

Susheel Nuguru — Mon, 17 Jun 2024 05:14:44 GMT

It is either the pin is reserved in the device tree or there is some conflict that we are unable to see. Can you attach your project here so that I can quickly flash and see why we see this error. Trying to use sw4 button_4 in nrf53_audio dk gives me some errors. So it is best if I use exact same setup as you are using to test this.

RE: nRF5340 Audio application - moving button5 to gpio1 instead of gpio0

d.nguyen — Fri, 14 Jun 2024 19:23:20 GMT

Hello Susheel,

Thanks for the reply.

[quote userid="6207" url="~/f/nordic-q-a/112098/nrf5340-audio-application---moving-button5-to-gpio1-instead-of-gpio0/488814"]What is the API that gives this error? [/quote]

The error originates from the ASSERT in `zephyr/include/zephyr/drivers/gpio.h` at line 1001.

	__ASSERT((cfg->port_pin_mask & (gpio_port_pins_t)BIT(pin)) != 0U,
		 "Unsupported pin");

I have no issues with gpios that are outputs on gpio1. But trying to set an input button on gpio1 with the nRF5340 Audio app is causing problems. If i switch to another pin on gpio0, its fine and works fine. Any insights?

RE: nRF5340 Audio application - moving button5 to gpio1 instead of gpio0

Susheel Nuguru — Fri, 14 Jun 2024 08:46:27 GMT

Hi,

[quote user=""]I tried doing + 32 here directly as suggested in this post, but then I get "Unsupported pin" error. [/quote]

What is the API that gives this error? Maybe you can step into that function call using a debugger and see in the code exactly where in the libraries or driver you get this error. That will give you more context on why this is happening.