AT uart

RE: AT uart

dejans — Mon, 02 Sep 2024 10:41:19 GMT

Hi,

I am not sure if this answers your question, but the Note in Pin configuration discourages adding pin configuration defaults in pre-defined nodes.

Best regards,
Dejan

RE: AT uart

dave — Fri, 30 Aug 2024 01:13:52 GMT

With respect to pin ctrl, are you saying that the current way I have them defined in the overlay file is not recommended?

RE: AT uart

dejans — Thu, 29 Aug 2024 11:11:32 GMT

Hi,

AT Host library uses UART0 by default but this can be changed using ncs,at-host-uart choice in devicetree.
Regarding the pins, there is likely pin conflict in your configuration, i.e. pins are not chosen correctly. You can check GPIO pin usage in the default pin settings table in the chapter 4.6 (GPIO interfaces) of the nRF9160-dk hardware user guide.
You could try to use pins for buttons or leds which are routed to the pin header.
You should also use your own pinctrl instances instead of matching ones already set up in the board. For example,

&pinctrl {
   my_pin_configuration: my_pin_configuration {
      group1 {
         psels = <NRF_PSEL(UART_TX, 0, 14)>,
                 <NRF_PSEL(UART_RX, 0, 16)>;
      };
   };
};

and

&uart0 {
  pinctrl-0 = <&my_pin_configuration>;
  pinctrl-names = "default";
};

Best regards,
Dejan

RE: AT uart

dave — Wed, 28 Aug 2024 01:17:50 GMT

Right now I have uart0 set up for P0.016/P0.17 which should be for the AT uart, and then uart 1 set up with P0.00/P0.01 for logging / shell.

If I don't have the AT host library enabled the shell and logging works ok.. but if I enable the AT host library, neither works.

RE: AT uart

dejans — Tue, 27 Aug 2024 13:59:53 GMT

Hi,

Information about GPIO pins on the nRF9160-dk hardware can be found in the documentation.

[quote user="dave_s"]I tried building the AT_client sample but it was giving build errors. I'll try again[/quote]

If you still experience an issue, please provide your build log.

Best regards,
Dejan

RE: AT uart

mark.blackburn.orpyx — Mon, 26 Aug 2024 17:07:19 GMT

I think P0.16 and P0.17 would be safe to use. They are on the nRF52 interface, but those should not be driven if the default firmware on that chip is left as is or erased.

RE: AT uart

mark.blackburn.orpyx — Mon, 26 Aug 2024 17:05:07 GMT

I think you are running into a contention because the IC there a a MCU that is driving the VCOM lines on the DK. I think you should change which pins you are using for your UART on pins P0.00 and P0.01 if you want to use the Arduino connectors.

RE: AT uart

dave — Mon, 26 Aug 2024 14:26:33 GMT

I tried building the AT_client sample but it was giving build errors. I'll try again

But either way, I need to use regular GPIO pins for the uart since that is what I'll use in production and not a virtual com port over the USB

RE: AT uart

dejans — Fri, 23 Aug 2024 13:58:07 GMT

Hi,

Here is the link to Cellular AT client sample documentation page.

Best regards,
Dejan

RE: AT uart

mark.blackburn.orpyx — Fri, 23 Aug 2024 00:31:15 GMT

You don't need to connect USB to UART convertor to any pins. The DK already has VCOM ports over the USB connection.

I recommend trying the at_client sample.

In VS Code "Create a new application"

"Copy a sample"

Start typing "at_client" and select at_client Sample

Create a build configuration for nrf9160 dk and don't make any changes to the device tree configuration. The DK has 3 UARTs. Two of them are for the nRF9160. Try connecting to all of them at 115200, and keep type AT<ENTER> util one of them responds with "OK"