Currently, I have not been able to get -TinyGPS++ - examples working. The FIRE has a serial connection and is reading the GPS sentences but is not printing data because the 'valid data' test = FALSE.
I have successfully run the -TinyGPS++ - examples on Arduino UNO and DUE no problem. Can any one help with my issue?
If I have well understood, from the schematics available, the M5GO Base has its own IP5306. If so, there are two IP5306 devices that must coexist (the one in the Fire Core and the one in the base M5GO). Can you help me understand how this coexistence works? Do both IP5306 charge the battery at the same time? If I'm right only the IP5306 on the Fire Core has I2C functionality, is it true?
@mawg Both the raspberry pi and M5Stack have 3.3v io pins and 5v supply pins.
Most M5Stack units and modules have their own 5v >3.3v regulator but in.
Take a look at my wip book here.
@ajb2k3 said in Application M5Stack Demo-Board (Factory-Test):
Try deleting the circle at the beginning of the line.
I've already done that, erased the circle in front of the bracket.
But nevertheless it runs only up to function 6!
Just found out, that I get the following error message working with Arduino 1.8.9 when I load the code into Arduino !!
Error message : "MFRC522_i2C.cpp" contains unknown characters. If the code was created with an older version of Arduino, you might want to use Tool -> Correct Coding & Reload etc. etc. to correct the code.
But even afterwards the program runs only up to function 6!
@krso said in M5stack STEP 3D files:
Would it be possible to add STEP 3D models to all products. It's very convenient for project planning.
Now (last month) JTAG debugging went free on PlatformIO/Visual Studio Code and Andreas Spiess did a YouTube video on debugging with the Espressif ESP-prog board JTAG interface for the ESP-32.
First thing I did was check into M5Stack Core and found it wouldn't work.
Another version with IO12-15 available for JTAG inline debugging would be necessary and appreciated.
@staind87 said in Problems with the I2C Grove Interface:
Hello dear M5Stack Team,
I come from Germany and unfortunately my English is not perfect.
I hope you can understand me.
I think the 5MStack product line is really good. It's all in a nice case and the products are well made.
Now I unfortunately noticed a few things which are not so beautiful, but maybe I didn't see it correctly.
It's about the I2C Grove interface. I think there are some hardware design bugs.
Unfortunately I can't see the I2C Grove interface in the schematics of the M5Stack.
Therefore I assume that SCL and SDA from the Grove interface are directly connected to the ESP32. (without logic)
Now to the problems:
A level shifter is missing in the M5Stack.
If I look at the schematics of the sensors (e.g. the ENV unit) I can see that the pull-up resistors in the sensor modules are connected to 5V (VCC).
This means that 5V is connected to the inputs of the ESP32. The ESP32 only supports voltages up to 3.6V. The 5V voltage could demage the I2C inputs of the M5Stack.
With a level shifter in the M5Stack this problem could be solved.
The pull-up resistors are built into the sensors.
Unfortunately the pull-up resistors are built into the sensors. This is very unfortunate because if I use the Unit Hub to use several sensors then I have several pull-up resistors parallel to my I2C bus.
The total resistance of the pullup is getting smaller and smaller due to this.
So maybe bigger circuits can't work anymore because the pullup resistance is too small.
Why is the pull-up resistor not installed centrally in the M5Stack?
I hope you don't misunderstand me. I love the M5Stack, but I noticed these problems.
Greetings from Germany
I recently have problems with using both ENV unit and TOF unit on a I2C hub on M5StickC. Using just 1 one of them at one time works. I wonder if this is related to what you discovered?
Also, would using a PaHub solve the problem?
Thanx a 1,000,000 for taking the time to help me.
Oops, my bad! I had also been playing with a Heltec 32 WiFi kit, and forgot to change the board (how embarrassing).
I am still indoors, so will either need to use a battery or, perhaps, sit by the window to test GPS.
At the moment, after a few seconds the software reports "Brownout detector was triggered" over serial, then reboots. I will investigate that & ask a new question if I can't solve it. Sorry to have taken your time.