- The Zynq MPSoc is the Ultrascale Zynq (released 4 years later), not the plain Zynq. A “good” (7020) plain Zynq board with decent I/O ports costs about £100, the very cheapest Ultrascale boards are twice that with far less expansion ports - to get similar I/O you’ll be up in the 3-4x price bracket at least. They’re very different products, fabricated on different technologies (16nm, not 28nm), with fundamentally different internal architecture (eg: Ultrascale has built-in Ultraram, far better power management, quad A53 + dual R5F vs (max)dual A9, codecs on some, ddr4 support,…)
- This isn’t the first OS I (without the quotes) have written for the Zynq. I wrote the OS for the Apple Vision Pro, quite some time before LLM’s existed, when it was a prototype on my desk, consisting of a Zynq being the boot-up device and architecture controller for a bunch of the fastest and largest FPGAs on the planet interconnected with optical fibre. And this one did not rely on FreeRTOS (or any other OS) for anything.
- I would agree with you that it ought to be blatantly obvious that I’ve used an LLM to help out, the timescale itself should be a dead giveaway. However, the very first comment I got (“How is this supposed to be relevant to the article we're discussing?”) seemed to miss the quotes around the “I”. The signoff comment was more a “get a life” response to the subsequent down-voting haters than anything else. LLMs are just tools, you still need the skills and knowledge to direct them and correct them on anything as significant as a compiler.
- “modified” is carrying significant water… XTOS has shared libraries, dynamic linking, can launch external programs from disk not just compiled-in tasks, has shared memory, CoW pages, page-protection (nx, pid locking), swap, threading, system calls, a posix layer, networking, virtual filesystem support, boot-script support, interactive shells with ptys, and a graphical compositing window manager which outputs 1080p HDMI (ie: with the embedded audio islands, not just DVI over an HDMI interface). But yes, “I” still use FreeRTOS for context switching and interrupt control. It boots far far faster than Linux, which was the point. I wanted a switch-on-and-go appliance-like OS, not a visible boot sequence.
- The Zynq MPSoc is the Ultrascale Zynq (released 4 years later), not the plain Zynq. A “good” (7020) plain Zynq board with decent I/O ports costs about £100, the very cheapest Ultrascale boards are twice that with far less expansion ports - to get similar I/O you’ll be up in the 3-4x price bracket at least. They’re very different products, fabricated on different technologies (16nm, not 28nm), with fundamentally different internal architecture (eg: Ultrascale has built-in Ultraram, far better power management, quad A53 + dual R5F vs (max)dual A9, codecs on some, ddr4 support,…)
- This isn’t the first OS I (without the quotes) have written for the Zynq. I wrote the OS for the Apple Vision Pro, quite some time before LLM’s existed, when it was a prototype on my desk, consisting of a Zynq being the boot-up device and architecture controller for a bunch of the fastest and largest FPGAs on the planet interconnected with optical fibre. And this one did not rely on FreeRTOS (or any other OS) for anything.
- I would agree with you that it ought to be blatantly obvious that I’ve used an LLM to help out, the timescale itself should be a dead giveaway. However, the very first comment I got (“How is this supposed to be relevant to the article we're discussing?”) seemed to miss the quotes around the “I”. The signoff comment was more a “get a life” response to the subsequent down-voting haters than anything else. LLMs are just tools, you still need the skills and knowledge to direct them and correct them on anything as significant as a compiler.
- “modified” is carrying significant water… XTOS has shared libraries, dynamic linking, can launch external programs from disk not just compiled-in tasks, has shared memory, CoW pages, page-protection (nx, pid locking), swap, threading, system calls, a posix layer, networking, virtual filesystem support, boot-script support, interactive shells with ptys, and a graphical compositing window manager which outputs 1080p HDMI (ie: with the embedded audio islands, not just DVI over an HDMI interface). But yes, “I” still use FreeRTOS for context switching and interrupt control. It boots far far faster than Linux, which was the point. I wanted a switch-on-and-go appliance-like OS, not a visible boot sequence.