Posts made by felmue

Hello @RubberDuck

I can confirm the shark fin like signals on my M5CoreS3. I am no I2C expert, but I think they might be marginal and so maybe just barely working on one M5CoreS3 but not on the other when talking to AXP2101. Maybe a stronger pull-up resistor might help?

BTW: I checked the I2C SCL line on an M5Core2 and it is much more rectangular, e.g. much more like I would expect it.

Thanks
Felix

Hello @RubberDuck

just curious, any particular reason you did not read out register 0x22? It is my understanding that this register determines whether the system powers off or does a reset when writing 0x01 to register 0x10.

Also curious, when the issue happens, is the battery full or close to be fully discharged?

The register values of the bad AXP2101 seem to be random. Have you tried to lower the I2C bus speed?

In my experience seemingly random issues often stem from bad / not sufficient power supply. Is the battery in good shape?

Thanks
Felix

Hello @scroggyg

I modified my test program to use internal I2C, did a i2c scan w/o ExtIO2 connected and with it - there seems to be no i2c address conflict.

For me ExtIO2 works either connected to port A or to internal. What I noticed though is that I need to wait (after powering up M5Tab5) for the UIFlow2 screen fully being loaded before running the program.

If I do not wait long enough I occasionally see a crash too.

Thanks
Felix

Hello @scroggyg

here are the result of my tests with various firmware versions:
v2.3.5 : running program -> crash
v2.3.6 : running program -> crash
v2.3.6 hotfix : running program -> ok
v2.3.6 hotfix2 : running program -> ok

Note:

• I had no issue burning an running any of the above firmware versions.
• I run all my tests with no battery attached.

You can find the program I used in the UIFlow Project Zone: M5Tab5_ExtIO2_Test_UIFlow2.3.6

Thanks
Felix

Hello @Handcannon

M5Tab5 UIFlow v2.3.6-hotfix solves the no power on port A issue.

Thanks
Felix

Hello @HappyUser

I found an SX1276 LoRa in my box of electronics and wired it up to an M5Core2 using the same GPIOs as the LoRa module is using.

Then I tested with the stock LoRaReceiver example (adapted to M5Core2) and with some added output to the display successfully. E.g. both LoRa and display worked fine together. You can find my example here.

What do you mean by restart? Powering up M5Core2 or pressing the reset button or after uploading new firmware?

How are you powering the M5Core2? Maybe there is a power supply issue?

Thanks
Felix

Hello @HappyUser

you do not need to explicitly call M5.Power.begin() as it is already called from within M5.begin().

Well, as soon as you call M5.Display.startWrite() it will assert the display CS line and occupy the SPI bus for the display until you call M5.Display.endWrite(). In other words, between those two calls the SPI bus can only be used for display updates.

Question: why are you calling M5.Display.startWrite() explicitly at all? You should be able to write onto the display by calling M5.Display.println() or similar without first calling M5.Display.startWrite(). Doesn't that work for you?

Thanks
Felix

Hello @HappyUser

I think you are missing the M5.begin() in setup(). Without that call, the 5 V isn't turned on, e.g. the LoRa module is not powered. (At least on my M5Core2 5 V is not present without the M5.begin() call.)

And I think the RST_PIN should be GPIO 26 (as it hasn't changed from M5Core to M5Core2).

Note: I do not have this LoRa module so I cannot test myself.

Thanks
Felix

Hello @eleonorafontana16

just to clarify - your current setup (controlling 2 servos using GPIO25 and GPIO26) doesn't include the GoPlus2 module anymore, correct?

Thanks
Felix

Hello @HappyUser

I mean this arduino library.

Maybe this article helps.

Note: I am using Visual Code (and not Arduino IDE).

Thanks
Felix

Hello @HappyUser

hmm, the button sample code works fine as it is for me. Tested with M5Core2 and M5Core2 v1.1.

For reference: I was using Arduino library v3.2.1, M5Unfied v0.2.8 and M5GFX v0.2.13.

@henryCharm : you are correct, the line M5.Display.setEpdMode(epd_mode_t::epd_fastest); is only used / required for ePaper however it is simply ignored on non ePaper displays. So yes, it would be cleaner to remove the line, but I don't think it does any harm. I think the reason it is there is so that the example works on different M5Cores.

Thanks
Felix

Hello @gscorrea

using the latest library versions, e.g. M5GFX 0.2.13 and M5Unified 0.2.8 I can build M5Dial firmware with no error.

Thanks
Felix

Hello @Handcannon

yes, I see that too. It seems that the latest versions (2.3.5 and 2.3.6) have power to port A disabled. E.g. port A has no power.

Please find my example in the UIFlow2 Project Zone which manually turns on power to port A: M5Tab5_Enable_Ext5V_EnvIV_Test_UIFlow2.3.6

I created an issue on github for this issue.

Thanks
Felix

Hello @BR123456

the trick is to only set a flag in the button clicked callback function and then in the main loop do whatever needs to be done when that flag has been set.

I created an example of what I mean in the UIFlow Project Zone: M5Tab5_Count_In_Loop_Test_UIFlow2.3.5

Thanks
Felix

Hello @eleonorafontana16

I don't know whether it will affect one or the other or both long term. The fact that both use the same I2C address is like talking to two people with the same name. Some answers might get lost due to both people responding at the same time with different answers.

Thanks
Felix

Hello @aleekwen

I am testing with the speaker sample code in M5Unified and then force a crash. And yes, after the automatic reboot the speaker is silent. However a short press on the power/reset button brings the speaker back.

The only thing I noticed, is, that when the battery is attached I sometimes need to reset M5Tab5 twice before the speaker comes back.

BTW: after a reboot the call to M5.begin() automatically enables the speaker; there is no need to call M5Tab5.SetSpeakerEnable(true).

Thanks
Felix

Hello @Schwibach

while using UI designer to draw a rectangle works fine, getting the rectangle's parameters (e.g. x, y, ...) is not implemented (at least I couldn't find any get functions for rectangles).

That said, I created a Micropython example which uses a Button class to draw the buttons, labels and check for touch. You can find it here. It's not using the UI designer nor is it using blocks but it should give you an idea hopefully.

Thanks
Felix

Hello @eleonorafontana16

Unfortunately M5Core2 and GoPlus2 are not compatible. From the GoPlus2 shop page:

Note: This module has an I2C address conflict with the touch screen of the CORE2, so it cannot be used together.

Thanks
Felix

Hello @nvko23

after opening my M5StamPLC I found that the RTC battery is located at the underside of the CPU board. It is soldered to the board. So yes, I'd say it is replaceable, but the proper soldering tools are required.

BTW: the RTC battery in my M5StamPLC seems to be completely flat as I measure 0 volts.

Thanks
Felix

Hello @nvko23

well, according to the schematics, SYS_INT is connected to multiple ICs, including PI4IOE5V6408, RX8130, AW9523, LM75 and INA226.

The required pull-up resistor (5.1k) is R10 - it's drawn near PI4IOE5V6408 on the CPU schematic.

Edit: I ran some tests - this is what I found:

• Without any connections to Inputs 1 - 8 SYS_INT is high (as expected).
• However if any input is asserted while powering up M5StampPLC SYS_INT goes low even though AW9523 interrupts are disabled during its initialization. See here.

Adding _io_expander_b->resetIrq(); in the M5StapPLC library after disabling interrupts changes SYS_INT back to high.

My conclusion: AW9523 by default at power up has interrupts enabled and any interrupt sticks even when interrupts are disabled later on.

Thanks
Felix