IOIO: updated spiMaster handling.

Author: chrisws

ioio/main.cpp

@@ -367,7 +367,9 @@ void sblib_close(void) {
     fprintf(stderr, "IOTask leak detected\n");
     _ioTaskMap.clear();
   }
-  jvm->DetachCurrentThread();
+  if (jvm) {
+    jvm->DetachCurrentThread();
+  }
   // calling this hangs
   //jvm->DestroyJavaVM();
   env = nullptr;

ioio/samples/duino-1088AS.bas

@@ -1,70 +1,27 @@
-rem
-rem Hardware Setup:
-rem Power Supply: Connect VCC of the 1088AS to a suitable power supply voltage (usually 5V).
-rem Ground Connection: Connect GND of the 1088AS to the ground (GND) of the IOIO-OTG board.
-rem Data Connections:
-rem Connect the DIN pin of the 1088AS to a digital output pin on the IOIO-OTG board.
-rem Connect the CS pin of the 1088AS to another digital output pin on the IOIO-OTG board.
-rem Connect the CLK pin of the 1088AS to yet another digital output pin on the IOIO-OTG board.
-rem
-rem In the context of an LED matrix display like the 8x8 Duinotech 1088AS,
-rem writing to the DIN (Data Input) pin is not directly addressing a
-rem particular LED. Instead, it's part of a process to send data to the
-rem display to control which LEDs are lit up.
-rem 
-rem Here's a simplified overview of how it works:
-rem 
-rem Data Shifted In: You send a stream of data serially to the
-rem display. Each bit of data represents whether a corresponding LED
-rem should be on or off.
-rem 
-rem Data Shifted Out to LEDs: As the data is shifted into the display
-rem through the DIN pin, it is internally stored in shift registers. When
-rem enough data is received (for example, 8 bits for an 8x8 LED matrix),
-rem the display will update the LEDs accordingly.
-rem 
-rem Control Signals: Alongside the data, you typically send control
-rem signals like clock pulses (CLK) to synchronize the shifting of data
-rem and chip select (CS) to indicate when the data is valid.
-rem 
-rem Matrix Multiplexing: The LED matrix is typically arranged in rows and
-rem columns. By controlling the state of each row and column (using
-rem additional control pins or internally within the display), you can
-rem select individual LEDs or groups of LEDs to turn on or off.
-rem 
-rem Updating Display: After sending the necessary data and control
-rem signals, the display refreshes itself to reflect the new state of the
-rem LEDs based on the received data.
-rem 
-rem So, when you write to the DIN pin, you're not directly addressing a
-rem particular LED. Instead, you're sending data to the display to update
-rem the entire matrix, and by controlling the row and column pins, you
-rem indirectly address specific LEDs or groups of LEDs within the matrix.
-rem
-
 import ioio
 
-const dinPin = 2
+const mosiPin = 2
+const misoPin = 6
 const csPin = 3
 const clkPin = 4
 
-din = ioio.openDigitalOutput(dinPin)
+spi = ioio.openSpiMaster(misoPin, mosiPin, sckPin, csPin)
 cs = ioio.openDigitalOutput(csPin)
-clk = ioio.openDigitalOutput(clkPin)
 
 ioio.waitForConnect(10)
 
-while 1
-  shiftOut(0x55) 
-  delay 10000
-wend
+rem true sets the initial state to high (deasserted)
+cs.write(true)
 
-sub shiftOut(_data)
-  cs.write(false); ' Enable the chip
-  for i = 7 to 0 step -1
-    clk.write(false) ' Start clock pulse
-    din.write((_data band (1 lshift i)) != 0) ' Send bit
-    clk.write(true) ' End clock pulse
+spi.write(0x09, 0x00)  ' Decode mode: no decode for digits 0-7
+spi.write(0x0A, 0x07)  ' Intensity: maximum intensity 0x0 -> 0x0F
+spi.write(0x0B, 0x07)  ' Scan limit: all digits
+spi.write(0x0C, 0x01)  ' Shutdown: normal operation
+
+while 1
+  for i = 1 to 8
+    spi.write(0x55)
   next
-  cs.write(true) ' Disable the chip
-end
+  delay 1000
+wend
+'

ioio/src/main/java/net/sourceforge/smallbasic/ioio/DigitalInputImpl.java

@@ -31,6 +31,7 @@ public void loop() throws InterruptedException, ConnectionLostException {
 
   @Override
   public boolean read() {
+    handleError();
     return value.get();
   }
 

ioio/src/main/java/net/sourceforge/smallbasic/ioio/DigitalOutputImpl.java

@@ -29,7 +29,7 @@ public void loop() throws ConnectionLostException {
 
   @Override
   public void setup(IOIO ioio) throws ConnectionLostException {
-    Log.i(TAG, "setup entered");
+    Log.i(TAG, "setup entered: " + pin);
     output = ioio.openDigitalOutput(pin);
   }
 

ioio/src/main/java/net/sourceforge/smallbasic/ioio/SpiMasterImpl.java

@@ -1,12 +1,14 @@
 package net.sourceforge.smallbasic.ioio;
 
+import java.io.IOException;
+
 import ioio.lib.api.IOIO;
 import ioio.lib.api.SpiMaster;
 import ioio.lib.api.exception.ConnectionLostException;
 import ioio.lib.spi.Log;
 
 public class SpiMasterImpl extends IOTask {
-  private static final String TAG = "TwiMasterImpl";
+  private static final String TAG = "SpiMasterImpl";
   private final IOLock<SpiMaster> lock = new IOLock<>();
   private SpiMaster spiMaster = null;
   private int miso;
@@ -19,14 +21,16 @@ public SpiMasterImpl() {
     Log.i(TAG, "created");
   }
 
-  public void open(int miso, int mosi, int clk, int slaveSelect) {
+  public void open(int miso, int mosi, int clk, int slaveSelect) throws IOException {
+    super.open(miso);
     this.miso = miso;
     this.mosi = mosi;
     this.clk = clk;
     this.slaveSelect = slaveSelect;
   }
 
   public void write(int address, int data) {
+    handleError();
     lock.invoke((i) -> {
       byte[] buffer = {(byte) address, (byte) data};
       spiMaster.writeRead(buffer, buffer.length, buffer.length, null, 0);
@@ -40,7 +44,7 @@ void loop() throws ConnectionLostException, InterruptedException {
 
   @Override
   void setup(IOIO ioio) throws ConnectionLostException {
-    Log.i(TAG, "setup entered");
+    Log.i(TAG, "setup entered: " + miso + " " + mosi + " " + clk + " " + slaveSelect);
     spiMaster = ioio.openSpiMaster(miso, mosi, clk, slaveSelect, SpiMaster.Rate.RATE_1M);
   }
 }