Klistrar in en brutalt lång text från xda. Här är en person som verkligen vet vad han snackar om.
"Hi, my first post here, but I've been following this topic for some time, with some amusement, and now you're getting close to the truth, I finally feel compelled to register and shed some light on the subject.
Firstly, a bit about myself; I'm a software developer with an electronics background. I work in embedded systems development; a mobile phone is an embedded system although I'm in a very different market, but the principles are very similar. More specifically, I develop all the low level code for our systems, the first instructions that execute after power on are the ones I write in machine code. Reading and interpreting HW datasheets is my day job, so I'm in a pretty good position to explain a few things.
Anyway, enough about me and onto the X10 and multitouch debate
Firstly, thanks to Utking for providing the key info to finding the controller. I'm pretty much with you on this one, looking at the numbers on the chip and your magnified view it seems we know the controller chip. There is an 'A' missing from the chip number, but that is not so unusual, so it seems that the X10 is fitted with a CY8C20466A-24LQXI device.
For those that are interested, you can find the datasheet here:
www cypress com /?docID=24157
To break down the part number
CY = Cypress
8 = PSoC (I'll get to this in a bit)
C = CMOS technology
20 = Family Code
466A = Part Number
-24 = Speed

24MHz)
LQX = Packaging (LQX=QFN Package [matches the posted image])
I = Industrial applications
So from this info, we can determine a few specifics about the device, namely:
- It has a 32-pin QFN package
- It has 32KB of FLASH memory
- It has 2KB SRAM
- It has a single CapSense block
- It has 28 IO pins configurable as Digital I/O or Analogue Input
- It has an XRES pin (whatever that does )
- It does not support USB
- It has a built in Analogue to Digital converter.
You can all argue day and night about different part numbers if you like, it only changes a few of the parameters above but doesn't really change anything about what the device can or can't do!
But does it support multitouch I hear you all cry? Well that's where you have to look a little deeper (and understand) a bit more about what the datasheet is telling us!
Firstly we need to understand what this device actually is! The general assumption that has been made so far on these forums is that the touch screen controller is some magical chip that you just connect up to the touchpad and it just works and either does or doesn't support MT depending on the type of chip you installed! WRONG!!!
This device is very different; it is a very generic capacitive touch controller device that can be configured (n.b. programmed) for each specific application. The same chip can be used for controlling mobile phone touch screens, the little mouse pad on your laptop, simple capacitive touch buttons, basically anything that changes its capacitance when you touch it. The key give-away here is that it has 32KB FLASH and 2KB RAM - Dedicated controllers don't have FLASH and RAM (at least not that you would care about).
Basically, this is a programmable device, that MUST be programmed by the HW developer (SE in this case) for it to do anything. So during the manufacturing stage, in the same way that the latest FW is written to the main FLASH memory, all programmable devices on the main circuit board (there are probably others) are also flashed with their programs.
This is where I get back to that 8 digit in the device number and PSoC. The Electronics Guru's that make the HW, generally don't do software, so for devices like this they are provided with PC applications to configure and program the devices for their specific needs. In the case of this device, the application they use is called PSoC. Basically with this application, the HW guys use a GUI interface to drag and drop functional blocks which can then be tied together and where necessary, assigned to HW pins. Have a look here for some info on PSoC:
www cypress com /?id=2522&rID=40632
So... THE BIG QUESTION!
CAN THIS CONTROLLER DO MULTITOUCH?
The answer is YES ....If you want it to!
To elaborate; if the SE HW guys dragged and drop the multitouch handling block into their GUI window, then it can do multitouch. If they dragged the single touch block, then no it can't! Its all down to the way it was programmedin the factory!
Without so detailed info from the SE hardware guys who did the device programming, it's unfortunately impossible to tell if the X10's hardware does or does not support MT. All we can say, is that the X10 is fitted with a controller that COULD support MT if so desired!
But can't the devs just re-program it?
Unfortunately that's not so simple. Flashing these devices can't normally be done remotely, rather they have to be connected to a special HW programmer and the board powered on in such a way that the device enters its programming mode (usually with a different voltage). That means it can (probably) only really be re-programmed in the SE factory. Also the devs here would have to get their hands on the original PSoC design in order to produce a compatible program.
So, the long and short of it is, we technically have HW support for MT, but the actual configuration of the HW may be such that we have no MT. Only SE can tell us if it does or does not support MT, and they are saying it doesn't, so the chances are IT DOESN'T
We can only hope that some nice SE HW engineer who really does know, will magically appear and tell us that it does support it.... well, here's dreaming
One thing that is for sure, we can stop arguing about what controller is fitted and if it supports MT because its a dead end!
I hope you enjoyed my first post here and are not too disappointed by it "
Click to expand...