sifive / freedom-devicetree-tools

A linker script generator for SiFive's Freedom platform

Device Tree Tools for the Freedom SDK

This project contains a handful of tools that are designed to aid embedded software developers to generate statically parameterized designs from Freedom platform device trees. Help for the various tools can be found by passing the --help argument, to the tool once they have been built.

If you're interested in using the tools then it's probably best to check out the Freedom SDK, which uses these tools to parameterize the Freedom METAL for the various targets that it can support.

As a quick overview, here are the tools that are installed as part of this project:

• freedom-ldscript-generator: Generates linker scripts that are compatible with the Freedom METAL from a device tree.
• freedom-makeattributes-generator: Generates Makefile attributes (CFLAGS, LDFLAGS, etc) from a device tree.
• freedom-mee_header-generator: Generates a METAL header parameterization file, which allows the METAL to target the device described by the given device tree.
• freedom-openocdcfg-generator: Generates an OpenOCD configuration file from a device tree.
• freedom-zephyrdtsfixup-generator: Generates a dts.fixup configuration file from a device tree. This is a temporary requirement of the Zephyr RTOS project to support DTS-based driver configuration.

How to Build

If you're just planning on using this project then you should use the latest tarball release, which is always available from the GitHub releases page. Builds are uploaded from Travis after they succeed.

Ubuntu 16.04 LTS

The following packages are necessary to build from a tarball

• build-essential
• libfdt-dev
• device-tree-compiler

Additionally, the following packages are necessary to build from git sources:

• autoconf
• automake
• git

freedom-devicetree-tools's Issues

Refactor ldscript generator

Allow the user to target specific memories

We have the --scratchpad argument, but that's not particularly general because lots of systems are more complicated than just having a single memory. We should really allow users to pick the memory they want to target for various segments, as well as a tool to list what memories are available.

Heap size count is wrong in generated linker script

The generated heap info:
.heap : {
PROVIDE( metal_segment_heap_target_start = . );
. = __heap_size;
PROVIDE( metal_segment_heap_target_end = . );
PROVIDE( _heap_end = . );

Which should be
. += __heap_size;

Consider IO solutions that aren't iostreams

Discussion in PR #13 about using IO formatting solutions that aren't iostreams

@michaeljclark suggested fmtlib

configure should fail of libftd.h is not present.

Currently, the AC_SEARCH_LIB() does not not have an "action if not found", which should cause an exit with error.