URL
https://opencores.org/ocsvn/or1k/or1k/trunk
Subversion Repositories or1k
[/] [or1k/] [trunk/] [rtems/] [make/] [custom/] [dmv177.cfg] - Rev 1765
Compare with Previous | Blame | View Log
## Config file for a PowerPC 603e based DY-4 VMEbus Single Board Computer.# This BSP should work with the following models:## + SVME-171/DMV-171# + SVME-176/DMV-176## $Id: dmv177.cfg,v 1.2 2001-09-27 12:02:52 chris Exp $#include $(RTEMS_ROOT)/make/custom/default.cfgRTEMS_CPU=powerpcRTEMS_CPU_MODEL=ppc603e# This is the actual bsp directory used during the build process.RTEMS_BSP_FAMILY=dmv177# This section makes the target dependent options file.# NDEBUG (C library)# if defined asserts do not generate code. This is commonly used# as a command line option.## RTEMS_TEST_NO_PAUSE (RTEMS tests)# do not pause between screens of output in the rtems tests## RTEMS_DEBUG (RTEMS)# If defined, debug checks in RTEMS and support library code are enabled.## CONSOLE_USE_POLLED (psim_bsp)# CONSOLE_USE_INTERRUPTS (psim_bsp)# The psim console driver has the structure to operate in either# polled or interrupt mode. However both modes only trap to the# monitor currently.## PPC_VECTOR_FILE_BASE (ppc)# This defines the base address of the exception table.# NOTE: Vectors are actually at 0xFFF00000 but file starts at offset 0x0100## PPC_USE_SPRG (RTEMS PowerPC port)# If defined, then the PowerPC specific code in RTEMS will use some# of the special purpose registers to slightly optimize interrupt# response time. The use of these registers can conflict with# other tools like debuggers.## PPC_USE_DATA_CACHE (RTEMS PowerPC port/BSP)# If defined, then the PowerPC specific code in RTEMS will use# data cache instructions to optimize the context switch code.# This code can conflict with debuggers or emulators. It is known# to break the Corelis PowerPC emulator with at least some combinations# of PowerPC 603e revisions and emulator versions.# The BSP actually contains the call that enables this.## PPC_USE_INSTRUCTION_CACHE (RTEMS PowerPC port/BSP)# If defined, then the PowerPC specific code in RTEMS will use# data cache instructions to optimize the context switch code.# This code can conflict with debuggers or emulators.# The BSP actually contains the call that enables this.define make-target-options@echo "/* #define NDEBUG 1 */ " >>$@@echo "#define RTEMS_TEST_NO_PAUSE 1" >>$@@echo "/* #define RTEMS_DEBUG 1 */" >>$@@echo "#define CONSOLE_USE_INTERRUPTS 0" >>$@@echo "#define CONSOLE_USE_POLLED !CONSOLE_USE_INTERRUPTS" >>$@@echo "#define PPC_VECTOR_FILE_BASE 0x0100" >>$@@echo "#define PPC_USE_SPRG 0" >>$@@echo "#define PPC_USE_DATA_CACHE 0" >>$@@echo "#define PPC_USE_INSTRUCTION_CACHE 1" >>$@endef# This contains the compiler options necessary to select the CPU model# and (hopefully) optimize for it.#CPU_CFLAGS = -mcpu=603# optimize flag: typically -0, could use -O4 or -fast# -O4 is ok for RTEMS# NOTE: some level of -O may be actually required by inline assemblerCFLAGS_OPTIMIZE_V=-O4 -fno-keep-inline-functions# Define this to yes if this target supports a real-time clock.HAS_RTC=yes# The following is a ld command file which works without using the# -specs system in gcc 2.8. IT HAS NEVER BEEN TESTED WITH THIS BSP!!!# $(LD) $(XLDFLAGS) -T $(LINKCMDS) \# -o $@ -u atexit -u __vectors -u download_entry $(LINK_FILES)# $(LD) $(XLDFLAGS) -Ttext 0x20000 \# -o $@ -u atexit -u __vectors -u download_entry $(LINK_FILES)# $(CC) -mmvme -mrtems -nostartfiles -mcpu=603 \# -o $(basename $@).exe -L $(PROJECT_RELEASE)/lib \# $(START_FILE) $(LINK_OBJS) \# $(LD_LIBS) \# -Wl,-\( -Wl,-lc -Wl,-lrtemsall -Wl,-lgcc -Wl,-\)define make-exe$(LINK.c) $(AM_CFLAGS) $(AM_LDFLAGS) \-o $(basename $@).nxe $(LINK_OBJS) $(LINK_LIBS)$(OBJCOPY) -O srec $(basename $@).nxe $(basename $@).i$(SED) -e 's/.$$//' -e '/^S0/d' $(basename $@).i | \$(PACKHEX) > $(basename $@).exe$(NM) -g -n $(basename $@).nxe > $(basename $@).num$(SIZE) $(basename $@).nxe$(STRIP) $(basename $@).nxeendef# Miscellaneous additions go here# Let the HWAPI know which set of drivers to buildDRIVER_ARCHITECTURE=vmebus
