Hmm, the "best" method would be something that is doable with the available resources while beeing pleasant enough to look at. :-) Bridgetech has a fancy example code somewhere that has a round graph that is using a few tricks like scissors. Or you could use a rectangle, that is just two p...

Yes, I am a tad bit sceptic about the mini-M0 I received. It probably is even working fine - after figuring out which bootloader it uses and what Arduino Core to really use with it. But I could not find documentation for it, it maybe is a knockoff from the RobotDyn design. The M4 in this regard real...

Ah, you mean the macros from FTDI that I still carry in my code, like this one: #define COLOR_RGB(red,green,blue) ((4UL<<24)|(((red)&255UL)<<16)|(((green)&255UL)<<8)|(((blue)&255UL)<<0)) Yeah, I guess I could go over these and delete some. But then these are kind of expected as FTDI put ...

Sure, I do give up as everyone else. :-) Well, I have it up and running on my Metro M4 now. I did not have to change anything, only wire it up correctly to the ICSP pins for SPI. Yesterday I hooked up a Logic Analyzer to the Metro M4 and found that the default SPI speed is 4MHz. And with "SPI.s...

Today I learned that the Metro M4 does not support SPI on the same header as the UNO, at least not directly out-of-the-box. I'll try to use it with the hardware SPI from the ICSP header as it is intended to be used. And I ordered one of these: M0-Mini.jpg Just because I would like to know what the i...

Hello, I found some code on github, which is reported to work on many targets. That one is mine and yes it does indeed work fine on several targets and for some time now. :-) But in fact, the background of a button is defined by CMD_FGCOLOR. So the REG_CMDB_WRITE story is not needed. That said, I wo...

Well, I still have to assume that I broke something but I can not reproduce the issue. 20201103_174055.jpg The display in the green case is an EVE3-43G. Why the green? Just because I had it on the printer when I test-printed the case. Below is one of these Unicorns we do not talk around here, should...

Okay, this is the same project but it has Arcade_R: EVE_Test_Arduino_PlatformIO_EVE3-43G_UTF-8.zip The difference is that for some reason I had to place the "Loop..." text line a little lower. And the "Hello UTF-8: €µäöü" line is all upper-case now and has no special chars at the...

Today at work I had the idea that I might have introduced a bug in the Arduino support. So I just gave it a spin and it is now up and running an a Seeduino V4.2 with ATMega328P. It just does run a lot slower but this is to be expected without DMA. I even re-activated the spinning picture from the sa...

If you are doing something wrong, I do not see it. I have been using this: ... EVE_color_rgb_burst(WHITE); EVE_cmd_fgcolor_burst(0x00c0c0c0); /* some grey */ EVE_cmd_dl_burst(TAG(10)); /* assign tag-value '10' to the button that follows */ EVE_cmd_button_burst(20,20,80,30, 28, toggle_state,"Tou...

I changed my EVE_cmd_setfont2() from the static part to a EVE_cmd_setfont2_burst() in the generated list and it stopped working for me as well. Turned out that EVE_cmd_setfont2_burst() was using CMD_SETFONT instead of CMD_SETFONT2. I just pushed a fixed version to Github, thank you for pointing out ...

- I didn't pay attention to "Address Of Glyph Data" in EAB : Glyph data stays on flash and is not copied in RAM, so the address specified here has to be the same when generating flash image. Again, no, EAB takes care of that when you put the .glyph and .xfont in a flash file by modifying ...

going over my post above my code looks a little different now: #if 0 /* this is only needed once to transfer the flash-image to the external flash */ uint32_t datasize; EVE_cmd_inflate(0, flash, sizeof(flash)); /* de-compress flash-image to RAM_G */ datasize = EVE_cmd_getptr(); /* we unpacked to RAM...

I just tried it with a different font again using my latest simple demo code as a starting point. Of course using an EVE3-43G and not something from that other company you mentioned and no-one ever heard of before. :-) And going over your post now I found the issue: #define MEM_FONT2 0x00215168 This...

Following the official release of BT817 / BT818 with datasheet and programming manual I just pushed the first release of my code library to Github with support for BT817 / BT818. https://github.com/RudolphRiedel/FT800-FT813 There may be some kinks left as I did not have the programming manual before...