• State Not Answered
  • Replies 6 replies
  • Subscribers 63 subscribers
  • Views 3131 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 268069
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF9160 HTTP client AT commands always returns +CME ERROR: 0

Mr.Newlove

Hello,

I am trying to get my nRF9160 to connect to a https server via AT commands, but this is as far as I've been able to get.

In the end this will be used in a project where another micro is monitoring peripherals and doing a bunch of logging, then powering the modem power supply up, initializing via AT commands and uploading data logs via HTTPS POST using a security token to authorize the device server side. I know I could be using the modem micro for all of this, but the RTOS/Zephyr toolchain has been painful to work with.

Log:

2021-04-12T21:52:25.858Z INFO Application data folder: C:\Users\user\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2021-04-12T21:52:25.991Z DEBUG App pc-nrfconnect-linkmonitor v1.1.10 official
2021-04-12T21:52:25.991Z DEBUG App path: C:\Users\user\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2021-04-12T21:52:25.991Z DEBUG nRFConnect 3.6.1 is supported by the app (^3.6.0)
2021-04-12T21:52:25.992Z DEBUG nRFConnect path: C:\Users\user\AppData\Local\Programs\nrfconnect\resources\app.asar
2021-04-12T21:52:25.992Z DEBUG HomeDir: C:\Users\user
2021-04-12T21:52:25.992Z DEBUG TmpDir: C:\Users\user\AppData\Local\Temp
2021-04-12T21:52:26.017Z VERBOSE Could not fetch serial number for serial port at COM1
2021-04-12T21:52:34.311Z INFO Modem port is opened
2021-04-12T21:52:34.321Z DEBUG modem >> AT+CFUN?
2021-04-12T21:52:34.359Z DEBUG modem << +CFUN: 0
2021-04-12T21:52:34.368Z DEBUG modem << OK
2021-04-12T21:52:40.478Z DEBUG modem >> AT
2021-04-12T21:52:40.494Z DEBUG modem << OK
2021-04-12T21:52:43.110Z DEBUG modem >> AT+CFUN=1
2021-04-12T21:52:43.158Z DEBUG modem << OK
2021-04-12T21:52:47.848Z DEBUG modem >> AT+CFUN?
2021-04-12T21:52:47.858Z DEBUG modem << +CFUN: 1
2021-04-12T21:52:47.877Z DEBUG modem << OK
2021-04-12T21:52:47.883Z DEBUG modem >> AT+CGSN=1
2021-04-12T21:52:47.894Z DEBUG modem << +CGSN: "352656106114062"
2021-04-12T21:52:47.906Z DEBUG modem << 
2021-04-12T21:52:47.909Z DEBUG modem << OK
2021-04-12T21:52:47.914Z DEBUG modem >> AT+CGMI
2021-04-12T21:52:47.929Z DEBUG modem << Nordic Semiconductor ASA
2021-04-12T21:52:47.933Z DEBUG modem << OK
2021-04-12T21:52:47.952Z DEBUG modem >> AT+CGMM
2021-04-12T21:52:47.960Z DEBUG modem << nRF9160-SICA
2021-04-12T21:52:47.972Z DEBUG modem << 
2021-04-12T21:52:47.974Z DEBUG modem << OK
2021-04-12T21:52:47.977Z DEBUG modem >> AT+CGMR
2021-04-12T21:52:47.984Z DEBUG modem << mfw_nrf9160_1.2.1
2021-04-12T21:52:47.989Z DEBUG modem << 
2021-04-12T21:52:47.992Z DEBUG modem << OK
2021-04-12T21:52:47.995Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.2.1] SerNr: 352656106114062
2021-04-12T21:52:47.996Z DEBUG modem >> AT+CEMODE?
2021-04-12T21:52:48.006Z DEBUG modem << +CEMODE: 0
2021-04-12T21:52:48.010Z DEBUG modem << 
2021-04-12T21:52:48.012Z DEBUG modem << OK
2021-04-12T21:52:48.032Z DEBUG modem >> AT%XCBAND=?
2021-04-12T21:52:48.046Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2021-04-12T21:52:48.051Z DEBUG modem << OK
2021-04-12T21:52:48.080Z DEBUG modem >> AT+CMEE?
2021-04-12T21:52:48.093Z DEBUG modem << +CMEE: 0
2021-04-12T21:52:48.095Z DEBUG modem << OK
2021-04-12T21:52:48.099Z DEBUG modem >> AT+CMEE=1
2021-04-12T21:52:48.112Z DEBUG modem << OK
2021-04-12T21:52:48.116Z DEBUG modem >> AT+CNEC?
2021-04-12T21:52:48.126Z DEBUG modem << +CNEC: 0
2021-04-12T21:52:48.129Z DEBUG modem << OK
2021-04-12T21:52:48.143Z DEBUG modem >> AT+CNEC=24
2021-04-12T21:52:48.165Z DEBUG modem << OK
2021-04-12T21:52:48.170Z DEBUG modem >> AT+CGEREP?
2021-04-12T21:52:48.187Z DEBUG modem << +CGEREP: 0,0
2021-04-12T21:52:48.191Z DEBUG modem << OK
2021-04-12T21:52:48.194Z DEBUG modem >> AT+CGDCONT?
2021-04-12T21:52:48.209Z DEBUG modem << +CGDCONT: 0,"IP","","",0,0
2021-04-12T21:52:48.211Z DEBUG modem << OK
2021-04-12T21:52:48.227Z DEBUG modem >> AT+CGACT?
2021-04-12T21:52:48.236Z DEBUG modem << +CGACT: 0,0
2021-04-12T21:52:48.239Z DEBUG modem << OK
2021-04-12T21:52:48.251Z DEBUG modem >> AT+CGEREP=1
2021-04-12T21:52:48.260Z DEBUG modem << OK
2021-04-12T21:52:48.269Z DEBUG modem >> AT+CIND=1,1,1
2021-04-12T21:52:48.277Z DEBUG modem << OK
2021-04-12T21:52:48.280Z DEBUG modem >> AT+CEREG=5
2021-04-12T21:52:48.293Z DEBUG modem << OK
2021-04-12T21:52:48.296Z DEBUG modem >> AT+CEREG?
2021-04-12T21:52:48.310Z DEBUG modem << +CEREG: 5,2,"2B1C","01AFEA0C",7,0,0,"11100000","11100000"
2021-04-12T21:52:48.320Z DEBUG modem << 
2021-04-12T21:52:48.322Z DEBUG modem << OK
2021-04-12T21:52:48.332Z DEBUG modem >> AT%CESQ=1
2021-04-12T21:52:48.345Z DEBUG modem << OK
2021-04-12T21:52:48.349Z DEBUG modem >> AT+CESQ
2021-04-12T21:52:48.364Z DEBUG modem << +CESQ: 99,99,255,255,11,28
2021-04-12T21:52:48.367Z DEBUG modem << OK
2021-04-12T21:52:48.380Z DEBUG modem >> AT%XSIM=1
2021-04-12T21:52:48.387Z DEBUG modem << OK
2021-04-12T21:52:48.390Z DEBUG modem >> AT%XSIM?
2021-04-12T21:52:48.401Z DEBUG modem << %XSIM: 1
2021-04-12T21:52:48.403Z DEBUG modem << OK
2021-04-12T21:52:48.411Z DEBUG modem >> AT+CPIN?
2021-04-12T21:52:48.423Z DEBUG modem << +CPIN: READY
2021-04-12T21:52:48.425Z DEBUG modem << OK
2021-04-12T21:52:48.437Z DEBUG modem >> AT+CPINR="SIM PIN"
2021-04-12T21:52:48.453Z DEBUG modem << +CPINR: "SIM PIN",3
2021-04-12T21:52:48.460Z DEBUG modem << 
2021-04-12T21:52:48.461Z DEBUG modem << OK
2021-04-12T21:52:48.467Z DEBUG modem >> AT+CIMI
2021-04-12T21:52:48.476Z DEBUG modem << 302760000873553
2021-04-12T21:52:48.479Z DEBUG modem << OK
2021-04-12T21:52:48.480Z INFO IMSIdentity: 302760000873553
2021-04-12T21:52:48.703Z DEBUG modem << %CESQ: 23,1,10,1
2021-04-12T21:52:48.945Z DEBUG modem << +CGEV: ME PDN ACT 0,0
2021-04-12T21:52:48.959Z DEBUG modem >> AT+CGDCONT?
2021-04-12T21:52:48.963Z DEBUG modem << +CNEC_ESM: 50,0
2021-04-12T21:52:48.966Z DEBUG modem << +CEREG: 1,"2B1C","01AFEA0C",7,,,"11100000","11100000"
2021-04-12T21:52:48.968Z DEBUG modem << +CIND: "service",1
2021-04-12T21:52:48.980Z DEBUG modem << 
2021-04-12T21:52:48.982Z DEBUG modem << +CGDCONT: 0,"IP","attach.telus.com","25.250.72.77",0,0
2021-04-12T21:52:48.984Z DEBUG modem << OK
2021-04-12T21:52:48.998Z DEBUG modem >> AT+CGACT?
2021-04-12T21:52:49.010Z DEBUG modem << +CGACT: 0,1
2021-04-12T21:52:49.013Z DEBUG modem << OK
2021-04-12T21:52:49.377Z DEBUG modem << %CESQ: 28,1,10,1
2021-04-12T21:52:53.371Z DEBUG modem >> AT+CGDCONT=1,"IP","m2m.telus.iot"
2021-04-12T21:52:53.388Z DEBUG modem << OK
2021-04-12T21:52:59.605Z DEBUG modem >> AT+CFUN?
2021-04-12T21:52:59.612Z DEBUG modem << +CFUN: 1
2021-04-12T21:52:59.624Z DEBUG modem << OK
2021-04-12T21:52:59.628Z DEBUG modem >> AT+CGSN=1
2021-04-12T21:52:59.646Z DEBUG modem << +CGSN: "352656106114062"
2021-04-12T21:52:59.648Z DEBUG modem << OK
2021-04-12T21:52:59.652Z DEBUG modem >> AT+CGMI
2021-04-12T21:52:59.661Z DEBUG modem << Nordic Semiconductor ASA
2021-04-12T21:52:59.672Z DEBUG modem << 
2021-04-12T21:52:59.674Z DEBUG modem << OK
2021-04-12T21:52:59.678Z DEBUG modem >> AT+CGMM
2021-04-12T21:52:59.697Z DEBUG modem << nRF9160-SICA
2021-04-12T21:52:59.701Z DEBUG modem << 
2021-04-12T21:52:59.702Z DEBUG modem << OK
2021-04-12T21:52:59.708Z DEBUG modem >> AT+CGMR
2021-04-12T21:52:59.727Z DEBUG modem << mfw_nrf9160_1.2.1
2021-04-12T21:52:59.736Z DEBUG modem << 
2021-04-12T21:52:59.738Z DEBUG modem << OK
2021-04-12T21:52:59.740Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.2.1] SerNr: #############
2021-04-12T21:52:59.743Z DEBUG modem >> AT+CEMODE?
2021-04-12T21:52:59.760Z DEBUG modem << +CEMODE: 0
2021-04-12T21:52:59.764Z DEBUG modem << 
2021-04-12T21:52:59.765Z DEBUG modem << OK
2021-04-12T21:52:59.771Z DEBUG modem >> AT%XCBAND=?
2021-04-12T21:52:59.796Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,18,19,20,25,26,28,66)
2021-04-12T21:52:59.800Z DEBUG modem << OK
2021-04-12T21:52:59.806Z DEBUG modem >> AT+CMEE?
2021-04-12T21:52:59.825Z DEBUG modem << +CMEE: 1
2021-04-12T21:52:59.826Z DEBUG modem << OK
2021-04-12T21:52:59.830Z DEBUG modem >> AT+CNEC?
2021-04-12T21:52:59.846Z DEBUG modem << +CNEC: 24
2021-04-12T21:52:59.849Z DEBUG modem << OK
2021-04-12T21:52:59.853Z DEBUG modem >> AT+CGEREP?
2021-04-12T21:52:59.869Z DEBUG modem << +CGEREP: 1,0
2021-04-12T21:52:59.877Z DEBUG modem << 
2021-04-12T21:52:59.878Z DEBUG modem << OK
2021-04-12T21:52:59.881Z DEBUG modem >> AT+CIND=1,1,1
2021-04-12T21:52:59.888Z DEBUG modem << OK
2021-04-12T21:52:59.893Z DEBUG modem >> AT+CEREG=5
2021-04-12T21:52:59.904Z DEBUG modem << OK
2021-04-12T21:52:59.910Z DEBUG modem >> AT+CEREG?
2021-04-12T21:52:59.926Z DEBUG modem << +CEREG: 5,1,"2B1C","01AFEA0C",7,,,"11100000","11100000"
2021-04-12T21:52:59.928Z DEBUG modem << OK
2021-04-12T21:52:59.940Z DEBUG modem >> AT+COPS=3,2
2021-04-12T21:52:59.948Z DEBUG modem << OK
2021-04-12T21:52:59.951Z DEBUG modem >> AT+COPS?
2021-04-12T21:52:59.959Z DEBUG modem << +COPS: 0,2,"302220",7
2021-04-12T21:52:59.962Z DEBUG modem << OK
2021-04-12T21:52:59.974Z DEBUG modem >> AT%XCBAND
2021-04-12T21:52:59.991Z DEBUG modem << %XCBAND: 12
2021-04-12T21:52:59.993Z DEBUG modem << OK
2021-04-12T21:53:00.004Z DEBUG modem >> AT+CGDCONT?
2021-04-12T21:53:00.023Z DEBUG modem << +CGDCONT: 0,"IP","attach.telus.com","25.250.72.77",0,0
2021-04-12T21:53:00.035Z DEBUG modem << +CGDCONT: 1,"IP","m2m.telus.iot","",0,0
2021-04-12T21:53:00.041Z DEBUG modem << OK
2021-04-12T21:53:00.058Z DEBUG modem >> AT+CGACT?
2021-04-12T21:53:00.075Z DEBUG modem << +CGACT: 0,1
2021-04-12T21:53:00.079Z DEBUG modem << 
2021-04-12T21:53:00.081Z DEBUG modem << +CGACT: 1,0
2021-04-12T21:53:00.082Z DEBUG modem << OK
2021-04-12T21:53:00.090Z DEBUG modem >> AT%CESQ=1
2021-04-12T21:53:00.107Z DEBUG modem << OK
2021-04-12T21:53:00.110Z DEBUG modem >> AT+CESQ
2021-04-12T21:53:00.127Z DEBUG modem << +CESQ: 99,99,255,255,10,27
2021-04-12T21:53:00.131Z DEBUG modem << 
2021-04-12T21:53:00.133Z DEBUG modem << OK
2021-04-12T21:53:00.141Z DEBUG modem >> AT%XSIM=1
2021-04-12T21:53:00.158Z DEBUG modem << OK
2021-04-12T21:53:00.164Z DEBUG modem >> AT%XSIM?
2021-04-12T21:53:00.184Z DEBUG modem << %XSIM: 1
2021-04-12T21:53:00.187Z DEBUG modem << OK
2021-04-12T21:53:00.199Z DEBUG modem >> AT+CPIN?
2021-04-12T21:53:00.210Z DEBUG modem << +CPIN: READY
2021-04-12T21:53:00.213Z DEBUG modem << OK
2021-04-12T21:53:00.223Z DEBUG modem >> AT+CPINR="SIM PIN"
2021-04-12T21:53:00.238Z DEBUG modem << +CPINR: "SIM PIN",3
2021-04-12T21:53:00.241Z DEBUG modem << OK
2021-04-12T21:53:00.252Z DEBUG modem >> AT+CIMI
2021-04-12T21:53:00.268Z DEBUG modem << ######
2021-04-12T21:53:00.270Z DEBUG modem << OK
2021-04-12T21:53:00.271Z INFO IMSIdentity: ######
2021-04-12T21:53:10.340Z DEBUG modem << %CESQ: 255,0,255,0
2021-04-12T21:53:10.352Z DEBUG modem << +CEREG: 1,"2B1C","01B05C0C",7,,,"11100000","11100000"
2021-04-12T21:53:10.367Z DEBUG modem >> AT+COPS=3,2
2021-04-12T21:53:10.392Z DEBUG modem << OK
2021-04-12T21:53:10.397Z DEBUG modem >> AT+COPS?
2021-04-12T21:53:10.417Z DEBUG modem << +COPS: 0,2,"302220",7
2021-04-12T21:53:10.418Z DEBUG modem << OK
2021-04-12T21:53:10.424Z DEBUG modem >> AT%XCBAND
2021-04-12T21:53:10.442Z DEBUG modem << %XCBAND: 12
2021-04-12T21:53:10.444Z DEBUG modem << OK
2021-04-12T21:53:10.460Z DEBUG modem >> AT+CGDCONT?
2021-04-12T21:53:10.483Z DEBUG modem << +CGDCONT: 0,"IP","attach.telus.com","25.250.72.77",0,0
2021-04-12T21:53:10.490Z DEBUG modem << +CGDCONT: 1,"IP","m2m.telus.iot","",0,0
2021-04-12T21:53:10.492Z DEBUG modem << OK
2021-04-12T21:53:10.525Z DEBUG modem >> AT+CGACT?
2021-04-12T21:53:10.555Z DEBUG modem << +CGACT: 0,1
2021-04-12T21:53:10.557Z DEBUG modem << +CGACT: 1,0
2021-04-12T21:53:10.559Z DEBUG modem << OK
2021-04-12T21:53:11.105Z DEBUG modem << %CESQ: 23,1,3,0
2021-04-12T21:53:14.945Z DEBUG modem << %CESQ: 22,1,9,1
2021-04-12T21:53:38.975Z DEBUG modem >> AT#XHTTPCCON=1,"google.ca",80
2021-04-12T21:53:38.995Z DEBUG modem << +CME ERROR: 0
2021-04-12T21:53:38.998Z ERROR Error: AT#XHTTPCCON=1,"google.ca",80
 failed: phone failure
2021-04-12T21:53:44.854Z INFO Modem port is closed
2021-04-12T21:54:58.744Z INFO Restoring from C:\Users\user\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor\logs\2021-04-12T21_52_24.837Z-log.txt

seems fine

Mostly right now, I turn the modem power on, then send:

AT+CFUN=1
AT+CFUN?
AT+CGDCONT=1,"IP","m2m.telus.iot"
AT+CFUN?
AT+CFUN?
AT#XHTTPCCON=1,"google.ca",80

Thanks,

Kyle

Edit:
It appears the FW doesn't support the HTTPCCON command?? even though its in the documentation?

2021-04-12T22:34:30.215Z DEBUG modem >> AT#XCLAC
2021-04-12T22:34:30.226Z DEBUG modem << AT#XSLMVER
2021-04-12T22:34:30.228Z DEBUG modem << AT#XSLMUART
2021-04-12T22:34:30.232Z DEBUG modem << AT#XSLEEP
2021-04-12T22:34:30.234Z DEBUG modem << AT#XRESET
2021-04-12T22:34:30.234Z DEBUG modem << AT#XDATACTRL
2021-04-12T22:34:30.246Z DEBUG modem << AT#XTCPFILTER
2021-04-12T22:34:30.248Z DEBUG modem << AT#XTCPSVR
2021-04-12T22:34:30.249Z DEBUG modem << AT#XTCPCLI
2021-04-12T22:34:30.250Z DEBUG modem << AT#XTCPSEND
2021-04-12T22:34:30.252Z DEBUG modem << AT#XTCPRECV
2021-04-12T22:34:30.254Z DEBUG modem << AT#XUDPSVR
2021-04-12T22:34:30.255Z DEBUG modem << AT#XUDPCLI
2021-04-12T22:34:30.256Z DEBUG modem << AT#XUDPSEND
2021-04-12T22:34:30.257Z DEBUG modem << AT#XSOCKET
2021-04-12T22:34:30.258Z DEBUG modem << AT#XSOCKETOPT
2021-04-12T22:34:30.259Z DEBUG modem << AT#XBIND
2021-04-12T22:34:30.260Z DEBUG modem << AT#XCONNECT
2021-04-12T22:34:30.261Z DEBUG modem << AT#XLISTEN
2021-04-12T22:34:30.276Z DEBUG modem << AT#XACCEPT
2021-04-12T22:34:30.277Z DEBUG modem << AT#XSEND
2021-04-12T22:34:30.283Z DEBUG modem << AT#XRECV
2021-04-12T22:34:30.284Z DEBUG modem << AT#XSENDTO
2021-04-12T22:34:30.285Z DEBUG modem << AT#XRECVFROM
2021-04-12T22:34:30.285Z DEBUG modem << AT#XGETADDRINFO
2021-04-12T22:34:30.285Z DEBUG modem << AT#XPING
2021-04-12T22:34:30.287Z DEBUG modem << AT#XFOTA
2021-04-12T22:34:30.287Z DEBUG modem << OK


Trying 
img_app_bl/serial_lte_modem_2021-03-01_8e8c6089.hex

and 

img_app_bl/nrf9160dk_at_client_2021-03-01_8e8c6089.hex   << doesn't do anything different other than it no longer responds to AT#XCLAC

Edit2:

The FTP commands seem to be missing from both FW as well?

Edit3:

Part of good news, it does connect to the network and I can ping things, and use a normal TCP socket to manually request a non-SSL page, but this is not great because we want SSL and not have to build the HTTP layer.

  • 0

    Hi,

    HTTP support is disabled by default in the Serial LTE Modem application in NCS v1.5.0, and is therefore also disabled in the pre-compiled hex file.

    This was changed in this PR: https://github.com/nrfconnect/sdk-nrf/pull/4153

    So to enable HTTP, FTP, MQTT and GPS support, you must compile the application yourself with the relevant options enabled.

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    Hello Didrik,

    Sorry for the delay, I ended up busy with another problem.

    That is a bit disappointing, not being able to just load the serial_lte_modem application and have access to all documented AT commands. I have not had a good time with the nRF9160 development compared to AVR or Pic thus far.

    The link you gave leads to a 404 page, I will be trying to recompile in the next couple days here. Can you please send me a link works so I can read changes that where made?

    Thanks,

    Kyle

    Edit: there was a comma at the end of the URL somehow

    Edit: I have tried to open the existing serial_lte_modem application, but I can't figiure out how to open it in the SEGGER IDE recommended in nRF connect.

  • 0 in reply to Mr.Newlove

    Sorry for the faulty link, I have fixed it now.

    But you shouldn't necessarily apply the same changes. The PR changes the defaults, while it might be better for you to just change the applied configuration.

    The easiest way to do that is to uncomment lines 91, 92, 94 and 96 (or just the ones you want) in the prj.conf file.

    The easiest way to install and use the nRF Connect SDK is explained here:

    https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.1/nrf/gs_assistant.html#toolchain-manager

    https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.5.1/nrf/gs_programming.html

    Note that when installing the SDK through the Toolchain Manager, you must open SES or the command line from the Toolchain Manager for the environment to be configured correctly.

    I've also attached a image with all the features enabled, compiled for the nRF9160 DK.

    slm_all_features_dk.hex

  • 0 in reply to Didrik Rokhaug

    Hello Didrik,

    I will try that slm_all_features.hex file. That is the full feature version of "serial_lte_modem" I take it?

    Now that we are on the topic of building your own projects.

    Here is a video showing my problems when trying to compile myself: https://youtu.be/-u4lV7Ohl-s

    For the future it would be good if I can get it compiled on my own to keep things up to date.

    I would really like to be able to write code to run on the modem itself, rather than rely on an external microprocessor.

    Thanks,

    Kyle

  • 0 in reply to Mr.Newlove

    Thanks for the video.

    I would recommend that you stick to the SDK versions you install with the Toolchain Manager (TM). That way, you can be sure that the provided tools works with the given SDK version, and it makes it easier for us to replicate any potential problems you have as the environments will be similar.

    If you want to download the code yourself (e.g. if you want to maintain your own fork of the SDK), you should still keep to the tagged releases, as the master branch sometimes require newer tools than what is provided by the TM, or it might not work at all.

    The reason why you couldn't find any HTTP related configs in the prj.conf is because you were using the master branch, which has the PR where all features are enabled by default merged. So in that version, you do not need to enable them yourself.

    Another point I want to clarify is that the check-boxes in the "Open NCS project" dialog box only selects which samples are shown in the drop down menu. The project will still include all the libraries it needs (and which are enabled in Kconfig, etc.).

    It also looked like you picked the wrong board. When you are using the modem, you must build your application as non-secure. To do that, you must choose the nrf9160dk_nrf9160ns board (notice the "ns" at the end). Although, if you didn't pick the non-secure version, you shouldn't have been able to open the project at all, so maybe I saw incorrectly, or missed something when you skipped forward.

    I haven't seen the build errors you got before, but my guess is that it is because you are using the master branch. If you check out the v1.5.0 tag and run west update, it should work (though you will have to enable HTTP support yourself). It could also be that you didn't use "build solution" as you did when you built the blinky sample, though I don't know enough about SES to say if what you did are supposed to work or not. I mostly use the command line myself.

Related

core_v2_widget.Hide()