@konstantint Thankyou for doing that! very useful.

I see your config puts the reset pin definitions directly in the correct driver sections for the touchscreen and LCD so that those driver handle them correctly. I think this is better than doing it separately the way I suggested :-)

@felmue Thank you for doing the test :-)

I guess this simplifies things for anybody writing a driver; but does prevent people having fun-and-games with under/over clocking the camera module.

I think it also means you cannot 'stop' the camera, which may be problem for extreme power saving. But I suspect the reset pin can be used to halt the module too.

@MurzikYEET I think that you cannot do this if you want the firmware to run while the device is on. The way all computers work is they load the program into RAM and then run it from there. The firmware just tells the computer what to do (in this case, open boot the device and then run the python file).
I believe you can't flash two sets of firmware from M5Burner anyway because each time, it erases the whole device before starting again.
With esptool the same applies. It can't load firmware into the RAM. What it does do is load the stub loader which helps the device and esptool install faster.

However there is a way to do it. I myself am not familiar with it but I believe that you can create OTA slots that store firmware in different slots on the device and then you can boot into different firmware.
Here is documentation on OTA: Espressif Docs
Hope this helps,
RPi

I tried the following code:

import os, sys, io import M5 from M5 import * from unit import KeyUnit from usb.device.keyboard import Keyboard from usb.device.hid import KeyCode keyboard = None key_0 = None def key_0_wasClicked_event(state): global keyboard, key_0 keyboard.set_keys(KeyCode.A, 0, 0, 0, 0, 0) def setup(): global keyboard, key_0 M5.begin() keyboard = Keyboard() key_0 = KeyUnit((1, 2)) key_0.setCallback(type=key_0.CB_TYPE.WAS_CLICKED, cb=key_0_wasClicked_event) def loop(): global keyboard, key_0 M5.update() key_0.tick(None) if __name__ == '__main__': try: setup() while True: loop() except (Exception, KeyboardInterrupt) as e: try: from utility import print_error_msg print_error_msg(e) except ImportError: print("please update to latest firmware")

And I got the following error:

Traceback (most recent call last): File "main.py", line 5, in <module> ImportError: no module named 'usb'

So the usb module is not present in the firmware.

Is that on purpose, or is this a bug? Is there a way to add the library?

@RPI25 how to fix this errors??0b1875b3-50cb-4abd-8763-a858b84ed8d5-image.png

Hi,

In my application the m5paper goes to deep sleep and should wake after 5 minutes. Sometimes it appears to hang at startup and I also get a series of these messages:

[W][Panel_IT8951.cpp:258] _wait_busy(): [Panel_IT8951] wait_busy: timeout

As @felmu suggested it can be a pullup issue.

In M5GFX.cpp the busy pin is configured with:

lgfx::pinMode(GPIO_NUM_27, lgfx::pin_mode_t::input_pullup); // M5Paper EPD busy pin

However in Panel_IT8951.cpp (Panel_IT8951::init(bool use_reset)) the busy pin is configured with

pinMode(_cfg.pin_busy, pin_mode_t::input);

So it looks like the pin is incorrectly reconfigured and the required pullup is missing.

Now how can I override this behaviour in my application without having to modify the M5GFX.cpp file?

(I am using the Arduino IDE with M5GFX 0.2.17 and M5Unified 0.2.11.)

regards,

Willem-Jan

@mrconstanti,

I found on Win 11 don't work really the USB / Serial driver from M5Stack.
I found after some own Trouble with can't find device the driver developer with an update driver also for Win 11. (Driver year 2025)

I test, unknown device still exist, but I think with Arduino IDE can work, until now my own project stopped with some other errors, so I'm not sure to 100% but if help other and you.

wch-ic.com

Kind regards
Chris

I fix the problem by remove condensator C9
audioModuleFix.png

https://youtube.com/shorts/OJ2RSZR5Y94?si=I5c_K-Tsh-rh9QJC