@wsanders At least with respect to the LCD library: The only function implemented so far to manipulate whole images is drawBitmap. drawJpg and drawJpgFile are commented out in https://github.com/m5stack/M5StickC-Plus/blob/master/src/M5Display.h so I assume they aren't working yet.

So my workflow for now is:

Save the image from gimp in gimp's ".h" format. This is smaller than a xpm or bmp. You will get a static char *data structure of all the pixels in the image. The .h file includes a macro to extract the pixels:

#define HEADER_PIXEL(data,pixel) {
pixel[0] = (((data[0] - 33) << 2) | ((data[1] - 33) >> 4));
pixel[1] = ((((data[1] - 33) & 0xF) << 4) | ((data[2] - 33) >> 2));
pixel[2] = ((((data[2] - 33) & 0x3) << 6) | ((data[3] - 33)));
data += 4;
}

Write your own function rgb888to565 to compress the pixels into a uint16_t.

Draw a bitmap of the image as fast as you can:

#include <M5StickCPlus.h>
#include "1.h"
int pixel[3];
// pointer fu to preserve the start of .h data
char *datastart;
uint16_t *bitmap;

void setup() {
M5.begin();
M5.Lcd.setRotation(3);
bitmap = (uint16_t *)malloc(height * width * 2);
}

void loop() {
M5.Lcd.fillScreen(GREEN);
datastart = data;
for (int16_t y=0; y < height; y++) {
for (int16_t x=0; x < width; x++) {
HEADER_PIXEL(data, pixel);
bitmap[60*y + x] = rgb888to565(pixel[0], pixel[1], pixel[2]);
}
}
M5.Lcd.drawBitmap(0,0,width,height,bitmap);
data = datastart;
}

Or you can use the Sprite library, which works well.

Well, it's working.

The path to my Windows profile has a space in it. I created a local account without a space, and my empty program compiled with no issues. Don't know if that's the reason. Very strange.

Makes me want to reinstall Ubuntu, or something.

Thanks for the replies, Terry.

@sleepyfatcat said in DigitalWrite:

Hello,

I am trying to use C to on the LED on my M5 stick c plus.

I have initialise pin 10 as the output, and when I send digitalWrite(led_pin, 0), it ons the LED.

My code causes the LED to on when 0 is sent, and off when 1 is sent. Any idea why it seemed like it is flipped? Thank you

This apparently is normal behaviour for most ESP Cores from what I have found in data sheets and is very confusing.

Hi @paulskpt,

What additional board URL did you put in? I had similar problems until I changed the URL to this:

https://m5stack.oss-cn-shenzhen.aliyuncs.com/resource/arduino/package_m5stack_index.json

Ricky

Hello @aezero

I am glad to hear you found a solution. And thank you for sharing.

BTW: for me a rate limit of 10 reduces the download time (from about 70 s to 55 s).

Thanks
Felix

yes!!

I replaced the macro analogInputToDigitalPin(p) in the file packages\m5stack\hardware\esp32\2.0.5\variants\m5stick_c_plus\pins_arduino.h and it seemed to work:

//#define analogInputToDigitalPin(p) (((p)<20)?(esp32_adc2gpio[(p)]):-1) #define analogInputToDigitalPin(p) (((p)<20)?(analogChannelToDigitalPin(p)):-1)

I tested it with the following sketch, which printed the correct sequence of mappings (36, 37, 38, 39, 32, 33, 34, 35, -1, -1, 4, 0, 2, 15, 13, 12, 14, 27, 25, 26):

#include <M5StickCPlus.h> void setup() { M5.begin(); M5.Lcd.fillScreen(RED); for (uint8_t i = 0; i < 20; i++) { Serial.println(analogInputToDigitalPin(i)); } } void loop() { }

With this change, I was able to get the Blynk Quickstart example working with my M5StickCPlus, which is what led me down this rabbit hole in the first place!

I spent about and hour trying things and the best solution I could find was to manually copy the desired csv file to the build folder and then rebuild. I also had to turn off compiler warnings because it would treat them as errors.

Here are the details. The csv files are located in AppData/Local/Arduino15/packages/m5stack/hardware/esp32/2.0.5+1.0/tools/partitions. I used minimal.csv, copies it to the build folder, and renamed it to partitions.csv. That fixed it!

I hope this helps!
Adam

Glad to hear it worked for you too!

the first sketch works, with M5Stack basic, if I modify the M5Stack.cpp library from:

// TF Card if (SDEnable == true) { SD.begin(TFCARD_CS_PIN, SPI, 40000000); }

to

// TF Card if (SDEnable == true) { SD.begin(TFCARD_CS_PIN, SPI, 10000000); }

Hi Felix,
Sorry for the delay... my STAMP_PICO project was momentarily shelved but I just resurrected it and found your response.
I will definitely try your suggestion since I would like to keep the native port to flash but I need another UART.
Thank you!

Hello @Caterpillaraoz

you could try something like this every time you want to log something:

Serial.begin(115200); Serial.println("Hello World"); Serial.end(true); ModbusRTUClient.begin(115200, SERIAL_8N1);

Please note that all debug output you send this way will also be sent to the Modus RTU server. This could potentially lead to unwanted results, should the parser in the Modbus RTU server choke on it.
In addition you'll see everything the Modbus RTU server is sending back in the log as well.

As an alternative you could use a second serial connection for debug output through one of the Groove ports using a separate USB Serial converter. E.g. like this:

Serial1.begin(115200, SERIAL_8N1, 16, 17); Serial1.println("Hello world");

Thanks
Felix