EVE2-38A-BLH-TPR Screen resolution & Touch screen issue

[msuresh168]

Hi sir,

This is Suresh from Chennai,India. Recently I bought two displays from your side (EVE2-38A-BLH-TPR & EVE2-38G-BLH-TPC ). As now I started with resistive type display. Basically its is working well. But I found the following issues.

1) When I have run calibration thread. I have found axis issue in my display. That means dots are not appearing correct place. I have attached my snapshots which I have taken during calibration processing time.

2)I am facing issue on my Y axis also. I am printing "Cylinder 1", "Cylinder 2" and "Cylinder 3" for the following axis (0,20) ,(200,10) and (400,0) respectively. But the above last two axis are not appearing well. I have attached my code screen shot.

3) My REG_TOUCH_TAG is not performing well. I used TAG with 117x116 size image. But the touch function is working for the partial image. I can't receive touch TAG value for entire image.

Please give me your valuable response as soon as possible . I have to use this display for my production.

I used the following LCD timing parameters,

/************** For Matrix Orbital Display 3.8 inch **************/

ft_int16_t FT_DispWidth = 480;
ft_int16_t FT_DispHeight = 272;

ft_int16_t FT_DispHCycle = 524;
ft_int16_t FT_DispHOffset = 43;
ft_int16_t FT_DispHSync0 = 0;
ft_int16_t FT_DispHSync1 = 41;

ft_int16_t FT_DispVCycle = 288;
ft_int16_t FT_DispVOffset = 12;
ft_int16_t FT_DispVSync0 = 156;
ft_int16_t FT_DispVSync1 = 10;

ft_uint8_t FT_DispPCLK = 5;
ft_char8_t FT_DispSwizzle = 0;
ft_char8_t FT_DispPCLKPol = 1;
ft_char8_t FT_DispCSpread = 1;
ft_char8_t FT_DispDither = 1;

[Daniel Divino]

Hi Suresh,

1) The EV2-38A is a little bit different from our other displays, as it is a 4.3" display cut in half. This means that it needs to use the 4.3" timing data in order to operate properly. Due to this, the FT81X's calibration command won't operate properly. That said, we have made a calibration code example that you can use to calibrate your display.

2) Due to how the display is cut, you will need to offset all of your assets and widgets by 10 pixels. So, if you want an asset to appear at (0,0), you will have to place it at (0,10) on your EVE2-38A.

3) I believe this is due to the lack of proper calibration.

Cheers,
Daniel

[msuresh168]

Hi Daniel,
Thanks for your reply. Right now I am working with code. But meanwhile please can you send predefined Calibration data for both resistive and capacitive touch screen calibration data. I can move that data to calibration manually. Currently I am working with STM32F4 series controller. So it's having lot of space.

[Daniel Divino]

Hi Suresh,

Each resistive touch panel has it's own calibration values, and therefore, values that work for my display may not work properly for yours. I strongly suggest you try implementing the calibration function into your code and extracting the appropriate calibration values that way.

Cheers,
Daniel

[msuresh168]

Hi Daniel,
I have fixed my issues. As of now the both displays are working well (Resistive & Capacitive). As you said, finally I have changed lcd timing clock and manual calibration thread. I am just coming to end up with application. Thank you so much for your support.

[msuresh168]

Hi Daniel,

Now everything fine and have planned to move from R&D to production .

But during our final full load test(24*7) , we are facing hanging issue in the "Ft_Gpu_Hal_WaitCmdfifo_empty" function.In that situation ,"REG_CMD_READ" register will not be equal to "REG_CMD_WRITE" register. So the Micro-controller will not come out from this "while" loop. Please find the below image for my initial code.

Initial Code

Image1_1.jpg (59.31 KiB) Viewed 40538 times

After that i found the Test code in your GITGUB (https://github.com/MatrixOrbital/Basic- ... Eve2_81x.c). Then i changed my code with reference of your sample code . Please find the below image for my modified code.But we have not yet fix this hanging issue.

Modified code

image2_2.jpg (171.01 KiB) Viewed 40538 times

You used extra two registers which are "RAM_ERR_REPORT" and "REG_COPRO_PATCH_PTR ". But they are not declared in datasheet/user manual. So i could't proceed without clear understanding of usage of these 2 register. Please help me to solve the "display hang" issue by explaining this.
I have uploaded my project code also. If you need please refer my entire code and suggest me to solve the issue.

[Raquel]

Hi Suresh,

Very glad to hear that you are moving to production soon.
Kindly please check out section 5.8 Coprocessor Faults in the programming guide:
https://brtchip.com/wp-content/uploads/ ... _Guide.pdf

Best Regards,
Raquel

[msuresh168]

Hi Daniel,

Thank you so much for your valuable reply.

I read the programming guide which was sent by you, in this Registers RAM_ERR_REPORT and REG_COPRO_PATCH_PTR are defined and suggested to use at the time of Coprocessor Faults. But that one is BT81X series' programming guide. But i am using FT813 series. I have attached the Datasheet and programming manual link bellow for FT813 .

Datasheet : https://brtchip.com/wp-content/uploads/ ... _FT81x.pdf
Programmer Guide : https://brtchip.com/wp-content/uploads/ ... _Guide.pdf

In the FT813 series' guide, Registers RAM_ERR_REPORT and REG_COPRO_PATCH_PTR are not defined and not suggest to use.

Now my doubt is that even though these registers are not defined, shall i use them for Co processor Faults condition? Do FT813 support for these Registers?

[Henry]

Suresh,

Can you touch base with me about your project so we can make sure we can support your production plans.

sales@matrixorbital.ca

[msuresh168]

We mailed you about our product but here we don't understand what are you trying to say?

[Henry]

We mailed you about our product but here we don't understand what are you trying to say?

When did you email? I don't see an e-mail from you.