• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Brooklynoutlier

  1. Thanks for your reply. The schematic shows pull-up resistors on GPIO2 and GPIO3, which are the pins used for the "allowed" I2C.1 protocol on the Raspberry Pi 3B. Pins GPIO0 (ID_SD) and GPIO1 (ID_SC) are used for the "forbidden" I2C.0 protocol, reserved for updating EEPROM, I gather (this is way above my pay grade), and don't have pull-up resistors.
  2. I am looking to connect a Pmod HYGRO module to a Raspberry Pi 3B through a Pmod HAT. The Pmod HYGRO uses the I2C protocol, and I understand that this requires pull-up resistors on the SCL/SDA lines. However, from what I've read, the RPi has built in resistors to handle this, and I'm wondering when/if I would use the pull-up jumpers on the Pmod HAT?
  3. Problem resolved .... note to self, remember to look more closely at simulation results, even simple modules can have simple problems.
  4. Anyone else experienced a problem with communicating to an HP laptop running Windows 7 SP 1 from an Arty S7 50 through the UART port? I boiled the application down to just two simple modules, but I still get an extra character (x"FF") added to every character sent from the board to the laptop. In other words, trying to send "01234" from the board results in "0ÿ1ÿ2ÿ3ÿ4ÿ" being received (ÿ has ascii value xFF). I've tried reinstalling drivers using files from the FTDI site, and tested with two different terminal programs (PuTTY and Termite), but the result is always the same. Communication in the other direction works just fine.
  5. Brooklynoutlier


    Thanks! I've already added the SSD LCD and the mono 128x32 OLED Pmods, and connected to a PC through the UART interface, using mostly my own source code. I'm planning on playing with the HYGRO and I2S Stereo Audio Output Pmods next. I'm not afraid of programming my own interfaces, but the thing that worries me is that there might be some incompletely documented hardware features/requirements that could hang me up. For instance, I had access to source code for the initialization routine for the OLED Pmod, and I think I could have struggled quite a bit without that. I guess I'll rely on what documentation and samples there are for the various interfaces, and come here for help if I get lost ... 8-)
  6. Brooklynoutlier


    Am I correct in concluding that Digilent Pmod IP's cannot be used with an Arty S7 board if I am not using MicroBlaze? I downloaded and installed the file from github, but all but one of the IP's are flagged as incompatible with my hardware. I have been able to use a couple of the IP's delivered with Vivado in my VHDL projects, so I think I've figured that part out.
  7. The oledinit.vhd file in the resources section for pmod oled seems to use a very low setting for initializing display contrast: 0fh vs. the RESET default, 7fh. Is this because the display is being driven off the 3.3v line from my Arty S7 board? Has anyone else successfully set it higher without letting the magic smoke out of some part of board/add-on?
  8. Any recommendations for an FPU/Math co-processor chip (DIP) or board to add to an Arty S7 board would be appreciated. Something like the legendary (because it is no longer available ) uM-FPU V3.1 formerly from Micromega or the PAK II from AWC Electronics. This is strictly for a hobbyist's entertainment, an addition to my grown-up Busy Box.