Search found 125 matches

You could look at this document for DWIN HMI
https://ecdn6.globalso.com/upload/p/1355/source/2024-09/T5L_DGUSII-Application-Development-Guide-V2.9-0905.pdf

I am not in any way affiliated with DWIN ...

@Jerson: I guess the problem now is how to buy these from Canada.... I'm looking online for something like the GME0831B but there aren't much results.

That seems to be just the capacitive touch ove ...

If you are willing to use a UART running anywhere from 9600 to 115200 baud, I suggest you look at HMI displays like the DWIN displays with either capacitive or resistive touch. Their website is www.d ...

I wonder if you're trying to implement an HMI type display. If so, using a TFT with capacitive touch will be a lot of work and code space. You can mitigate this by using a HMI display from either Ne ...

The value in tcomb will range from 0 till 65535.

Thus, using the native integer math of the processor, tcomb/65535 will result either in a 0 for values less than 65535 or 1 when it is equal. Fract ...

Wish you all the peace and joy of Christmas. Have a merry Christmas

#define hi(x) (*((int8 *)&x+1))

Try to read it like this

define macro

hi of x
as
the value pointed at (*
which is of type int8 pointer (int8 *)
whose location is address x+1 (& ...

If you're referring to an arduino TFT shield type display, they can be used with a 8 bit data bus. As far as I know, there is no ready library that you will find other than the ones written for ardui ...

you could try something like this

// more accuracy using long variables
value = ((int32)value * 39L)/100

or perhaps if you can tolerate some error in calculation

...

Most terminals online will support 9 bits. Maybe you're looking for the wrong keywords.

It would be 8bit data with parity. Most terminals will support this.

Look for @bray terminal My favour ...

I suspect this to be the Read-Modify-Write issue with bit access on I/O ports. A way to solve this would be to keep a shadow byte variable in RAM which you modify and then whenever modified, write o ...

If you do need to use delays, I suggest you write non-blocking type delays so that the USB is serviced in the background @ approx 1mS

Two things:

1.- HID_Report_Create() seems yo be a method you defined and didn't provide the definition.
2.- I did try the usb_tbe(1) and it still does the strange behaviour of keep pluging and unp ...

This is how I have managed USB. Maybe you're missing the tx buf empty check.

if (usb_enumerated()){
if (usb_tbe(1))
{
HID_Re ...

The download has code examples in the rar file.