avockley Posted June 5, 2012 Report Share Posted June 5, 2012 (edited) I am having trouble compiling anything using the eeprom module in mios32. Any code that doesn't use the eeprom library compiles correctly, but even the eeprom tutorial doesn't work. I am on OS X 10.7. Aarons-Macbook-Pro:025_sysex_and_eeprom aaron$ make rm -f project.hex make: *** No rule to make target `project_build/~/svn/mios32/trunk/modules/eeprom//eeprom.o', needed by `project_build/project.elf'. Stop. Aarons-Macbook-Pro:025_sysex_and_eeprom aaron$ The next problem, which I think is part of the same issue, is that I can't include the eeprom header in my own apps using #include <eeprom.h>. Aarons-Macbook-Pro:ArtNet Node aaron$ make rm -f project.hex Creating object file for app.c app.c:21:20: fatal error: eeprom.h: No such file or directory compilation terminated. make: *** [project_build/app.o] Error 1 Aarons-Macbook-Pro:ArtNet Node aaron$ I'm not sure if it's a makefile issue, but just in case, here is my makefile. # $Id: Makefile 502 2009-05-09 14:20:30Z tk $ ################################################################################ # following setup taken from environment variables ################################################################################ MIOS32_PATH = ~/svn/mios32/trunk MIOS32_BIN_PATH = ~/svn/mios32/trunk/bin MIOS32_GCC_PREFIX = arm-none-eabi PROCESSOR = LPC1769 FAMILY = LPC17xx BOARD = MBHP_CORE_LPC17 LCD = universal ################################################################################ # Source Files, include paths and libraries ################################################################################ THUMB_SOURCE = app.c # (following source stubs not relevant for Cortex M3 derivatives) THUMB_AS_SOURCE = ARM_SOURCE = ARM_AS_SOURCE = C_INCLUDE = -I . A_INCLUDE = -I . LIBS = ################################################################################ # Remaining variables ################################################################################ LD_FILE = $(MIOS32_PATH)/etc/ld/$(FAMILY)/$(PROCESSOR).ld PROJECT = project DEBUG = -g OPTIMIZE = -Os CFLAGS = $(DEBUG) $(OPTIMIZE) ################################################################################ # Include source modules via additional makefiles ################################################################################ # sources of programming model include $(MIOS32_PATH)/programming_models/traditional/programming_model.mk # application specific LCD driver (selected via makefile variable) include $(MIOS32_PATH)/modules/app_lcd/$(LCD)/app_lcd.mk # common make rules include $(MIOS32_PATH)/include/makefile/common.mk Any ideas? Edited June 5, 2012 by avockley Quote Link to comment Share on other sites More sharing options...
avockley Posted June 6, 2012 Author Report Share Posted June 6, 2012 I have done some more testing, and this seems to be the case with all non-standard modules. Anything in the modules directory can't be included. I have followed all the instructions from http://www.midibox.org/dokuwiki/doku.php?id=macos_mios32_toolchain_core but it just doesn't work. Quote Link to comment Share on other sites More sharing options...
avockley Posted June 6, 2012 Author Report Share Posted June 6, 2012 Solved it. It was a makefile issue. I hadn't included the additional source modules at the end of the makefile. Quote Link to comment Share on other sites More sharing options...
TK. Posted June 6, 2012 Report Share Posted June 6, 2012 Sidenote: you can use the original makefile if you set environment variables before "make" (which executes Makefile) I'm using different "setup files" for different scenarios, e.g. this one for LPC17: export MIOS32_PATH=~/svn/mios32/trunk export MIOS32_BIN_PATH=$MIOS_PATH/bin export MIOS32_FAMILY=LPC17xx export MIOS32_PROCESSOR=LPC1769 export MIOS32_BOARD=MBHP_CORE_LPC17 export MIOS32_LCD=universal export MIOS32_GCC_PREFIX=arm-none-eabi [/code] It's stored in my user directory under the name "lpc_init", and I call it with: [code] source ~/lpc_init thereafter all makefiles automatically take over these parameters when I'm typing: make [/code] in the directory of the application. Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.