Larry McGovern

Members
  • Content count

    16
  • Joined

  • Last visited

  • Days Won

    1

Community Reputation

1 Neutral

About Larry McGovern

  • Rank
    Member
  1. Fantastic! That bit file works perfectly with the client software. Thank you!
  2. And missed your question about the Duo earlier. Yes, I have verified it in the past, but not with this exact test. I was using the logic analyzer with it a month or two ago, with no problems. I have it wrapped up in another project at the moment, but could pull it out if there is anything you want me to try on it.
  3. Hi Jack, no dice The 250k bit file has exactly the same behavior on channels 16-31. I could not get channels 0-15 to work at all. I went back to the bit file that comes with DesignLab 1.0.7. (By the way, I did try the 500k file as well, but couldn't collect any data with that one.) Incidentally, my "test" was super simple. I just loaded the following sketch to an arduino board, and connected pin Tx and GND to the Papilio. Just in case you wished to replicate these results. void setup() { Serial.begin(115200); } void loop() { Serial.println("The quick brown fox jumped over the lazy dog"); delay(30); }
  4. The chip says 250K, and I selected the 250K version in designlab. I've repeated these steps several times to rule out human error.
  5. I just uploaded a snap together case for the Papilio One Logic Analyzer over at Thingiverse: http://www.thingiverse.com/thing:1889271 Enjoy!
  6. I'm seeing some strange behavior with the Papilio One Logic Analyzer any time I select a sample size greater than 6 kB. It is easiest to demonstrate with an example. I have a test signal coming in on Pin 0. I am writing the sentence "The quick brown fox jumped over the lazy dog" over a serial port at 115200 baud, and repeating the sentence every 30 msec. The sentence itself takes 4 msec to write. The first image below shows a 1 MHz, 6 kB capture enabling channel group 0. This should cover 6 msec of data, and that is what I see on the logic analyzer. The UART analyzer shows the correct sentence coming across. The second image shows a 50 kHz capture, with 120 msec of data. This shows the sentence is repeated every 30 msec. The third image shows a 2 MHz, 12 kB capture enabling channel group 0. It should look exactly the same as the first image, but it doesn't. Instead, it shows a 1.5 msec word, 1.5 msec gap, and another 1.5 msec word. The two words read "er the lazy dog er the lazy dog". The fourth image shows a 5 MHz, 24 kB capture. Again, it should look like image 1 but it doesn't. Instead, we see the last 0.75 msec of the sentence, repeated 4 times. It essentially says "** dog" four times, where ** are garbage characters. That was all with only channel group 1 enabled. When I enable all four channel groups, and do a 1 MHz, 6 kB capture, I am told I will only receive 1.5 msec of data, but instead I receive 6 msec of data! When I try to capture 12 kB or 24 kB of data, it complains "Sample count too large for chosen channel groups!" So... Is this a known bug, or something new? I installed the bitfile using the "OLS" button on DesignLab 1.0.7. I have been extra careful to ensure I have selected the Papilio One 250K on both DesignLab and OLS. I've even uninstalled and reinstalled DesignLab. I also have a Papilio Duo, and the logic analyzer works for me with that board. Any ideas? Anything I should try?
  7. Thanks Jack! I see the repost.
  8. Hi Jack, I noticed that you put this project on your blog back in mid-July. Thanks for creating it on my behalf! If possible, could you replace the picture with an image and link to my YouTube video? Link: https://youtu.be/OqxMnT_Ruuk. The current picture there is not from my project, and I would hate for the author of that picture to think that I had taken credit for their work! Also, I am certainly happy to share my VHDL code, though I’m not sure it’s best to learn VHDL from me, clearly a novice. I approached this project as a learning opportunity, and my best recommendation is for others to do the same and create as much from scratch as they can. I can certainly provide a link to the source code if you think it would enhance the blog entry. Again, thanks for putting that up there. Also (on a different topic altogether), looking forward to the Papillio Nano. I'll definitely be ordering one of those when they are ready.
  9. Hi Jack, thanks for your enthusiasm! At my household, the reactions ranged from bafflement on why I had wasted so many hours doing this to "you need to get a real hobby"! LOL! Actually, my 11 year old enjoyed finding all sorts of crazy fractal patterns. She keeps coming back to this little gadget for more. It is strangely addictive, and one can get lost for long stretches of time exploring the Mandelbrot set. I just posted the SketchUp and STL files on Thingiverse with a few instructions, in case anyone is interested: https://www.thingiverse.com/thing:1655662 Although my application was very specific, it is pretty easy to modify if someone wanted to have a different placement for the joystick and buttons. I could see rotating the screen 90 deg, moving the joystick, and setting this up as an arcade. It is a very simple design, and I'm sure someone who designed consumer products for a living would find plenty wrong with it. I'm not really interested in mass producing these, but might be persuaded to print off one or two for a few interested folks for the price of the filament (a few dollars) and shipping. (Or if you're interested, maybe in exchange for a discount on one of your new Nanos when it is ready. I'll definitely need to pick up one of those!) And I notice that Thingiverse has a new "Order this printed" button, convenient for those without access to their own 3D printer.
  10. Thanks Jack! It would be an honor to see this on the Gadget Factory blog. This project was quite suitable for the Duo, since it makes use of the AVR chip for some of the basic math and input controls processing, and leaves the hard stuff to the FPGA. Also, hats off to Hamster, whose own Mandelbrot project were the inspiration for this. My project was not a copy of his (after all, my objective here was to learn), but I did learn quite a bit from his implementation on how to pipeline a project like this. I posted a few other details on the project on the YouTube post, but I suspect some of the readers here would be more interested. Here is the bullet point description: • The Atmega32U4 is used to process the analog joystick, buttons, and rotary encoder to set the cursor position, zoom, and color map. This information is sent over to the FPGA via an SPI interface. • The FPGA runs the 800x600 pixel fractal calculations at 200 MHz using the onboard DSP48s. • The fractals are saved to SRAM, with each pixel stored as a 1 byte word. • A set of selectable 12-bit color maps are stored using the FPGA BRAM. I currently have over a dozen, and am planning on adding more color maps. • An 800x600 pixel SVGA controller on the FPGA is used to send a 12-bit color image to the LCD. I used the snap-off VGA wing from the LogicStart Shield. The LCD was an inexpensive 7” screen purchased off eBay, typically used for Raspberry Pi projects. • The case for this design was 3D printed, and custom designed just for this project. Finally, the 3D case could be easily modified for a more general purpose Papilio Arcade. The Papilio Duo drops right into it. Perhaps I'll post the SketchUp file on Thingiverse if there is interest.
  11. Thought I would share what I've been up to with your board. This has been a really enjoyable way to learn VHDL. This was inspired by a similar project by Hamster.
  12. Thanks Jack. Your answer makes a lot of sense. I've worked professionally with FPGA and ASIC engineers for years, but never really explored how they do their job until now. There's nothing like digging in and doing it yourself to figure out how stuff works. There is plenty here to keep me busy for a while. Though I may need to pick up another board in the not too distant future!
  13. Alvie, I'm looking forward to that blog post. In looking over the Spartan documentation, I noticed that Xilinx also has its own soft processor IP called "MicroBlaze", so clearly these are important in the world of FPGAs. I am curious how frequently a typical FPGA engineer will include one in his/her design. Always? Occasionally? It certainly seems useful if one can afford the resources. Jaxartes, I agree that creating an SPI interface from scratch to communicate with the AVR looks like a useful learning opportunity. I'm already digging into more of the many features included in the Duo and seeing plenty of potential.
  14. What an outstanding board! Thank you Jack & Co.! My single goal in purchasing the Papilio Duo and Logic Start Shield was to learn about FPGAs and VHDL, and I would call this experience an unqualified success. I methodically went through Mike Field's PDF "Introducing the Spartan 3E FPGA and VHDL" and found it to be a very fast way to learn VHDL and the Xilinx tool sets. Mike Fields, if you are out there, thank you for that great guide! Your final chapter requests a postcard, and one shall be coming to you from California. Although the guide was written for the Papilio One development board, it works quite well with the Papilio Duo. The only chapters I did not do were Ch. 22 (A high speed external interface) designed for the Digilent Basys2, and Ch. 24 (Using an ADC) which uses the ADC chip on the Papilio One Logic Start wing. I probably could have interfaced with the AVR on the Duo with SPI, and might end up doing that anyway just for the learning experience. One thing to note: although Mike states that Ch 25 (Tri-State Logic) cannot be done with the Papilio One Logic Start Wing, it can be done on the Duo using the GPIO pins (which I didn't see referenced in the Logic Start Shield Hardware Guide, but are clearly on the board and schematic). Anyway, I highly suggest this guide to anyone else starting out who has either the One or the Duo. I'm figuring the next step is to learn how to use DesignLab, now that I'm a VHDL expert (ha ha) thanks to Mike. I'm no stranger to programming AVR microcontrollers, and the Arduino-like IDE is sure familiar, so it is now time to see what I can do with the two working together. A few general questions for the community: Are there any essential projects out there well suited for continuing my FPGA self-study? At this stage of my education, I'm more interested in the journey than the destination, but it would be nice to find a more involved project. I am fascinated by the ZPUino soft processor, but confess at this point I don't see the big picture here. Why would I want to recreate a processor on an FPGA, with so many cheap microcontrollers out there that do the same thing? Is it the novelty? Is the purpose to ease the transition to programming FPGAs for those who are more comfortable with software? Or is there some other larger purpose I'm missing? It looks compelling, but given that there is already an AVR chip on the Duo board, I think I might be inclined to use that instead, and interface the AVR with the FPGA over SPI. Speaking of interfacing with the AVR, I notice that the recommended way to interface is by setting it up as a Wishbone peripheral using the ZPU processor. Suppose I wish to do this without using the ZPU... Is there a recommended way to do this, without writing my own SPI interface from scratch? I know this must be an ignorant question, but I am still very much a beginner in the world of FPGAs. That's all for now. Looking forward to using this board in many future projects!
  15. Ok, I feel like a dummy. I'll answer my own question. It appears the resistor ladder on the LogicStart board depends on the monitor having a 75 Ohm impedance, providing the other half of the voltage divider. I had assumed the impedance would be much higher, but now understand 75 is the standard. VGA test circuit working now on my Papilio Duo.