Leaderboard


Popular Content

Showing content with the highest reputation on 06/12/15 in Posts

  1. 1 point
    Hello, Here is what I found: When we update a part we sell out of the current rev and then start to sell the new one. There can be a short time when we are still shipping and earlier rev, but our intent is to be always shipping the newest, highest rev. MAX32: We are currently shipping Rev D, we only have 9 left, so sometime next week or so we will be shipping Rev E. If anyone wishes explicitly a Rev E, they can go through customer support and exchange it. Network Shield, we are shipping Rev C for the foreseeable future. Regards, Cristian
  2. 1 point
    rp-prew

    Digilent Basys 3

    Hi Muthupriya, I think I may have the answers you are looking for. 1) Do you mean a .xdc file? the .xdc files are the constraints for the board; so the file will define the labels for the ball locations of the basys3 board. It pretty much is defining the board locations to the software. This file is case sensitive so watch out for your typing. The .v files are the actual project files for Vivado. .v files are the Verilog programming language files. 2) You can use either VHDL or verilog to program the Basys3. They can be interchangeable but it is best to keep to one language at a time. You can choose which ever one you're more comfortable with but it's always good to try your hand at something new. 3) The Basys3 is exclusively made to be used in Vivado design suite. Vivado is made by Xilinx though so that's another answer to your question. I hope these answered some of your questions. If you have any other questions feel free ask. We do have a FPGA forum section if you would like to browse through there. Also check out the wikipage for more on the Basys3. https://reference.digilentinc.com/doku.php?id=basys3:basys3#documentation Good luck, Bobby
  3. 1 point
    Josh

    Digilent Basys 3

    Don't worry, these are great questions! (I moved this to the FPGA forum)
  4. 1 point
    Thank you for the correction. Writing/logging to file can be done like this: var file = File("C:/log.txt") file.write("") //clear //... var sz = hz +"\t"+ Math.log(Scope1.Channel2.measure("Amplitude")/Scope1.Channel1.measure("Amplitude"))/Math.LN10*20 file.appendLine(sz)See help for more options. On recent MS Windows, writing to C: from applications without root permission will be placed to: C:\Users\[user]\AppData\Local\VirtualStore\