This is not true.
The M5Stack ESP32 Camera Module is using a OV2640 with a "hack" of the I2S interface because this ESP32 subsystem is able to DMA for the data. The camera control is over the Serial Camera Control Bus (SCCB) protocol that is using I2C routines. Additionally the GROVE connector makes the I2C accessible for peripherals.
The M5Stack ESP32 WROVER with PSRAM Camera Module additionally has the BME280 and MPU6050 on a second I2C.
But who knows? Still there are no up to date schematics. I mean something with the actual wiring of the PCB. Not the overview picture. Which is btw only posted on Aliexpress:
My opinion: It is a silly idea to share the camera VSYNC and SIOC with the BME280 and MPU6050.
Actually it does not have the BME and MPU (I have had this convo with m5stack and dissasembled it.
The MPU version is on its way!
The Grove is on a seperate I2C bus.
Ahhh I see, Buy hacing the I2S bus you gain the full duplex needed for the camera along with the other lines which allow you to use the same clock line but seperate data lines. @playthegame Cool didn't know that as Just been concentrating on running the two I2C buses. @M5Stack, can we get some clear up here over the configuration?
@jpilarski Hey, glad you are enjoying 7.1. Yes the remote function is a little buggy at the moment, I think it is to do with the url generated being too long. This issue will be solved once we set up a dedicated server for the remote function. Great suggestions, the SD function is definitely possible but it is a way off yet. Our priority right now is enabling save and upload of programs to the flow website. We will setup a Ui flow page on github mainly for bug tracking at this point but it would be good to see user created blocks in the future.
Look in your "downloads folder" (where ever you download files to)
You should see a strange file. When you open the file, there will be captured images in it.
I'm waiting on my MK2 camera (WROVER) to arrive to see what the difference in the 2 are.