If you are asking a question, please follow this template:
- My goal is:
To provision the Things on AWS directly (not using aws-iot-setup) or use an existing Thing key/certificate.
- My actions are:
Create the certificate and keys via the AWS console, attach a policy and a thing.
Download the files to the device (esp8266) and set the mos.yml with the correct values
- [“mqtt.server”, “12345.iot.eu-west-1.amazonaws.com:8883”]
- [“mqtt.enable”, true]
- [“mqtt.ssl_cert”, “aws-esp8266_12345.crt.pem”]
- [“mqtt.ssl_key”, “aws-esp8266_12345.key.pem”]
- [“mqtt.ssl_ca_cert”, “root-CA.crt”]
- [“aws.shadow.thing_name”, “esp8266_2518EA”]
- [“aws.thing_name”, “esp8266_123456”]
- [“device.id”, “esp8266_123456”]
- The result I see is:
[Apr 9 10:26:00.414] mgos_mongoose.c:66 New heap free LWM: 24408
[Apr 9 10:26:00.421] mg_ssl_if_mbedtls.c:35 0x3fff2cbc ciphersuite: TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256
[Apr 9 10:26:01.127] SW ECDH curve 3
[Apr 9 10:26:06.341] E:M 136 (18 blocks)
[Apr 9 10:26:06.343]
[Apr 9 10:26:06.344] Exception 29 @ 0x4000e1b2, vaddr 0x00000000
[Apr 9 10:26:06.347] A0: 0x4028764b A1: 0x3ffff540 A2: 0x00000000 A3: 0x00000000
[Apr 9 10:26:06.353] A4: 0x00000088 A5: 0x00000000 A6: 0x00000080 A7: 0x00000008
[Apr 9 10:26:06.359] A8: 0x3ffe83cc A9: 0x00000190 A10: 0x00000000 A11: 0x0000007c
[Apr 9 10:26:06.364] A12: 0x00000000 A13: 0x00000088 A14: 0x00000000 A15: 0x3fff1ae8
[Apr 9 10:26:06.370]
[Apr 9 10:26:06.370] (exc SP: 0x3ffff3a0)
[Apr 9 10:26:06.372]
[Apr 9 10:26:06.372] — BEGIN CORE DUMP —
[Apr 9 10:26:06.374] mos: catching core dump
If I provision via aws-iot-setup and replace the files with the generated ones it works ok.
The certificate/key generated via AWS console also work fine using another application.
- My expectation & question is:
I seem to have read everything on this and still cant get it to work (unless my googleFu is on the wane).
Just trying to get a tool to analyse the log dumps to see if that throws anymore light on the subject.