Thanks all for the insight. I've looked at the flowUI and at making an interface in the Arduino IDE. The flowUI is really easy with great looking results but I really doubt I can get the frame rates where I'd like them in an interpreted language. I also think that writing an interface natively in the Arduino IDE would have a big impact on the frame rates as well. I may have to look at some co-processor arrangement where flowUI Handles the higher level functions and issues commands to a procesessor handling the IO.
You would be correct with processing as the arduino allows access to all 3 of the esp32's cores where as micropython code runs on one core, the interpreter runs on the other and the 3rd, the ULP core is inaccessible.
Thanks again for your time and insight. I'm really impresses with the M5Stack, I have a lot of learning to do.
@hague I could be wrong, but I believe if you use as lib_deps is a better solution, because the PlatformIO can update automatically the library in the future. Not only that, your code build more faster (because the library use a shared objects - *.o files).
Other interesting point is to add more libraries to project. But again, this is IMHO about the way to use PlatformIO.
You need just one Serial;
Serial.begin(10000000);
//connect to proper TX<>RX pins of M5Stack
For proper debug you can connect sensor with any USB<>UART board and try to run it with any terminal software (I use TeraTerm)
If you want to debug derictly with M5Stack you will need Serial2 as your example shows, but keep in mind that if its a software serial, such high speed wont work properly most likely
Hi @steinoxyd ,
I had the same issue which I got help with on the m5stack github before seeing this. I may as well direct you straight to it than repeating it fully here; https://github.com/m5stack/M5Stack/issues/194
The issue is the 'IMU.calibrateMPU9250(IMU.gyroBias, IMU.accelBias);' which if commented out, the code will run.
From the comment from @lukasmaximus I have not realised the probable reason for the issue.
sorry for resurrecting this post from the dead but where exactly do you run the esptool --port <YOUR PORT> write_flash_status --non-volatile 0 command?
You run this in a terminal or command line program.
Replace YOUR PORT with the name of the port that appears in arduino. On windows this may be COM followed by a number on OSX this is often somelike USBslab.
I know I'm late to the game but I just bought one of these. Did you ever manage to connect it to your m5stack @dfabro ? if not I'm gonna try, and if I'm successful will post my findings here
@wikistik I have tried that, but the Windows system seems to be trying to insert a random outdated driver for the USB cable instead of the one you suggested. You're right, though, because on a different Windows 7 computer, I installed the drivers and it started working automatically.