GPIO

IRQ

Tue, 2019-11-19 00:09 -- ant777222

I am making some changes to the CodeLess code to fit the application that I need. I have added a read notify characteristic that I would like to use to monitor when the input of one of the GPIO pins goes high and when it goes back to low. I want to use an IRQ to do this but I am not too sure where the best place to add the IRQ in the CodeLess code is. Where would the best place to add this IRQ be?

Thanks,

Anthony

DSPS project and periph_init

Fri, 2018-08-24 08:13 -- Daekeun Yun

Hello
I'm trying to use DSPS project(DSPS 5.150.2). I added one characteristic to control GPIO at DSPS original project.
I can check the gpio is changed when I change the value of the characteristic.
The problem is that 'BLE_WAKEUP_LP_Handler' is continuously called which is calling the 'periph_init' function so that the gpio's state goes back to default state right after changing by BLE.
Could give me some advice about this?

external GPIO interrupt on rising edge

Mon, 2017-07-10 04:59 -- stanley_yeh

Hello,
I am using DA14585 with SDK 6.0.4, I also enabled ext-sleep mode.
A g-sensor is connected to a DA14585 through i2c. There is a interrupt pin.
The interruption of the sensor is designed as initially high, once the data ready, the interrupt pin will be low and then be high.
I would like to detect the rising edge for the interrupt pin, and I configure it as followings:

GPIO_ResetIRQ

Sat, 2016-07-30 02:26 -- justinturley

I need help understanding what the GPIO_ResetIRQ( ) call does, please.

Just to test its function I register the GPIO callback, enable the IRQ, then immediately RESET the IRQ (as shown below). I set a break point in button1_press( ), and even though I reset the IRQ the callback function is still called after an interrupt from pressing the button. So then, what does it do? The description found in the SDK documentation is less than helpful -> "Resets a GPIOn_IRQ interrupt."

Limitations to using pin 1_2 and 1_3

Fri, 2016-05-27 09:04 -- ankitdaf

Hi

I came across a custom board design around the Da14580 which has something peculiar in it's schematic. It states that "P1_2 and P1_3 cannot be toggled when 16 MHz XTAL is" .(the last word is cut off).

Is there any restriction on using pin 1_2 and 1_3 ? Is there any special dependency on the XTAL or some other peripheral ?

I tried looking for this in the datasheet but didn't find anything

Can I safely use it in my design for I2C ?

Thanks,

GPIO state during sleep during BLE connection

Fri, 2015-10-02 03:56 -- Jonathan Forrest

Hi,

I am having a very strange issue.

I am using an ADC channel on Port 0, Pin 1.
This line has a very weak pull down to 0V (about 1.5M).
During advertising, this pin happily sits at 0V whether the DA14580 is running or in sleep.

However, once a Bluetooth Connection has been made when the DA14580 goes into sleep, Port 0 Pin 1 goes to about 750mV.

GPIO_Set function reverting back to default state

Sat, 2015-08-15 00:52 -- skyng22003

Hi I am trying to add a connection indicator to the DSPS example,

In version DSPS 3.150.1.5:
I reserved the port and pin RESERVE_GPIO(RGB_LED_B, RGB_LED_B_PORT, RGB_LED_B_PIN, PID_GPIO); and configured pin GPIO_ConfigurePin(RGB_LED_B_PORT, RGB_LED_B_PIN,OUTPUT,PID_GPIO,true);

and upon state set APP_CONNECTED I ran the function GPIO_SetInactive(RGB_LED_B_PORT,RGB_LED_B_PIN); which switches on the LED,

the commands above works as expected when a connection is established the LED comes on and stays on.

Subscribe to RSS - GPIO