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 Ian,

 

Yano said:

It looks like there is a bit of a mix-up between aws_iot and aws_fota!

The samples are different, but both connect to AWS services, so the sequence of events, especially wrt. certificates, is equal algorithm wise; but they show different roads to Rome.

 

My former answer shows you the two ways of provisioning certificates.

This is the implementation that is used in aws_fota:

https://github.com/nrfconnect/sdk-nrf/blob/v1.5.0/samples/nrf9160/aws_fota/src/main.c#L327-L372

If you choose this method, you add your certificates to the header file:

https://github.com/nrfconnect/sdk-nrf/blob/v1.5.0/samples/nrf9160/aws_fota/src/certificates.h

 

They should then hold the format as I described underneath with quotes and newlines.

Once you write the certificates to a specific sec_tag, you can re-use the tag a new firmware, as the certificates are then stored in the modem.

 

Kind regards,

Håkon

[Yano]

Hi Håkon,

Thanks!

I have them both going now using the certificate.h method.

Do you have a timeline for the fix to LTE-link serial?

One last question, which of the two aws samples is best to use as the basis of a project?

We need our code to be able to publish and subscribe initially (quickly) but fota capability will be needed at some stage.

Thanks

Ian

[Håkon Alseth]

Hi Ian,

 

Yano said:

Thanks!

I have them both going now using the certificate.h method.

Great to hear! 

 

Yano said:

Do you have a timeline for the fix to LTE-link serial?

 Unfortunately, I do not have a timeline. I have made the team aware of the issue, and asked them to plan this into their next sprint.

 

Yano said:

One last question, which of the two aws samples is best to use as the basis of a project?

We need our code to be able to publish and subscribe initially (quickly) but fota capability will be needed at some stage.

 This highly depends on what your application is expected to do.

The aws_iot sample shows how to connect and communicate over AWS IoT message broker, while the aws_fota shows how to perform an over-the-air firmware update of an nRF9160 device via MQTT and HTTP. These samples also showcase FOTA features over http: https://github.com/nrfconnect/sdk-nrf/tree/master/samples/nrf9160/http_update

You can look at several samples, and implement specific features from samples into your own application, based on your requirements. If your application needs to connect to a generic mqtt broker, the mqtt_simple sample could be a good starting point.

 

Kind regards,

Håkon