Custom PCB nRF9160 Link monitor ports

[Yano]

Hi, We have a custom design using an nRF9160.

We can connect and program the device using a jLink though the debug port.

How can we connect the LTE link monitor to the board to transfer AT commands?

Currently our PCB only has access to P0.18 and P0.19 for debug (this can be modified in the next PCB revision).

Can these be re-programmed or are they part of the soft device?

Thanks

[Håkon Alseth]

Hi,

 

How can we connect the LTE link monitor to the board to transfer AT commands?

The CONFIG_AT_HOST option uses a generic UART for communication. As long as you connect your device to a usb-uart converter, you should be able to select the device in the drop-down meny in LTE Link Monitor, but you have to un-tick the "Auto device / port filter", then select your device.

 

Firmware-wise, what you need to do is to change the pinout of uart0 for both non-secure and secure region. This can be done by creating your own board, or use a overlay for an existing board (like nrf9160dk_nrf9160ns).

Changes required to CMakeLists.txt for your specific project can be found here:

https://devzone.nordicsemi.com/f/nordic-q-a/60471/nrf9160-psm-current-consumption-test-problem/245872#245872

Then you can create a $(BOARD).overlay file, for instance nrf9160dk_nrf9160ns.overlay in the same folder, and populate it with:

&uart0 {
	status = "okay";
	current-speed = <115200>;
	tx-pin = <18>;
	rx-pin = <19>;
	rts-pin = <0xFFFFFFFF>;
	cts-pin = <0xFFFFFFFF>;
};

 

Now, re-configure your project, and the uart0 pinout should have been changed to your wanted pins.

 

Kind regards,

Håkon

[Yano]

Hi Håkon,

Can you help some more please?

For some reason the change of port is not working however it is connecting to nRF cloud fine?

For now I am testing on the nRF9160DK before porting over to our own hardware.

The output from the LTE link monitor (through the on board UART0/USB) has stopped, so something has changed, but there is no output from my external port?

I went for the overlay option, this is what I did:

1. I created a file nrf9160dk_nrf9160ns.overlay and added the code you suggested (swapped tx/rx pins) and placed it in same directory as the CMake

2. I modified the CMake as per your link.

3. Created a spm.conf file and added the line CONFIG_SERIAL=n ( I'm not sure if this is right? )

3. I re-built and ran the project successfully.

I have attached the complete project zipped up.

Any ideas please?

Thanks Ian

7536.asset_tracker.zip

[Håkon Alseth]

Hi,

 

Yano said:

For now I am testing on the nRF9160DK before porting over to our own hardware.

Its not all gpios that are routed out to the pin headers on the DK. Which version are you testing with?

I usually test by outputting bus signals on P0.10 and P0.11 on the DK, as this is (almost) safe on all revisions of the DK.

 

Kind regards,

Håkon

[Yano]

Hi Håkon,

That was on rev 0.8.5 but I tried moving to P0.10 and 11 but that didn't work.

I also tried it on a rev1.0.0 but that didn't work either.

Serial port seems fine (loop back works).

Any other ideas?

Could you try out my code there?

Thanks Ian

 

[Håkon Alseth]

Hi Ian,

 

I tried your code and it looks to work just fine here, but I am not using P0.18/P0.19, as I'm testing on a DK, and not all pins are routed to the arduino header.

I'm using P0.10 and P0.11, and since I'm only connecting to a logic analyzer, the RXD pin is left floating, but it does print over the new pins:

 

Kind regards,

Håkon

[Yano]

Hi Hakon,

I tried it on my DK and it worked on the analyser on ports 10/11.

Then I swapped to another serial interface and it worked so I guess is must the interface.

However I need to program the certs, send AT commands to the modem etc. so I think I have the wrong port?

Is it just a change of uart or do I need to do more?

Thanks Ian 

[Håkon Alseth]

Hi,

 

Yano said:

However I need to program the certs, send AT commands to the modem etc. so I think I have the wrong port?

There's certain AT commands that cannot be provided once the modem is active (CFUN=1), writing certificates is one of these.

I would recommend that you use at_client instead of asset_tracker to write certificates into the modem.

 

Kind regards,

Håkon