OmniTechnoMancer

Members
  • Content count

    83
  • Joined

  • Last visited

Community Reputation

0 Neutral

About OmniTechnoMancer

  • Rank
    Advanced Member

Profile Information

  • Gender Not Telling
  1. If you read the description of that it would not be very useful as each voltage terminal is fused at 1.25A so not useful for supplying 10A@5V unless you want to short/change the fuse.
  2. Perhaps we should start a new thread if this discussion continues. I have not tried it with larger programs, but the instruction sizes scale directly with the number of transport buses and the short immediate width of those buses as the slot for a bus has to be wide enough for the short immediate that can be used on it. If you use an immediate unit and long immediates with a few busses you can shorten the short immediate sizes but still keep the ability to use 32bit immediate values. Aside from the instruction width I guess the issue is mostly how many instructions you can fit in the blockrams available and whether your processor is able to be used efficiently by your program, resulting in fewer overall instructions. Also you have to be careful since the transport bus connection logic is the most resource consuming part usually, you don't want every bus connected to ever FU in the processor.
  3. The software here http://tce.cs.tut.fi/ can be used to design them and has a C compiler.
  4. Perhaps use a TTA processor instead?
  5. It's not really doing ethernet if you dont use just a PHY on the wing
  6. Don't ever use a signal as if it were a clock, and, at least for VHDL don't have any processes that have if's and assign signals in only one branch (this will cause the synthesis to generate storage elements).
  7. It isn't an asynchronous mode. You simply either use the flip-flops and clock or you don't, you can use entirely combinational logic if you want.
  8. Well its probably the char* and int overloads causing it as 0 could be either, note that you need to use '\0' if you want a character with value zero sent on the serial rather than the digit 0
  9. The issue is more that in order to get the conversion noise far enough away from your signal you need to oversample by a significant margin, this will require several hundred megasamples per second to get input on the order of a few MHz, you could try band pass sampling, but for that to work you will need a band pass filter on the input.
  10. You might have some issues getting a high enough sample rate if you are doing MHz frequency sampling...
  11. Do you need USB host or USB device, (I assume host as one doesnt usually have more than one device port) if so then it may be better to use one USB core an an external HUB or HUBs to get 30 ports, there are not enough pins on any of the papilios for 30 USB ports anyway needless to say space for 30 host cores in the FPGA, why do you need so many anyway? On the subject of high level development, I personally think that learning digital design is more useful in the long run as it allows you more understanding of what is going on, the high level tools are fine for if what you really want is a computer that instead of being general purpose just does this specific DSP stuff instead but you can't exactly do general purpose digital development with them. And to add new function for the thing Jack is working on one would write a wishbone core in verliog VHDL or use the schematic editor (A bad choice as it will be extremely slow and far less expressive than HDL).
  12. This is a 1 bit ROM implementation. Its the same pattern you use to make ROM but with a std_logic_vector instead of an array of them and the input bits concatenated rather than an address.
  13. What Jack is referring to here can be accomplished by a conjunction of loopMIDI and the dashboard, you set the dashboard to take a MIDI input and use loopMIDI to create a MIDI device that can be set as that input but also used as an output for the desired program.
  14. The Retrocade ZPUino code implements two MIDI interfaces, one for the MIDI ports on the board and one on the FTDI UART connected to the FPGA, this is what the windows dashboard uses to control the synth. Adding USB MIDI in any way other than buying a USB midi adapter and plugging it into the ports will not be easy, so take this as a no for now. You could access the exposed sound chips the same way that the dashboard does by speaking MIDI over the UART connection, alternatively you could write a different sketch for the board that provides a more suitable interface and use that.
  15. Yes you can change the baud rate on linux whenever, its a standard serial port operation, I don't know if you can use arbitrary rates though, you can definitely pick any of the usual ones like 115200 though.