Focaltech FT5316电容式触控卡住了

在帮助客户支持显示安装FT5XX6系列的经验中，我们发现最好的方法是从MTCH6303（不是MTCH6301）的驱动程序开始，因为过程的要求非常相似：它需要首先对寄存器进行写操作，然后读取我。圣战在MTCH6301中只发送一条读取消息。另一件需要注意的是来自芯片的数据顺序。基本上，一旦您将数据指针更改为正确的数据，得到的结果应该非常容易。将FT53x6与MTCH6303:FT53X6MTCH6303See附件进行比较，两个附件从MTCH6303触控驱动程序开始，并修改一个例程，由一个定义为ftx支持的HACK启用。下面的示例是针对QVGA（3x230）支持的缩放，但是可以很容易地修改其他屏幕大小。Michael W. Mann主要应用工程师MCU32应用程序



      以下为原文

    In our experience in helping customers support displays mounting FT5XX6 series we've found that the best way to get it working is to start from the driver of the MTCH6303 (not the MTCH6301) since the request of process is very similar: It requires first a write action to a register then the read message. In MTCH6301 only a read message is sent out.
The other thing to be aware is the data order coming from the chip. Basically once you change the data pointers to the correct data to get the result should be very easy.
 
Comparing the FT53x6 to the MTCH6303:
FT53X6
MTCH6303
 See Attachment One See Attachment Two
 
 
Start out with the MTCH6303 touch driver and modify one routine with a hack enabled by a #define FT_SUPPORT.
The example below is scaled for QVGA (320x230) support, but can be easily modified for other screen sizes.

void _DRV_TOUCH_MTCH6303_BufferQueueTasks(DRV_TOUCH_MTCH6303_STATIC_OBJ * hDriver)
{
    DRV_TOUCH_MTCH6303_BUFFER_OBJ * bufferObj = ( DRV_TOUCH_MTCH6303_BUFFER_OBJ * ) NULL;

    bufferObj = hDriver->queue;

    if( DRV_HANDLE_INVALID != hDriver->drvBusHandle &&
        NULL != bufferObj )
    {
        if( 0 == bufferObj->size )
        {
            hDriver->queue = bufferObj->next;
            bufferObj->inUse = false;
            hDriver->queueSizeCurrent--;
#ifdef FT_SUPPORT
            touch_x=(unsigned int)(hDriver->touchData.touch[0].X_M***)<<8;
            touch_y=(unsigned int)(hDriver->touchData.touch[0].Y_M***)<<8;
            
            touch_x=touch_x+(unsigned int)(hDriver->touchData.touch[0].X_L***);
            touch_y=touch_y+(unsigned int)(hDriver->touchData.touch[0].Y_L***);
            
            if( hDriver->touchData.status.nTouch != 0 &&
                /*hDriver->touchData.touch[0].nibble_0.inRange != 0 &&*/
                /*hDriver->touchData.touch[0].x*/ touch_x != 0 &&
                /*hDriver->touchData.touch[0].y*/touch_y != 0 )
            {
// //Translate the touch data to X/Y coordinates
                hDriver->mostRecentTouchX =touch_x;// (int16_t)DRV_TOUCH_MTCH6303_TouchInputMap(/*hDriver->touchData.touch[0].x*/ touch_x<<4 , 240);
                hDriver->mostRecentTouchY =touch_y;// (int16_t)DRV_TOUCH_MTCH6303_TouchInputMap(/*hDriver->touchData.touch[0].y*/touch_y<<4, 320);
                //Translate the touch data to X/Y coordinates
// hDriver->mostRecentTouchX =touch_y;// (int16_t)DRV_TOUCH_MTCH6303_TouchInputMap(/*hDriver->touchData.touch[0].x*/ touch_x<<4 , 240);
// hDriver->mostRecentTouchY =240-touch_x;// (int16_t)DRV_TOUCH_MTCH6303_TouchInputMap(/*hDriver->touchData.touch[0].y*/touch_y<<4, 320);

            }
            else
            {
                hDriver->mostRecentTouchX = -1;
                hDriver->mostRecentTouchY = -1;
            }
#else
            if( hDriver->touchData.status.nTouch != 0 &&
                hDriver->touchData.touch[0].nibble_0.inRange != 0 &&
                hDriver->touchData.touch[0].x != 0 &&
                hDriver->touchData.touch[0].y != 0 )
            {
                //Translate the touch data to X/Y coordinates
                hDriver->mostRecentTouchX = (int16_t)DRV_TOUCH_MTCH6303_TouchInputMap(hDriver->touchData.touch[0].x, 240);
                hDriver->mostRecentTouchY = (int16_t)DRV_TOUCH_MTCH6303_TouchInputMap(hDriver->touchData.touch[0].y, 320);
            }
            else
            {
                hDriver->mostRecentTouchX = -1;
                hDriver->mostRecentTouchY = -1;
            }
#endif
            hDriver->touchStatus = DRV_TOUCH_POSITION_SINGLE;

            if( NULL != hDriver->queue )
            {
                bufferObj = hDriver->queue;

                switch( bufferObj->flags )
                {
                    case DRV_TOUCH_MTCH6303_BUFFER_OBJ_FLAG_REG_READ:
                    {
                        bufferObj->hBusBuffer =
                                DRV_I2C_BufferAddWriteRead( hDriver->drvBusHandle,
                                                            (uint8_t *)&hDriver->deviceAddress,
                                                            ( void *)&bufferObj->regAddress,
                                                            1,
                                                            ( void * )bufferObj->readBuffer,
                                                            bufferObj->size,
                                                            (void *)NULL );

                        break;
                    }

                    case DRV_TOUCH_MTCH6303_BUFFER_OBJ_FLAG_REG_WRITE:
                    {
                        bufferObj->hBusBuffer =
                                    DRV_I2C_BufferAddWrite( hDriver->drvBusHandle,
                                                            (uint8_t *)&hDriver->deviceAddress,
                                                            (uint8_t *)bufferObj->writeBuffer,
                                                            bufferObj->size,
                                                            (void *) NULL);
                        break;
                    }

                }
            }
        }
    }

    return;
}

 Michael W. Mann
Principal Applications Engineer
MCU32 Applications
   Attached Image(s)

非常感谢你，米迦勒，把它交上去。最好的是弗朗西斯科。



      以下为原文

    Thank you so much Michael, gettings hands on it.
 
Best regards.Francisco.

嗨，弗朗西斯科（吉高利）！你有没有让你的FT5316司机工作？我想开始类似的AFT5306。谢谢！帕特里克



      以下为原文

    Hi Francisco (Jiggoly)!
 
Did you ever get your FT5316 driver working? I will be wanting to start something similar for a FT5306.
 
Thanks!
Patrick

嗨，帕特里克，我用一个黑客从微芯片Michael W. Mann发布在另一个线程工作。我正在为所有FT5XX6系列创建一个自定义驱动程序，将在这里发布（如果它工作的话）。



      以下为原文

    Hi Patrick, I got it working using a hack that Michael W. Mann from microchip posted in another thread. I'm creating a custom driver for all FT5xx6 series that will be posted here (if it works).

如果你分享这些代码那就太好了！



      以下为原文

   


It would be so nice if you shared that code!

我已经想出了一个教程，包括如何使用一些适配器板向EF初学者工具包添加Mikroe显示。Mikroe显示器使用一个SSD1963图形控制器和一个焦点技术FT5X06电容式触摸控制器。附上两个文件：1）创建AgRAPHICsAppA3rdPARTYDISPLAY.ZIP教程文档2）3RDYPARTYL DISPLAY.ZIP项目，应该安装在./app /示例中。
3RDY PARTYAL DISPARYPARTS.ZIP（174.40 KB）-下载111次



      以下为原文

    I've come up with a tutorial that covers how to add a Mikroe display to an EF starter kit using some adapter boards.  The Mikroe display uses a SSD1963 graphics controller and a Focal Tech FT5x06 capacitive touch controller.
Attached are two files:
1) CreatingAGraphicsAppWithA3rdPartyDisplay.zip - tutorial documentation
2) 3rd_party_display.zip - resulting project , should be installed in ./apps/examples.
   Attachment(s)

CreatingAGraphicsA...yDisplay_parts.zip (56.43 KB) - downloaded 89 times
3rd_Party_Display_parts.zip (174.40 KB) - downloaded 111 times

以前帖子中的附件不好。我会把文件分开提供。



      以下为原文

    The attachments in the prior post are bad.  I'll provide the files in a separate post.
 

米迦勒，我在Windows 10 MealEndIt中提取教程文档zip遇到了一些问题。



      以下为原文

    Michael,
I seem to be having some problems extracting the tutorial documentation zip on my windows 10 machine
Edit: and so you noted.

文件：3RDYPARTIGHOLID.zIP:12FCA2DA-6AE1-4C8C-A6AA3B4B433／SDZJBDXF8F5A20PUZ6HMW2创建AgRAPHICS AppAd3aRD PARTIAL显示：http://www-TrimigFiel.COM/F958B2FA-3E55-9A4E-B3CFB3E8F15A/FZWN-DGP8GRO7GRIWITEMW2WI下面是使用TigBigBy的两个链接NKS将在6/1/2018工作。之后，我将提供如何获取这些文件的附加说明。



      以下为原文

    Here are two links using TransferBigFiles:
3rd_party_display.zip: https://www.transferbigfiles.com/12fca2da-6ae1-4c8c-a8dc-e6aa3b49b433/SdzujdbxF8F5A20puZ6HMw2
CreatingAGraphicsAppWithA3rdPartyDisplay: https://www.transferbigfiles.com/f958b2fa-3df5-4e55-9a4e-b3cfb3e8f15a/fZwn-DGp8GRo7GREiWtEmw2
 
These links will work through 6/1/2018.  After that I will provide additional instructions on how to get these files.

谢谢MichaelThese文件摘录精美



      以下为原文

    Thank you Michael
These files extract fine

谢谢米迦勒，BTW为什么司机需要一个BITBUG I2C？



      以下为原文

    Thanks Michael,
 
BTW why does the driver need a bitbanged I2C?

另外一个警告。示例项目将建立和运行，但它可能不会运行在MHC的和谐2.05.01，因为它是建立在一个原型的和谐2.06。试图重新配置它可能不起作用。



      以下为原文

    One additional warning.  The example project will build and run, but it probably won't run under the MHC in Harmony 2.05.01, since it was built under a prototype for Harmony 2.06.  Attempting to reconfigure it will probably not work.  

我们使用一个有点冲击的I2C驱动程序与EF初学者工具包的所有版本兼容。



      以下为原文

    We use a bit-banged I2C driver to be compatible with all versions of the EF starter kit.

嗯，使用米迦勒提供的代码，我创建了一个独立的FT5XX6驱动程序。附加的是将驱动程序添加到触摸节下的MHC树配置文件的文件。只需配置参数并准备就绪。解压缩文件夹并覆盖到/Orthy/V2Y05Y001>。



      以下为原文

    Well, using the code Michael provided I created a standalone FT5XX6 driver. Attached are the files that adds the driver to the MHC tree config under touch section. Just config the parameters and ready to go.
Unzip folders and overwrite to /harmony/v2_05_01
 
Best regards.
Francisco.
   Attachment(s)

DRV_FT5XX6.zip (47.41 KB) - downloaded 100 times

嗨，我还没有深入了解代码，但是我缺少了DrvouTouChyft5x66TouCHYBuffryEnviaHand定义。所以它没有编译



      以下为原文

    Hi,
 
I haven't had an in depth look at the code but I am missing the DRV_TOUCH_FT5XX6_TOUCH_BUFFER_EVENT_HANDLER definition. So it does not compile
 
 

也许米迦勒在《邮报》13中的评论是相关的。



      以下为原文

    maybe Michael's comments in post 13 are relevant 

我指的是吉格利的代码，但也许我今天晚些时候再看一下。



      以下为原文

    I meant jiggoly's code, but maybe I'll take a look at it later today wink:

我欠你一箱啤酒。非常感谢！



      以下为原文

    I owe you a carton of beer. Big thanks!

伟大的！咧嘴笑：我希望对你有用。用和声2.05和2.05.01检查。



      以下为原文

   
 
Great!!  grin:
 
I hope it works for you. Checked it with Harmony 2.05 and 2.05.01.