Hello @Kenzo

I think you might have misread my post. I do not have a Tube Pressure unit so I cannot test this case, sorry.

Thanks
Felix

Hi guys

I tested M5Tab5 (running UIFlow 2.3.1) with all the units I have available and most of them worked ok.

Note: I also got the i2c driver install error, but it didn't cause I2C to actually fail.

GPIO units

• SSR - ok

I2C units (bus speed 100k)

• Env III - ok
• Env IV - ok
• ExtIO2 - ok
• Color LCD - ok
• OLED - ok
• PaHUB - Env IV - ok

I2C units (bus speed 400k)

• PbHUB - ok
• 4Relay - ok

Unit Gesture and AMeter did not work for me with either bus speed 100k or 400k. M5Tab5 seemed to hang in setup and a hard reset was required.

Thanks
Felix

@montanaman
Generally speaking, this situation is because the UiFlow2 driver does not support this Unit

Hello @foofera

hmm, the I2C communication working in setup() suggest the wiring is ok.

Are you using pull-up resistors on intSCL and intSDA?

Have you tried lowering the I2C bus speed?

Have you tried to put a delay between issuing I2C commands in your loop() code?

Have you tried to control a different I2C slave device from your STM32? Does that work in both setup() and loop()?

Thanks
Felix

@Devigan
which demo code are u using? i suspect it's the library version problem

@Poppa-Large Did you try erasing and writing the Core2 firmware and not the firmware for another different core?
Blank screen usually means you wrote the wrong firmware or you wrote some code that doesn't use the screen.

@zism5
post your code will be more helpful

@Handcannon It is not a computer, it is a microcontroller and so only one firmware can be burned at a time.

@Handcannon We are not telepathic can you explain what your problem actually is?

@Handcannon what are you talking about