Compiling for maple on raspberry pi

LeafLabs Garden » Support » Maple Hardware Support

Compiling for maple on raspberry pi

(11 posts) (5 voices)

Started 3 years ago by ahunter10@gmail.com
Latest reply from gbulmer

ahunter10@gmail.com
Member

Hello,

I am trying to compile code for the maple on the raspberry pi, running their standard OS image. I am using the libmaple command line toolchain. Has anyone been successful with this?

I am getting an error:
/home/pi/libmaple/arm/bin/arm-none-eabi-gcc: 1: /home/pi/libmaple/arm/bin/arm-none-eabi-gcc: Syntax error: "(" unexpected

I think this may be caused by using an incorrect compiler. Since i'm running on an ARM, I think I should be able to use the native version of gcc.

Any suggestions for getting this working?

Posted 3 years ago #
feurig
Member

you may want to do gcc --target-help and see if the cortex-m3 is supported. After that you could give us a little more to go on like in what file the syntax error occurs and which version of libmaple you are using.

Posted 3 years ago #
ahunter10@gmail.com
Member

thanks for the help!

When I run "gcc --target-help", cortex-m3 is listed under the heading "Known ARM CPUs (for use with the -mcpu= and -mtune= options)"

I am using the latest version of libmaple, downloaded from the github server yesterday.

I am trying to compile the example file included with libmaple. I get the same error no matter what I compile. I get an error on make clean...

pi@raspberrypi ~/libmaple $ make clean
/home/pi/libmaple/arm/bin/arm-none-eabi-gcc: 1: /home/pi/libmaple/arm/bin/arm-none-eabi-gcc: Syntax error: "(" unexpected
rm -rf build
pi@raspberrypi ~/libmaple $

Posted 3 years ago #
mconners
Member

It seems like you are not using the native compiler, given that the error message produced points to /home/pi/libmaple/arm/bin/arm-none-eabi-gcc, so I'm guessing that you downloaded the intel version from somewhere, unless you cross compiled it yourself.

I went into libmaple/support/make/build-rules.mk and changed all the instances of arm-none-eabi- to blanks leaving gcc,g++, ld -v, etc...

I then changed directory to libmaple and ran make again, it started compile several of the files using the gcc distributed with the debian install for the pi.

This was the output:
[CC] ./libmaple/adc.c
[CC] ./libmaple/dac.c
[CC] ./libmaple/dma.c
[CC] ./libmaple/exti.c
[CC] ./libmaple/flash.c
[CC] ./libmaple/gpio.c
[CC] ./libmaple/iwdg.c
[CC] ./libmaple/nvic.c
[CC] ./libmaple/pwr.c
[CC] ./libmaple/rcc.c
[CC] ./libmaple/spi.c
[CC] ./libmaple/systick.c
[CC] ./libmaple/timer.c
libmaple/timer.c:318:20: error: conflicting types for 'enable_irq'
libmaple/timer.c:41:20: note: previous declaration of 'enable_irq' was here
libmaple/timer.c:41:20: error: 'enable_irq' used but never defined [-Werror]
cc1: all warnings being treated as errors
make: *** [build/./libmaple/timer.o] Error 1

I haven't resolved those issues yet, but maybe you can start there, it seems closer than you were.

Mike

Posted 3 years ago #
mconners
Member

I was able to get through the above issues. It turns out that the declaration of enable_irq had the second parameter defined as uint, while in the actual code for the function/method it was defined as something else. Once I made them the same timer.c compiled fine.

I then ran into the next problem, the wirish code didn't want to compile, complaining about lack of declaration of caddr_t and size_t. I think that is because the gcc distributed with debian wheezy doesn't contain newlib as part of the distribution.

Although it seems odd, I may follow these instructions to make an arm-none-gnueabi cross compiler for baremetal compilations on the ras-pi.

Unless of course some enterprising person beats me to it and links it here, or figures out how to get wirish to compile on the pi with the standard compiler.

Mike

Posted 3 years ago #
mconners
Member

OK. I was able to follow the instructions linked above and made the arm-none-eabi gcc package on the pi. From that point on instructions for the the maple command line tools work as described.

I may do some maple development on the pi.

Mike

Posted 3 years ago #
ahunter10@gmail.com
Member

Wow, thanks for the tip. I was working through the compilation issues, but had some problems with the linker I wasn't able to solve. I'll check out the link.

Posted 3 years ago #
mconners
Member

One more comment on this and I'm done :-)

I had to install several library-dev packages, you'll get the error when compiling gcc, it's easy to figure out.

I had to configure newlib as follows (and I upgraded to the latest versions of everything):

../../src/newlib-1.20.0/configure --target=arm-none-eabi --prefix=$MYTOOLS --enable-interwork --disable-newlib-supplied-syscalls

the --disable-newlib-supplied-syscalls was important because of conflicts in several functions, and one other thing I needed to do was create an exit() function.

I had to install dfu-utils and the python serial package, but after that I coped main.cpp.example to main.cpp and did make install and all went well.

There is quite a bit of time waiting for compiles to finish, but its not hard, good luck.

Mike

Posted 3 years ago #
nickc
Member

I have the example building following mconners instructions, get a clean build and can upload with make install, but the code doesn't run.

"the --disable-newlib-supplied-syscalls was important because of conflicts in several functions, and one other thing I needed to do was create an exit() function."

The one thing I didn't do was creat the exit() function. What's this specifically?

Posted 1 year ago #
feurig
Member

any chance of a .deb coming out of this thread?

Posted 1 year ago #
gbulmer
Moderator

nickc - "The one thing I didn't do was creat the exit() function. What's this specifically?"

The exit() function terminates the program. On a machine with an Operating System, it is the last thing your program does. (Edit: strictly, there are 'hooks' which might run after exit() is called, but you get the idea; once a user program calls exit() it should never return)

I'd recommend either:
1. never ever using exit(), and try to remove all uses until your programs link.
2. implement it yourself so it calls the libmaple error function throb() (in util.h), i.e.
void exit(int status) { throb(); }

(Full disclosure: I am not a member of LeafLabs staff.)

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.