Open pawsko opened 7 months ago
I don't believe you are in error. I have example devices that use this same write of a byte. They have worked correctly a long time on both pi4 I have. I tried this example code of both pi and now one failed with your error. The pi that operates correctly has the OS updates. The machine that failed has been used in various testing with different java etc. i know i updated the firmware early this month. The update that warns you of the danger in doing it. I tried the steps to revert the firmware to the correct level and it failed. So i created a new SD card. The failing pi operated correctly on this new OS image. So i question if there is a problem with the OS or fixes or firmware on your pi. Can you image a new SD and retry your code ?
Linux raspberrypi 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux Raspberry Pi 3B+ Pi4J 2.4.0 pigpio-i2c provider
I am trying to use the pigpio-i2c provider to write to a device using
And I am faced with the issue. I know that byte has range from -128 to 127. Inside there is a magic which transforms Java signedbyte value to native C library unsigned value. I cannot write using the pigpio-i2c provider any value lower than 0. I spent a lot of time debugging but still no results. The same error appears: SUCCESS=false; RESULT=-81 which means PIGPIO ERROR: PI_BAD_PARAM; bad i2c/spi/ser parameter. Below are a couple of console logs:
Success write 0 (0x00)
Success write 127 (0x7F)
Unsuccess write -127 (0x80)
Unsuccess write -1 (0xFF)
What am I doing wrong? :) Any ideas, suggestions, directions? Thanks in advance