<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hello Alan<br>
      <br>
      On 07/18/14 14:06, Alan Cudmore wrote:<br>
    </div>
    <blockquote
cite="mid:CAJrjN71eYPVUSm==Z1vbUZx3NnZTNUUw+dw+gf4yGzb2gf2Zzg@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi <span
          style="font-family:arial,sans-serif;font-size:13px">André,</span>
        <div><span style="font-family:arial,sans-serif;font-size:13px">I
            have a couple of SPI devices to try now. I have the SPI FRAM
            chip:</span></div>
        <div><a moz-do-not-send="true"
            href="https://www.adafruit.com/product/1897">https://www.adafruit.com/product/1897</a><span
            style="font-family:arial,sans-serif;font-size:13px"><br>
          </span></div>
      </div>
    </blockquote>
    <br>
    I have here a similar device <br>
    <a class="moz-txt-link-freetext" href="http://www.microchip.com/wwwproducts/Devices.aspx?product=23K256">http://www.microchip.com/wwwproducts/Devices.aspx?product=23K256</a><br>
    <br>
    Will try to test it with the PI this weekend.<br>
    <br>
    I also have the following devices here:<br>
    <br>
    (I2C)
    <a class="moz-txt-link-freetext" href="http://www.microchip.com/wwwproducts/Devices.aspx?product=MCP23008">http://www.microchip.com/wwwproducts/Devices.aspx?product=MCP23008</a><br>
    <br>
    (SPI)(I2C)
    <a class="moz-txt-link-freetext" href="http://www.newhavendisplay.com/nhd0216k3zflgbwv3-p-5738.html">http://www.newhavendisplay.com/nhd0216k3zflgbwv3-p-5738.html</a><br>
    <br>
    <blockquote
cite="mid:CAJrjN71eYPVUSm==Z1vbUZx3NnZTNUUw+dw+gf4yGzb2gf2Zzg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>and something that could be interesting, an SPI based
          LCD/touchscreen:</div>
        <div><a moz-do-not-send="true"
            href="https://www.adafruit.com/products/1601">https://www.adafruit.com/products/1601</a><br>
        </div>
        <div><br>
        </div>
      </div>
    </blockquote>
    <br>
    It does look interesting.<br>
    <br>
    <blockquote
cite="mid:CAJrjN71eYPVUSm==Z1vbUZx3NnZTNUUw+dw+gf4yGzb2gf2Zzg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>I can also verify that the RTEMS BSP works fine on the new
          Raspberry Pi Model B+</div>
      </div>
    </blockquote>
    <br>
    Nice. By the way, currently the BSP does not recognize (or I have
    missed it) which raspberry Pi version it is running on, and as new
    peripherals are added to the BSP it becomes important to have that
    info. For instance, the I2C interface on the P1 GPIO header uses
    different pin numbers for model A and model B/B+.<br>
    <br>
    <blockquote
cite="mid:CAJrjN71eYPVUSm==Z1vbUZx3NnZTNUUw+dw+gf4yGzb2gf2Zzg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div><br>
        </div>
        <div>Alan</div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Sat, Jul 5, 2014 at 6:58 PM, Andre
          Marques <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:andre.lousa.marques@gmail.com"
              target="_blank">andre.lousa.marques@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
            <br>
            The Raspberry Pi GPIO interrupts are already working, and a
            test case is available to test that [1]. A function is also
            provided to debounce a switch if needed. The test case
            requires two switches and two LEDS using the same setup
            described at [2] by only changing the pin numbers.<br>
            <br>
            The test works by setting interrupts on both edges of the
            switches, which handlers will turn on or off the
            corresponding LED. One of the LEDs also has a level
            interrupt which prints a message on the screen when the LED
            is on (high level).<br>
            <br>
            While I wait for some feedback on that, I will be looking at
            the next step: the I2C interface. To test both the I2C and
            the SPI interfaces I have here a simple display [3]. The
            idea is to create a low level driver for I2C to provide the
            needed directives for the libi2c API, so the driver for the
            display will actually use the libi2c API. Any thoughts here
            are welcome too!<br>
            <br>
            Thanks,<br>
            André Marques.<br>
            <br>
            [1] - <a moz-do-not-send="true"
href="https://github.com/asuol/rtems/blob/GPIO_API/testsuites/samples/LIBGPIO_TEST_IQR/init.c"
              target="_blank">https://github.com/asuol/rtems/blob/GPIO_API/testsuites/samples/LIBGPIO_TEST_IQR/init.c</a><br>
            [2] - <a moz-do-not-send="true"
href="http://asuolgsoc2014.wordpress.com/2014/06/22/testing-the-gpio-api/"
              target="_blank">http://asuolgsoc2014.wordpress.com/2014/06/22/testing-the-gpio-api/</a><br>
            [3] - <a moz-do-not-send="true"
              href="http://www.newhavendisplay.com/nhd0216k3zflgbwv3-p-5738.html"
              target="_blank">http://www.newhavendisplay.com/nhd0216k3zflgbwv3-p-5738.html</a><br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>