Howdy y'all, I am working on bringing up some of the features on the Laird BT610 board. I've been able to bring up the digital and magnetic sensors. However, I'm a bit confused with the analog and tem

#driver #nrf52840 #gpio

Thanks Erik for the pointer. There was a race issue in initializing the pin before the driver was ready. I changed from SYS_INIT(board_init, POST_KERNEL, CONFIG_KERNEL_INIT_PRIORITY_DEFAULT); to SYS_I

#gpio #nrf52840 #sys_init

I realize I mentioned the need to set the pin low and that code above is attempting to set the pin high. If I just start the board without this code, the pin is measured low on my oscilloscope even wi

#gpio #nrf52840 #sys_init

Greetings, I'm working on adding a board to Zephyr. I'm attempting to use a board.c file to configure GPIO pins as output and initialize them low on start-up. I've attempted to follow existing boards,

#gpio #nrf52840 #sys_init

Hello, Can someone please tell how to read/write to GPIO pins (ports P0 and P1)? I am using zephyr and NRF Connect v1.30 Thank you. Kind regards Mohamed Belaroussi

#gpio

Ok, found the issue: It was do to pin mapping naming. I was assuming that the pinmaps in Arduino D5, D6, and so on, corresponded to a direct GPIO map, so D5->GPIO_5 and so on... and that's not true. A

#gpio #nrf52832

Have you done the initialization by running gpio_pin_configure with GPIO_OUTPUT_ACTIVE as third argument ? Just to be clear, you´re trying to set pin p0.05 ? That´s located on chip pin7 (QFN48 pkg) ?

#gpio #nrf52832

Hi, No MCUBoot. And yes, the board boots correctly and I can use GDB to debug. I can see the GPIO driver calls, the values that are set and so on. My prj.conf file is as simple as it can get: CONFIG_G

#gpio #nrf52832

Are you sure that your board boots correctly? ( debug through gdb or just simple serial output ) What version of the SDK are you using? Is MCUBoot activated in your prj.conf?

#gpio #nrf52832

Not sure if I'm going to have any help on this, but anyway: I've a standard NRF52832 module that has connected to pin 5 a red LED. If I flash the module (through JLink) with the Arduino framework, the

#gpio #nrf52832

Hi, I am wondering if anyone has tried reading for a serial port using node-red Currently, I'm using putty to read messages sent from my device built with help from zephyr mesh demo, as I'm using the

#ble #bluetoothmesh #gpio #usb #bluetooth

Danny, I find the best place to start is the samples, you should find examples of unsolicited messages in the mesh samples. You may also find that the Micro:bit is notoriously difficult to work with d

#ble #bluetoothmesh #gpio #bluetooth #nrf51822

Hi, I am currently doing an engineering project for my final year, I have been using the bluetooth mesh demo on the zephyr project using the bbc microbits, I have set up a pir sensor up to produce a s

#ble #bluetoothmesh #gpio #bluetooth #nrf51822

I just realized I responded to you privately by accident, Lawrence. Sorry about that. I will copy the message I sent to you to the group so that the discussion is up to date. The suggestion regarding

#gpio #nrf52832

Hi Brian: You can always test the value of the GPIO with gpio_pin_read() in the callback, if it is 1, then the cause is a rising edge, and if it is 0 the cause was a falling edge. Unfortunately if the

#gpio #nrf52832

Hello, I hope I am posting this question in the correct place. I have an interrupt handler which can be configured to trigger on either edge. This is working perfectly, but I want to perform a differe

#gpio #nrf52832

Hi, You may want to look at a couple of things to help you answer your own question: In the zephyr folders; It has the list of defines and corresponding pins The other useful information would be a cl

#zephyrbluetoothmesh #sensor #ble #bluetoothmesh #gpio

Hi All, Im currently working on my 3rd year engineering project and I need some help/guidance as I'm a complete beginner. My project is a home monitoring system and my plan is to use PIR motion sensor

#zephyrbluetoothmesh #sensor #ble #bluetoothmesh #gpio

Hello again :) "leonardomt via Lists.Zephyrproject.Org" <leonardomt=gmail.com@...> writes: I would say that if the hardware supports interrupts, then the Zephyr GPIO driver for it

#gpio #dts

Is there a way to detect programmatically if a given pin can be configured as interrupt using Zephyr? (e.g. some sort of a map/list or macros that I could reuse). Are there any side effects in configu

#gpio #dts