disclaimer: I work for Kagi
278 karma · joined September 15, 2020
https://blog.eowyn.net/
disclaimer: I work for Kagi
[1]: https://streaks.app/ [2]: https://f-droid.org/en/packages/org.isoron.uhabits/
This is because ARM uses device trees to know what hardware's on the device, versus x86 which discovers it at boot. Every rom has to be specifically built for that exact device model.
$ curl https://nobodywasishere.github.io # moved to https://blog.eowyn.net
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>
$ curl https://blog.eowyn.net/vhdlref-jtd # moved to https://blog.eowyn.net/vhdlref
<html>
<head><title>301 Moved Permanently</title></head>
<body>
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>- multi-driven nets where two or more signals are driving the same node
- the target not supporting certain features like multi-clocked FFs
- missing components or libraries (not uncommon if you're trying to use VHDL 2008, for example)
- timing analysis failing, meaning the HDL isn't fast enough / the critical path is too long for how fast the fpga is going to go
And while not necessarily being unsynthesizable, a lot of tools like Vivado will heavily optimize the HDL, meaning if you forget to connect a part of the HDL to the output or do something with it, it will be removed from the design.
[1]: https://schema.org/Recipe [2]: https://github.com/nextcloud/cookbook/