Set PIO base pin based on board name

Author: sfe-SparkFro

red_vision_examples/ex08_high_fps_camera.py

@@ -28,12 +28,16 @@
 # Import NumPy.
 from ulab import numpy as np
 
-# Import machine and rp2 for I2C and PIO.
-import machine
-from machine import Pin
-import rp2
-i2c = machine.I2C()
-rp2.PIO(1).gpio_base(16)
+# Import the Pin class for the board's default pins, as well as SPI and I2C.
+from machine import Pin, SPI, I2C
+
+# When the Red Vision Kit for RedBoard is used with the IoT RedBoard RP2350,
+# both the display and camera use GPIO 16-47 instead of GPIO 0-31, so we need to
+# adjust the base GPIO for PIO drivers.
+import sys
+if "IoT RedBoard RP2350" in sys.implementation._machine:
+    import rp2
+    rp2.PIO(1).gpio_base(16)
 
 # Image size and bytes per pixel (depends on color mode). This example defaults
 # to 320x240 with BGR565.
@@ -59,7 +63,7 @@
 # color format. SPI is used here for compatibility with most platforms, but
 # other interfaces can be faster.
 interface_display = rv.displays.SPI_Generic(
-    spi = machine.SPI(
+    spi = SPI(
         baudrate = 24_000_000,
     ),
     pin_dc = Pin.board.DISPLAY_DC,
@@ -87,7 +91,7 @@
 )
 driver_camera = rv.cameras.OV5640(
     interface = interface_camera,
-    i2c = i2c,
+    i2c = I2C(),
     continuous = True, # Continuous capture mode for fastest frame rate.
     height = height,
     width = width,

red_vision_examples/rv_init/__init__.py

@@ -14,8 +14,10 @@
 # When the Red Vision Kit for RedBoard is used with the IoT RedBoard RP2350,
 # both the display and camera use GPIO 16-47 instead of GPIO 0-31, so we need to
 # adjust the base GPIO for PIO drivers
-import rp2
-rp2.PIO(1).gpio_base(16)
+import sys
+if "IoT RedBoard RP2350" in sys.implementation._machine:
+    import rp2
+    rp2.PIO(1).gpio_base(16)
 
 # Import the camera driver
 try: