Wiki

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
university:tools:pluto:devs:embedded_code [23 Aug 2019 21:56] – [Running on Pluto] Robin Getzuniversity:tools:pluto:devs:embedded_code [14 Jan 2021 05:38] – use xilinx> interwiki links Robin Getz
Line 6: Line 6:
   * A host machine to run a compiler on. This can be either Windows (x86) or Linux (x86 or ARM) (yes, you can build PlutoSDR Applications on Raspberry Pi). (it's possible on macOS, but just more difficult, since you will need to build a toolchain from scratch, beyond the scope of what I'm willing to write - check google, you are on your own).    * A host machine to run a compiler on. This can be either Windows (x86) or Linux (x86 or ARM) (yes, you can build PlutoSDR Applications on Raspberry Pi). (it's possible on macOS, but just more difficult, since you will need to build a toolchain from scratch, beyond the scope of what I'm willing to write - check google, you are on your own). 
   * A compiler with the same version used to compile the PlutoSDR firmware. See the Pluto SDR mass storage device file "index.html", or check [[https://github.com/analogdevicesinc/plutosdr-fw/releases|PlutoSDR firmware releases page]] for the relevant information.   * A compiler with the same version used to compile the PlutoSDR firmware. See the Pluto SDR mass storage device file "index.html", or check [[https://github.com/analogdevicesinc/plutosdr-fw/releases|PlutoSDR firmware releases page]] for the relevant information.
-      * [[https://www.xilinx.com/products/design-tools/embedded-software/sdk.html|Xilinx SDK]] +      * [[xilinx>products/design-tools/embedded-software/sdk.html|Xilinx SDK]] 
       * [[http://releases.linaro.org/components/toolchain/binaries/|Linaro toolchain]]       * [[http://releases.linaro.org/components/toolchain/binaries/|Linaro toolchain]]
   * System Root of the firmware used on PlutoSDR itself (this will be downloaded in the example). This includes the libraries (binaries, so you can statically link to things if you want), and headers for those libraries. It's important that the compiler be told where things are, so it can find the headers and libraries for the Pluto. This can either be done on the command line, or by replacing the default sysroot that the compiler comes with. If you are only compiling things for Pluto - this is a convenient solution, but will eventually will cause problems when you forget, and try to compile something else with this same toolchain.   * System Root of the firmware used on PlutoSDR itself (this will be downloaded in the example). This includes the libraries (binaries, so you can statically link to things if you want), and headers for those libraries. It's important that the compiler be told where things are, so it can find the headers and libraries for the Pluto. This can either be done on the command line, or by replacing the default sysroot that the compiler comes with. If you are only compiling things for Pluto - this is a convenient solution, but will eventually will cause problems when you forget, and try to compile something else with this same toolchain.
university/tools/pluto/devs/embedded_code.txt · Last modified: 06 Oct 2023 11:02 by Adrian Suciu