Thanks Jared,
I am using Ubuntu 22.04 as a development platform.
Whilst my cable is on order. I tried doing some debugging with a build of the application_update sample built first for the DK board and then the Feather.
In the case of the feather this method times out waiting on the modem to connect.
static int connect_lte(bool blocking)
in ncs/v2.3.0/nrf/lib/lte_link_control/lte_lc.c
is blocking waiting on the semaphore to indicate that connection has been established.
In the case of the DK board the at_monitor_task
will ensure at_handler_creg method
gets called with:-
+CEREG notificaiton +CEREG: 2,“8651”,“07AEF16E”,7
and
+CEREG notificaiton +CEREG: 5,“8651”,“07AEF16E”,7,,,“11100000”,“11100000”
I inserted some debug messages into these methods and in the case of feather the at_monitor_task doesn’t initially get invoked and when it does it is called with
+CEREG notificaiton +CEREG: 4
Sorry I am still trying to get an understanding of the architecture and code flow and very much feels like I am poking at black boxes at the moment. I am just putting this up in the hopes that it indicates to some one with understanding what I am doing wrong.
I also tried building the AWS Fota sample and saw similar behaviour.
I also repeated the process with a build of the sms app and got a similar issue with Network connection timing out
#CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y
I also attempted to get a modem trace but this caused issues when I tried to build it for the feather. I would get an error that there was an IRQ conflict