Where did the touch driver code go?

Martin, my apology to you personally if my critique of the product offended, but after hours of head banging (which included reading literally everything published on this topic, including the material you reiterated, plus scouring the forums in an attempt to piece together a coherent path to success), I had to express my dissatisfaction to someone. I actually feel sorry for you, as I have been following your posts regularly and know for certain you have been a VERY busy man, thrown into quite a mess. But yes, I have done this for many years, and I detect an air of emergency in the boards lighting up out there. When a system that was working no longer does after a new release, this tells me that, indeed, there is not adequate testing in place, as I know that regression testing in software is designed to ensure that such things do not catch an installed user base off guard. So, again, my critique is not aimed at you specifically, an employee of ST doing the best you can to put out fires, and "train wreck" is less a value judgement, and more a description of what I take to have been an avoidable problem on ST's part. Live and learn, I guess.

That said, I have read everything I can get my hands on about this new release, and spent several hours bringing up a demo on a Discovery board. Part of the problem, I think, is that the “Templates�? are nowhere to be found within my installation of Designer 4.13 (I have installed/repaired it three times now; only the simulator is available to select. I do not know why this is. It certainly contradicts the published guides I have seen.) Even so, I managed to go in from the Cube side and get a screen up and running, using the .part file that was generated there, but without the touch facility. This is when I discovered that the cpp file which formerly implemented this feature apparently no longer does. This is pretty much dead in the water at this point, as there are no examples without the template. Perhaps I missed a step along the way. Taking what I can from various users out there, I have learned much, but I'm not finding a single source that shows how this last piece is done. Again, I could have missed something that in retrospect will seem obvious, but from the trenches, it is hidden at this point.

Best regards to you and your support team, and thanks for any insight you might provide. Eventually these things settle out, and I can wait until the next clean release if necessary.

-Vince

I don't get it, sorry :) What "snippets" are you talking about?

Here's the STM32TouchController.cpp you get from the F746G-DISCO Application template. Works fine, i just tested it (again) :)

#include <STM32TouchController.hpp>
#include <TouchGFXHAL.hpp>
#include <ft5336.h>
#include <stm32f7xx_hal.h>
#include <touchgfx/hal/OSWrappers.hpp>
 
static TS_DrvTypeDef* tsDriver;
extern I2C_HandleTypeDef hi2c3;
 
void STM32TouchController::init()
{
 /* Initialize the TS driver structure */
 tsDriver = &ft5336_ts_drv;
 
 /* Initialize the TS driver */
 tsDriver->Start(TS_I2C_ADDRESS);
}
 
bool STM32TouchController::sampleTouch(int32_t& x, int32_t& y)
{
 /* Checking if the screen has been touched */
 
 if (tsDriver)
 {
 if (tsDriver->DetectTouch(TS_I2C_ADDRESS))
 {
 /* Get each touch coordinates */
 tsDriver->GetXY(TS_I2C_ADDRESS, (uint16_t*)&y, (uint16_t*)&x);
 return true;
 }
 }
 return false;
}
 
/**
 * @brief Manages error callback by re-initializing I2C.
 * @param i2c_handler : I2C handler
 * @param Addr: I2C Address
 * @retval None
 */
static void I2Cx_Error(I2C_HandleTypeDef* i2c_handler, uint8_t Addr)
{
 /* De-initialize the I2C communication bus */
 HAL_I2C_DeInit(i2c_handler);
 
 /* Re-Initialize the I2C communication bus */
 //I2Cx_Init(i2c_handler);
}
 
/**
 * @brief Reads multiple data.
 * @param i2c_handler : I2C handler
 * @param Addr: I2C address
 * @param Reg: Reg address
 * @param MemAddress: Memory address
 * @param Buffer: Pointer to data buffer
 * @param Length: Length of the data
 * @retval Number of read data
 */
static HAL_StatusTypeDef I2Cx_ReadMultiple(I2C_HandleTypeDef* i2c_handler,
 uint8_t Addr,
 uint16_t Reg,
 uint16_t MemAddress,
 uint8_t* Buffer,
 uint16_t Length)
{
 HAL_StatusTypeDef status = HAL_OK;
 
 status = HAL_I2C_Mem_Read(i2c_handler, Addr, (uint16_t)Reg, MemAddress, Buffer, Length, 1000);
 
 /* Check the communication status */
 if (status != HAL_OK)
 {
 /* I2C error occurred */
 I2Cx_Error(i2c_handler, Addr);
 }
 return status;
}
 
/**
 * @brief Writes a value in a register of the device through BUS in using DMA mode.
 * @param i2c_handler : I2C handler
 * @param Addr: Device address on BUS Bus.
 * @param Reg: The target register address to write
 * @param MemAddress: Memory address
 * @param Buffer: The target register value to be written
 * @param Length: buffer size to be written
 * @retval HAL status
 */
static HAL_StatusTypeDef I2Cx_WriteMultiple(I2C_HandleTypeDef* i2c_handler,
 uint8_t Addr,
 uint16_t Reg,
 uint16_t MemAddress,
 uint8_t* Buffer,
 uint16_t Length)
{
 HAL_StatusTypeDef status = HAL_OK;
 
 status = HAL_I2C_Mem_Write(i2c_handler, Addr, (uint16_t)Reg, MemAddress, Buffer, Length, 1000);
 
 /* Check the communication status */
 if (status != HAL_OK)
 {
 /* Re-Initiaize the I2C Bus */
 I2Cx_Error(i2c_handler, Addr);
 }
 return status;
}
 
/**
 * @brief Writes a single data.
 * @param Addr: I2C address
 * @param Reg: Reg address
 * @param Value: Data to be written
 * @retval None
 */
void TS_IO_Write(uint8_t Addr, uint8_t Reg, uint8_t Value)
{
 I2Cx_WriteMultiple(&hi2c3, Addr, (uint16_t)Reg, I2C_MEMADD_SIZE_8BIT, (uint8_t*)&Value, 1);
}
 
/**
 * @brief Reads a single data.
 * @param Addr: I2C address
 * @param Reg: Reg address
 * @retval Data to be read
 */
uint8_t TS_IO_Read(uint8_t Addr, uint8_t Reg)
{
 uint8_t read_value = 0;
 
 I2Cx_ReadMultiple(&hi2c3, Addr, Reg, I2C_MEMADD_SIZE_8BIT, (uint8_t*)&read_value, 1);
 
 return read_value;
}
 
/**
 * @brief TS delay
 * @param Delay: Delay in ms
 * @retval None
 */
void TS_IO_Delay(uint32_t Delay)
{
 HAL_Delay(Delay);
}

Have you included the component folder and the TS driver?

All the variables and addresses should be available when you tab-complete otherwise there's something missing