Beneath breakout board image:
Note: The nRF52 port has one available I2C, SPI and USART (and infinite software SPI and I2C)
ref: http://www.espruino.com/MDBT42Q
Other questions resulted:
Q1: Is the 'nRF52 port' just a reference to pins D6 and D8 ? (what port?)
Q2: It is not possible to have both BLE and the NEO-6M communicating at the same time (?T one or the other?)
Q3: I presume that I2C and SPI are allowed only on pins D6 and D8 if Q1 is true (doc isn't really clear here, where are the hardware I2C and SPI?)
@Robin, Re Q1, I believe that Gordon is referring to the software 'port' of the code to the nRF52, not a specific hardware port. In the case of the MDBT42Q, the Espruino code only identifies one of each type of port even though the device supports up to 3 SPI, etc.
Q2: If NEO-6M is connected to any available SPI or I2C then it certainly can be used while BLE is active.
Q3: SPI or I2C ports can be arbitrarily assigned to any available GPIO pin. There are default pins, as defined in the Espruino Board package, but these can be overridden. Pin re-assignment occurs when you configure a SPI or I2C port as in:
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Robin, Re Q1, I believe that Gordon is referring to the software 'port' of the code to the nRF52, not a specific hardware port. In the case of the MDBT42Q, the Espruino code only identifies one of each type of port even though the device supports up to 3 SPI, etc.
Q2: If NEO-6M is connected to any available SPI or I2C then it certainly can be used while BLE is active.
Q3: SPI or I2C ports can be arbitrarily assigned to any available GPIO pin. There are default pins, as defined in the Espruino Board package, but these can be overridden. Pin re-assignment occurs when you configure a SPI or I2C port as in: