Using P0.27 as GPIO with nRF9160

RE: Using P0.27 as GPIO with nRF9160

Fabien Comte — Sun, 12 Jan 2020 09:04:47 GMT

Hello Didrik, that's perfect.

Thank you.

Didrik Rokhaug — Fri, 10 Jan 2020 12:27:50 GMT

No, each image has its own overlay file (application, SPM, MCUBoot).

You can add an overlay file for the bootloader by adding the following to your CMakeLists.txt:

set(mcuboot_DTC_OVERLAY_FILE
  ${CMAKE_CURRENT_SOURCE_DIR}/mcuboot.overlay
  )

If you want to, instead of having multiple overlay files, you can point all images to the same one.

Fabien Comte — Fri, 10 Jan 2020 11:48:04 GMT

I forced in all files and it works now.

Thank you for your help Didrik.

Fabien Comte — Fri, 10 Jan 2020 10:13:45 GMT

Not used in application but bootloader (MCUboot) does. Do my nrf9160_pca10090ns.overlay apply on bootloader ?

Didrik Rokhaug — Fri, 10 Jan 2020 10:00:20 GMT

Have you tried to search through <your build folder>/zephyr/<board_name>.dts_compiled to see if the pin is used for something else?

Fabien Comte — Fri, 10 Jan 2020 09:38:40 GMT

Hello Didrik,

But on my custom board, how to disable VCOM to use P0.27 ?

Didrik Rokhaug — Fri, 10 Jan 2020 09:11:17 GMT

Hi.

By default, P0.27 is used as the CTS pin for UART0 on pca10090.

On the DK, that pin is not routed to the header by default.

In this ticket, I explain how to change the pin routing, and provide an application that routes the pins used by UART0 to the headers.

Can you try to flash the application provided there to the nRF52840 board controller on the DK, and see if that helps?

You might also have to assign a different pin to UART0.

Best regards,

Didrik