Topic: WolfMQTT PIC32
Two years ago I started testing WolfMQTT with PIC32 and you helped me solve the problem I was having connecting to a broker. The project was delayed and has now started up again.
I am using the wolfmqtt_demo example to communicate with different brokers using PIC32MZ. Without TLS it works fine but adding TLS 1.3 only works with the test.mosquitto.org broker.
The next step is to use it with an Amazon broker (AWS) that we use to communicate, I have the certificates and the private key in PEM format but it does not communicate successfully:
MQTT pub/sub demo has been started
>MQTT Task - Client Start: QoS 0, broker a3oellqp4u1niz-ats.iot.us-east-2.amazonaws.com
MQTT Task - run message: WMQTT_NETGlue_Initialize, res: 0
MQTT Task - run message: MqttClient_Init, res: 0
MQTT Task - run message: MqttClient_SetDisconnectCallback, res: 0
WMQTT_NET_GLUE Info: Started Connect
WMQTT_NET_GLUE Info: Connected Successfully
WMQTT_NET_GLUE Info: Start TLS
WMQTT_NET_GLUE Error: TLS Negotiation, occurred in func: WMQTT_NETGlue_Connect, line: 328,
MQTT Task - run message: MqttClient_NetConnect, res: -6
MQTT Task - MQTT cycle Failed in state: 6, error code: -6!
I don't know if I'm using correctly the certificates and the key in the project (I modify them in the erts_test.h file, I converted them to DER format). Would you know how to help me with this issue? Microchip support has not responded to me.