This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Making UART0 or UART1 externally accessible for serial_lte_modem

I am working on a custom board for the nRF9160 and currently have a DK and a thingy.

I need to make a serial interface available on the DK, thingy and a custom board I am working on for serial AT commands. I would prefer for it to be UART1 so I can still use the USB interface.

A few weird things I have run into, I tried to edit "nrf9160dk_nrf9160ns.overlay": (formatting gets screwed up if you try to insert as code)

&uart2 {
compatible = "nordic,nrf-uarte";
current-speed = <115200>;
status = "okay";
tx-pin = <10>;
rx-pin = <11>;
rts-pin = <12>;
cts-pin = <13>;
hw-flow-control;
};

I have tried changing pins and buadrate to no effect, even after reloading the project in SEGGER, but if I do the same for UART1/0 but still nothing.

When I goto make my own custom board how do I actually go about selecting pins for the AT command UART?

Edit:

I tried this solution: https://devzone.nordicsemi.com/f/nordic-q-a/45941/nrf9160-asset-tracker-configure-uart but the project gets errors when I try to open it

There was another one I tried, but I can't find it right now. Was to do with some kind of Arduino flag.

Parents
  • Hello Kyle,

    thanks a lot for your feedback! I really enjoy your videos, it is a cosy variation in my everyday working life :-) And I like your bird very much ;-)

    I’m glad to hear that you could solve the issue. And I can absolutely understand that getting started with Zephyr is confusing at some points. As a little tip, I could recommend you to check the Zephyr Devicetreee Guide, as it provides very useful information on how the toolchain is set-up in general.

    And then there is the nRF Connect SDK Tutorial, written by my colleague Simon, which introduces the nRF Connect SDK upon the Zephyr RTOS.

    Regarding the UART2 issue you were facing: one potential reason for that could be Memory Instantiation, as the default enabled peripheral of the nRF9160 DK is the i2c2 unit.

    Cheers,

    Markus

Reply
  • Hello Kyle,

    thanks a lot for your feedback! I really enjoy your videos, it is a cosy variation in my everyday working life :-) And I like your bird very much ;-)

    I’m glad to hear that you could solve the issue. And I can absolutely understand that getting started with Zephyr is confusing at some points. As a little tip, I could recommend you to check the Zephyr Devicetreee Guide, as it provides very useful information on how the toolchain is set-up in general.

    And then there is the nRF Connect SDK Tutorial, written by my colleague Simon, which introduces the nRF Connect SDK upon the Zephyr RTOS.

    Regarding the UART2 issue you were facing: one potential reason for that could be Memory Instantiation, as the default enabled peripheral of the nRF9160 DK is the i2c2 unit.

    Cheers,

    Markus

Children
No Data
Related