Posts made by tokuhira

@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."

Please check your PLUS.

Would you like to create a sub category for M5 StickC?

Anyway, I have caught a following error at downloading with "ESP32 Pico Kit".
Do you have a counter measure about that?

-------->8---------------->8---------------->8--------
/Users/username/Library/Arduino15/packages/esp32/tools/esptool_py/2.6.1/esptool --chip esp32 --port /dev/cu.usbserial-AD52EECE41 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0xe000 /Users/username/Library/Arduino15/packages/esp32/hardware/esp32/1.0.2-rc1/tools/partitions/boot_app0.bin 0x1000 /Users/username/Library/Arduino15/packages/esp32/hardware/esp32/1.0.2-rc1/tools/sdk/bin/bootloader_dio_80m.bin 0x10000 /var/folders/bw/h67q3vkj4rl_2pdg5k3h5yqm0000gn/T/arduino_build_835267/FactoryTest.ino.bin 0x8000 /var/folders/bw/h67q3vkj4rl_2pdg5k3h5yqm0000gn/T/arduino_build_835267/FactoryTest.ino.partitions.bin
esptool.py v2.6
Serial port /dev/cu.usbserial-AD52EECE41
Connecting....
Chip is ESP32-PICO-D4 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, Embedded Flash, VRef calibration in efuse, Coding Scheme None
MAC: d8:a0:1d:69:5d:b8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...

A fatal error occurred: Timed out waiting for packet header
A fatal error occurred: Timed out waiting for packet header
-------->8---------------->8---------------->8--------

At first, I have tried to use TXD=16 and RXD=17. However, it conflicts downloading a bin by Arduino IDE. On this configuration, the program could be download without GPS Module. Later, stacked GPS Module works.

Second, I have tried to use TXD=0, RXD=15 and PPS=34. This configuration is similar to the article by @Rop, but 13 is reserved for PLUS Module. It works with GRAY, GPS, PLUS and FINGER (via PORT.B on PLUS). Thank you!

Wow! that is great help for me. I would like to follow the document about GPS Module by "So that means I started by carefully scraping away the traces between the solder bridges marked 16 and 17". Then, I will be able to use GRAY, GPS, PLUS and FINGER (via PORT.C on PLUS) together. Thank you so much.

@lukasmaximus , thanks for your replay both. I am on similar situation.

I am going to force the GPS module escape physically from UART2 to another pins. On the schematic you mentions, it is possible by selecting R1 to R2 or R3, R4 to R5 or R6 (I do not have a plan using PPS). I would like to soldering operation on them. However, R1 and R4 could not be found on PCB. Thus, I am looking for certain information of cutting point on PCB.

I am going to switch the UART port of GPS Module from UART2 to UART0 or to SoftwareSerial with GPIO 5 and 13. I have a image how to bridge on 1 and 3 or 5 and 13. However, I could not find R1 and R4 for cutting the binding of UART2. Is it done by cutting right side of 17 and 16 by knive?

PORTB(GPIO) and PORTC(UART) of the PLUS Module looks like that both the color of the connector and the silk printing are reversed.