Jack Gassett

Administrators
  • Content count

    2,968
  • Joined

  • Last visited

Everything posted by Jack Gassett

  1. Hey everyone, I'm working on a new product line for GadgetFactory that might you might find interesting. It's called GadgetBox and in a nutshell it is an Arduino that solves the shield stacking problem and fits into a nice sleek case. There are eCogs - which are like Wings - that form the top of the case when they are plugged into the board. Don't get me wrong, I love FPGAs but sometimes they are just too expensive for simple things. GadgtBox is meant to take a proven and affordable platform, the Arduino Leonardo, and do some innovations that will hopefully solve the problems people have with it. The biggest problem I see is shield stacking and the ugly mess of wires/pcbs that you end up with when you make something with it! GadgetBox is going to be super inexpensive - hopefully less then $20 and result in an IoT device you won't hesitate to deploy in your house. To learn more check out the daily progress over at Hackaday.io. Jack.
  2. Yes, it will have the jtag header which will be totally open for an external jtag programmer. Sent from my iPhone using Tapatalk
  3. I might look into doing another batch of Papilio One 250ks soon. But overall, I'm working on a new Papilio design that will replace the Papilio One and Papilio Pro boards with a single board called the Papilio Unity. This board will use much lower priced components and should get the price for a Spartan 6 based design hopefully down to the 250k pricing. It uses lower cost voltage regulators, the cp2104 USB to serial chip, and provides a socket for a memory upgrade. The trick with this board is that we don't need the expensive FTDI JTAG capable chip because we are making a boot loader, like the arduino has. Programming the SPI flash is much faster with this new board. It takes 20 seconds or so on existing boards and is 5 seconds on the new board. The design is working well and we are just getting everything in order before making the first batch. Sent from my iPhone using Tapatalk
  4. Yay, glad you got it working. If you want to trade it out for a new one just send us an email at support@gadgetfactory.net and include a link to this forum thread. Thanks, Jack.
  5. You need to use make to synthesize the project.
  6. Hello, It's black boxed because it greatly speeds up the synthesis time for the end user and most people have no need to modify ZPUino, just the peripherals attached to it. The source code for the black box is here: https://github.com/alvieboy/ZPUino-HDL/tree/master/zpu/hdl/zpuino/boards/papilio_one/s3e250/variants/designlab Jack.
  7. Sorry, that site has been offline for quite some time now. Jack.
  8. Sweet! I'm going to put this on my list of things to get setup in the office. Jack.
  9. You should be able to just select watchdog.v in Xilinx ISE and then go under processes. There should be an option to generate a symbol which should generate the symbol for you. Jack.
  10. That should be related to what board you have selected. That message usually means that there is not an example for the board that you have selected. If you hit CTRL-K in DesignLab and look in the circuits directory you should see what boards are supported by the example. I also usually put in the notes at the top of the sketch what boards are supported. Jack
  11. Hmmm, this is interesting. Was this with the Wii-Chucks that we are selling from the Gadget Factory store? I'm pretty sure I tested with those but maybe I got something different the last time I ordered... Jack.
  12. Or try this bit file: 1.3.1 should be latest version with LCD fix. Jack.
  13. Hello Anthony, What version of the RetroCade code are you running? I think if you try the very latest version by downloading the DesignLab software and using that to upload the latest code you might see the problems go away. Jack.
  14. Hello Blake, Sorry for the slow response, I've been on a job which was running late every night last week and then Fathers day weekend this weekend... I should get some time this wednesday to take a look at this and help out. Jack.
  15. Hello Blake, Unfortunately I won't get much time to put together an example until next weekend so I will try to talk you through what you need to do. If you look at the image below (from the tutorial) you will see that the Wishbone_to_Registers_x10 symbol exposes the pads for 10 different registers. So anything you connect to them will be readable from your C code on the AVR. In the example below the input is connected to the output, this just means that the registers echo whatever to put in from the C code on the AVR. For your application you will want to remove those wires connecting the inputs to the outputs. Then experiment with connecting VCC and then GND to the register0_in and then verifying that you read back a zero or one from your C code. You can also wire the register0_out to an I/O marker (connected to a physical pin on the Papilio Board) and then verify that you can write to register0 in your code and see the physical pin has the corresponding change. You could then find the example that shows how to make a counter in the schematic editor and implement it and then connect the counters output into the register0_in. One important thing that I just noticed is that each register is 32 bits so it is not as simple as just connecting register0_in to an I/O marker or VCC or GND. You will need to connect those single signals to register0_in(0) or register0_out(0) and read the first bit of the 32 bit wide register. You will want to use a bus tap to accomplish that. There is a tutorial here. Once you get comfortable with doing this from the schematic editor then move on to VHDL. You will want to make a VHDL module that outputs your counter as a port at its top level. Start with making a module that just outputs a 0 or 1 from a port at the top level. After you have created the VHDL module (as a file included in your project) then right click on that file in your file hierarchy list on the left side of ISE and there should be an option to turn the VHDL file into a symbol. Once you successfully run the command to generate a symbol from your VHDL file you should then be able to find it in the symbol navigator and add it to your schematic. Then you connect it to the pads of the Wishbone_to_Registers_x10 symbol. Hope this gets you rolling in the right direction. Jack.
  16. In the meantime, try to comment out this section like it says: //Comment out this section for Papilio One. #ifdef __ZPUINO_PAPILIO_PRO__ #include <SD.h> #include "SmallFS.h" #include "modplayer.h" #include "ramFS.h" #include "cbuffer.h" MODPLAYER modplayer; #endif Like this: //Comment out this section for Papilio One. //#ifdef __ZPUINO_PAPILIO_PRO__ // #include <SD.h> // #include "SmallFS.h" // #include "modplayer.h" // #include "ramFS.h" // #include "cbuffer.h" // MODPLAYER modplayer; //#endif
  17. OK, I will try to take a look at this tonight and get back to you. Jack.
  18. I have never tried out the ethernet shield with the Papilio DUO so not sure what the problem is that you are running into... If you load a blank circuit to the FPGA side then there should not be any conflicts... You could also try to use one of these types of ethernet modules: http://store.gadgetfactory.net/ethernet-module/ Jack.
  19. Yes, I haven't visited that code in a while but I'm pretty sure what you are running into is that certain libraries are disabled for the Papilio One because there is not enough memory to support them. What are you trying to compile anyway, I can't really tell from your pasted information... It should say in the comments for the example what boards are supported. I think the Papilio One barely supported the Amiga mod player by itself, but definitely not with other players... That was the whole reason for the RetroCade light version. It was made for the Papilio One. Jack.
  20. Not everything will fit into the Hyperion version of ZPUino. Hyperion sacrifices some memory that was available for program space for video memory. The Papilio One does not have any external memory so it is very memory constrained compared to the Papilio Pro. Then Hyperion makes it even more so... I would recommend trying the regular version of ZPUino for the Papilio One and see if it works. If not then the Papilio One does not have enough memory for the example you are trying to synthesize. Jack
  21. This looks really cool, I can't wait until I get some time to dig into this and check it out some more. Jack
  22. Hello, The USB channel on the Papilio is a max of 3Mb/s so it will probably not be fast enough for what you are wanting to do. Alvie has created a USB wing that is a PHY and a USB core for the FPGA but it is just USB 1.1 I think so probably not fast enough. If we can get a USB 2.0 USB PHY wing then that would open up a lot more possibilities for projects like this one... Jack.
  23. Thank you for the understanding and I'm sorry we don't have a better answer. The material in the old ebook is still valid with the Papilio DUO, so it is still a great read... Jack.
  24. Hello RoelandK, I'm sorry but the eBook was never updated. Mike Field was going to do the ebook but right after the kickstarter finished he got hired on at a new job where he suddenly found himself with much less time to work on Open Source projects... We spoke about the book several times since, and he really wants to do the book, but he just does not have the time anymore... I'm sorry that was never completed, if you would like a partial refund or a store credit please send us an email at support@gadgetfactory.net and we will try to make this right for you. I have actually considered updating the ebook myself, but I think it would be after I finish up the next Papilio board and a new software suite to go with it since that will probably be the most beneficial to the Papilio community. After those are done then I think updating the ebook is the next step. Jack.
  25. Hello adamada, You should check all of your configuration settings. The easiest way to do that is to open the *.xise file and compare it to an xise file that is successfully generating a bit file that loads to spi flash. You have probably accidentally set the configuration to a quad spi chip or something... Jack.