Hardware/Software Co-design for Heterogeneous Multi-core by Koen Bertels (auth.), Koen Bertels (eds.)

By Koen Bertels (auth.), Koen Bertels (eds.)

HW/SW Co-Design for Heterogeneous Multi-Core systems describes the implications and end result of the FP6 undertaking which specializes in the advance of an built-in device chain focusing on a heterogeneous multi center platform comprising of a common goal processor (ARM or powerPC), a DSP (the diopsis) and an FPGA. The software chain takes latest resource code and proposes ameliorations and mappings such that legacy code can simply be ported to a contemporary, multi-core platform. Downloadable software program can be supplied for simulation purposes.

Show description

Read Online or Download Hardware/Software Co-design for Heterogeneous Multi-core Platforms: The hArtes Toolchain PDF

Best nonfiction_5 books

Additional resources for Hardware/Software Co-design for Heterogeneous Multi-core Platforms: The hArtes Toolchain

Sample text

Lattanzi et al. • additional tools and libraries for format conversion, metrics extractions, interaction with the operating system running on the platform. The hgcc Compiler for the target GPP is extended to support pragma annotations to call the selected HW implementation. The effect of these pragmas is to expand functions into a sequence of Molen APIs (see later). This customized version of the C compiler for the GPP is called hgcc since it is a customization for hArtes (h) of the gcc compiler.

Lattanzi et al. The former ones should be excluded from the parallelism extraction. g. IO or supervisor calls), it shall be marked with a specific directive to be excluded from the partitioning. In this way, a better performing code will be obtained since the parallelism extraction operates only on the data processing region, where no interfacing with external world occurs. For this reason, the source code has to be compliant with this structure to allow the parallelism extractor tool to concentrate its effort on meaningful parts of the application.

Example: MEM1 SDRAM 128 0 0xFFFFFFFF The BUS_COMPONENT contains: • NAME: used to identify the bus. • BANDWIDTH: the size of one memory transfer in kbytes/sec (for example: 1024). • FUNCTIONAL_COMPONENTS: functional components that can access this bus – NAME: the name of the functional component. • STORAGE_COMPONENTS: storage components connected on this bus – NAME: the name of the storage component.

Download PDF sample

Rated 4.01 of 5 – based on 33 votes