I'm trying to upload a new firmware on the unit roller connecting a ST_Link v2 to the SPI connector with STM32CubeProgrammer.

Roller SPI ---------------- ST_LinkV2 V --------------------- 3.3 G -------------------- GND C ------------------ SWCLOCK D ------------------ SWDIO O ------------------- NC

when the firmware si uploaded the unit roller works (display right boot image and information, led is on, button and encoder works and menu works too), but if I disconnect the SPI cable and I power the unit from grove or dc in 6/16v, the unit doesn't work(black display, led off, etc).

this is the .hex firmware used.

and this is the cube log:

22:11:59 : MASS ERASE ... 22:11:59 : Mass erase successfully achieved 22:11:59 : UPLOADING ... 22:11:59 : Size : 1024 Bytes 22:11:59 : Address : 0x8000000 22:11:59 : Read progress: 22:11:59 : Data read successfully 22:11:59 : Time elapsed during the read operation is: 00:00:00.019 22:12:36 : Opening and parsing file: ROLLERCAN.hex 22:12:36 : Memory Programming ... 22:12:36 : File : ROLLERCAN.hex 22:12:36 : Size : 94.38 KB 22:12:36 : Address : 0x08002000 22:12:36 : Erasing memory corresponding to segment 0: 22:12:36 : Erasing internal memory sectors [4 51] 22:12:37 : Download in Progress: 22:12:39 : File download complete 22:12:39 : Time elapsed during download operation: 00:00:02.735 22:12:39 : Verifying... 22:12:39 : Read progress: 22:12:39 : Time elapsed during verifying operation: 00:00:00.645 22:12:39 : Download verified successfully 22:12:39 : Memory [0x08000000 : 0x08020000] - Checksum : 0x011ED0C0 22:12:39 : RUNNING Program ... 22:12:39 : Address: : 0x08002000 22:12:39 : Application is running, Please Hold on... 22:12:39 : Start operation achieved successfully

this is the log of OB:

{ "deviceId" : 1128, "bitNameToValue" : { "RDP" : 170, "BOR_LEV" : 0, "nRST_STOP" : 1, "nRST_STDBY" : 1, "nRST_SHDW" : 1, "IWDG_SW" : 1, "IWDG_STOP" : 1, "IWDG_STDBY" : 1, "WWDG_SW" : 1, "nBOOT1" : 1, "SRAM_PE" : 1, "CCMSRAM_RST" : 1, "nSWBOOT0" : 1, "nBOOT0" : 1, "NRST_MODE" : 3, "IRHEN" : 1, "PCROP1_STRT" : 16383, "PCROP1_END" : 0, "PCROP_RDP" : 0, "WRP1A_STRT" : 63, "WRP1A_END" : 0, "WRP1B_STRT" : 63, "WRP1B_END" : 0, "SEC_SIZE1" : 0, "BOOT_LOCK" : 0 } }

If I power the unit from grove or DC in, I have 3.3v on SPI (V,G).

I tried to merge and burn a bootloader.hex too but no joy.

after uploading the firmware if I connect the grove cable of an atom lite running a i2c scanner code, I can see 0x64 on serial monitor. I can also disconnect the SPI cable and the roller still works until a power cycle.

ideas??

tnks a lot!!

@maiknaef Hello.
I have same problem with AtomS3, nanoC6 and Atom lite and Din Meter.
However M5dial works fine. I tested Uiflow2.4.0 and 2.4.1.
It is strange because M5dial and M5Din meter are uses StampS3.
Sorry I have no idea at this moment, however hopefully it solved in future.

Dear @Steve-Mack @andrew.winton,
Did you solve the problem? I have the same issue with a Raspberry PI Zero W (no detection with "i2cdetect -y 1"). As I have 2 AIN4-20ma and 2 raspberry PI Zero W, I tried to exchange them but it is never detected. Other I2C devices are working well.
Thanks,
Seb

from M5Docs:
ENV Pro Unit is an environmental sensor that utilizes the BME688 sensor solution, supporting the measurement of various environmental parameters such as
volatile organic compounds (VOCs),
indoor air quality (IAQ),
temperature, humidity,
and atmospheric pressure.

env pro.JPG

@felmue
Thanks for replying. I'm currently using UIFlow2 v2.3.7. If I remove the "GET" commands, as shown in the image, it works without displaying these values, obviously.

I'm using Core Basic with the latest version UIFlow2 v2.3.7. Could that be related?

6427e3b2-595e-4456-a647-1395a76d634d-image.png

But when I add a single "GET" command, this error occurs at startup.

b6971018-763d-4c4a-88ec-fcc4a5f7a333-image.png

0c33d82b-4dd9-4eec-bf80-15af19f49716-image.png

Thanks in advance for replying, I have several open messages and no one is answering.

well sorted it out by counting characters...however this will break if the preamble data changes length and i can't locate a spec for this protocol.

The UIFlow2 section of the online specs in m5.docs also just says 'coming soon' for UIFlow2....although it does actually exist (albeit undocumented....).

Is there another source for this documentation???

@adamm5

Well ChatGPT solved my problem....increasing the spreading factor to 11 has suddenly made everything work. Not sure why such a high SF would be needed between two devices on the same desktop? Will soon find out.

In the meantime, the following table gives some interesting perspective on the transmission time for a 19byte payload.

SF Symbol Duration Payload Symbols Total Symbols Airtime 7 1.024 ms 37 51.25 0.052 s 8 2.048 ms 37 51.25 0.105 s 9 4.096 ms 37 51.25 0.210 s 10 8.192 ms 37 51.25 0.420 s 11 16.384 ms 37 51.25 0.839 s 12 32.768 ms 37 51.25 1.678 s

@kuriko A follow-up question, if I may...

Can an M5Stack controller accept power from the Grove connector? If I connect an Atom-Lite to a Roller485Lite via the I2C port and supply 12V to the Roller485 through the PWR485 port, will this provide power to the Atom-Lite? There appears to be a path through the schematics...

TIA

Martin

press and hold red button then slide it out

@djairguilherme said in New ESPHome Support for M5StamPLC:

Thanks ChirpyChips aka @Beormund.

I used your implementation with ESPHome to interface with a Schneider Phase Inverter. I wrote a tutorial on Hackster.io.
https://www.hackster.io/nicolaudosbrinquedos/m5stack-stamp-plc-as-real-plc-3ec3ed
Thank you very much for your work!

@djairguilherme Nice! At some point I really do need to utilise ESPHome's RS-485 support to expose the M5StamPLC's PWR-485 interface as a Modbus slave. It's on my TODO list.

I don't recommend this product. This is what it looks like after being in a barely damp plant overnight! No wonder I couldn't get any readings! IMG_9390.jpg

It sounds like the Core2 isn’t maintaining a stable connection with UIFlow. A few things to try:

1. Reflash the firmware with the latest stable UIFlow_Core2 version using M5Burner, and ensure "Internet Mode" is selected. 2. Double-check that the Device Name/API Key in UIFlow matches what's shown on the Core2 screen. 3. Disable any firewalls or antivirus that might block the connection. 4. Try using UIFlow Desktop IDE instead of the web version for better stability. If issues persist, test on another PC to rule out local system conflicts.

Hello @wrs642

from this and your previous post I would guess that there is no battery connected or it is not charged (enough).

Thanks
Felix