Posts made by Paulskpt

@Paulskpt Hi members, FYI I created a Version_2 of the source code of this repo.
Adding double type of use for the Grove Port A of the M5Cardputer: 1) I2C communication; 2) reading buttons of a M5Stack mini doublebutton unit. Further enhanced the functionalities of the M5Cardputer Arduino sketch.

@robski Update: from within an online Uiflow2.0 session I used the M5Burner. I choose to not to burn the v2.2.5 but the v.2.2.4 hotfix. And this went OK. The main page of the Uiflow2 on the M5PaperS3 is now showing MODE "Public" and ACCOUNT my account e-mail address.
See images.

Problem solved. I didn't find a place in Github/M5Stack where I eventually could create an issue. However, we are here in UiFlow 2.0.

Thanks for your assistance robski!
Paulskpt

@robski Thank you. I just flashed and registered a M5StickC-Plus2 with UIFlow2. It was recognised in online UIFlow2 session.

@robski thank you for your reply. After binding I flashed the UIFlow2 for the M5PaperS3. Then I opened uitflow2.m6stack.com, however, at that moment I had my PaperS3 connected to my desktop PC (MS Windows 11 Pro) via USB cable. I don't know if it makes a difference if the device is connected via USB or via WiFi. I'll go to make that check.

Additional info:
First, in the online Uiflow2.0 page I deleted the existing registration of the M5PaperS3, so M5Burner would go to ask me to bind this device to my account.
I reflashed UIFlow2 using M5Burner V3 (beta-win64) (I googled for an older version however I didn't find). During the burn process inside M5Burner I was asked to bind the deviced. I did and accepted the default option "Public". After a successful flashing I disconnected the M5PaperS3 from the desktop PC. I rebooted the M5PaperS3. I saw on the display of the M5PaperS3, main window, under "MODE": "Private" and under "ACCOUNT": "None".
I remember from using other M5Stack devices in Uiflow2, that it can take some seconds, after the device has connected to the M5stack server, to update its account information on the Uiflow2.0 webpage and on the device itself.
However, this time with this M5PaperS3 I saw no account info update. On the desktop PC I started a Uiflow2 session within a Chrome browser. When I clicked on the device info, the Uiflow webpage showed MAC-address, a TOKEN value, a device-ID and Permissions: "Public". On the M5PaperS3, main window, I saw that the info did not change. It showed the same data as I wrote above.
I created a short video of the boot process. In this video one can see that on the bottom line, left side, two icons appear. Left: a WiFi-icon. Right next to it, a Server-icon. Initially the Server-icon looks like what I interprete as "connected". A few seconds later this Server-icon changes. From then on the Server-icon has a "x" in it. This I interpreted as "disconnected from Server".
In the Uiflow2.0 webpage, the icon of the M5PaperS3 device is shown with a red dot and a red question mark ("?") inside of it. When I clicked on that logo, there appeared on the right-top of the UIflow2.0 window a pop-up message window saying "Error: the device type is unknown".
I don't think there is a WiFi problem with this M5PaperS3. Why? Because, after I had built and flashed uiflow-micopython firmware to this M5PaperS3, I created a MPY sketch that connected to a WiFi Access Point here in the house and have the device connecting to a NTP-server and ask for an NTP-datetimestamp which was received OK. Conclusion: the WiFi of this M5PaperS3 is working.
Sofar my response. I don't know what I can do more. Maybe create an issue on Github.
FYI here is a link to the video.
Regards,
Paulskpt

Hi, using M5Burner I flashed my M5PaperS3 (v1.2) with UIFlow2 v2.2.5. I binded this device in M5Burner to my account (being logged-in). However, when using the online version of UIFlow2 the M5PaperS3 is not recognized as if it was not binded. Also on the main page of UIFlow2 on the M5PaperS3 below the word "ACCOUNT" there is no information.
See the images
Anyone has an idea what could be the reason why a device binded to ones account is not recognized as such?

In the mean time I have cloned and built uiflow-micropython. I am now using the M5PaperS2 in Thonny.

For my M5Stack M5PaperS3 I built uiflow-micropython firmware,

MicroPython v1.24.0-dirty on 2025-04-12; M5STACK PaperS3 with ESP32S3

See also my post about this building experience.

While using the Thonny IDE, in the Shell. I issued the commands:

import hardware
display(hardware)

Nothing happened. I waited some minutes. Then I broke out with a KeyboardInterrrupt (<ctrl>C).

When I issue the command:

dir(hardware.RTC)

this results in:

['__class__', '__name__', '__bases__', '__dict__', 'datetime', 'init', 'local_datetime', 'memory', 'timezone']

when I enter the command "dir(board.sdcard)" this also results in ouput:

>>> dir(hardware.sdcard)
['__class__', '__name__', 'SDCard', '__dict__', '__file__', 'machine', 'os', 'create_sdcard_closure']

See the: screenshot.

Regards,
PaulskPt

Afterburner:
I was able to create and run a small display test script.
See the image

Hi, members!
I would like to share with you my experiences when, today, I tried to build MStack's uiflow-micropython:

First a little history of the past days, if you don't mind:
Two days ago I flashed my M5PaperS3 with UIFlow2 firmware, however I encountered various problems. One of them: notwithstanding the fact that I, from within M5Burner, I was logged in; did "bind" the M5PaperS3 successfully to my account, this fact was not recognized by Uiflow online. Also on the "</> CODE information" on the display of the M5PaperS3 under "ACCOUNT" was shown the text: "None". Beside this problem, inside UIFlow2 I find myself "caged". I cannot do what I want. I am missing functionalities.
That is why I "left" the UIFlow2 "road", so to speak.
Next I flashed the M5PaperS3 with the latest, standard version of micropython fw for an ESP32S3. Using this fw I ran into several problems like: trying to make WiFi connection or connecting to the SD-card.

Then I searched for a solution. I discovered that M5Stack published a repo called "uiflow-micropython" link.

After reading the README.md instructions, I decided to try to build this fw for the M5PaperS3.
Below the problems I encountered as the changes I made to finally be able to build the fw successfully: As a development platform I used a Raspberry Pi CM5.

The first build ended with an error that the module "future" was missing. When I tried to use pip to install this module, the result was:

paulsk@RPiCM5:~/uiflow_workspace/uiflow_micropython/m5stack $ pip3 install future
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: future in /home/paulsk/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages (1.0.0)  

To solve this I made a change to the file: ~/.profile I added these lines:

# Needed to make M5Stack uiflow_micropython for the M5PaperS3
if [ -d "$HOME/home/paulsk/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages (1.0.0)" ] ; then
  path="$HOME/home/paulsk/.espressif/python_env/idf5.2_py3.11_env/lib/python3.11/site-packages (1.0.0):PATH"
fi

then I issued the CLI-command:

source ~/.profile

to make the new PATH known.

Other changes I made to have a successful build and flash on the development platform were:
In the file: paulsk@RPiCM5:~/uiflow_workspace/uiflow_micropython/m5stack/Makefile
change the line: "BOARD ?= M5STACK_AtomS3"
into: "BOARD ?= M5STACK_PaperS3"
In the same file, below the line: "Device serial settings.", change the line: "PORT ?= /dev/ttyUSB0"
into: "PORT ?= /dev/ttyACM0".

next, executing the CLI-command:

make flash_all

finished OK. See the last lines below:

PAPERS3: m5stack/build-M5STACK_PaperS3/uiflow-cf61f739-esp32s3-spiram-16mb-papers3-v2.2.5-20250412.bin
esptool.py --chip esp32s3 --port /dev/ttyACM0 --baud 1500000 write_flash 0x0 build-M5STACK_PaperS3/uiflow-cf61f739.bin
esptool.py v4.8.1
Serial port /dev/ttyACM0
Connecting...
Chip is ESP32-S3 (QFN56) (revision v0.2)
Features: WiFi, BLE, Embedded PSRAM 8MB (AP_3v3)
Crystal is 40MHz
MAC: a0:85:e3:f0:ad:4c
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 1500000
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x00ffefff...
Compressed 16773120 bytes to 3585048...
Writing at 0x00272df4... (49 %)
Lost connection, retrying...
Waiting for the chip to reconnect
Connecting...
Uploading stub...
Running stub...
Stub running...
Compressed 16773120 bytes to 3585048...
Wrote 16773120 bytes (3585048 compressed) at 0x00000000 in 53.3 seconds (effective 2515.8 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

After these successful build and flash steps, I learned that it was not necessary to make changes to the files: CMakeLists.txt and Makefile. The instruction from M5Stack says:

The default board build the M5STACK_AtomS3 one, 
You can specify a different board by passing 
BOARD=<board> to the make commands. 
More BOARD type define is under 
m5satck/boards path.

As a final check, I connected the M5PaperS3 to a USB port of my desktop PC running MS Windows 11 Pro. Then I started Thonny. In Tools > Interpreter > Port I selected the correct COM port.

After pressing the "Stop" button of Thonny, the M5PaperS3 replied with:

MicroPython v1.24.0-dirty on 2025-04-12; M5STACK PaperS3 with ESP32S3
Type "help()" for more information.
>>> 
MPY: soft reboot
       _  __ _               
 _   _(_)/ _| | _____      __
| | | | | |_| |/ _ \ \ /\ / /
| |_| | |  _| | (_) \ V  V / 
 \__,_|_|_| |_|\___/ \_/\_/  V2.2.5

That's all folks!
Have a nice weekend y'all.
Paulskpt

Hi there members, I published a new repo on Github, which is an extension to the project in my last post of 9 days ago. repo

The README file of the repo explains.
Regards,
Paulskpt

@Knobsi Hi, your question is already two years old. I guess you'll have found the answer, however I just came across it today. I want to share with you an experience I had yesterday:

Suddenly I encountered a problem after upgrading the Arduino IDE from v2.3.4 to v2.3.5.

The board that I use is an M5 Atom Echo which has an ESP32-PICO processor.

After compiling and building a sketch, that compiled, built, and ran OK with v2.3.4,
It crashed after compiling and building and running with v2.3.5.

In the crash report I saw "DIO".
In Arduino v2.3.5 I checked the setting: > Tools > Flash Mode.
I saw that the Flash Mode was set for: "QIO".
After I changed the setting Flash Mode it to DIO, re-compiling and building, the sketch ran OK.

Regards,
@Paulskpt

Hi, FYI, I published a new repo on Github:
morse code

I am experiencing various unwanted anomalies with the M5Dial display:

1. at random momemts the display goes black while continuing to execute the sketch OK;
2. at random moments artifacts in the display. See the following to links:
   a) artifact image;
   b) artifact video

Question: anyone that has experienced similar problems with the display of the M5Stack M5Dial?

FYI, I just created a repo on Github, containing an Arduino sketch in which certain data is sent to a Google Sheets spreadsheet via a HTTP POST request to a Google Apps Scripts script. See repo.

I see that 50 people saw my post. Nobody out there that had similar experience or knows / saw about a solution?

I worked for weeks on an enhancement of an Arduino sketch that shows time data of seven different timezones in the world. At intervals the RTC is updated with a datetime stamp from an SNTP service server.
The past two weeks I was adding the functionality to send some data, like time sync time_t value to a Google Sheets spreadsheet. This all works OK.
The sketch ran a whole night, every 15 minutes sending data to a Google Apps Scripts script that adds the data to the spreadsheet.
In the sketch I have built the possibility to switch the display off (go to sleep) by using the command: "M5.Display.sleep()" and switch the display
on (awake) by using the command: "M5.Display.wakeup()". The switching off or switching on is done by holding an RFID card in front of the display. The sketch also has the possibility to switch the display on or off by touching the display (it is one or the other option. For now I use the RFID tag option). I used the Arduino IDE v2.3.3. for MS Windows 11. The Arduino IDE compile and build reports :

Sketch uses 1190657 bytes (90%) of program storage space. Maximum is 1310720 bytes.
Global variables use 53384 bytes (16%) of dynamic memory, leaving 274296 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.5.1
Serial port COM6
Connecting...
Chip is ESP32-S3 (revision v0.2)
Features: WiFi, BLE
Crystal is 40MHz
[...]
Wrote 1191024 bytes (721826 compressed) at 0x00010000 in 8.6 seconds (effective 1113.8 kbit/s)...

During the execution of the sketch calls to ESP.getFreeHeap(), result in values like: 265556 downto 264052.

After the display goes black, the sketch continues to execute fine, sending at the preset intervals its data to the Google Sheets spreadsheet.

Anyone that give me a clue to solve this abnormal behaviour?

I just uploaded a very short video impression to X. Here is the link: Post on X

I just uploaded a very short video impression to X. Here is the link: Post on X

FYI, I added functionality to make WiFi connection to a mobile phone. The WiFi credentials for the mobile phone are in the file secret.h. After reset the sketch will first try to establish WiFi contact with the mobile phone (when it's credentials are present in secret.h). If this fails, the sketch tries to establish WiFi connection with the fixed WiFi Access Point. In case of WiFi connection lost, the sketch will try to re-establish WiFi connection. The user will be informed on the OLED through brief messages.

Hi there, members. Last Saturday I received an ordered M5NanoC6. I ported the sketch that I created earlier for M5Dial and other devices as published in this forum. Amazing what fits in 4Mb or RAM!. The sketch is available on Github: repo.

@BoM_M5 I had the same problem today. In Arduino IDE v.2.3.3, BOARDS MANAGER, searched for esp32. Found "esp32" from Espressif Systems. It appeared that I had version "3.1.0 RC" installed. On Espressif's site on Github I saw that the latest stable version is: "3.0.5", so I downgraded to 3.0.5. Then I saw that the M5NanoC6 was available via: Tools -> Board -> esp32 -> M5NanoC6. After having selected this board, I saw also that: Tools -> CDC on Boot was "Enabled". I saw that there was here no more option "Disabled".
From this moment all Serial.print and Serial.println command worked as expected.