GLOBAL_ADC: Architecture Description

GLOBAL ADC

GLOBAL_ADC
Architecture Description

Architecture Description

Figure 1 explains the architecture of the APP:
This would pictorially represent the internal workings of the GLOBAL_ADC. This shows the hardware resources that are consumed, the depended APPs and the various signals that would be exported out.

Figure 1 : Architecture of GLOBAL_ADC APP

The diagram above represents the internal software architecture of the GLOBAL_ADC APP. A GLOBAL_ADC APP instance exists in a DAVE-4.0 project with fixed attributes as shown and configures the VADC peripheral. This in addition requires the consumption of the CLOCK APPS for its configuration and functioning. The GLOBAL_ADC APP also provides output signals for inter-peripheral connections.


Signals:

The following table presents the signals provided by the APP for connection. It also gives the flexibility to configure and extend the connectivity to other APPs.
Table 1: APP IO signals

Signal Name Input/Output Availability

Description

global_signal Output Always

Global connection signal:
Should be connected to the APP which consumes the GLOBAL_ADC APP (By default).

end_of_arbitration_round_group0 Output Always End of arbitration round signal from group-0:
Can be connected to the VADC module for gating or trigger for the various request sources .
An end of the arbitration round raises a signal which can also be given to other peripherals.
end_of_sampling_signal_of_group0 Output Always

End of sampling phase signal from group-0:
Can be connected internally to the VADC module for gating or trigger for the various request sources.
Generates a signal when the sampling of a signal is completed.

end_of_arbitration_round_group1 Output Always End of arbitration round signal from group-1:
Can be connected to the VADC module for gating or trigger for the various request sources .
An end of the arbitration round raises a signal which can also be given to other peripherals.
end_of_sampling_signal_of_group1 Output Always

End of sampling phase signal from group-1:
Can be connected internally to the VADC module for gating or trigger for the various request sources.
Generates a signal when the sampling of a signal is completed.

end_of_arbitration_round_group2 Output Always End of arbitration round signal from group-2:
Can be connected to the VADC module for gating or trigger for the various request sources .
An end of the arbitration round raises a signal which can also be given to other peripherals.
end_of_sampling_signal_of_group2 Output Always

End of sampling phase signal from group-2:
Can be connected internally to the VADC module for gating or trigger for the various request sources.
Generates a signal when the sampling of a signal is completed.

end_of_arbitration_round_group3 Output Always End of arbitration round signal from group-3:
Can be connected to the VADC module for gating or trigger for the various request sources .
An end of the arbitration round raises a signal which can also be given to other peripherals.
end_of_sampling_signal_of_group3 Output Always

End of sampling phase signal from group-3:
Can be connected internally to the VADC module for gating or trigger for the various request sources.
Generates a signal when the sampling of a signal is completed.

group0_input_queue Input Always Queue selection for Group-0
If a ADC_QUEUE APP is consumed and the group to which the Queue belongs has to be forced to group-0 a connection can be made to the ADC_QUEUE APP
group0_input_scan Input Always Scan selection for Group-0
If a ADC_SCAN APP is consumed and the group to which the scan belongs has to be forced to group-0 a connection can be made to the ADC_SCAN APP
sync_request_signal_group0 Input Always

Sync request signal for Group-0
If a sync operation is needed and if the slave group must be forced to group-0 this connection can be made.

group1_input_queue Input Always Queue selection for Group-1
If a ADC_QUEUE APP is consumed and the group to which the Queue belongs has to be forced to group-1 a connection can be made to the ADC_QUEUE APP
group1_input_scan Input Always Scan selection for Group-1
If a ADC_SCAN APP is consumed and the group to which the scan belongs has to be forced to group-1 a connection can be made to the ADC_SCAN APP
sync_request_signal_group1 Input Always

Sync request signal for Group-1
If a sync operation is needed and if the slave group must be forced to group-1 this connection can be made.

group2_input_queue Input Always Queue selection for Group-2
If a ADC_QUEUE APP is consumed and the group to which the Queue belongs has to be forced to group-2 a connection can be made to the ADC_QUEUE APP
group2_input_scan Input Always Scan selection for Group-2
If a ADC_SCAN APP is consumed and the group to which the scan belongs has to be forced to group-2 a connection can be made to the ADC_SCAN APP
sync_request_signal_group2 Input Always

Sync request signal for Group-2
If a sync operation is needed and if the slave group must be forced to group-2 this connection can be made.

group3_input_queue Input Always Queue selection for Group-3
If a ADC_QUEUE APP is consumed and the group to which the Queue belongs has to be forced to group-3 a connection can be made to the ADC_QUEUE APP
group3_input_scan Input Always Scan selection for Group-3
If a ADC_SCAN APP is consumed and the group to which the scan belongs has to be forced to group-3 a connection can be made to the ADC_SCAN APP
sync_request_signal_group3 Input Always

Sync request signal for Group-3
If a sync operation is needed and if the slave group must be forced to group-3 this connection can be made.