Errors trying to connect

[jonathanpallant]

I was trying to use the nrf9160-demo application with the latest version of this repo, but I had some errors.

1. I had to change the nrf9160-hal to use 0x0000_C000 as the load address, because that's what the latest SPM seems to use. Or at least, that's what the SPM built with the "at_sample" application was expecting; I think they might auto-configure the flash partition layout depending on the application you are building.
2. I couldn't init nrfxlib with trace off, but it did work with trace on.
3. Creating a TLS socket failed with Err(Nrfxlib(Nordic("new_socket", -1, 41))) if I tried to make a TLS v1.3 socket with verification enabled. Error 41 is NRF_EPROTOTYPE.
4. Creating a TLS socket worked if I made a TLS v1.2 socket with verification disabled, but connecting to it gave Err(Nrfxlib(Nordic("tls_connect", -1, 45)), which is NRF_EOPNOTSUPP.

[huntc]

Are these issues still relevant given recent activity?

[jonathanpallant]

Probably not, but I don't have a functioning SIM to test with.

[turbinenreiter]

I am experiencing the same issues.

Connecting to jsonplaceholder.typicode.com following the example in the demo repo (https://github.com/42-technology-ltd/nrf9160-demo) works, but when I try my own endpoint, I get the errors described above.

I tried storing the correct CA_CHAIN, but nrfxlib::tls::provision_certificates fails with AtError(Error).

Currently unsure as to where to start locking for the problem.