internal pullup and external interrupt issue about arduinocore-gd32 HOT 9 CLOSED

Can I ask you to pio pkg update -g -p gd32 again and test your original sketch, still without hardware pullups? I've tried to fix the bug in 5593435.

from arduinocore-gd32.

Could you remove the hardware pullups again and try this suggestion about the switched order?

#include <Arduino.h>

HardwareSerial Serial(PB7, PB6, 0);

void pinDidChange() {
Serial.println("pinDidChange");
}

void prepare() {
attachInterrupt(digitalPinToInterrupt(PA8), pinDidChange, CHANGE);
attachInterrupt(digitalPinToInterrupt(PA9), pinDidChange, CHANGE);
attachInterrupt(digitalPinToInterrupt(PA10), pinDidChange, CHANGE);
}

void setup() {

Serial.begin(115200);
Serial.println("EC11 Test");
// first setup interrupt (inits pin to "INPUT(_FLOATING)"
prepare();
// then activate their pullups
pinMode(PA9, INPUT_PULLUP);
pinMode(PA8, INPUT_PULLUP);
pinMode(PA10, INPUT_PULLUP);
}

void loop() {

delay(10);
// put your main code here, to run repeatedly:
}

from arduinocore-gd32.

work like a charm, thank you !

from arduinocore-gd32.

With what platformio.ini is that exactly for reference?

We previously did have issues with pin modes being incorrect but I was convinced they're all properly fixed now in this file.

When you only do pinMode(PA9, INPUT_PULLUP);, as the only command in setup() and nothing in loop(), is the pullup still off? We could have a bug in attachInterrupt that resets the input mode back to INPUT after all. Exchanging the order of prepare() and pinMode(PA9, INPUT_PULLUP); may be a workaround for this, but if that's true, then it's a bug.

from arduinocore-gd32.

Yes it's exactly like this. We have a bug.

pinMode(x, INPUT_PULLUP); should work perfectly fine, the only problem is that we're resetting it to input mode (without pullup or pulldown) during the attachInterrupt process. Will be fixed.

from arduinocore-gd32.

I use the board bluepill plus (https://github.com/WeActStudio/BluePill-Plus)

below is the ini file

[env:weact_bluepillplus_gd32f303cc]
platform = gd32
board = weact_bluepillplus_gd32f303cc
framework = arduino

from arduinocore-gd32.

oid gpio_interrupt_enable(uint32_t portNum, uint32_t pinNum, vo

in the future in case if I suspect some thing wrong with a function, I can I locate the right place right file as you did, say for example the interrupt? maybe I can do some pre-study/pre-investigation to help with.

from arduinocore-gd32.

it works! but this looks not compatible with standard Arduino "style" :-)

from arduinocore-gd32.

Exactly, that's why we're going to fix this bug in our code here. I think what's either correct is to simply not do the gpio_init() to INPUT_FLOATING (but still turn on the GPIO clock in case that's the first time the pin was used and there's no pinMode() done previously on it), or try to read the old pullup/pulldown mode and set it as the same. The first thing should be easier becasue it's just code removal and the INPUT_FLOATING case is the default GPIO configuration in all microcontrollers I've read.

from arduinocore-gd32.