Zoltán Lehóczky

  • Content Count

  • Joined

  • Last visited

  1. OK, great then, thank you!
  2. Thanks Jon, this is exactly what I've looked at, but the "the boards are nearly identical" statement is that confuses me since in my understanding they're not nearly, but completely identical.
  3. Could somebody shed some light on the differences between the new Nexys A7 and Nexys 4 DDR? The A7 has a 50T version, but aren't the 100T version and the Nexys 4 DDR identical? Thanks in advance.
  4. Thank you, that's a great idea. While our project is not mature yet, it's usable so probably worth sharing there any way, so have done that:
  5. To allow software developers to be able to easily get the computational benefits of FPGAs we created Hastlayer: it turns software written for the .NET platform into an equivalent (VHDL) hardware description. It does this while also handling everything in the background to allow the usage of the resulting hardware in the same way as the original software was run - basically where there was a function call there's still a function call but now it really executes on an FPGA, as logic hardware. Here's a demo video of how it works: And why do I post it here? You can also see from the above thumbnail that you can use Hastlayer with Nexys 4 DDR boards! Connecting the board to a host PC via USB as well as Ethernet is supported. You can even use multiple boards simultaneously if you use the latter. Do you own a Nexys 4 DDR? You can get access to Hastlayer, just ask! (And you can get access to it otherwise too!)
  6. It tuns out the problem wasn't with the drivers (though those were missing too), but rather that not a Nexys 4 DDR, but a Nexys 4 was connected... Naturally the SDK program couldn't start, lacking the DDR RAM it was configured to use. Thanks for your help @D@n!
  7. Thank you @D@n, so indeed those are the drivers. We'll see if the affected machine has these.
  8. Thank you @D@n. Do you mean the "Cable Drivers" you can select to install when setting up Vivado? We haven't installed anything else apart from what ships with VIvado on the machines where it's working (except copying board support files).
  9. We use Nexys 4 DDR boards for testing our platform. While with most of the Windows host PCs there are no issues, with one of our clients' when the board is plugged in (using the supplied micro USB cable) it shows up as two COM ports under Windows's Device Manager. We suspect this is behind that we can't properly run Xilinx SDK programs on the board, the debugger looses the connection. Is it normal that the board shows up as two COM ports? (When the board is de-attached the ports disappear, so both are surely the single board.) If yes, can this cause issues? If now, how can we begin to troubleshoot the problem, what can possible be behind it? Thank you in advance!