Posts made by felmue

Hi @Kris

that is entirely up to you - pin0-4 are just variables.

In UIFlow use the first statement to initialise the desired GPIO (0-36) to be used with one of the 5 variables (pin0-4).

MicroPython example: variable pin0 is used for GPIO18:

pin0 = machine.Pin(18, mode=machine.Pin.IN, pull=machine.Pin.PULL_UP)

Cheers
Felix

Hello Rop

nice, now we already have two keyboard layouts (anybody working on Dvorak?).

I like your solution for uppercase letters and the caret handling is nifty - well done.

Cheers
Fexli

Hi @michaelblight

yes, that is to be expected. The M5GO CHG Base has it's own charger IC which is used in this case.

Thanks
Felix

Hello @michaelblight

sorry to hear. There is a fuse (labelled T200) in the M5Core Fire which might be the only thing that blew.

Thanks
Felix

Hi Van

thank you for the test application. I've added my test (using a finger) in the issues section. I think I have a stylus somewhere and when I find it I'll give it another go.

Cheers
Felix

Hello Jack

you are welcome and thank you.

You'll need to check the MPU6886 datasheet

There is a sleep mode bit (Bit 6) in register 107 (power management 1). When I read that register I get 0x01 which seems to be the default. To put MPU6886 into sleep mode I'd write 0x41 into that register like that:

import i2c_bus
i2c0 = i2c_bus.easyI2C(i2c_bus.PORTA, 0x68, freq=400000)
i2c0.write_u8(107, 0x41)

Thanks
Felix

Hello @koreanEggCoffee

yes, that is possible - I am powering my M5Atom this way.

However please note: There is no protection against wrong polarity so please be careful not to accidentally swapping 5 volts and GND.

I also suggest you disconnect the external 5 volts before connecting USB-C. Or in other words only connect one power source at the same time.

Please also refer to the M5Atom schematics which outlines the 5 volts connections between USB, 5v pin, Groove, LEDs and 3.3 volts regulator.

https://docs.m5stack.com/#/en/core/atom_matrix

Cheers
Felix

Hello @toddkrein

you are correct, there is no RTC battery backup in M5Stack Fire.

Please note: In sleep modes time accuracy might be affected depending on the clock source used.

Please also refer to:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32/api-reference/system/system_time.html

Cheers
Felix

Hello @M95D

interrupt functions need to be as short as possible, run from RAM and everything in it (e.g. every function you call from within) also needs to run from RAM. In your case only onTimer() is in RAM, but everything else is probably not. All this is causing the watchdog to trigger.

To solve the issue, you should only set a flag in the interrupt function and test this flag in the loop() function and then act upon it.

Try something like this:

#include <M5StickC.h>  //define M5StickC hardware components and functions
#define BUTTON_MAIN 37  //The main button pin number
#define SCREEN_TIMEOUT 10 //Screen-off timeout in seconds
hw_timer_t *timer;

volatile bool onButtonFlag = false;
volatile bool onTimerFlag = false;

void IRAM_ATTR onButton() { //Interrupt on button press => turn on the screen
  onButtonFlag = true;
}

void IRAM_ATTR onTimer(){  //Interrupt on timer => turn off the screen
  onTimerFlag = true;
}

void setup() {
M5.begin(); //Init M5
M5.Lcd.fillScreen(YELLOW); //Make screen yellow
pinMode(BUTTON_MAIN, INPUT_PULLUP); //Button GPIO set as input, pull-up enabled
timer=timerBegin(1,40000,true); //Init screen light timer, divisor 40000 => 0.5ms steps
timerAttachInterrupt(timer,&onTimer,true);  //Set screen light timer interrupt function
timerAlarmWrite(timer,SCREEN_TIMEOUT*2000,true); //Set interrupt to turn off screen after X timer steps of 0.5ms each.
timerAlarmEnable(timer); //Start timer for screen-off delay
}

void loop() {
  if(onButtonFlag) {
    onButtonFlag = false;
    detachInterrupt(BUTTON_MAIN); //Ignore more button presses
    M5.Axp.ScreenBreath(10); //Set screen light ON
    timerAlarmEnable(timer); //Start timer for screen-off delay
  }
  if(onTimerFlag) {
    onTimerFlag = false;
    timerAlarmDisable(timer); //Stop the timer.
    M5.Axp.ScreenBreath(0); //Set screen light OFF
    attachInterrupt(BUTTON_MAIN,onButton,FALLING); //Attach interrupt on button press => turn on the screen
  }
}

Cheers
Felix

Hello Jack

you could try the following to make GPIO36 floating:

p36 = Pin(36, Pin.IN, None)

Please note: I do not own a M5StickC Plus so I've tried above code on a M5Stack Fire. It runs without error.

That said, I don't think GPIO36 has internal pull-up or pull-down circuitry to begin with since the following code did not change the voltage reading at all:

p36 = Pin(36, Pin.IN, Pin.PULL_UP)

BTW: When I define a pull-up for let's say GPIO25 the voltage goes up to about 3.2 volts as I would expect.

For reference: https://docs.micropython.org/en/latest/library/machine.Pin.html

Cheers
Felix

Hey Rop

never resting - it seems. Very nice! Just tried it successfully with my old rotary phone.

Cheers
Felix

Hello David

wow, nice project!

Regarding power supply via 5v bus. There is a function called SetBusPowerMode() which allows to switch between internal 5v boost (default) and being powered externally, e.g. from 5v bus. Unfortunately it is broken and the pull-request I've posted a while ago has not been merged yet. If you're interested you can still give it a try:

https://github.com/m5stack/M5Core2/pull/10

Calling the function in setup() with input parameter set to 1 switches to external power and the 5v from the bus are taken to power the Core2. It also charges the battery.

e.g. M5.Axp.SetBusPowerMode(1);

Note: Without battery installed you'll need to modify the existing call to this function in void AXP192::begin(void) else the M5Core2 cuts itself off shorty after booting.

Greetings from Winterthur
Felix

Hi Rob

if you look into Power.cpp you'll see that the current already is set to about 400 mA:
https://github.com/m5stack/M5Stack/blob/master/src/utility/Power.cpp

void POWER::begin() {
  uint8_t data;
  //Initial I2C 
  Wire.begin(21, 22);
  // 450ma 
  setVinMaxCurrent(CURRENT_400MA);

are you calling M5.Power.begin() in your setup code?
Or maybe the current has been reduced due the the battery being close to full?

Cheers
Felix

Hi Van

no worries and thank you for the feedback. Glad to hear it's working and useful.

Happy Stacking!
Felix

Hi @JoaoB

not exactly what you are looking for but it will give you at least voltage and current of the battery:

https://github.com/m5stack/M5StickC/blob/master/examples/Basics/AXP192/AXP192.ino

Cheers
Felix

Hello Van

sounds like a plan - thank you. Glad to help out.

Cheers
Felix

P.S. I am very sorry for misspelling your name previously (fixed now).

Hi Van

you're very welcome. I don't have a partition map and so far I didn't need one. For the additional PSRAM I've added these two lines for M5Core2:

build_flags = 
    -DBOARD_HAS_PSRAM
    -mfix-esp32-psram-cache-issue

(I am not sure if the second line actually is really needed still, but it doesn't seem to hurt.)

Cheers
Felix

Hi Van

you could try to define two environments and use lib_ignore to only compile one of the two libraries, depending on the selected device:

[platformio]
default_envs = m5stack
;default_envs = m5core2

[env:m5stack]
platform = espressif32
board = m5stack-core-esp32
framework = arduino
lib_ignore = M5Core2

[env:m5core2]
platform = espressif32
board = m5stack-fire
framework = arduino
lib_ignore = M5Stack

Cheers
Felix

Hi Van

thank you for pointing that out. No worries, I've adapted the touch keyboard library to the new reality without Event object. I am happy you find the touch keyboard useful.

Have fun!
Felix

Hi @Rop

I think I've played with that register setting myself at one point in the past and I also did not see any difference in regard of the area under the circles. It will be interesting to see if that will be improved in one of the next M5Core2 hardware revisions.

Thanks
Felix