This is plain ridiculous... All my sticks wont boot up. I opened one of them to see if here is any obvious damage such as exploded battery or something... Nope. They are just plain useless on arrival.
No matter what combination of buttons. I can erase and burn new firmwares using m5burner seemingly without a problem, if there is any it's in the burner.
The resistor "fix" is factory pre-applied. See pics.
No amount of usb charging with any cable or power sources will make them boot up.
Measuring the current with ruideng usb doctor always shows ridiculous values, fluctuating wildly... See pics.
How do you guys even get working devices given my experience...
I have purchased one from the same seller.
After i have updated the firmware to v1.3.2 the gyro sensor not working.
Tried to read the values from "Hardware ->imu" i.e Acc X,Y & Gyro X,Y.
Result: Error, imu not found.
Could you please let me know is it genuine or need it to be return.
When I am trying to capture roll angle using M5stack Gray it is working fine and separate code for sending data to Azure IoT Hub is also working fine. But when I try to club the two modules the roll angle return by module get highly unstable and it throws random absurd values.
Hi @heybin !
What do you want to show us with the picture: flickering due to problems with contacts?
Do you know what the meaning is of:
flashing? ( = 1s on > 1s off > 1s on > and so on: charging?)
What I noticed so far:
a) USB charging cable connected to M5GO CHG Base and M5GO CHG Base attached to M5GO Base: LED is flashing and obviously charging
b) M5GO disconnected from M5GO Base: LED = ON for 30 seconds , than OFF, but FIRE is still on and operational (Power from internal Lipo Battery?)
c) M5GO CHG Base attached to M5GO Base, but no power on USB-Cable: same behaviour as item b) above. (Power from internal Lipo battery AND/OR CHG Base Battery?)
For a) and b) so far, I didn't test, for how long the FIRE stays ON.
If it's not connecting to the device, what errors do you see? Paste your command line output here and maybe I can help further.
One other custom I did for ampy... I created the file ~/.ampy with these contents:
# Example .ampy file
# Please fill in your own port, baud rate, and delay
# Fix for macOS users' "Could not enter raw repl"; try 2.0 and lower from there:
If you create that file, you will not have to pass the port and baud rate options when running the ampy command. This is the standard way to run ampy when you don't have the .ampy file created.
world101$ ampy -p /dev/tty.SLAB_USBtoUART -b 115200 ls
Also, I was mistaken on the the v1.2.3 firmware with the beeps disabled by default. I just flashed one of my cores with the M5Burner and the beeps are there. I must have been running a custom firmware before.
How about this example code?
@ajb2k3 Thanks a lot !
@cepics "A custom ESP-WROOM-32 build without any flash chip added, so the existing GPIO6, GPIO7, GPIO8, GPIO9, GPIO10 and GPIO11 pins can be used to allow us to add a GD25Q127C (or similar) on our external circuit."
@kat @Rop you need to create and M5ez project, create a text place holder and set the code to replace the text with the values. Hopefully @Rop will pick up the notification and help you out. My knowledge is more towards Uiflow
Currently there is no support for png images in the micropython port that form the firmware of the m5Stack range.
BMP is its raw uncompressed state is a simple file to translate along with base level jpg (not JPEG!)
Until such time that a codec exist for micropython, we are all stuck with converting graphics into base level formats.
@rob-biernat which M5Stack or Stick are you using?
The M5Stacks and Sticks have an I2C grove port (port A) but this is also a digital I/O port in that it can read or write 0 or 1 values (on or off) I am currently triggering a relay unit from the port.
The M5Go base has has 2 additional port which are multi I/O (port b) and UART (port C) Unlike Arduinos, the esp32 which powers the M5Stack has no set pin functions and all pins can be used for a range of functions.
When using Port A Yellow is SCL (pin 22) and white is SDA (pin 21) and need to be defined.
I have started to document the different functions of the grove connector and you can find them on pg 19 and 20 of my WIP book here https://github.com/Ajb2k3/UIFlowHandbook/blob/master/UIHB1404192.pdf
@brij300 So sorry about that. We haven't tried to connect to AIOT website yet? But some guys make a project about opendimes. You can contact them. Thanks a lot.
What some people dont know is that the esp32 is not like an arduino.
the esp32 has 3 cores, 2 primary and 1 Ultra Low power.
In true deep sleep, the primary core are deactivated and the basic "Upkeep" code is off loaded to the ULP.
Because the M5Stack is based on the ESP32 and not much is understood about the ULP, very little progress has been made on deep sleep.
In theory, from what I have read the ULP could maintain a low power screen for a Like (to use your example) and then wake up the core to take the sensor measurements before storing them (for the ulp to recall and display) putting the cores back to sleep.
If you are interested in leaning more, look into the ESP32's ULP (Ultra Low Power core)