Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Commanderfranz

  1. Hi SC3, We attempted to replicate your issue with no success due to other issues. Unfortunately I don't think we can find a fix for the issue in a timely enough manner for the students to fix it, then finish their projects in only one week. However, we will keep looking for a solution. Since your students only have one week to finish this project I would highly suggest that they save all their work, and install windows on their machines, or use another windows machine since MPIDE is such a quick download on Windows. I personally like having my computer dual booted with Windows and Linux, that
  2. Hi Jim, Let me just start by saying, I'm sorry you've had such trouble getting your spartan 3E board working. I wanted to post to clear up one point of confusion. Nate suggested He didn't suggest that you buy the JTAG programming cable but suggested that you use iMPACT to program the board. I can understand your confusion based on the wording of his suggestion, so let me clear it up for you. All Digilent boards contain a JTAG programming circuit natively so they do not need JTAG cables, as is indicated on the product pages for the JTAG cables. iMPACT is the correct software to program the b
  3. Ricardo, I'm currently working on a guide for moving a project from one board to another by changing the UCF file. That will help you understand the UCF file enough to use it. I will comment on this thread when I've finished it. Kaitlyn
  4. Priya, There are a number of places you could edit the value depending on your desired usage. All screenshots refer to the XADCdemo.v file. The first screenshot block of code uses an existing IP to convert the input values from the XADC Pmod header into a binary representation. The binary output is the wire data. If you wanted to modify the binary value you can modify it by changing data. Say you want to multiply data by ten then, data*10. The second and third screenshots show a block of code that converts the binary value data, to a 6 digit decimal representation, i.e. dig0 - dig6. If you w
  5. Ricardo, When you downloaded the demo did you use the Nexys 3 UCF file included in the demo, or did you switch over to the Basys 2 UCF file?
  6. almoser, The C32 compiler already contains this header file, so you do not need it in the zip file. If you downloaded the C32 compiler you should be all set to run this demo. You can find the compiler on this page, Let me know if you have any more questions about this process. Kaitlyn
  7. Hi shingo, It is possible that when you installed Vivado the cable drivers didn't install correctly. There is a thread in the Xilinx forum that discusses reinstalling cable drivers. If this is your issue, then reinstalling the drivers should work. Also, I know you said you are using a known good microUSB cable. I just wanted to make sure it was know good for programming and not just for charging. Let me know if either of these fixes work or if you have more problems. Kaitlyn
  8. Hi Billel, As long as the signals are within the specifications of the oscilloscope, and the signals are accessible (routed to a Pmod connector) that is a great use for the EE board. The specifications can be found here. Kaitlyn Franz
  9. Hamster, Thanks for posting this awesome Nexys Video project.
  10. Hi Kbb64, It's great to hear that you are trying to start your kids in electronics so young. For the first years of discovery I would recommend a microcontroller such as the uC32 or WF32. If you add the chipKIT Starter Kit you will give your kids more opportunity for discovery. Our box monster uses the UC32 and is specifically targeted towards K-12. We happen to have some extra box monsters lying around, and if you are in the US we can send you a sample. Kaitlyn
  11. Hi Priya, I've done some digging into the demo to figure out the pin locations. Below I have a picture of the XDC file from the demo, which you can view when you open the demo project in Vivado. In the first comment you can see it says Pmod Header JXADC, this indicates the Pmod header the demo is using. This corresponds to the far right column in your table. In the un-commented lines is given all of the pin locations, as well as corresponding variable names. For example, to find AD6, I look at the first line in the image and the variable in the curly brackets is vauxp6. This corresponds to pi
  12. g.neri12, Digilent Adept 2 is now compatible with the Nexys 4 DDR. Kaitlyn
  13. Jonsm, I'm glad you resolved the issue without much trouble. Thanks for posting the resolution for others to see. Kaitlyn
  14. Hi Radoslaw, Currently there isn't an OS X version of Digilent Adept, and there is no immediate plan to make one. Your best bet would be to set up USB pass through, bootcamp your mac or stick with your Linux machine. Kaitlyn
  15. Hi Mike, I found this video on the Microchip site that goes through exactly what you want to do. It goes through how to program a board with MPLAB X and a hex file. I hope this helps. Kaitlyn
  16. You may find this post helpful. Someone asked a similar question about applying brakes. Kaitlyn
  17. Chris, If you plan on continuing work with embedded linux or you have trouble with a virtual machine, you may consider dual booting your computer. You can find detailed instructions here. Kaitlyn
  18. Hi Alex, I am re-posting this answer so forum users can see that this question has been answered. ____________________________________________________________________________________ Here are instructions: 1) Take out the nut and washer from the power terminal 2) Insert the terminal into the hole on the board (e.g. the black one for the ground) 3) Put the washer back on the back of the board 4) Put the nut on top of the washer and fasten it. 5) Flip the board and fasten the top of the terminal
  19. Hi there, There isn't currently a demo for the PmodCLP targeting the Basys2 but if you look on the product page there are several that target the Nexys 3. If you download the demo in either VHDL or Verilog you can go into the sources file and look at the .v file. From there you can modify the UCF file to target the Basys2. Kaitlyn
  20. Gmv, I found this thread on the XIlinx forums that you may find useful. Kaitlyn
  21. Hi Alex, I'm not sure if your problem was solved yet or not but I figured I would share my experience with MPLABX. I often had the same problem that you were showing, and usually all I needed to do was close the program and restart it, or unplug the programming cable and plug it back in again. It seemed to be a common problem that people had. Kaitlyn
  22. Hi again M, A good way to test to make sure the sensors are functioning properly is with a white and black piece of paper. The LEDs on the PmodLS1 indicate what signal the sensors are recieving. You can use this to debug the sensors operation as well as find the correct sensitivity. Kaitlyn
  23. Hi M, I'm sorry for all the confusion you are having. I think I may know the problem you are having with the sensors based on the photos you posted. The distance between the right and left sensors has to be the same as the thickness of the line the robot is following. Follow this link to view my instructable on putting together the line follower. Note step 18, there is an image of proper sensor placement. Kaitlyn
  24. Shahin, ​Yes for both of these. You can create a test bench and view the output waveform, or if you attach the output to a pin you can scope the output with an oscilloscope. Kaitlyn
  25. Ryan, Since you don't need the full tool set I would recommend using Adept. The first version of Adept should be compatible with the device you are using and you can program with adept using .jed files. Adept doesn't have any design tools but is simply for programming the device. Let us know if that works! Kaitlyn