Hello!

Sorry, just replying to a part of my own post.
Compressing in ASTC format on Ubuntu:
1. Install by
sudo apt install astcenc
2. Run astcenc.
-> This will list a couple of examples which will be good to start before learning how
to tune the bitmaps for a given purpose.

Now the other questions remain: how to choose the right ASTC format.

Regards,

R

Hello!
I'm using a FT813 7-inch display. I would like to make a keyboard object with entry field.
Ideally, this would be an opaque object that would come on top of all the other objects
when I tap a value to be edited.
Is there a problem overlapping objects? I mean, writing many widgets, and then displaying
a bigger object that hides other widgets previously drawn in the same session (between command start
and display swap).

Beside this, other than hiding other widgets, I would like to first draw a very large button which covers
a bit more than the area of the keyboard itself. This would solve the problem of spaces between the
buttons.

Thanks for any hint!
R

Hello!

Thanks for your reply, and sorry for the delay, I was dealing with real work (i.e.
the one I get paid for)...
It works with 0xffffff2e, thanks. That said, I don't know how this definition came here,
I didn't invent it and I didn't make the file myself. I downloaded it from GitHub, most likely.
The only thing I did is to define all the commands as absolute, not as an offset from RAM start.

Thanks anyway.

Best regards,

R.

Hello!

Thanks for your reply.
Yes, that's right, I just want to know how to use the coprocessor to write a single slider.
When I set to COP_SLIDER = 0, it works fine, I get a blue screen with a white rectangle.
I can also draw sliders myself, and that's what I did in the first version of my current software.
It was working well, but it's always difficult to get fancy effects, so I would like to upgrade
my software so that it now uses the coprocessor widgets (for instance in the present case,
a single slider).

CMD_DL_START // Tells co-pro to begin writing DL at RAM_DL+0

OK, I have added wr32(RAM_DL, CMD_DLSTART);, exactly as if I was writing direcly to the
non-coprocessor area.

CLEAR_COLOR_RGB // Co-processor writes this instruction to the DL
CLEAR(1,1,1) // Co-processor writes this instruction to the DL

So you mean I don't have to write anything myself? If the coprocessor writes these 2 instructions,
then I have to leave room for these instructions, and then at the end I will write the instructions at offset 8
(4 for clear_color + 4 for clerar(1,1,1)?

#co-pro commands
Color_RGB(0,0,255)
Point_Size(20)
Begin(Points)
Vertex2F(0,0)

I don't understand this part. What does it do? Do I need it to draw a slider? It looks like it will draw a point.
Is it written in RAM_CMD or RAM_DL? I can write RGB(0,0,255) directly to RAM_DL, so it doesn't look like a
coprocessor command. In my snippet below I

#end procedure
End()

Is this End() to be written to the DL memory? If yes, at which offset? Last time I wrote was at offset 8, is it 12 now?

Similarily as before:
DISPLAY // Co-processor writes this instruction to the DL
CMD_SWAP // Co-processor writes REG_DL_SWAP

Do I have to do anything here?

[update REG_CMD_WRITE to point to end of new commands]

How do I do that? I can read where the REG_CMD_WRITE is by rd16(REG_CMD_WRITE + RAM_REG);
but what should I do with the value?

I replaced the DL part with the code found at 2.5.1 in FT81X documentation. I get the FTDI logo on black background.
Same as before, it works with COP_SLIDER = 0, not yet with 1. I guess the missing part is the REG_CMD_WRITE
stuff, but I'm stuck...

Thanks for any hint!

R

#define COP_SLIDER 1

void FT813::Test(void) {
#if COP_SLIDER
// Offsets come from BridgeTek's programmers guide, version 1.2, page 204.
// Start procedure
wr32(RAM_DL, CMD_DLSTART);
wr32(RAM_DL + 4, CLEAR_COLOR_RGB(0x30, 0x60, 0x90));
wr32(RAM_DL + 8, CLEAR(1, 1, 1));
// Coprocessor commands
wr32(RAM_CMD, CMD_SLIDER); // Command offset is 0
wr16(RAM_CMD + 4, 32); // X
wr16(RAM_CMD + 6, 32); // Y
wr16(RAM_CMD + 8, 320); // W
wr16(RAM_CMD + 10, 32); // H
wr16(RAM_CMD + 12, 0); // Options (default is 0)
wr16(RAM_CMD + 14, 100); // Val
wr16(RAM_CMD + 16, 40); // Size (width of the knob??)
wr16(RAM_CMD + 18, 300); // Range
// End procedure
wr32(RAM_DL+12, END());
wr32(RAM_DL+16, DISPLAY());
wr8(REG_DLSWAP, DLSWAP_FRAME); // Display list swap
#else
wr32(RAM_DL, CLEAR_COLOR_RGB(0, 0, 0));
wr32(RAM_DL + 4, CLEAR(1, 1, 1)); // clear screen
wr32(RAM_DL + 8, BEGIN(BITMAPS)); // start drawing bitmaps
wr32(RAM_DL + 12, VERTEX2II(220, 110, 31, 'F')); // ascii F in font 31
wr32(RAM_DL + 16, VERTEX2II(244, 110, 31, 'T')); // ascii T
wr32(RAM_DL + 20, VERTEX2II(270, 110, 31, 'D')); // ascii D
wr32(RAM_DL + 24, VERTEX2II(299, 110, 31, 'I')); // ascii I
wr32(RAM_DL + 28, END());
wr32(RAM_DL + 32, COLOR_RGB(160, 22, 22)); // change colour to red
wr32(RAM_DL + 36, POINT_SIZE(320)); // set point size to 20 pixels in radius
wr32(RAM_DL + 40, BEGIN(POINTS)); // start drawing points
wr32(RAM_DL + 44, VERTEX2II(192, 133, 0, 0)); // red point
wr32(RAM_DL + 48, END());
wr32(RAM_DL + 52, DISPLAY()); // display the image
wr8(REG_DLSWAP, DLSWAP_FRAME);

#endif
}