KKING

Newcomers
  • Content Count

    5
  • Joined

  • Last visited

  1. KKING

    Type 6 Expanded?

    Thank you very much for your consideration and work, -Kevin
  2. KKING

    Type 6 Expanded?

    Hello JColvin, Tell the team, thanks for considering, I hope I can answer to your satisfaction. In first ROW, we are already using RESET and INT, the alternate signals in Type 6. First, I am not sure we should define the second row with anything but GPIO, but if you are planning on defining alternate signals, I have 3 desired.. Second, the currently planned signals may apply to other vendors of I2C devices. Right now, the 3 I need are: BUSY# - Wired ORed, low true so tells the MCU someone on the I2C chain is Busy. You can poll the status of certain sensor without making a lot of digital noise on the I2C bus. Might keep the board a little "quieter" while AD conversions are going on. Might be good for any I2C ADC boards as well (sensor of sorts). ENABLE (have not decided if it low true or high true, but leaning toward high true so just a pull-up enables if no one drivers that GPIO and the sensor default to ENABLED). POWER_ENABLE for Sensor without RESET where the I2C bus can be hung up by noise. Leaning toward high true for same reason as ENABLE. If no one drives it low, the device is on by default. Finally, we are documenting our 12 pin (Type 6 + Type 1) such that if you want to daisy chain type 6 (6 pin), which we plan to do, you would put it on the end of the chain. Currently we are only planning to Daisy chain 2-4 mix of I2C based sensors which make "logic system solutions". We would have a mix of devices that have INT#, and BUSY# at this point. Regards, Kevin
  3. KKING

    Type 6 Expanded?

    Yes, would desire that a Type 6A be added. We are in process of designing some Sensor modules that need a couple of extra GPIO on the second row. We can control our own MCU board designs, but would like to say we use a "PMOD standard" that is in the specification. Seems like there are a couple of "Expanded" standards, so hopefully this fits the flow of the specification. I understand that the dual row are GPIO, but it does not guaranteed SCL and SDA on the correct pins for I2C (aside from bit-banging which is painful). Am I correct? Thanks for your consideration in this matter..
  4. KKING

    Type 6 Expanded?

    We are using the type 6, but we want a second row to add “proprietary functions” for some I2C sensors (i.e. power control / enable, BUSY#, etc…). Right now we are calling it Type 6 + Type 1 in second row. Much like there is a type 2 SPI and a type 2A Expanded SPI, it would be nice to have Type 6A Expanded I2C. What are the possibilities of adding a type 6A Expanded I2C where the second row is all GPIO? How do I put in an official request to Digilent Engineering? PMOD_example.bmp