JColvin

Administrators
  • Content Count

    3305
  • Joined

  • Last visited

  • Days Won

    115

Everything posted by JColvin

  1. Hi Yann, That is correct, there is not a way to configure the FTDI chip with our boards. Thanks, JColvin
  2. Hi Leon, Not necessarily. Sometimes the issue is with the Vivado cable drivers or even the USB cable itself. Check out this other forum post for some more information on this. Let me know if you have any more questions, Thanks, JColvin
  3. Hi shahabamo, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  4. Hi Kevin, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  5. Hi Emil, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  6. Hi Leon, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  7. Hi accel, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  8. JColvin

    add ip in vivado

    Hi bahare, What sort of "earlier errors" does Vivado report? I imagine that Vivado would have listed some other errors in addition to this one. Thanks, JColvin
  9. Hi Tarik, Here is a post that explains how to program the SPI flash on a Basys 3 board from Vivado: What you'll likely need to change what memory you're searching for; according to ZYBO reference manual in section 4, this is S25FL128S. The reference manual also shows here, that you'll need to adjust a jumper to then boot the board from the SPI flash. Let me know if you have any more questions. Thanks, JColvin
  10. Hi Muminek, Presuming you already have the J16 jumpered in the UART position (which is usually the source of the error you're describing), there isn't going to be a whole lot you can do through MPIDE. If it is in fact the FlowCloud app that is using the Serial port which is not letting you program the board otherwise, the only thing I can conveniently think of is if the FlowCloud app allows you internally change which Serial (UART) port it is using on the chipKIT WiFIRE since the USB port on the board is hard-wired to Serial (as opposed to Serial1 which uses alternate UART pins available on the MZ chip). I do not know if this is possible with the FlowCloud app though. However, even if you do manage to do that, when you upload the Blink sketch from MPIDE, it is my understanding that it will overwrite any pre-existing code that has been uploaded to the board (excluding things like the bootloader and whatnot), so it would likely overwrite the FlowCloud app that has been preloaded. After doing some digging around on my own, it looks like (according to this page) that no configuration exists for the WiFi setup. It looks like you can change some of those settings as listed here. In the end though, I don't think you're going to be able to use MPIDE to program the board conveniently. The MPLAB X (developed by Microchip) looks like it could program the board without overwriting some of those settings, which is probably why they recommend using some sort of programmer like the chipKIT PGM. Digilent only manufactures the Wi-FIRE board though; the FlowCloud app was developed by Imagination and appears to be (I can't speak on this for certain) supported through their forum. Thanks, JColvin
  11. Hi Louis, I did some quick asking around to see if there was something that jumps out about this, but didn't find anything in particular. Since this is a driver developed by Xilinx (and what is having the issue), you will need to contact Xilinx support to receive the most effective help with the driver. Thanks, JColvin
  12. JColvin

    I2S L1

    I looked it up and found a little more information about it, it has a part number of 490-1028-1-ND, and it is actually a ferrite bead as opposed to an inductor. I apologize for the mis-information earlier. Thanks, JColvin
  13. If that is inside of your void loop function, then yes, that should (at least as far as I can tell) work out for you. Again, I haven't gotten to verify this myself, but I believe it should work out in principle. Thanks, JColvin
  14. JColvin

    I2S L1

    Hi JGRMSL, In this instance (and in most cases) parts labeled with an "L" on schematics traditionally indicate that part is an inductor. So on the PmodI2S, L1 is an inductor with a value of 2500 uH. Thanks, JColvin
  15. Hi Josh, I talked with the appropriate people at Digilent and they said yes, the ARTY board (from the Digilent website) will come with a Vivado Design Suite: Design Edition that is both node locked and device locked. Thanks, JColvin
  16. JColvin

    [Arty] Power Sequencing

    Hi Michael, I have asked some of our applications engineers about this who will get back to you here on the forum. Thanks, JColvin
  17. After looking into the SD library, when you call the begin() function for it (and do some digging in the folders) there is a line that resets all of the SPI settings to default. I personally don't know if the initialization of the PmodAD5 changes any of the SPI settings (which would then be all reset when you called SD.begin), but it may be worth a try to have the SD.begin() line be placed before all of the initialization of the A/D occurs. Let me know if this helps. Thanks, JColvin
  18. Hi Jrlin, I'm looking into this now. I keep getting a timeout error when I try to download the AD7193 library from Analog Devices so I can't look at that just yet, but I'm looking at the standard SD library and board files for the MX3 as well to see if anything jumps out at me from there. Thanks, JColvin
  19. Hi Mark, I re-looked at the spacing with some calipers and found the pitch between the pin 1's is 0.9 inches. I think the number Josh had before wasn't pitch distance. Thanks, JColvin
  20. JColvin

    Pmod

    Hi Brooke, Pmod boards do work with chipKIT boards. The idea behind Pmods is that they use a de-facto interface protocol such as SPI or I2C so they are able to communicate with any system (such as LabVIEW, chipKIT, FPGAs, or other microcontroller boards) that are able to use that communication protocol. You can find the most up to date list of Pmods and their related materials on our Wiki here. Let me know if you have any more questions. Thanks, JColvin
  21. JColvin

    Nexys4 DDR & MIG

    Hi Pedro, I'd recommend checking out our getting started with microblaze tutorial for the Nexys 4 DDR. It has a section (starting here) that talks about how you would add the MIG IP block. Let me know if you have any more questions. Thanks, JColvin
  22. Hi, Alex is right, the Pmod can only get up to a range of +/- 4V in bipolar mode because the programmable gain array (pg 32 of the datasheet) has an overhead of 1.25V. The reference voltage (Avdd) can be supplied through REFIN2+ and REFIN2- pins on the J2 header of the PmodAD5. As for changing your sample rate, you would need to change the Mode Register to adjust the "filter output data rate select bits" from the default of 96 to 1 to get a much faster output data rate. With the inherent settling time associated with the on-board chip, I'm not sure you will be able to get as high of a output rate as you want, but I can't confirm or deny this. Either way, it sounds like you're using the Analog Devices library for this chip, so you would need to contact them to find out how to best utilize it. Let me know if you have any more questions. Thanks, JColvin
  23. Hi Flyline, You are completely right, those pins should be defined as you determined in the board defs file. I have corrected the WF32 reference manual that is available on our wiki here; I'll also request that the reference manual (in pdf) form is also updated to reflect these changes. As for the board defs file, I personally don't have any control over that, but I will make mention of this to our chipKIT guy and see if he can appropriately update them. Thank you for the feedback! Thanks, JColvin
  24. Hi Jmac68, The chipKIT Max32 does not output PWM from 0-5V. All of it's pins including the analog pins operate from 0 to 3.3V. Most of the pins are 5V tolerant, but are not actually able to supply 5V. As for the individual stepper controllers for each stepper motor, that really depends on your design. If all of your motors are going to be running and turning exactly the same way, then you could in principle use the same stepper controller. However, based on the way stepper controllers are designed (such as a Darlington Transistor Array or a L293DD or any number of other chips based on how powerful your stepper motor is), you would then also probably be sending power through the same pins on the chip for all of the stepper motors, which will likely not be strong enough to have that much power flowing through it to power all of them. With 10 stepper motors, I would recommend using individual stepper controllers (based on my personal knowledge and experience; other people may have a more experienced recommendation). As for the code recommendation, I might be able to offer some advice on what kind of things you would want to do, but in the end you know the setup the best. What exactly are the stepper motors doing? Are they the things controlling how much mass is flowing through your system based on the feedback from the mass flow controllers? Are they inside the mass flow controllers? Or something else entirely? Thanks, JColvin
  25. That's what I was initially thinking as well, but when I was looking through at what pins the Timer2 and SPI used, they didn't appear to have any conflict (Timer2 seemed to use pin 5), so I wasn't sure what the problem might have been. But if Timer3 works out for you, then go for it.