Missing Makefile

MIOS programming (C)
1

I have decide to revise my digital piano to include the Dio-Matrix module and to make some minor changes to the program.  The first problem was a makefile problem which related to a non existing LCD file.  I decided to update the SVN repository.  This caused another problem; the makefile has been deleted!

 

I am using a modified Fast Scan Matrix in the examples in the MIOS Toolchain.

 

I do not really understand this aspect of programming, although I have a small knowledge of MIOS C programming.

 

Can anyone help with the missing makefile?

 

Thanks Robin

2

Hi Robin,

I don’t know if I can help you but you will have to give the group more information. Things like the path that the missing makefile is located and what project you are trying to build. There are many makefiles in the system, most found in the apps/controllers directories. It is these makefiles that include separate .mk files in other directories that contain the file dependency information for the specific functions.

Pete

3

I know I spoke to soon. You did give the project information. I haven’t updated my trunk directory for a few months.

I did go to the repository and viewed the Makefile with the html display function. On the top 2 rows of revision 1424 of the Makefile it shows a message that I copied and is shown below.

Warning: array_key_exists() [function.array-key-exists]: The first argument should be either a string or an integer in /home/midibox/public_html/websvn/include/svnlook.php on line 643

I don’t know where this message came from but maybe this is part of the problem. I’m fairly sure it doesn’t belong in the Makefile.

Pete

4

Thanks for the reply

 

I have somehow manage to restore a makefile. I am back to my first problem.  Here is the result when trying to compile

 

E:\mios32\trunk\apps\examples\fastscan_button_matrix_16x16>make

Makefile:51: /E/mios32/trunk/modules/app_lcd/clcd/app_lcd.mk: No such file or di

rectory

make: *** No rule to make target `/E/mios32/trunk/modules/app_lcd/clcd/app_lcd.m

k’.  Stop.

 

E:\mios32\trunk\apps\examples\fastscan_button_matrix_16x16>

 

I have looked at the LCD module in the toolchain and it shows an additional directory “universal” in the path.

 

Robin

5

Do you have all the environment variables set on your system right before you do the make?

There should be one that reads “MIOS_32_LCD=universal”. It looks like you have it set to “clcd” which is a directory that I can’t find in the repository.

Pete

6

Pete 

 

When the program was developed by TK the"clcd" was valid, (Version 1104)

 

The toolchain shows conflicts and the current attempts using MAKE yield:-

 

Robin 

 

PS 

E:\mios32\trunk\apps\examples\fastscan_button_matrix_16x16>make

rm -f project.hex

e:/mios32_toolchain/bin/../lib/gcc/arm-none-eabi/4.5.1/../../../../arm-none-eabi

/bin/ld.exe: crt0.o: No such file: No such file or directory

collect2: ld returned 1 exit status

make: *** [project_build/project.elf] Error 1

7

I just went to my sandbox and did a make and this was what it did:

C:\Users\Pete\Documents\MidiDesignProjects\Midio128V3\trunk\apps\examples\fastsc

an_button_matrix_16x16>make

rm -f project.hex

Creating object file for app.c

Creating object file for main.c

Creating object file for strtol.c

Creating object file for tasks.c

Creating object file for list.c

Creating object file for queue.c

Creating object file for timers.c

Creating object file for port.c

Creating object file for umm_malloc.c

Creating object file for startup_LPC17xx.c

Creating object file for mios32_srio.c

Creating object file for mios32_din.c

Creating object file for mios32_dout.c

Creating object file for mios32_enc.c

Creating object file for mios32_lcd.c

Creating object file for mios32_midi.c

Creating object file for mios32_osc.c

Creating object file for mios32_com.c

Creating object file for mios32_uart_midi.c

Creating object file for mios32_iic_midi.c

Creating object file for mios32_iic_bs.c

Creating object file for mios32_mf.c

Creating object file for mios32_sdcard.c

Creating object file for mios32_enc28j60.c

Creating object file for mios32_bsl.c

Creating object file for mios32_sys.c

Creating object file for mios32_irq.c

Creating object file for mios32_spi.c

Creating object file for mios32_i2s.c

Creating object file for mios32_board.c

Creating object file for mios32_timer.c

Creating object file for mios32_stopwatch.c

Creating object file for mios32_delay.c

Creating object file for mios32_ain.c

Creating object file for mios32_usb.c

Creating object file for mios32_usb_midi.c

Creating object file for mios32_usb_com.c

Creating object file for mios32_uart.c

Creating object file for mios32_iic.c

Creating object file for printf-stdarg.c

Creating object file for core_cm3.c

Creating object file for usbhw_lpc.c

Creating object file for usbcontrol.c

Creating object file for usbstdreq.c

Creating object file for usbinit.c

Creating object file for app_lcd.c

Creating object file for glcd_font_big.c

Creating object file for glcd_font_small.c

Creating object file for glcd_font_normal.c

Creating object file for glcd_font_knob_icons.c

Creating object file for glcd_font_meter_icons_h.c

Creating object file for glcd_font_meter_icons_v.c

Creating object file for mini_cpp.cpp

Creating object file for freertos_heap.cpp

Application successfully built for:

Processor: LPC1769

Family: LPC17xx

Board: MBHP_CORE_LPC17

LCD: universal

arm-none-eabi-size project_build/project.elf

text data bss dec hex filename

41190 32 13752 54974 d6be project_build/project.elf

10000000 B __ram_start

10000db8 ? __ram_end

2007c000 D __ram_start_ahb

2007e920 B __ram_end_ahb

C:\Users\Pete\Documents\MidiDesignProjects\Midio128V3\trunk\apps\examples\fastsc

an_button_matrix_16x16>

____________________________________________________________________________

My sandbox was made from a version about 2 months ago (I think).

What I think your problem is that you have a very old sandbox with old software that’s not compatible with how things are done today. It may also be because of other tools you have loaded which conflict with the MidiBox tools.

What I suggest is for you to create a new TRUNK that is at the current level of revision of the repository. When validate your toolchain and environment is properly setup. This is the link I used for WINDOWS http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core

Only merge your changes into the directory after you verified you can compile the current version in your sandbox. I don’t know what else to tell you. Maybe someone else should get involved here.

Pete

8

Thanks again Pete

 

I took up your suggestion to rebuild the system.  I have a 2nd PC where I attempted to build the toolchain etc.

 

I failed !  However in parallel I examined the environmental variables at each stage and actually found some errors in PC no 1.  This is difficult to understand.  I had used PC No 1 a few weeks ago to make a simple code change and then suddenly it failed to work.

 

I am up and running now.

 

Robin