Merge pull request #131 from Pi4J/bmeSpi_device_driver_updates

update BMESPI device for recent Driver updates. Basically remove the …

Author: taartspi

pom.xml

@@ -110,13 +110,11 @@
             <artifactId>pi4j-plugin-gpiod</artifactId>
             <version>${pi4j.version}</version>
         </dependency>
-        <!--  requires driver verification >
-       <dependency>
+        <dependency>
            <groupId>com.pi4j</groupId>
            <artifactId>pi4j-plugin-ffm</artifactId>
            <version>${pi4j.version}</version>
        </dependency>
-       <-->
        <dependency>
            <groupId>com.pi4j</groupId>
            <artifactId>pi4j-plugin-linuxfs</artifactId>

src/main/java/com/pi4j/devices/bme280/BME280DeviceSPI.java

@@ -40,8 +40,6 @@
 import com.pi4j.drivers.sensor.environment.bmx280.Bmx280Driver;
 import com.pi4j.drivers.sensor.environment.bmx280.Bmx280Driver.Measurement;
 import com.pi4j.drivers.sensor.environment.bmx280.Bmx280Driver.Model;
-import com.pi4j.io.gpio.digital.DigitalOutput;
-import com.pi4j.io.gpio.digital.DigitalState;
 import com.pi4j.io.spi.Spi;
 import com.pi4j.io.spi.SpiBus;
 import com.pi4j.io.spi.SpiMode;
@@ -81,7 +79,6 @@ public class BME280DeviceSPI {
 
     private static final int chipSelect = 0;
     private static final SpiBus spiBus = SpiBus.BUS_0;
-    private static DigitalOutput csGpio;
     private static Spi spi;
 
     public static void main(String[] args) throws Exception {
@@ -91,31 +88,13 @@ public static void main(String[] args) throws Exception {
         // Initialize SPI
         console.println("Initializing the sensor via SPI");
 
-        String helpString = " parms:      -csp  chipSelectGPIO    \n ";
+        String helpString = " parms:   NONE    \n ";
         for (int i = 0; i < args.length; i++) {
             String o = args[i];
-            if (o.contentEquals("-csp")) { // device address
-                String a = args[i + 1];
-                i++;
-                csPin = Integer.parseInt(a);
-            } else if (o.contentEquals("-h")) {
-                console.println(helpString);
-                System.exit(39);
-            } else {
-                console.println("  !!! Invalid Parm " + args);
-                console.println(helpString);
-                System.exit(42);
-            }
+            console.println(helpString);
+            System.exit(39);
         }
 
-        var csGpioConfig = DigitalOutput.newConfigBuilder(pi4j)
-            .id("CS_pin")
-            .name("CS")
-            .bcm(csPin)
-            .shutdown(DigitalState.HIGH)
-            .initial(DigitalState.HIGH);
-        csGpio = pi4j.create(csGpioConfig);
-
         var spiConfig = Spi.newConfigBuilder(pi4j)
             .id(SPI_PROVIDER_ID)
             .name(SPI_PROVIDER_NAME)
@@ -126,7 +105,7 @@ public static void main(String[] args) throws Exception {
             .build();
         spi = pi4j.create(spiConfig);
 
-        Bmx280Driver bmx280Driver = new Bmx280Driver(spi, csGpio);
+        Bmx280Driver bmx280Driver = new Bmx280Driver(spi);
 
         console.println("Device model detected: " + bmx280Driver.getModel());
 

src/main/java/com/pi4j/devices/bmp280/README.md

@@ -15,38 +15,25 @@ class documentation to understand its various logging options.
 
 The I2C connection functions as written in the Phillips spec.
 
-I2C connection path.
 
+I2C
 1. ./mvnw clean package
 2. cd target/distribution
 3. sudo ./runBMP280I2C.sh
    Args if bus and or address must be set
    -b 0x01 -a 0x77
 
-The SPI connection per the Datasheet supports MODE0 or MODE3. The spec shows reading a register consists of:
-
-1. Chip select driven low
-2. Eight clocks pulses to write the register address via the Pi MOSI
-3. Multiple eight clock pulses for each byte of data returned thru the Pi MISO
-4. Chip select driven high
-
-In either Mode0 or Mode3 the read data bytes are miss-read and the clock pulses are not signaled for the expected reads.
-The SPI open flags support configuration of writing a determined number of bytes before continuing the clock pulses
-for the expected read data . This however requires the BMP280 chip connect using the 3-wire configuration and
-the chips config register be modified. As most chips use 4-wire configuration I use 4-wire, and use a configurable
-GPIO as the CS (chip select)
-
-SPI connection path.
+The SPI connection per the Datasheet supports MODE0 or MODE3.
 
+SPI 
 1. ./mvnw clean package
 2. cd target/distribution
 3. sudo ./runBMP280SPI.sh
 
-Use of different bus or device address, use the applicable values in the following command.
-sudo ./runBMP280I2C.sh -b 0x01 -a 0x77
+
 
 Will create the BMP280 device to create a BMP280Device instance Call the various temperature and pressure methods
-defined in the interface. The device defaults to Pi Bus 1 and device address 0X77
+defined in the interface. 
 
 No parameters are required. However, if 'any' parameter value is to be supplied:
 parms: -b hex value bus -a hex value address -t trace