@felmue said in M5-TOUGH / unable to change display brightness:

M5.Axp.SetLDOVoltage(3,3000);

Hi Felmue!

That one works, thanks a lot!

Really confusing that there is a PWM backlight LED mentioned in the library which does not work. And that the usage of SetLcdVoltage is inconsistent between the Core2 and TOUGH.

On Core2 the LcdVoltage changes DCDC3 (@param number 0=DCDC1 / 1=DCDC2 / 2=DCDC3 ) which is connected to LCD_BL. For the TOUGH on the other hand DCDC3 is unused and they used the LDO3.

So maybe they should simply change the line SetDCVoltage(2, voltage); to M5.Axp.SetLDOVoltage(3,voltage); or maybe even better introduce a new function SetLCDBacklightVoltage(...) in their library.

Thanks to all for your hints.

No it was from this place:
https://github.com/m5stack/m5stack-linux-dtoverlays/tree/main/examples

The issue is actually a dependence missing from the install instructions (user writeup error) fixed with adding the following command:

sudo apt-get install qtdeclarative5-dev

before running

cmake .. && make

@themusicman, I checked out your code because my graphics are rather boring/default.
I will try implementing some of your examples!

@ajb2k3 said in How do I enter BOOT mode on M5Core2: Wrong boot mode detected (0x0)! The chip needs to be in download mode:

@themusicman This means that something else in OSX is access the USBport via a terminal preventing M5Burner from being able to access the port.

Please make sure only M5Burner is running and that no other terminal software is running.

I tried on my MacBookPro (original issue was on iMac) with no other serial terminal software running, exactly the same issues unfortunately. I have now returned the M5Core2 device back to thePiHut and am awaiting a replacement.

Thanks for your support though @ajb2k3 - it is much appreciated.

@kk likely 0-60, as is the standard core basic and core2.
LCDs malfunction and possibly freeze damage below 0.
Cannot withstand condensating environment.

I have been able to get it working with the correct wiring using the grove port in a Core Basic Gray unit.

No I will start to use the io pins in the bottom of the unit so I can use the grove port for other things.

thanks for all your assistance.

Thanks to both of you who replied, I got it working with your help!

The problem was the port I was connecting to. Using a USB-A to USB-C cable, connected to the Mac Mini M1's USB-A port got it to work and the device now shows up as /dev/tty.wchusbserialXXXXX

Very happy about this, just in time before the weekend. ;)

Thanks again!

@taako What country are you in and what are the wiring regulations?
you want a waterproof and wether resistant box along with cable glads for the power cable which prevent the ingress of water and critters.

@holofloh You weren't lying... Great results with M5Stamp C3

If anyone comes across this thread who are also disappointed by their generic WROOM-32 modules. Just buy the M5Stamp C3, they aren't much more (actually the same price when compared to the generic WROOM-32 modules on amazon!!) and they made my phone RSSI go from -80ish to -60 at the same distance and lower transmission power! My Watch transmission power i kept the same but it went from -85 to -60ish as well! That's a truly insane gain for such a small little thing. The generic modules trace antenna just doesn't cut it!

Plus they have a fun RGB LED you can configure!

I'm convinced, I'm going full M5Stamp!

At a glance I would say commenting out noInterrupts() and interrupts() is the correct thing to do. Can anyone tell us why are they even there?

The purpose of noInterrupts() is to prevent interrupt handlers from running in the middle of a critical section of code. But this makes no sense -- we are already in an interrupt handler here, where protection from other interrupts is already in effect until the function returns. At least that's the case for other Arduino microcontrollers -- admittedly, I haven't coded much for ESP32. Someone say something if I misunderstand this here.

Furthermore, setting a byte size variable to a constant value like 1 isn't the sort of thing that counts as a critical section of code that would ever need noInterrupts() in the first place.

I say it's safe to comment these two lines out and then I raise the question why were they ever there.