So who at Xilinx decided that their toolchain should only support a years old Ubuntu version which is buggy and one minor release behind LTS?

  • 3
    It's not uncommon in embedded...

    Old unmaintained kernel, some GCC from 10 years ago and compiling...

    Compiler has warnings diarrhea shitting all over the screen
  • 1
    Wait until you see "board support packages".

    Oh, and the "devrant" tag is for stuff about devrant.com itself. It's not for "developer rant" because there are only devs here - hence, no finance, HR and management rants as opposed to developer rants.
  • 1
    Eh? Vivado HLx supports up to Ubuntu 18.04 LTS as mentioned in the June 2020 update of UG973

    They even support CentOS 8.1, what more do you want
  • 1
    @Fast-Nop BSPs are actually really pleasant in Xilinx tools. Since you literally make hardware in the FPGA fabric, as long as you're using a standard interface that Vivado recognises, the tool will generate the BSP for you right there when you open the embedded development environment. And the generated code is pretty pleasant to work with. Same with Altera/Intel's FPGA tools for chips with embedded processors. Both of them have really worked hard to make the UX quite pleasant (compared to your average hardware tool).

    It's a much much nicer flow than say, stm32Cube MX or TI's CCS, both of which can just please go die in hellfire

    BSPs aren't the problem, it's just the general prevalence of bad tooling and practices in the embedded industry :p
  • 1
    @RememberMe I meant vendor Linux BSPs for ARM SoCs, that's usually a nightmare to work with because you just can't use them bare metal.

    I mean, shit like ST's Cube MX is nasty, but you can just not use it and be happy.
  • 1
    @Fast-Nop yup, they're an absolute nightmare. Also an absolutely avoidable nightmare but what to do, it'll take too much time to rewrite their code.
Add Comment