Thanks guys adding the build flags fixed the blank serial terminal in PlatformIO.

@lukes said in C++ syntax question - Defining an object in a class that requires arguments?: HardwareSerial Maybe this solves your problem ... class StaticClass { private: int myContent; public: StaticClass(int v){myContent = v;} void printout(){printf("%d\n",myContent);} }; class TestClass { public: //StaticClass myClass = StaticClass(42); // With C11 StaticClass myClass; TestClass() : myClass(42) { } void doit() { myClass.printout(); } }; int main(void) { TestClass tc; tc.doit(); }

@lukes There is no schematic, which is unusual. I "made an Issue" with M5Stack's GitHub page for AtomS3 last year about this, but, nada.

I'm having the same problem testing a similar example in https://github.com/m5stack/ATOM_DTU_LoRaWAN/blob/master/examples/Modbus/ModBus-RTU/Slave/Slave.ino Does anyone have a working example to share?

Hello @LukeS I don't think the RGB LED has been integrated into M5Unified library for M5AtomLite. Even for M5AtomS3 the code for the RGB LED is kind of outside M5Unified library, e.g. in utility/LedDisplay.c. All I can find in M5Unified is the GPIO definition for the RGB LED for different M5Stack devices. However I don't think they are used. For M5AtomLite the RGB LED GPIO is (re-)defined and used from here. And for M5AtomS3 it is (re-)defined and used from here. Thanks Felix

All esp’s are like modern controllers are only 3.3V tolerant, the 5v on the grove is for the grove Standered and for sensors that still require 5v.

@hallinen Yes, I saw your comment over on https://github.com/m5stack/M5AtomS3/issues/23 The solution to my identical issue/14 was to burn-back (erase all) to 'Arduino15/staging/packages' and re-install the M5 latest board definition. Tinyu-Zhao's solution was: "Perhaps there is a local cache package that is not downloading the latest M5Stack version definition Please delete the following path, uninstall the M5Stack 2.0.6 definition and try again /Users//Library/Arduino15/staging/packages"