4 ms·
I was working on that around 2015 if I remember well. Some time after Xilinx was unifying their development tools into Vivado. The project attempted to use Zynq
by user5994461 6y ago
I was working on that around 2015 if I remember well. Some time after Xilinx was unifying their development tools into Vivado. The project attempted to use Zynq SoC, joint software and hardware development on the FPGA in HDL and on the embedded CPU in C. Not exactly trivial things to do but the scope was very small for a first go.
We found zero documentation whatsoever on the internet. None of the things you linked to existed. Looks like it took 5 years for some tutorials to be written, and it's not even from Xilinx, it's from some guy sharing on GitHub (maybe a university).
Interns were not to blame, more experienced engineers couldn't figure a thing and there was a 3 months deadline. If it were not for one employee who tried the Zynq platform 6 months before and was trained by Xilinx, the whole thing would surely have been canned.
There was lots of issues with the platform and the IDE once got a hello world working (I really hope Xilinx fixed most of them). Basic APIs were not working or were documented wrong, the compiler had issues (modified gcc under a modified eclipse), the IDE occasionally crashed or got stuck (it called a ton of sub processes that got lost or failed).
The SoC IO pins were undocumented (needed info and identifier to do the routing), had to get private doc from Xilinx and they had typo in their pin layouts, so there was a constant risk to misconfigure a pin and fry the board (FPGA don't forgive mixing up input and output and voltage).
Now that I remember about it. The whole thing was pretty insane. ^^
My only question if I had to work on this again would be, does vivado support Git/SVN nowadays?
- tails4e 6y agoThanks for the detailed reply, but FYI the github stuff is from xilinx, they just make it open source. In 2015 vivado was pretty new, it's come a long way, so I'd give it another look. There has been a strong push as you can see to make the developer experience much better, so hopefully if you give it another chance you may come to appreciate it as much as I do.
- user5994461 6y agoTo be fair, the HDL tools are decent. There are some quirks but they get the job done (obviously it's professional tooling, not something an enthusiast can pick up over a weekend). I think you're working on the FPGA side? However the software development experience is dismal overall. I doubt it will ever improve much, hardware companies just don't make good development tools. The closest experience developers get to embedded might be android development. The IDE are good, source control, auto completion, the platform documentation is amazing, fully documented API with examples, there are entire guides on how the system work, remote debugging on the device (I've developed on Android version 1 a decade ago and it was all there). It's just great. Now try developing for a MCU and half the manufacturers can't document how to read an IO pin or use the DAC. I'm not looking forward to moving back to embedded. ^^