Hi

Is there any update on the new 868 and 915 modules.

Just waiting for them.... :P

@vsthose Hi Vsthose,

The following code should work provided you use a Micro SD / TF card that only has a few files on it.... too many and the display will run off the screen and you won't see the write to card and read back.

#include <M5Stack.h> //Micro SD / TF Card Test void listDir(fs::FS &fs, const char * dirname, uint8_t levels){ // Print blank line on screen M5.Lcd.printf(" \n "); M5.Lcd.printf(" \n "); Serial.printf("Listing directory: %s\n", dirname); M5.Lcd.printf("Listing directory: %s\n", dirname); File root = fs.open(dirname); if(!root){ Serial.println("Failed to open directory"); M5.Lcd.println("Failed to open directory"); return; } if(!root.isDirectory()){ Serial.println("Not a directory"); M5.Lcd.println("Not a directory"); return; } File file = root.openNextFile(); while(file){ if(file.isDirectory()){ Serial.print(" DIR : "); M5.Lcd.print(" DIR : "); Serial.println(file.name()); M5.Lcd.println(file.name()); if(levels){ listDir(fs, file.name(), levels -1); } } else { Serial.print(" FILE: "); M5.Lcd.print(" FILE: "); Serial.print(file.name()); M5.Lcd.print(file.name()); Serial.print(" SIZE: "); M5.Lcd.print(" SIZE: "); Serial.println(file.size()); M5.Lcd.println(file.size()); } file = root.openNextFile(); } } void readFile(fs::FS &fs, const char * path) { Serial.printf("Reading file: %s\n", path); M5.Lcd.printf("Reading file: %s\n", path); File file = fs.open(path); if(!file){ Serial.println("Failed to open file for reading"); M5.Lcd.println("Failed to open file for reading"); return; } Serial.print("Read from file: "); M5.Lcd.print("Read from file: "); while(file.available()){ int ch = file.read(); Serial.write(ch); M5.Lcd.write(ch); } } void writeFile(fs::FS &fs, const char * path, const char * message){ Serial.printf("Writing file: %s\n", path); M5.Lcd.printf("Writing file: %s\n", path); File file = fs.open(path, FILE_WRITE); if(!file){ Serial.println("Failed to open file for writing"); M5.Lcd.println("Failed to open file for writing"); return; } if(file.print(message)){ Serial.println("File written"); M5.Lcd.println("File written"); } else { Serial.println("Write failed"); M5.Lcd.println("Write failed"); } } // the setup routine runs once when M5Stack starts up void setup() { // initialize the M5Stack object M5.begin(); M5.startupLogo(); Wire.begin(); // Lcd display M5.Lcd.setBrightness(100); M5.Lcd.fillScreen(BLACK); M5.Lcd.setCursor(0, 10); M5.Lcd.setTextColor(WHITE); M5.Lcd.setTextSize(1); // Page Header M5.Lcd.fillScreen(BLACK); M5.Lcd.setCursor(0, 05); M5.Lcd.printf(" Testing Micro SD Card Functions:\r\n"); // digitalWrite(TFT_CS, 1); // Print blank line on screen M5.Lcd.printf(" \n "); M5.Lcd.printf(" \n "); listDir(SD, "/", 0); M5.Lcd.printf(""); M5.Lcd.printf(""); // Print blank line on screen M5.Lcd.printf(" \n "); M5.Lcd.printf(" \n "); writeFile(SD, "/hello.txt", "Hello world from M5Stack !!"); M5.Lcd.printf(""); M5.Lcd.printf(""); // Print blank line on screen M5.Lcd.printf(" \n "); M5.Lcd.printf(" \n "); // Print blank line on screen M5.Lcd.printf(" \n "); M5.Lcd.printf(" \n "); readFile(SD, "/hello.txt"); } void loop() { // put your main code here, to run repeatedly: M5.update(); }

Hello,

I found some pictures on the web, the pads are not populated and yes it is a short!! I removed the short with some fluxed solderwick and hope nothing is damaged by the short.

Hopefully the M5Stack-team respondes on how that could happen in production and releases the schematics and placement of parts.

Something else that is really odd, on the Keypad there is no bypass capacitor for the Atmel Microcontroller!

Best Regards,

Seppel

You can use hardwareSerial to assign (ex)Serial1 and Serial2 to different pin's then use Serial1 and Serial2 to communicate with the GSM and GPS

HardwareSerial Serial1;
Serial1.begin(unsigned long baud, uint32_t config=SERIAL_8N1, int8_t rxPin=x, int8_t txPin=y, bool invert=false);

Just an ideea...

For those who have 'battery issue' with their M5Stack; please, use the 'contact now' button on any product page of our Aliexpress store to contact with our after-sale team. We will try our best to bring you a satisfying purchase experience.

@calin the bottom stack should be the watch 😂

Here is a little report on my progression. In short : it still doesn't work!

I checked that the pin "works" correctly by connecting a relay to test in OUTPUT mode, and a push button (to test in INPUT) : it works!
I checked, double checked and triple checked the setup (wires, connections,...), everything is good.
I ran the same code on a Wemos D1 Mini (ESP8266) : it works.

At this point, I'm lost? The pin and the code seem good, but it can't detect the sensor.

One thing I notice is that this weird whistling sound coming out of the board (not sure if it comes from the speaker or not) when the OneWire lib bitbangs the OneWire protocol on the pin.
So, I made another test program that toggles the pin rapidely (at the speed of the onewire lib - ~50µs) : I hear the sound!

I'll try to find an oscilloscope to check the signal on the pin, as I suspect that "something" is going wrong when the pin is driven at "high" speed.

In the meantime, I hope that someone with more electronical knowledge will help me find a solution!

@reaper7 在 M5.BtnA.wasPressed() conflicts with WiFi? 中说：

@Calin - this bug is reported as issue? I can't find it...

No... was not reported... i found it few days ago but i didn't report it...
I solved the problem by overwriting the files from Arduino-idf installed on my pc with files from older version.
You can report it to espresiff github repository if you want...
When i will have some time i will investigate exactly what function cause this issue...

Here is the solution. https://github.com/Bodmer/TFT_eSPI/tree/master/examples/Sprite/Sprite_scroll

Thanks to @Calin

It might be the chip revision i tested the multiapp only on M5 with chip revision 1
The MultiApp source code is available on github.
Compile the code and upload

At the moment, clearing the old position then printing is the fastest way to do it http://forum.m5stack.com/topic/173/how-to-avoid-text-flicker/3 you can print to sprite if you use the eSPI library and that'll gain you a few ns on the chip but I think the bottleneck is the SPI protocol, that's what Bodner was saying.
You can wrap the clear and print in a function which will make your code as concise as using an object.

@jimit sounds good! thank you.

@drwino
:-)
Good luck.

@calin freeze with no serial message.
What is the IDLE task and how do I control all this?