EG800AKCN - MQTTS certs parse fail

Hi team,

I am using EG800AKCN_LC quecOpen SDK. I have issues regarding mqtts connection. The private key Certs parsing fails. I have tried using the example code in the sdk also tired with my certs and domain. always fails at parsing.

SDK version: LTE01R07A16V03_C_SDK_A_SDK

Please find the logs with example program in the SDK

[STARTUP]<<<<>>>>> NO: 0

######## quec_system_init ok ########

LTE01R07A16_C_SDK_A V03

[QUEC APP]0x80395000 , 0x80000000

[U] fs Start Addr: 0x80395000

[U] mount successfully

Application Start…
23-06-2026 11:42:38.268 [RX] - AT command server ready!

Booting done

SW restart reason: Normal power on

23-06-2026 11:42:39.304 [RX] - 9fae ql_main entry

9fb0 appRegItemNum: 1

9fe1 app[0] (0x80322cdd) starting …

a064 app(0x80322cdd) started

[MQTT_EXAM][MQTTTest, 344] ========== mqtt test satrt ==========

[MQTT_EXAM][datacall_start, 301] wait for network register done

23-06-2026 11:42:42.979 [RX] - [MQTT_EXAM][datacall_start, 310] doing network activating …

23-06-2026 11:42:43.160 [RX] - [MQTT_EXAM][ql_nw_status_callback, 293] profile(1) status: 1

[MQTT_EXAM][datacall_start, 318] info.profile_idx: 1

[MQTT_EXAM][datacall_start, 319] info.ip_version: 0

[MQTT_EXAM][datacall_start, 320] info.v4.state: 1

[MQTT_EXAM][datacall_start, 321] info.v4.reconnect: 0

[MQTT_EXAM][datacall_start, 324] info.v4.addr.ip: 10.220.41.183

[MQTT_EXAM][datacall_start, 327] info.v4.addr.pri_dns: 117.96.122.162

[MQTT_EXAM][datacall_start, 330] info.v4.addr.sec_dns: 117.96.122.150

[FOTA_EXAM][SSLCtxInit, 595] *** failed !!! mbedtls_pk_parse_key returned -0x1

[MQTT_EXAM][MQTTEchoTask, 203] Return code from network connect is -1

[MQTT_EXAM][MQTTEchoTask, 280] ========== mqtt test end ==========

Can you please help me out with this

Hi @VimaladhithanR,

The demo is using “certs from buffer” mode and we’re expected to replace the hardcoded example cert.

When copying certs over, please make sure the format is consistent with the example cert or C language string format in general.

If you also use client key and cert, make sure to add them to your SSL config as well.

Hi Victor, Thanks for the reply.. This issue is fixed. looks like I have to enable MBEDTLS in the SDK