I wasn't aware of this forum, so my apologies if you didn't receive a solution right away.

To flash the factory firmware:

cd /<<PATH_TO_REPO>>/Core2-for-AWS-IoT-EduKit-Factory-Firmware
idf.py build flash

The tick/pop you hear is the sound of the device rebooting over and over since there's no firmware (after erasing the flash). It's not bricked.

All the links on the instructions as of a week ago all point directly to the us-west-2 region so you don't get taken to your default region by accident. Hoping that helps all users.

Since there appears to be a lot of interest in UIFlow, we will prioritize getting that going in partnership with M5Stack. I really appreciate the feedback.

@greenleaf, after doing some initial quick testing I found that many of the features are in parity, but things like the RBG LED is not functional because the pins are different from the M5Stack Fire. You might be able to take the existing M5Stack MicroPython library and update the pins to work with it.

The crypto module isn't supported. However, you can use the Adafruit Crypto library for the secure element.

M5Stack and AWS are working together to explore an option to deliver a MicroPython package specifically for the Core2 for AWS IoT EduKit.

I don't know if "Macintosh HD" actually part of your path. Your path is actually /Users/adambryant/Documents/PlatformIO/Core2-for-AWS-IoT-EduKit from what I can tell. You could try using the command pwd to get your current path.

The other reason I wouldn't think that was the root cause is because my personal laptop, work laptop, and our test instance in EC2 are all using different versions of macOS and they say "Macintosh HD" as the label for the OS drive and I haven't seen this issue due to that.

You should file a ticket with support to get a refund. I don't believe you should've been charged unless you were doing something else or using other features.

Hi Pradeep, different hardware will have different pin assignments. Your sensor should be connected to Port B if it's using the ADC and pinTempSensor should be set to pin 36.

@greenleaf I recently left Amazon. I don’t know what their plans are.

Your connection to your WiFi network with a password requirement is encrypted. Connection to AWS is also encrypted as AWS IoT does not support unauthenticated connections.

You should file a ticket with support to get a refund. I don't believe you should've been charged unless you were doing something else or using other features.

I don't know if "Macintosh HD" actually part of your path. Your path is actually /Users/adambryant/Documents/PlatformIO/Core2-for-AWS-IoT-EduKit from what I can tell. You could try using the command pwd to get your current path.

The other reason I wouldn't think that was the root cause is because my personal laptop, work laptop, and our test instance in EC2 are all using different versions of macOS and they say "Macintosh HD" as the label for the OS drive and I haven't seen this issue due to that.

I don't see that in our pricing matrix:
https://aws.amazon.com/iot-core/pricing/

Our pricing for simple usage to the message broker is generally connection minutes and messages transferred. We don't have location as part of that pricing.

I don't see the whitespace character. Have you tried just moving the project folder to a different location?

The Core2 for AWS has a pre-provisioned secure element that has a private key and paired public key to be used for registering the device to AWS and establishing a secure TLS connection. This not only prevents anyone from accidentally leaking the private key, but also enables a more systematic registration procedure. The provided script extracts the public key and signs it and sends it to AWS IoT. Ajb2k3's instructions won't apply here.

Using US West 2 when you're in Europe won't charge you any additional fees either. The only effect you should see is additional latency, but within the thresholds of what's allowed before triggering a timeout. We selected us-west-2 for this reason and tested in multiple countries.

The error code meanings from mbedtls' SSL APIs can be viewed here. So mbedtls_ssl_read returning a -0x7880 means /**< The peer notified us that the connection is going to be closed. */. So AWS is closing the connection.

Few things to check:

1. Did the registration script say it successfully registered the thing? If you re-run it, you should get an error at the end that says it couldn't register because the thing already exists.
2. Are you 100% sure you copied the endpoint address correctly? We've seen a few users either miss a character or add the quotation marks.
3. When you go to your AWS Console to view your things at https://us-west-2.console.aws.amazon.com/iot/home?region=us-west-2#/thinghub, do you see the device there? If you do and you click the thing name (e.g. 01xxxxxxx), then the certificates tab, you should see a long ID for the certificate that belongs to the device. If you click that certificate ID, then the Policies tab, you should see a policy that's attached to that certificate called Default.

If all of that checks out, the device should definitely connect. We know that the device is connected to WiFi because it won't try to connect to AWS IoT over MQTT otherwise. If the port was being blocked by the firewall, you should see a different error code. Let me know what happens there.

Sorry for the delayed response. We usually expect people going through the program assets to use the support links and post in the GitHub discussions.

Yes, there is a newer repository that has rust bindings for FreeRTOS/ESP-IDF by Espressif themselves:
https://github.com/espressif/rust-esp32-example

The blog that @flypeek shared is using that library with other libraries that seem to be able to access some of the peripherals on the device. Note that many of the features are not available or will need to be modified since the blog is on the older M5Stack devices. I would love to see a more robust port and example with all/most of the features working—would be a fun project. I'd love to promote it on the AWS IoT EduKit Content Library.

Seems like the message coming from the device over the serial port is malformed for some reason. Have you tried switching to a different cable?

Please see: https://github.com/m5stack/Core2forAWS-MicroPython for an example using the ATECC608 when establishing TLS to the AWS IoT Core MQTT broker.