AS0260CSSC28SUD20 datasheet(50/83 Pages) ONSEMI

50 / 83 page

AS0260 DS Rev. G Pub. 5/15 EN

©Semiconductor Components Industries, LLC, 2015.

AS0260: 1/6-Inch 1080P High-Definition (HD) System-On-A-Chip (SOC) Digi-

tal Image Sensor

The CamControl and UVC Control interfaces will be coherent (where applicable) on

completion of a 'Refresh' command. If a UVC variable's coherency is not applicable this

will be stated in the variable's description.

No Multivariable Atomic Changes All UVC control variable changes will be indepen-

dent - there is no mechanism to 'group' a set of changes to variables together (as in the

'Refresh' command for the CamControl variables). If multiple UVC control variables are

changed, there is no guarantee that all changes will occur on the same frame.

Indeterminate Change Latency The latency from when a UVC variable is changed, to

when the change takes effect, is indeterminate, and is dependent on where within the

frame the UVC change is made. The worse-case latency is two frames. The AS0260

implements the 'Wait For Event' command to allow the host to synchronize to the

AS0260 frame timing, and to be sure that a UVC change has been applied.

UVC Control Interface

The following subsections detail the variables exposed by the UVC page. Each variable is

documented in its own subsection, including its valid range and default value.

Note:

The default value of most UVC control variables is dependent upon the underlying

CamControl interface configuration, which is determined by the host at start-up.

All UVC control variables must indicate whether a change was accepted via the

UVC_RESULT_STATUS variable (R0xCC24 or VAR(0x13,0x0024)). This variable is

provided for diagnostic purposes only, to help track down why changes to UVC variables

are being ignored. It does not form part of the UVC 1.1 standard.

Whenever a change is made to a UVC variable, the firmware will process the change and

indicate the result of the change in UVC_RESULT_STATUS. Typically, a value of ENOERR

will indicate the change was accepted. Any other value indicates the change was

rejected. Table 1 shows the result status codes and their typical interpretations. Where

the typical interpretation does not match Table 1, this will be indicated within the indi-

vidual UVC variable documentation.

The host must be aware that UVC_RESULT_STATUS will always indicate the result of the

last-changed UVC variable; the previous value of UVC_RESULT_STATUS will be over-

written by each subsequent change. If the host simultaneously modifies multiple UVC

variables during the same frame, UVC_RESULT_STATUS will only indicate ENOERR if all

changes were accepted. If any change is rejected, there is no mechanism for the host to

determine which change it was. It is therefore strongly recommended that during devel-

opment, the host only modify one UVC variable per-frame.

Table 14:

UVC_Result_Status Codes

Value

Mnemonic

Typical Interpretation (each variable may re-interpret)

0x00

ENOERR

No error - change was accepted and acted upon

0x08

EACCES

Permission denied

0x09

EBUSY

Entity busy, cannot support operation

0x0C

EINVAL

Invalid argument

0x0E

ERANGE

Parameter out-of-range

0x0F

ENOSYS

Operation not supported

AS0260CSSC28SUD20 датащи(PDF) 50 Page - ON Semiconductor

AS0260CSSC28SUD20 датащи(HTML) 50 Page - ON Semiconductor

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83

датащи скачать

ссылки URL