Failed to open AT socket (err:-12)

[oKruszek]

Hello,

I developed board with NRF9160 chip and I am facing issue with "at_cmd: Failed to open AT socket (err:-12)", i am not able to communicate with modem. It is not working with any of examples and also asset_tracker application. I am able to update firmware in modem and flash the chip. The same examples works fine on NRF9160-DK Board, the only difference i noticed is that the DK board has NRF9160_xxAA_REV1, and my board is with NRF9160_xxAA_REV2. Did anyone faced the same issue?

Regards,

Michal

[Øyvind]

Hello Michal, 

What version of NCS and modem fw are you running? The error message means:

#define	ENOMEM		12	/* Out of memory */

Kind regards,
Øyvind

[oKruszek]

Hello,

I am using the 1.1.0 modem firmware ( due to certification for Deutsche Telekom ) and the same version of NCS v1.1.0

Regards,

Michal

[oKruszek]

Hi,

I changed my project to use NVS 1.3.0, and it is not working either. But now i different way because the application hangs on:

bsdlib_init(); - when CONFIG_BSD_LIBRARY_SYS_INIT=n

With

CONFIG_BSD_LIBRARY_SYS_INIT=y

the application does not enter main() function

Regards,

Michal

[Øyvind]

Michal, 

The Mobile network operator certifications only mentions modem FW 1.1.0, and not the version of nRF Connect SDK (NCS). NCS has been tested with modem FW 1.3.0 but does not require it to work. You should also be able to run NCS 1.2.0. 

Please test using NCS 1.2.0 or NCS 1.3.0.

Thanks,
-Øyvind

[oKruszek]

Hi,

I tried with the NCS 1.3.0 and newest firmware, the response is above yours.

Thanks,

Michal

[Øyvind]

Are you getting any error codes?

Are you able to run a standard sample from NCS 1.3.0 on you custom board e.g. at_client?

oKruszek said:

I tried with the NCS 1.3.0 and newest firmware, the response is above yours.

 Did not see that comment while writing my previous response.

Kind regards,

Øyvind

[oKruszek]

Hi,

I just tried at_client, but i have ERROR on every AT commands, the output below:

*** Booting Zephyr OS build v2.3.0-rc1-ncs1 ***
Flash regions..Domain..Permissions
00 00 0x00000 0x08000 .Secure..rwxl
01 31 0x08000 0x100000 .Non-Secure.rwxl

Non-secure callable region 0 placed in flash region 0 with size 32.

SRAM region..Domain..Permissions
00 07 0x00000 0x10000 .Secure..rwxl
08 31 0x10000 0x40000 .Non-Secure.rwxl

Peripheral..Domain..Status
00 NRF_P0 Non-Secure.OK
01 NRF_CLOCK Non-Secure.OK
02 NRF_RTC0 Non-Secure.OK
03 NRF_RTC1 Non-Secure.OK
04 NRF_NVMC Non-Secure.OK
05 NRF_UARTE1 Non-Secure.OK
06 NRF_UARTE2 Secure..SKIP
07 NRF_TWIM2 Non-Secure.OK
08 NRF_SPIM3 Non-Secure.OK
09 NRF_TIMER0 Non-Secure.OK
10 NRF_TIMER1 Non-Secure.OK
11 NRF_TIMER2 Non-Secure.OK
12 NRF_SAADC Non-Secure.OK
13 NRF_PWM0 Non-Secure.OK
14 NRF_PWM1 Non-Secure.OK
15 NRF_PWM2 Non-Secure.OK
16 NRF_PWM3 Non-Secure.OK
17 NRF_WDT Non-Secure.OK
18 NRF_IPC Non-Secure.OK
19 NRF_VMC Non-Secure.OK
20 NRF_FPU Non-Secure.OK
21 NRF_EGU1 Non-Secure.OK
22 NRF_EGU2 Non-Secure.OK
23 NRF_DPPIC Non-Secure.OK
24 NRF_GPIOTE1 Non-Secure.OK
25 NRF_REGULATORS Non-Secure.OK

SPM: NS image at 0xc000
SPM: NS MSP at 0x20027aa8
SPM: NS reset vector at 0xd08d
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.3.0-rc1-ncs1 ***
The AT host sample started

AT
ERROR

[Øyvind]

Can you provide the full markings on the device you have? Have you had a review of your custom board? If not, I encourage you to register a support ticket to get a HW review. Have you verified that the board is sufficiently soldered? And that the layout is according to our reference (Hardware files) e.g. Thingy:91 or nRF9160DK ?

Does your application, based on NCS 1.3.0, work with the DK running modem fw 1.1.0?

[oKruszek]

Hi, 

Thanks for advice! I sent the our custom board for review, and also check if the NCS 1.3.0 works with FW 1.1.0 and it seems that everything works ok ( i checked connection, fota update, and interrupts )

Regards,

Michal

[Øyvind]

Great! While waiting it would be good if you can reheat you board to ensure that the SiP is correctly soldered.

Kind regards,
Øyvind