TrapperBob

Members
  • Content Count

    12
  • Joined

  • Last visited

About TrapperBob

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. What is the recommended version of Labview for interfacing with the Analog Discovery 2. I have LabView 14 Home Edition installed as I was investigating the Linx functionality. Is this version sufficient for using with the AD2? Thanks
  2. I am new to the Analog Discovery 2 and would like to understand better the capability to program functionality with scripts. I see some Python scripts referenced in the Forums. How does this functionality manifest itself in day-to-day use of the AD2. Is there a repository of scripts for the AD2 somewhere that is available to be studied.
  3. Hi @Luis David Anchia, According to the specification you attached up to 4 MLX90393 could be accessed on one IIC AXI interface. The MLX90393 has two input pins, A0 and A1 that allow one to specify part of the IIC address by tying the pins to either GND or VDD.
  4. This link Link to Community Project to test the XADC, GPIO, buttons, LEDs, and SRAM on this page https://reference.digilentinc.com/reference/programmable-logic/cmod-a7/start?redirect=1 replies Precondition Failed
  5. MicroBlaze is a "soft" processor so to say Arty Z7 does not have it is not correct. Arty Z7 is a Zync-based board but a MicroBlaze soft processor could be added to the PL of the Zync device on the Arty. If you desire to use the PS in the Zync device (ARM based) to control your peripherals then you will use the SDK provided libraries and C and if you desire to use the PL section then you can use Verilog and/or VHDL to generate hardware controllers for you peripherals. Bob
  6. According to the schematic representation of the circuit in the reference manual https://reference.digilentinc.com/reference/programmable-logic/coolrunner-ii/reference-manual the LEDs (LD0-3) are configured such that a '0' on the output pin will illuminate the LED. This is permanently set by the hardware configuration.
  7. Hi @hhhhhhh, The current path is not through the AD2 when used to measure voltage. As Attila mentioned the input impedance of the AD2 is ~1M ohm. This presents very little current load in parallel with the measured circuit.
  8. Is this a typo in the reference manual? Seems , as Dan mentioned referring to the datasheet for the Spartan 3E family DCM , 300 MHz+ seems like a more plausible number
  9. FlyMario, I am not sure what your code is trying to accomplish. Are you trying to capture a sequence of keypress events and then indicating that by changing an output? A sequence implies examining state which implies memory which implies flip-flops which need a clock
  10. TrapperBob

    FPGA Clock

    Flymario, I am glad you are enjoying this activity! I would ask the following questions: 1. Are you using a FPGA board that you have acquired or one that you created? 2. What does the schematic look like both for the board and how you have it hooked to your C64? 3. You said you are using Verilog and that it really does not matter. It does not matter except that without seeing the Verilog code we are unable to determine what your logic may be doing. Are you using combinatorial logic , synchronous logic or a little of both? Please show the code so we are not guessing!
  11. You are "counting" on count to have state when you write count <= count + 1 or count <= count - 1. However you have a combinatorial process defined.