Hi Santiago,
I have found the following interpretation of the "UU" output on a Linux man page:
"UU". Probing was skipped, because this address is currently in use by a driver. This strongly suggests that there is a chip at this address.
I am not able to reproduce the issue of the i2c detect command, since we do only support our Linux BSP and boards. I would suggest you to get in contact with TQ so they help you more properly to address the solution to your problem using their board:
TQ support enquiry
You can also try to debug the I2C bus using a logic analyzer to determinate whether the device does respond with an acknowledge or find out if a wiring problem exists.
Best regards,
Ruben