@m5stack

Hi, I have two M5Stick-Cs purchased in the same lot, one succeeded in updating this firmware, the other failed. The error display is as follows. Is there any countermeasure?

% ./Updater_FW20200422

==================== M5 Serial Converter Firmware Updater ====================

FW Version: ft232_OD_20200422
:
:

==========================================================================

Press enter to continue . . .

Detecting M5Stack products.
Find M5Stack products.
Kernel driver deteched.
Apply magic success.
Waiting for device in DFU mode...
Find M5Stack device in DFU mode.
Traceback (most recent call last):
File "m5stick_firmware_upgrader_OD_20200422.py", line 97, in <module>
File "site-packages/usb/core.py", line 869, in set_configuration
File "site-packages/usb/core.py", line 102, in wrapper
File "site-packages/usb/core.py", line 148, in managed_set_configuration
File "site-packages/usb/backend/libusb1.py", line 794, in set_configuration
File "site-packages/usb/backend/libusb1.py", line 595, in _check
usb.core.USBError: [Errno None] Other error
[6711] Failed to execute script m5stick_firmware_upgrader_OD_20200422
%

We may be able to identify this revision by the serial number specified on the package. Mine seems to be a lot manufactured in June 2020.

Most of the pin headers that I can easily obtain have a contact length of 6 mm. However, it seems a bit too long for the pin socket on the bottom of ATOM.

What is the recommended contact length based on ATOM's design?

Is there a concern that the socket on the ATOM side will be damaged by continuing to use it with a gap as shown in the attached photo?

@world101 Thanks for nice link to inside shots! Certainly it says V1.0. On the other hand, I compared the appearance such as stickers, but I could not find any difference.

Thank you for establishing the ATOM category.

Please tell me if the sticker on the back is EXACTLY the same for my Echo and your Echo. If possible, also the version of the PCB inside.

@ajb2k3 , Thanks for your interesting.

1st, open the confirmation link with Safari on iPhone -> nginx 404
2nd, open the confirmation link with Safari on macOS -> nginx 404
3rd, open modified HTTPS link with Safari on macOS -> Confirmed (reached to 200)
After that, open both the original HTTP link and modified HTTPS link with any -> invalid token (reached to 200)

Umm. Even if I try it now, I can't reproduce it. At that time, I was in trouble because I couldn't break through 404.

The URL in the email to confirm your account email address is incorrect. Since HTTP is specified, it leads to 404 Not Found. Shouldn't HTTPS be specified?

Hi, I've heard rumors that the ATOM Echo has an early version and a modified version. If so, is it possible to tell from the appearance of the package or body? Also, is there a way to know using software as a workaround? If nothing can be done, is there no choice but to open it and check it with a tester?

The fix I'm hearing is eliminating the mismatch between speaker ratings and amplifier output. I would like to know if there are any other corrections.

Anyway, I want the ATOM category under PRODUCTS.

The error has been solved myself.
It seems that the baud rate 921600 does not supported by M5StickC.
1.5M might be best by modified "boards.txt."