Hello,
I have on my feather 9160 5 inputs, ⅔ outputs, 2 ADC, and an extra serial port.
Inputs on: p0.02, p0.15, p0.16, p0.17, p0.18
Output p0.04, p0.01 and an external led that does the same as the led on board.
ADC p0.13 p0.14
serial tx p0.19, rx p0.21
Everything works except for output p0.01 it keeps an output volt floating between 1.4 & 0.4v.
I use the same flags and configs for p0.04 that does work. It is going nice to 3.3v high and 0v low
I did try assigning other pins but with the same result, although the output voltage does differ. I also did try to switch p0.04 with p0.01 and after that p0.04 is still working and p0.01 not. This gives me the conclusion it is not a software problem.
Tried on more than 1 feather with same result.
Is this a known problem and is there a fix?

    @postpiet can you share the code you’re using to initialize P0.01? It is not shared with any other function so there shouldn’t be any hardware influencing the pin.

    What are you connecting it to?

      jaredwolff
      Devtree:

      / {
leds {
        compatible = "gpio-leds";
        ssr0: ssr_0 {
            gpios = <&gpio0 4 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>;
            label = "SSR";
        };
        buzz: buzz_0 {
            gpios = <&gpio0 1 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>;
            label = "Buzz";
        };
};

      Code:

      
static const struct gpio_dt_spec SSR_spec = GPIO_DT_SPEC_GET(DT_NODELABEL(ssr0), gpios);
static const struct gpio_dt_spec LED_spec = GPIO_DT_SPEC_GET(DT_NODELABEL(blue_led), gpios);
static const struct gpio_dt_spec BUZZER_spec = GPIO_DT_SPEC_GET(DT_NODELABEL(buzz), gpios);

void init_GPIO(void){
gpio_pin_configure_dt(&SSR_spec, GPIO_OUTPUT);
	gpio_pin_configure_dt(&LED_spec, GPIO_OUTPUT);
	gpio_pin_configure_dt(&BUZZER_spec, GPIO_OUTPUT);
}

void main(void){
gpio_pin_set_dt(&BUZZER_spec, 1);
				k_msleep(5000);
				gpio_pin_set_dt(&BUZZER_spec, 0);
				gpio_pin_set_dt(&SSR_spec, 1);
}

      I connect it to a npn transistor so p0.04 ‘SSR’ can switch on a solid state relay. And p0.01 to npn transistor to a buzzer. both transistors are on the ground side.

      when i switched the pin from ssr to p0.01 and buzz to p0.04 p0.04 still was the only one working altough it was then init as buzz and not the previously working ssr.

          Can you share the circuit diagram for that part of the circuit?

            I have run a few examples. Without a solution till now. The most basic one is 3 off board leds should be blinking at the same rate as the onboard led. The led on p0.04 works fine same as above LOW 0v HIGH 2V. The led on p0.01 stays between 0.05v and 0.5v but the difference in voltage doesn’t correlate with the blink signal. The p0.00 starts off with the same high voltage as p0.04 but low is fluctuating. So when in low state the voltage swings between led just on and just off. After some time the low state become 0v so it regulate it self after some time. All 3 external led should do the same thing. I will add a pic below if i find out how to do that.

              [https://github.com/Jorin-Post/stereo_camera_calibrate/blob/main/Screenshot%202024-09-26%20103328.png]

              Update: It is a software bug. I used a blank program and try to blink all 4 leds that works. Now I only need to find the bug in my code.

              My code is build further on NRF_cloud_multi_service. Inside cloud_connection_thread_fn(void) is the line conn_mgr_all_if_connect(true); that is messing with the gpio’s. Why I don’t know jet. If I find out, I will update this post. If you have an idea let me know.

              in my experience, it sometimes requires to build with

              west build ... --pristine

              because incremental builds may fail on changes in the config or device tree. At least, before I complain, I try a –pristine build.

              Alternatively you may move or remove the build-folder before building.

                Thanks @AchimKraus for thinking with us. Unfortunately pristine build didn’t work.

                I didn’t find the problem, but I have a fix. The problem was in the function nrf_modem_lib_trace_init();. So I in prj.conf changed CONFIG_NRF_MODEM_LIB_TRACE form y to n this prevents nrf_modem_lib.c > int nrf_modem_lib_init(void){} > nrf_modem_lib_trace_init(); to run in and the gpios keeps working as they should. So far I know runs my code as it should and no regressions.

                I hope this description will prevent someone else the time of debugging.

                  Thanks @AchimKraus for thinking with us. Unfortunately pristine build didn’t work.

                  I didn’t find the problem, but I have a fix. The problem was in the function nrf_modem_lib_trace_init();. So I in prj.conf changed CONFIG_NRF_MODEM_LIB_TRACE form y to n this prevents nrf_modem_lib.c > int nrf_modem_lib_init(void){} > nrf_modem_lib_trace_init(); to run in and the gpios keeps working as they should. So far I know runs my code as it should and no regressions.

                  I hope this description will prevent someone else the time of debugging.

                    pinctrl - UART1

                    <NRF_PSEL(UART_RX, 0, 1)>

                    Just in the case you need a modem trace as well, you need to change that in an overlay. But disable UART1 (by disable CONFIG_NRF_MODEM_LIB_TRACE) works for sure as well, as you already found out.

                    pinctrl - UART1

                    <NRF_PSEL(UART_RX, 0, 1)>

                    Just in the case you need a modem trace as well, you need to change that in an overlay. But disable UART1 (by disable CONFIG_NRF_MODEM_LIB_TRACE) works for sure as well, as you already found out.

                    Terms and Conditions | Privacy Policy