ADuCM4050 SensorStrobe inputs

Hi TRezucha,

A typical connection between ADuCM4050 and ADXL362 would be:

• Connect SensorStrobe pin on the MCU (output) with INT2 on the accelerometer (input).

        Purpose: MCU provides the trigger when the accelerometer has to acquire data

• Connect INT1 on the accelerometer (output) with any external interrupt pin (SYS_WAKEx) on the MCU (input)

        Purpose: Accelerometer wakes up the MCU when FIFO almost full (watermark)

The Input Sampling capability mentioned on page 21-8 of the Hardware Reference Manual is intended to monitor up to three GPIO inputs from an external device, which can be sampled based on the output pulse sent to that external device. Each SensorStrobe channel can be configured to interrupt the ADuCM4050 MCU when a specific activity is detected on these GPIO inputs, e.g. sensor states like FIFO full, switch open, threshold crossed…. It is very useful when different inputs need to be analyzed at the same time. In the case that you describe, as it is only one device being monitored it is recommended to use an external interrupt pin (easier to configure).

Right now the information with respect the GPIOs that might be sampled is missing on the Hardware Reference Manual, as you notice. We will include all the information on the next version. As you correctly pointed, those 8 GPIOs are P0.12, P2.0, P0.9, P0.8, P1.13, P1.2, P2.7 and P2.9 (to be configured as 0, 1, 2 …7 in SSxGPINySEL bitfields the RTC_GPMUX0 and RTC_GPMUX1 registers).

Currently there is no released example code showing the input sampling and input compare capabilities.

Kind regards,

Monica

Hi TRezucha,

A typical connection between ADuCM4050 and ADXL362 would be:

• Connect SensorStrobe pin on the MCU (output) with INT2 on the accelerometer (input).

        Purpose: MCU provides the trigger when the accelerometer has to acquire data

• Connect INT1 on the accelerometer (output) with any external interrupt pin (SYS_WAKEx) on the MCU (input)

        Purpose: Accelerometer wakes up the MCU when FIFO almost full (watermark)

The Input Sampling capability mentioned on page 21-8 of the Hardware Reference Manual is intended to monitor up to three GPIO inputs from an external device, which can be sampled based on the output pulse sent to that external device. Each SensorStrobe channel can be configured to interrupt the ADuCM4050 MCU when a specific activity is detected on these GPIO inputs, e.g. sensor states like FIFO full, switch open, threshold crossed…. It is very useful when different inputs need to be analyzed at the same time. In the case that you describe, as it is only one device being monitored it is recommended to use an external interrupt pin (easier to configure).

Right now the information with respect the GPIOs that might be sampled is missing on the Hardware Reference Manual, as you notice. We will include all the information on the next version. As you correctly pointed, those 8 GPIOs are P0.12, P2.0, P0.9, P0.8, P1.13, P1.2, P2.7 and P2.9 (to be configured as 0, 1, 2 …7 in SSxGPINySEL bitfields the RTC_GPMUX0 and RTC_GPMUX1 registers).

Currently there is no released example code showing the input sampling and input compare capabilities.

Kind regards,

Monica