First of all, thanks for replying!! I thought I was lost in desperate loliness... :)
I have given a look at the page proposed by Alex and I have to say it's the same procedure I have followed. I don't think the problem is in the compiler, it seems something is not right with linking, as you pointed out, but I can't get to make it right. And...no, I really DO NEED to use something just like sercom; I need to fully exploit the capabilities of the e-puck robot, so... I tried the Webots way, as suggested by Olivier, and...it WORKED!!! GREAT!!! I just had to export the WEBOTS_HOME variable as requested by the makefile, as I learned from the first output I had: pic30-elf-gcc -Wall -c -mcpu=30F6014A -I/transfer/e-puck/library -I/transfer/e-puck/std_microchip/include -I/transfer/e-puck/std_microchip/support/h firmware.c -o firmware.o firmware.c:4:23: error: p30f6014A.h: No such file or directory firmware.c:13:37: error: motor_led/e_epuck_ports.h: No such file or directory firmware.c:14:35: error: motor_led/e_init_port.h: No such file or directory firmware.c:15:47: error: motor_led/advance_one_timer/e_led.h: No such file or directory firmware.c:16:50: error: motor_led/advance_one_timer/e_motors.h: No such file or directory firmware.c:17:30: error: uart/e_uart_char.h: No such file or directory firmware.c:18:43: error: a_d/advance_ad_scan/e_ad_conv.h: No such file or directory firmware.c:19:39: error: a_d/advance_ad_scan/e_acc.h: No such file or directory firmware.c:20:40: error: a_d/advance_ad_scan/e_prox.h: No such file or directory firmware.c:21:41: error: a_d/advance_ad_scan/e_micro.h: No such file or directory firmware.c:22:50: error: motor_led/advance_one_timer/e_agenda.h: No such file or directory firmware.c:23:43: error: camera/fast_2_timer/e_po3030k.h: No such file or directory firmware.c:24:27: error: codec/e_sound.h: No such file or directory firmware.c:27:32: error: I2C/e_I2C_protocol.h: No such file or directory firmware.c:31:58: error: motor_led/advance_one_timer/e_remote_control.h: No such file or directory firmware.c:42: error: 'MIC_SAMP_NB' undeclared here (not in a function) firmware.c: In function 'calibrate_ir_sensors': firmware.c:49: warning: implicit declaration of function 'e_set_led' firmware.c:51: warning: implicit declaration of function 'e_led_clear' firmware.c:59: warning: implicit declaration of function 'e_get_prox' [...cut...] make: *** [firmware.o] Error 1 THANKS A LOT!! I think I could now follow some tracks backwards and get piklab to work too. It would be helpful to me, I'll let you know... Bye (A whole lot happier) Davide :))) > Date: Mon, 18 Feb 2008 22:19:13 +0100 > From: Olivier Michel <[EMAIL PROTECTED]> > Subject: Re: [E-puck-user] problems compiling with piklab > To: [email protected] > Cc: Alexandre Campo <[EMAIL PROTECTED]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, > > Webots comes with a free gcc cross-compiler properly compiled and > configured for Windows, Linux and Mac OS X. You could easily compile the > sercom on all three platform (you can even use the Webots built-in > editor and the cross-compile button). All this comes for free with the > demo version of Webots which you can download here: > http://www.cyberbotics.com/products/webots/download.html (choose either > Linux, Windows or Mac OS X). > After installation, go to the Webots / transfer / e-puck / firmware > folder and type make, it will recompile a variation of the sercom (named > firmware.c) and produce the corresponding firmware.hex file. > > Let me know if you need any assistance in using this cross-compiler. > > -Olivier > > Alexandre Campo wrote: >> Hi Davide, >> >> to get the cross compiler, you should be just fine if you follow >> the instructions here : >> http://iridia.ulb.ac.be/~e-puck/wiki/tiki-index.php?page=Cross+compiling+for+dsPic >> >> This gives you the cross compiler, working and thoroughly tested. >> For compiling sercom under linux, I have to say I never tried, but >> I think this is too ambitious :-) >> why not trying simple programs like leds, motors, and so on ? >> >> For your compilation problem, it seems that you are just missing a >> file, or that a file is not in the right place. >> You can change it's location where it is included / needed. >> >> >> Cheers, >> alex. >> >> >> >> >> On Mon, 18 Feb 2008 19:00:51 +0100 >> Davide Donetto <[EMAIL PROTECTED]> wrote: >> >> >>> Hi, >>> I'm a PhD student working at ISTC-CNR in Rome. I'm trying to compile >>> an .hex file for the e-puck robot under linux but I've found it more >>> difficult than I thought: >>> >>> I've compiled piklab and then gcc, binutils and support packages using >>> deb templates, following the instructions on this page: >>> http://www.nabble.com/Debian-templates-for-dsPIC-build-toolchain-3.01-td12265748.html >>> >>> My program is just a variation of sercom, so I used the same sources >>> specified in its project file, downloading the library (version >>> 1_1_1l) from the e-puck website. >>> >>> When I try to build the project it always stops saying: >>> Assembler messages: >>> Error: can't open epuck/library/motor_led/e_init_port.s for reading >>> >>> ...of course the file is not there but in the epuck dir. >>> >>> Can somebody help me, please?!? >>> Thanks >>> >>> Davide >>> >>> >>> _______________________________________________ E-puck-user mailing list [email protected] https://mail.gna.org/listinfo/e-puck-user
