[Touch controller] Luckfox Pico Ultra W Support

  • Hello, if you use LF40-480480-ARK the touch chip is GT911, if you still plan to use i2c control, the list of i2c touchscreen drivers supported by the SDK is as follows https://github.com/LuckfoxTECH/luckfox ... ouchscreen
  • Hello Crocodile
    Its OK for find touch controller part number.
    Thanks for your support.
  • Crocodile wrote: 2025-04-28 1:56 Hello, if you use LF40-480480-ARK the touch chip is GT911, if you still plan to use i2c control, the list of i2c touchscreen drivers supported by the SDK is as follows https://github.com/LuckfoxTECH/luckfox ... ouchscreen
    Hello Crocodile
    I rechecked that LF40-480480-ARK module have adapter contains MCU.
    Could you please explain the functions of Arm MCU?
    Therefore, for my custom res touch LCD, will i connect touch pin directly to Luckfox FPC header?
    I wonder that MCU on adapter will make a buffer circuit btw the RV1106 and touch conntroller?
    Please help to review and advise.
    Thanks.
  • For the normal RGB screen initialization, an initialization sequence needs to be sent via SPI. Since the Luckfox Pico Ultra has no extra pins, the LF40-480480-ARK uses the MCU to assist in the screen initialization. If you are sure that your screen pins match those of the Luckfox Pico Ultra, you can directly connect them without going through a adapter board.
  • Crocodile wrote: 2025-09-20 10:05 For the normal RGB screen initialization, an initialization sequence needs to be sent via SPI. Since the Luckfox Pico Ultra has no extra pins, the LF40-480480-ARK uses the MCU to assist in the screen initialization. If you are sure that your screen pins match those of the Luckfox Pico Ultra, you can directly connect them without going through a adapter board.
    Hello Crocodile
    My screen is RGB888 have SPI resistance touch.
    For display, I have your recommend to convert from RGB666 on Luckfox Pico W to RGB88.
    Its difficult to interface with SPI touch when SPI port on Luckfox board was used for LCD data bus, while soft SPI can reduce the performance.
    So could you please recommend some I2C res touch controller part number was build in the Kernel ?
    Thanks for your support.
  • RGB888 is a hardware requirement for the display interface and there is no room for compromise. Missing pin connections will prevent the screen from displaying properly. The interface of RV1106 supports a maximum of RGB666. If you need to determine which I2C touch chips are supported by the kernel, you can check in $SDK/sysdrv/source/kernel/drivers/input/touchscreen/.