• Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About Logxen

  • Rank

Profile Information

  • Gender Male
  1. If you just want to communicate between two fpga in a generic manner I would suggest the sata wings. Sata is 2 differential pairs which works out perfect for one send lane and one receive lane. Additionally sata cables are much cheaper than hdmi cables and many of us even have extras lying around at this point. Fyi, the simple hdmi wing is 4 differential pairs. I've oft thought the set could use a quad sma wing to be complete but I don't know that there is any interest.
  2. Ok, here's the first prototypes: I've got a set like this going out to Jack and Alvie for testing.
  3. I have been thinking about that too... currently I'm trying to decide between making a wing around the UDA1345 (http://www.nxp.com/documents/data_sheet/UDA1345TS.pdf) or the UDA1380 (http://www.nxp.com/documents/data_sheet/UDA1380.pdf). Both of those chips support 24bit... and in either case the wing will probably be a simple one with a single stereo input and a single stereo output, since more connectors probably won't fit on a single wing without using 'stacked' connectors like they do on motherboards. Since I2S is a relatively simple protocol (i.e. not differential) it will work on any port so you should be able to use up to 6 HD Audio Wings at time. Did anyone else have any chips in mind? The main points I'm looking for are a stereo input, stereo output, 16-24bit, and for as low cost as possible.
  4. There is no real reason to start with the Spartan3 first, it's just cheaper and slower. It's not any harder or easier to configure and use. If you have the cash I would definitely suggest getting the Papilio Pro.
  5. I've got some protos for a simple HDMI Wing for Papilio Pro on order and I'm cleaning up the design for an HDMI+CEC Wing. HDMI requires 4 differential pairs but luckily the Papilio Pro layout is set up very well for differential applications. It will be able to support up to two simple HDMI Wings attached to Wing C and up to two HDMI+CEC Wings attached to Wings A and B. This will allow prototyping with up to 4 HDMI ports on the same board! \o/ Here are some pcb renders of the HDMI Wings: I also went and looked through the differential mapping on the Papilio One... by a stroke of luck the HDMI+CEC Wing should be compatible with Wing AL+BH, so even the Spartan-3 can have some HDMI love!
  6. IT IS DONE! https://github.com/logxen/SPIEthernetWing Have at it Alex
  7. In theory other than pinout the only real difference should be the lack of a power led. I don't actually have a schematic for the original board ... I based it off the same chip though and attempted to follow the original board even where it deviates from spec (i.e. the wol pin). I don't currently have the .sch and .brd uploaded anywhere but I can fix that easy enough.
  8. So here's the first prototype for a proper ethernet wing. I just finished it over the weekend: I don't have any actual code to test it with but when I powered up the Papilio and plugged in an ethernet cable the link lights came on at both ends so things are looking good. Jack: That proto will be going in the mail to you today so you can get back to hacking.
  9. Here's a project I've been studying that should make a good starting point: http://www.holmea.demon.co.uk/GPS/Main.htm He's got both hardware and code up there. Wow... I need to read the original post a bit better, eh?
  10. Ok, so I tried decreasing the board size to see what would happen: On one hand I added the WING_D at Jack's request bringing it up to a neat 128 pins. I did a pincount and that would have used pretty much exactly ALL the pins on the BGA256 chip I was originally targeting (and using all the pins on a BGA256 is a bit iffy on a 4-layer board.) So I went ahead and swapped up to the CSG324 which is going to make routing a lot easier anyway. Other than that and the *squish* this is the same board as above. I think adding WING_D is a good plan... for one thing it (in theory anyway) would allow one to install a MegaWing facing either direction. I have the two MegaCocoons separated my 0.8" to make sure that MegaWings can fit without blocking access to the other 64 pins. However, I don't think it would fit two of any current MegaWings even with the *squish* design. So, I think it may be best to go back to my original board outline that allows a single MegaWing facing either direction on the lower MegaCocoon, and full use of 8bit and 16bit Wings on the upper MegaCocoon.
  11. Here's an example of that exact chip on a pcb prototyped through Oshpark: (photo courtesy of azonenberg on irc.freenode.net/#oshpark) And the gentleman that did that board isn't alone... several others in the Oshpark community have been successfully doing bga chips for a while now. With their guidance (and maybe buying myself a reballing kit off eBay) I expect to be able to prototype the board I described without much difficulty. As to the production run my assembly house is fully qualified to assemble bga. I recently e-mailed them and they assured me that their assembly machines support bga chips of this pitch.
  12. Yeah, I'm not sure I'd want to prototype bga through iTead (who I'd assume those quotes came from)... Oshpark just upgraded their 4-layer fab to 5/5 traces and 10/4 vias which is actually good enough to 0.8mm pitch bga. The $10/in2 for three boards certainly adds up, but I'm not too worried about prototype cost. If enough people are interested and I do a production run the pcb cost becomes negligible next to the component costs. Edit: Oh I missed that you mentioned Seeed. I have to admit I've not ordered from them before. At any rate I'm happy with the quality of the boards where I currently source them.
  13. Greetings! I am a contributor to the Smoothieboard project (http://smoothieware.org) and am interested in developing a Papilio-compatible board with higher pincount for cnc control. The basic idea involves bumping the fpga up to a bga package, much like the Pipistrello, but then breaking out 112 pins instead of the standard 48 pins. Here is a first draft concept layout: Clearly, this is built off of the Papilio Pro as a base, and is meant to be as compatible as possible with existing hardware and software designs. To this end, the lower three 16-bit wing ports A, B, and C match a standard Papilio and should accept existing Megawings. The next port, D, is left free for system concepts such as the built-in LED. The upper 4 ports are assigned ports E, F, G, and H. This neatly fills out the 128-pin potential of Zpuino's standard gpio block. The upper 4 ports are also spaced to allow two sets of inward facing wings without blocking a Megawing in the lower slots. 64MBit flash seems more than sufficient for basic programming even on to lx25 chips (especially with the addition of an sdcard slot) so I figure that can stay an easy to assemble soic. I still haven't really decided if it's really worth bumping the ram up from 64MBit soic to a more expandable bga package... Other than that I intend to follow the Papilio Pro designs closely, including the upgraded power supply systems. I will probably prototype this to some degree for my own purposes over the next few months... let me know what you all think and whether this is worth turning into a real product! If enough interest is shown I will act on it sooner and maybe even go past prototype.
  14. That sounds great! Do you have any plans about how to distribute the vendor ids?
  15. Yay! Finally got my button/led wing today and everything works fine. Thanks Alvie.