Hello @HappyUser

yes, that should solve the issue of how to power off (and back on) the SIM7080 unit (or any other unit for that matter).

Thanks
Felix

OK, thanks.

Steve

Thanks. I already have got UnitV2, UnitV (both OV7740 and OV2640) for evaluation. Do any of the K210 based UnitVs have built-in Wi-Fi's? It would be strange if they don't because once you deploy them in the field you want some sort of network connectivity and would be odd to use a controller with each one of them to go along (as I need multiple Units to be deployed) - keeping aside costs and looking at it purely from ease of use.

With UNITV2, it's very easy to work with as its simply a SBC with linux but the one I received gets really hot (higher temperatures: 70+) within 5-10 minutes of operation so would prefer not to use it for any real world application.

I think the unit is defective. Interesting, because other things work: display, program w/ UI Flow, etc.

I tried several M5Stick, M5StickPlus, M5StickPlus 1.1. They all work. Only the initial M5StickPlus 1.1 has this issue. And BTW, it behaves similarly when connected to a servo HAT.

@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!