Setting value of GPIO Output

RE: Setting value of GPIO Output

Jared — Fri, 05 Nov 2021 10:32:00 GMT

Hi,

As of right know, the edit should be done in the specific file. As you can read from the comment, the developers are aware of this non optimal solution, and I'm confident that this will change in a future release so that the pins assignment is done based on a overlay file instead of hardcoding values.

[quote user="jbf12"]

As far as I understand, this file is part of the Nordic toolchain. This means, that each developer building and running my project would have to manually edit the file. I do not really find this optimal..

[/quote]

I totally agree with you.

regards

Jared

RE: Setting value of GPIO Output

jbf12 — Thu, 04 Nov 2021 16:41:46 GMT

Hi Jared,

I modified the file as you suggested, set the pins CPUNET_UARTE_PIN_RTS and CPUNET_UARTE_PIN_CTS to a different value and the issue is now gone 🙂

I wonder if there is any alternative to manually modifying the pins in the nrf5340_cpunet_reset.c file. Can I maybe do it from the overlay file?
As far as I understand, this file is part of the Nordic toolchain. This means, that each developer building and running my project would have to manually edit the file. I do not really find this optimal..

Best regards.

RE: Setting value of GPIO Output

Jared — Tue, 05 Oct 2021 13:50:27 GMT

Hi,

[quote user="jbf12"]

Does this make any sense? Is there any incompatibility between GPIO and Bluetooth that I am overlooking?

[/quote]

Yes it does make sense :) You're actually correct.

Activating BLE will enable the network core which will allocates the pins specified here for the its UART. atm the uart pins are hard coded, so you would have to edit the file to reconfigure the pins.

best regards

Jared

RE: Setting value of GPIO Output

jbf12 — Sun, 03 Oct 2021 15:27:29 GMT

Hi Jared,

thanks for the reply, I was busy with other tasks but finally could get back to this issue.

I managed to control various pins (P1.01, P0.11, P1.04) and even use P0.11 as SS for an SPI interface without the need to cut any solder bridge. I did a minimal project configuration. As soon as I removed the configuration option CONFIG_BT=y from my prj.conf, the pin started working.

To be more clear, pin 0.11 can be set to high/low with the following prj.conf:

#GPIO
CONFIG_GPIO=y

whereas with the following prj.conf, the pin stays always low and cannot be controlled:

#GPIO
CONFIG_GPIO=y

#Bluetooth
CONFIG_BT=y 
//same behaviour regardless of value of following config options
#CONFIG_BT_PERIPHERAL=y             
#CONFIG_BT_DEVICE_NAME="Nordic_LBS"

Does this make any sense? Is there any incompatibility between GPIO and Bluetooth that I am overlooking?

Best regards.

RE: Setting value of GPIO Output

Jared — Mon, 20 Sep 2021 10:07:09 GMT

Hi,

Looking at the schematics for the DK I see that PIN P0.11 is also connected to a solder bridge that might need to be cut for it work. Could you try P0.04?

regards

Jared

RE: Setting value of GPIO Output

jbf12 — Fri, 17 Sep 2021 14:12:06 GMT

Hello,

I also tried with pin P0.11 as well. Unfortunately the result was the same.

Regards.

RE: Setting value of GPIO Output

Jared — Fri, 17 Sep 2021 14:04:14 GMT

Hi,

Have you tried setting any other pin on the board? Could you try cutting solder bridge SB30 on the board and see if it works now?

regards

Jared