Fun post, on opposite poles of advice .. Zygot (with his good work) a purist , XC a pragmatist .. Zygot forgets his lament on broken build tools , and how much time is spent in workarounds A miserable fact of this industry, esp in PGA , unless U buy a Data I/O ( i think obsolete) Why invite a nightmare to a newby when alternatives abound
AS to hiring a programmer, XC gave better advice when costs were only mildly affected. Zynq / ARM combo. Better to buy a PCIe Dev Board for $1200 than years wrestling with protocols used in trading on unsupported EVM (& look at Exchange industry and what it offers ( like tick real time price data & volume) IF that's your business target.
Why buy TEMAC IP license $1000 to $4500 for cores when functionality is built into a Dev board free. Are u going to emulate a NIC or work in AI with Exchange data ?
YEs zygot will recommend coding a NIC in VHDL, FIFO s , handlers, buffers , Packet inspection , Firewall rules, threaded event loops, a full stack, then Array processing
Sounds like fun. The wheel comes infinitely shaped in this age of revelation. Note u changed course from Wall St challenge to a job at the hub factory. Very educational
And u may invent a new type of wheel. Tho with right inclination you may create a intuitive PGA macro library to allow smoother work in a block diagram flowchart.
That would be worth an adventure providing you gained sufficient background in related art along the way.
tho if u find yourself back in the original pursuit of high frequency / low latency then get the 8K5 KU115 board for $3860 from Alpha Data when u can afford tools.
https://www.xilinx.com/products/boards-and-kits/1-dw5yg1.html as the best hardware or develop modular, ask Z to port this to Octave (not sure it has simulink)
https://www.xilinx.com/products/design-tools/vivado/integration/addon-matlab-simulink.html .. Unless u think to create your own macro library from scratch.
there u have 2 alternate industry standards. good luck with the guitar
I was able to program the spi flash memory on the cmod a7 by compiling xc3sprog from source on my raspberry pi. Here are the steps I used:
(1) install libftd2xx drivers
download libftd2xx-arm-v7-hf-1.4.22.gz and follow instructions in ReadMe.txt
case 0xba:
fprintf(stderr, "Found Numonyx N25Q Device, Device ID 0x%02x%02x\n",
fbuf[1], fbuf[2]);
switch (fbuf[2])
{
case 0x16:
pages = 16384;
sector_size = 65536;
break;
(4) Compile xc3sprog
mkdir xc3sprog/build
cd xc3sprog/build
cmake ..
make
sudo make install
(5) Run the program command with the "-I" option, using the attached first.bit to help detect the spi flash rom.
xc3sprog -c jtaghs1_fast -Ifirst.bit
xc3sprog -c jtaghs1_fast -I your_design.bit
Works like a charm.
I have attached the xc3sprog compiled to run on raspberry pi (it still needs the libftdi1 library to be installed... sudo apt-get install libftdi1).
first.bit run_first_spi_flash_cmod_a7.sh xc3sprog
The first.bit file was created by taking this VHDL design from the github xc3sprog repo: xc3sprog/bscan_spi/bscan_xc7_spi.vhd and making it into a bit file using Vivado (with the target being the CMOD A7 board). I have included the constrants file "constr.xdc" which I used to create the first.bit file.
well, by default your signal is between 0 V and Vref. The opamp circuit has a gain of 2 (range 0.. 2 VRef) but subtracts a constant VRef (range now -VRef..Vref).
It'll just shift the waveform on the scope, and double its AC magnitude.