gpio | Talk to your Single Board Computer 's gpio pins

I just started programming a STM32 and generated a code with CubeMX for an SPI communcation with a gyroscope (L3GD20) I have a problem with the HAL_SPI commands.

I first try to read the WHO_AM_I register which return a good response (0xD4) Then I tried to do the same with CTRL_REG1 register and it was still good by returning (0x07).

But if I try to get both of them one after the other, the HAL_SPI_Receive keeps sending the data of the first HAL_SPI_Transmit of the code... Tried to give it other buffers but still didn't work.

Here is the part of the code I'm intersted in :

I've taken a look at the device tree that is in use for a working i.MX6 based development board. I've noticed that in the case of the ethernet configuration, a confusing mix of directives are present. Namely:

1. Node fec1 contains a directive to delete node mdio
2. Node fec2 contains a reference to node ethphy1
3. Node ethphy1 is within mdio, the deleted node.

I realy hope im not the only one having this problem (i deleted my previous Question because it seems kinda missleading so heres my secont attempt)

I try to use the Rasbpery pi 4b GPIO Pins using a Uno app:

my setup:

i tried it before with a consol APP and it works:

Console APP Code:

I have a problem with memory violation problem that occurs if reach else if(argc == 2)

I'm trying to have a nice written script with no errors like that, anything else works like a charm...

Here's a code fragment:

I have a BeagleBone Black board and I'm using the below-mentioned image file. https://debian.beagleboard.org/images/bone-debian-10.3-iot-armhf-2020-04-06-4gb.img.xz

I aim to operate GPIO pins of this board with the c programming language.

To do so, I've gone through this link: https://beagleboard.org/static/librobotcontrol/installation.html

And after following all the steps according to this link the result I achieved is the same as mentioned in the checking functionality step [the last step] of this document.

Furthermore, I follow this document for c language setup: https://github.com/beagleboard/librobotcontrol/blob/master/docs/src/project_template.dox

and run this source code: https://beagleboard.org/static/librobotcontrol/rc_test_leds_8c-example.html

All these processes were completed without any error.

################################## Now I want to access the GPIO pins of the board. For that, I've prepared a basic code.

Let's take a pin P8_10 / GPIO2[4] for an example. So for that my code will be:

I am running a main python program on a Windows PC that is hooked to equipment that cannot be ran on an Raspberry pi. At a certain point in the main program, I want to call/execute a Rpi program to run. I need the GPIO pins from the Rpi to turn on a relay/s. Is there a way to wirelessly(or serially) open and run the program on the raspberry pi from the main program already running on the Windows PC?

Maybe I am not thinking of something, is there an easier and just as cheap solution to turn on a relay from the Windows PC program?

Any points in the right direction would be greatly appreciated.

I know similar question had already been answered, and I studied dilligently. I believe, I have tried nearly all possible combinations, without success:

I’m doing a home project with a raspi and a rain sensor.

Basically, with cronjobs, i run isitraining.py every 30 min.

If it is raining, i want it to increment a specific variable from another module (rains.water)

If it stops raining, i want it to decrease the same variable.

here are my codes:

rains.py

I am using Linux 4.19.55 armv7l on a omap3 processor. On my target there is a usb modem that gets power from a gpio pin value (defined under /sys/class/gpio). There are occasions when I change the value parameter of this gpio pin to bring down the hardware and while doing so I frequently get an error (thrown by musb_handle_intr_disconnect from inside drivers/usb/musb/musb_core.c ) as under:

"musb_handle_intr_disconnect 843: unhandled DISCONNECT transition (a_idle)"

I tried debugging the issue by mounting debugfs and capturing data from the concerned bus by using usbmon. Bus id is identified from lsusb output and confirmed by observing /sys/kernel/debug/usb/devices. I observe that usbmon is unable to capture data whenever the mentioned error shows up. In a no error scenario the usbmon does capture the traffic from the concerned bus. Please help how to debug this issue.