bobn2
Forum Pro
In the case of a sensor with on-chip ADCs and a digital output, it is. So now you have learned something.I didn't realize you think the sensor is the only hardware that matters in compiling the image.Sure, no-one denies that, but generally we don't call designing the software...
Who do you think I should ask? CPUs, by the way are things that run software. If you're using a CPU to 'compile the image', you're using software.That explains a lot. Maybe you should ask someone about application-specific integrated circuits (ASIC) , A/D converters and CPUs.
Well, maybe if you're one of the people I could be asking, perhaps you might explain, if you have a sensor in which the ADCs are on chip, the output is digital, and the internal operating parameters (such as clock frequencies, capture windows, capture timing, read chain gain) are controlled by programmable registers, just what are these 'ASICs and A/D converters' you speak of are doing? Given, that is, that the CPU you mentioned will be running software which will cause those registers to be programmed with the values chosen by the software developers.Then come back and we can talk.
BTW, I have actually designed an ASIC for interfacing a Sony sensor to an application processor. It doesn't change the numbers coming out of the sensor, it's only task is to translate Sony's proprietary data format (8 lane sub-LVDS) to a format that the application processor can accept (in this case MIPI CSI-2). So when you come up with your answer, you need to concentrate on ASICs which actually alter the performance of the sensor.
--
263, look deader.
Last edited: