I stumbled on this restriction again, and dug a bit deeper in the issue.
It appears that the hardware is not limiting the baudrate, but the M5Stack library. More specifically, M5.begin();
Luckily, you can skip the UART init, and do it yourself like this:

M5.begin(true,true,false);
Serial.begin(2000000);
Serial.flush();

And now it works for 2000000 baud.

Hello @AndyT

hmm, strange, if anything I'd expected the M5Stack Gray to work with low brightness level and the M5Stack Black to not behave due to the fact that the M5Stack Gray has additional hardware (e.g. IMU) consuming power to keep the device powered on.

That said, I suspect the IP5306 switching off due to too light load. Try to add the following statement before going into deep sleep. It should prevent the IP5306 from shutting down under light load.

M5.Power.setPowerBoostKeepOn(true);

Happy Stacking!
Felix

@m5stack Understood. Thanks

@sparkinman

Check that:

You have added the M5Core2 library and are doing #include <M5Core2.h> and not using M5Stack.h. Until they merge it my Pull Request and release a new version, my version is more like it will be, better documented and has graphical buttons. (Simply clone it or get the zip file and unpack so that M5Core2 is a subdir of your Arduino libraries dir.)

In Arduino Preferences, you have added https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/arduino/package_m5stack_index.json as an "Additional Board Manager URL"

Make sure you then select M5Stack-core2 from the "Tools / Board / M5Stack-Arduino" menu.

If this is all good, then you should be able to run one of the examples from the "File / Examples / M5Core2" menu.

Hello @veryalien

Sorry to hear about your troubles.

I looked into the factory test program today and got it to compile and running after enabling PSRAM, the above mentioned fix in SetLDOVoltage() and some cleanup of the old Wire vs Wire1 fight that seems to come back every now and then. I wished the developers could make up their mind and always use Wire for internal I2C devices. Oh well.

The factory test code does something interesting regarding vibration motor voltage. During the startup sequence it is first set to 2 volts, then the motor is quickly turned on and off again and then later on it is set to 3.3 volts (not sure why though). When testing the vibration motor from within the settings menu the latter voltage is used.

https://github.com/m5stack/M5-ProductExampleCodes/tree/master/Core/M5Core2/Arduino/Core2_Factory_test

Cheers
Felix

@efried said in Snap in fixture?:

I can't find such in the webshop.
https://www.thingiverse.com/thing:3133893
thanks

This isn't an M5Stack product, that is a user created free to download addon that needs 3D Printing.

To avoid possible conflicts with my app, I tested with Wifi Examples from ESP-IDF repo:
https://github.com/espressif/esp-idf/blob/master/examples/wifi/getting_started/station/main/station_example_main.c

Sorry for this missing point.

Hey, got a little sidetracked with some other projects. Hopefully will be closer to finishing by the end of the month.

it's a library to control a sensor, I had already built my custom blocks that worked with that library, but when I updated everything I was unable to make it go.
so do I have to import the library into the / flash root?

and then?

Hi @m5stack

you could pip install a pyserial module to solve it.

I tried that but the problem persists. As a quick fix, I just flashed it using a window virtual machine.

the LED always RED? which program are you use?

Yes, but after I flashed the new firmware everything is behaving well.

which program are you use?

It turned RED, after I tried to flash it with the newer esptool (2.8) as I showed in my initial topic

we will fix this bug in next version.

🤞🏻

Have a nice day

@m5stack Ah Thank you! I used Easy Loader and updated the firmware! Your help is awesome! I can see the device working now.

@robalstona excellent. Thank you for the clarification. It’s logical, and I agree that I don’t require anything higher, but I wanted to make sure for safety’s sake.

@steve_j83 voltage input range 4.5~5.2V . for the time being don't open source the schematic. if you just want the know about the pin map you could check the sticker on it back site.

@reaper7 said in Atom Lite - Serial Port access:

Serial1.begin(115200, SERIAL_8N1, 32, 26);

Thanks. Tried that and causes a crash. I thinned out my code to bare min and this can replicate the crash (sorry not sure if this site has <code> tags. Crash details are further down, but it looks like an issue with the Nextion library. Challenge is this library works fine on other ESP32s. Only difference here is calling out Seria1 with the defined ports. Usually I have ESP32 boards where I can connect direct to UART1 pins, so no need to do pin mapping.

#include <Nextion.h>

//PRODUCTION: Use this when using the physical MCU + Nextion TFT LCD Hardware or MCU + Serial Window.
#define nextion Serial1
boolean debug = true; //Be sure to set to false when done debugging!!

Nextion myNextion(nextion, 115200); //create a Nextion object named myNextion using the nextion serial port @ 115200bps

void setup()
{

Serial.begin(115200); //Standard Serial comms
Serial1.begin(115200, SERIAL_8N1, 26, 32); //Comms to Nextion

if (debug) {Serial.println(F("Connected. Processing loop..."));}
}

// END SETUP

void loop(){}

000000
A10 : 0x1dd4848c A11 : 0x0000001c A12 : 0x3ffba49c A13 : 0x00000000
A14 : 0x00000000 A15 : 0x00000000 SAR : 0x0000001c EXCCAUSE: 0x0000001c
EXCVADDR: 0x1dd4848c LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

Backtrace: 0x40080f75:0x3ffb1ec0 0x400d1986:0x3ffb1ee0 0x400d1d45:0x3ffb1f00 0x400d0e22:0x3ffb1f40 0x400d0bb9:0x3ffb1f80 0x400d13ab:0x3ffb1fb0 0x40088215:0x3ffb1fd0

Rebooting...
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 188777542, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0018,len:4
load:0x3fff001c,len:1216
ho 0 tail 12 room 4
load:0x40078000,len:9720
ho 0 tail 12 room 4
load:0x40080400,len:6352
entry 0x400806b8
Guru Meditation Error: Core 1 panic'ed (LoadProhibited). Exception was unhandled.
Core 1 register dump:
PC : 0x40080f75 PS : 0x00060530 A0 : 0x800d1989 A1 : 0x3ffb1ec0
A2 : 0x00000020 A3 : 0x00000002 A4 : 0x00000000 A5 : 0x00000001
A6 : 0x00060520 A7 : 0x00000000 A8 : 0x3f405808 A9 : 0x00000000
A10 : 0x1dd4848c A11 : 0x0000001c A12 : 0x3ffba49c A13 : 0x00000000
A14 : 0x00000000 A15 : 0x00000000 SAR : 0x0000001c EXCCAUSE: 0x0000001c
EXCVADDR: 0x1dd4848c LBEG : 0x00000000 LEND : 0x00000000 LCOUNT : 0x00000000

Hook it up to an AD input of the M5Stack (ESP32).
Watch : https://www.youtube.com/watch?v=DffZVyksYi4
I will use one as a spectrum analyzer recording the sound of bees.

@m5stack UiFlow Version 1.4.5 (Desktop) Issues

Pressing </> Python:
0_1586899662275_d5e1d27a-fb3e-4cf6-a804-ccb943374a93-image.png

At any time wipes out any code you have in the edit window, why?

Cannot save code, also two methods available to save:
0_1586899836134_4ebd7d13-b7fd-46f2-b82b-f235d7d1d99c-image.png

Or
0_1586899862312_ae0ea337-c3c8-4c38-812b-817cba96a19a-image.png

Using either method saves a main.m5f file (Note, not a main.py), opening the main.m5f results in:

rom m5stack import * from m5ui import * from uiflow import * rgb.set_screen([0,0,0,0,0xFFFFFF,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0]) setScreenColor(0x222222)

Ok, so I thought I would change version via the Ver button at the top of the screen, now all I get is:

0_1586900318444_c38ae718-927a-486d-b540-bc31fbbfe7f9-image.png

On startup I get:

0_1586900382795_704ee601-390a-4461-89be-2cde53e65372-image.png

Everytime even though the driver is installed. I select Skip which takes me to the main GUI which informs me the Atom-matrix is detected.

Basic editing navigation via shortcut keys such as <ctrl> S don't work - very annoying.

Because of the Javascript error I can't open in UIFlow anymore to continue.... Now I'm stuck.

Please tell me I'm doing something wrong and being a complete idiot...