Rpi 3 - Unable to determine hardware version (BCM2835) about diozero HOT 9 CLOSED

pom.xml

        <dependency>
            <groupId>com.diozero</groupId>
            <artifactId>diozero-provider-pi4j</artifactId>
            <version>0.10</version>
        </dependency>

        <dependency>
            <groupId>com.pi4j</groupId>
            <artifactId>pi4j-core</artifactId>
            <version>1.1</version>
        </dependency>

Using PI4J direct API it's working ...

Using this, I cause a strange file system error (remount in ready-only):

        <dependency>
            <groupId>com.pi4j</groupId>
            <artifactId>pi4j-core</artifactId>
            <version>1.2-SNAPSHOT</version>
        </dependency>

from diozero.

I believe this is a problem with pi4j itself relating to it containing a C library this is statically linked to an old version of wiringPi. There is a command line option to force it to use the dynamically linked version (Google should be able to tell you the exact command line option).
Let me know how you get on with that.
I've not yet tried pi4j 1.2-SNAPSHOT.
If you are using diozero I would recommend using the built-in provider (only include to diozero-core and tinylog). Is there a reason you need to use the pi4j provider?
Matt

from diozero.

I was trying to use the RFID reader. I thought it would work only using a pi4j provider. After your comment I used built-in provider and it worked

I tested using the pi4j API directly (1.2-SNAPSHOT) and it works correctly. When I use pi4j provider + pi4j 1.2-SNAPSHOT, a strange file system error occurs and hangs the raspberry

I was in doubt of which is the advantage of pi4j provider ?

from diozero.

PS: Actually the problem is in the pi4j, I tried to use a PWM function and the same error happened.

from diozero.

Great. Pi4j support in diozero largely historic; the portability of the library is based on the pluggable providers. Support via pi4j was easy and added before I developed my own portable provider that will work on any device. If you require high performance GPIO control on the Pi you would need to use pigpio or my own memory mapped implementation.
If I get a moment I will look into the pi4j problem myself. Did you find the command line flag to force loading the dynamic pi4j / wiringPi library?

from diozero.

"Unable to determine hardware version. I see: Hardware : BCM2835", this has been solved using 1.2-SNAPSHOT, no need flag (-Dpi4j.linking=dynamic).

I got another error: Pi4J/pi4j-v1#319 (comment)
But i'll try (PWM / SPI) as root ... when I'm home

from diozero.

Do you have a reason for using pi4j? You might want to try the pigpio provider, I've found it to be quite reliable and has excellent PWM support (not just on the Pi's hardware PWM pins). It does, however, also require you to run as root.

from diozero.

Do you have a reason for using pi4j?
I believe it is the best known, and would have better support

thanks for assist

I'm planning on integrating your library as the basis of my framework when it comes to SBC
http://opendevice.io

from diozero.

Great, let me know how you get on.

from diozero.