Hi

By inspecting source code generated from ESD I can see that explicit casting is available for some cases but not the other. Example with .c source code generated by ESD:

(1)
//Explicit casting is available for context
Ft_Esd_Layout_Stretch__Generated.c:: Ft_Esd_Layout_Stretch__Initializer(Ft_Esd_Layout_Stretch *context){
Ft_Esd_Widget__Initializer((Ft_Esd_Widget *)context);
}
(2)
//No explicit casting for context_1
Ft_Esd_SpinBox__Generated.c:: Ft_Esd_SpinBox_Update(Ft_Esd_SpinBox *context){
//...
if (if_1)
{
 Ft_Esd_PushButton * context_1 = &context->Push_Up;
 Ft_Esd_Layout_Linear * parent_1 = &context->Horizontal_Layout;
 Ft_Esd_Widget_InsertTop(context_1, parent_1);
}else{
//...
}
}
All __Generated.c source files are generated by ESD with some .widget files as blueprints. So I am thinking if there is any "switch" or some sort to control explicit casting v.s. implicit casting.

Asking this question because I am working on a project to port Eclipse project output for ESP32 and Arduino. ESP32-IDF in pure C has no problem. A python program developed to convert Eclipse output to ESP32-based project is working, because ESD and ESP32 are both using pure C.

However I am hitting a wall with Arduino in C++, which requires strict syntaxes with explicit casting. Modification by putting explicit casting like snippet below will get the project compiled successfully. But it would not be a friendly package if we need to do it manually for every project.

Ft_Esd_Widget_InsertTop((Ft_Esd_Widget*)context_1, (Ft_Esd_Widget*)parent_1);
ESD is a nice software that opens up node-based visual programming for embedded GUI development. I am fascinated by its features and the possibility of extending this software to MCUs next to FT9xx. I also believe its influence can be much more profound than just using it for FT9xx (FT9xx MCU series is good but ESD can be much more). The success of porting ESP32 has proven my thinking.

So I wish to see if the same task to Arduino can be done. I am almost there. With manual modification manually and patches applying an Eclipse output from ESD can work with Arduino (Teensy in particular).

The next phase is to get project conversion done in an elegant and automatic manner.

Wish to see if there is somebody sharing my thinking and like to provide any insight.

Studying how EVE Screen Designer 4.5 works and found a datatype mismatch in FT_Esd_Dl.c.

This file is stored at ./EVE Screen Designer/Libraries/FT_Esd_Framework/

Data type for FT_Esd_BitmapHandleUse[] declared as ft_bool_t.

However, browsing down the source code at line #251 an assignment to 2 is declared.

if ((handle < FT_ESD_BITMAPHANDLE_NB) && (handle != FT_ESD_SCRATCHHANDLE)) // When valid and not using scratch handle
{
Ft_Esd_BitmapHandleUse[handle] = 2; // In use
}
This leads to compile error for some other toolchain.

Hi

Testing EVE Screen Editor (BT815) with  different storage options, Embedded and Flash options. Msvc_Emulator under MS Visual Studio works 100% OK for Embedded option but the same image is not displayed when I changed it to Flash options.

Is Flash options supported for Msvc Emulator? Do I need to change code manually in Coprocessor list to make it work? I also notice that for both Embedded and Flash options the generated coprocessor list is the same, listed below:

BITMAP_HANDLE(0)
CMD_SETBITMAP(0, RGB565, 240, 423)
BEGIN(BITMAPS)
VERTEX2II(0, 0, 0, 0)
END()

When Embedded options is selected a constant array is generated in .h file. However, for Flash options there is nothing generated to represent the data array. Any suggestion?

John

Hi

I am porting a new LCD display to FT813 with a CTP controller FT6206 from FocalTech. This controller works with FT813 native hardware wiring to RST, INT, SCL and SDA directly between FT813 and FT6206. CMD_SKETCH() is working but I find sometimes the firmware doesn't detect a finger lift. That means a touch is reported properly with REG_TOUCH_TAG returning the tag number (in my case it is 2). One moment when the finger is lifted REG_TOUCH_TAG returns 0 which is OK, but the other time it just stays 2. This implies the hardware fails to detect a finger release. I have to touch on some other area of the CTP to force REG_TOUCH_TAG return to 0. Is there any method to improve the sensitivity? Is this issue common to other displays (with other CTP controllers)?


Here is my source code for your reference:

#include <FT81xImpluino.h> //this is a custom module for FT81x for Arduino

void setup()
{
  Serial.begin(115200);
  FT81xImpl.begin();

  FT81xImpl.DLStart(); //new display list
  FT81xImpl.Clear(1, 1, 1);
  FT81xImpl.Begin(BITMAPS);
  FT81xImpl.Tag(2);
  FT81xImpl.Cmd_Button(84, 30, 300, 200, 31, 0, "Button");
 
  FT81xImpl.Cmd_Track(84, 30, 300, 200, 2);
  FT81xImpl.End();
 
  FT81xImpl.DLEnd();   //equivalent swap()
  FT81xImpl.Finish();  //equivalent wait fifo buffer empty and clean up
}

void loop()
{
  int finger = Gpu_Hal_Rd8(phost, REG_TOUCH_TAG); //low level register read
  Serial.printf("Finger %d\n", finger); //print out REG_TOUCH_TAG continuously
}


Thanks to anyone supporting this.

John

It is stated on datasheet of BT81x that the max PLL frequency reaches 72MHz. Regarding this I wish to ask if BT81x can support a LCD of 1366*768 with pixel clock typ. @ 70MHz?

Attached jpg is a screen shot from the LCD's datasheet on timing data.