LeafLabs Garden » User Favorites: wyzarddoc

LeafLabs Garden » User Favorites: wyzarddoc 291 A place to share, learn, and grow... en-US Fri, 22 Jan 2016 00:03:08 +0000 http://bbpress.org/?v=1.0.2 <![CDATA[Search]]> q http://forums.leaflabs.com/search.php gbulmer on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-105322 Fri, 11 Apr 2014 10:55:12 +0000 gbulmer 105322@http://forums.leaflabs.com/ nickc - "The one thing I didn't do was creat the exit() function. What's this specifically?" The <code>exit()</code> 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 <code>exit()</code> is called, but you get the idea; once a user program calls <code>exit()</code> it should never return) I'd recommend either: 1. never ever using <code>exit()</code>, and try to remove all uses until your programs link. 2. implement it yourself so it calls the libmaple error function <code>throb()</code> (in util.h), i.e. <code>void exit(int status) { throb(); }</code> (Full disclosure: I am not a member of LeafLabs staff.) feurig on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-105321 Thu, 10 Apr 2014 12:38:13 +0000 feurig 105321@http://forums.leaflabs.com/ any chance of a .deb coming out of this thread? nickc on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-105305 Sat, 29 Mar 2014 11:32:19 +0000 nickc 105305@http://forums.leaflabs.com/ 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? menecken on "Eclipse - quick start" http://forums.leaflabs.com/topic.php?id=681&page=2#post-104786 Fri, 18 Oct 2013 10:52:09 +0000 menecken 104786@http://forums.leaflabs.com/ Hi all, I succeeded in eliminating all previous problems but I'm kind lost with this one (google doesnt help, maybe due to the wrong search terms). Anyways: Help is really appreciated: Console Output is: ---------------------------------------------------- file *.o not found maple-ide-0.0.12-windowsxp32\hardware\tools\arm\bin\arm-none-eabi-size.exe: 'a.out': No such file build-targets.mk:17: recipe for target 'build/maple.bin' failed make: *** [build/maple.bin] Error 123 ---------------------------------------------------- Problem is: "recipe for target 'build/maple.bin' failed I never used GCC or Eclipse before. I'm on Windows 8. Instead of using cygwin I set my path variable to "maple-ide-0.0.12-windowsxp32\hardware\tools\arm\bin". Thank you guys so much in advance! tufane on "Eclipse - quick start" http://forums.leaflabs.com/topic.php?id=681&page=2#post-23965 Thu, 28 Mar 2013 11:17:32 +0000 tufane 23965@http://forums.leaflabs.com/ Hi mlundinse, You don't need, but in utils folder there are many programd related with unix and Linux. Therefore if you use WinAvr, it is not necessary to change some commands in makefile to make compatible with windows. Like "rm -rf" >>>> "'del /s/q" modification as mentioned previous posts. But you are right, arm tool chain must be used for compilation. mlundinse on "Eclipse - quick start" http://forums.leaflabs.com/topic.php?id=681&page=2#post-23964 Thu, 28 Mar 2013 11:13:42 +0000 mlundinse 23964@http://forums.leaflabs.com/ Hi Do you really need the WinAVR stuff, it has no use for an arm processor. Insted it looks like you can keep the dfu-util.exe where it is and simply add the directory where it lives to the system path, or simply copy dfu-util.exe into the bin folder of your arm toolchain. You have already added this path to your system in order for Eclipse make to find the arm-none-eabi-cpp compiler and other tools. Best regards Magnus tufane on "Eclipse - quick start" http://forums.leaflabs.com/topic.php?id=681&page=2#post-23962 Thu, 28 Mar 2013 11:04:33 +0000 tufane 23962@http://forums.leaflabs.com/ Hi again, UPLOAD_ram := $(SUPPORT_PATH).......(BOARD).bin -R UPLOAD_flash:= $(SUPPORT_PATH).......(BOARD).bin -R each line must be individually single line. In my post they seem dubble line. Also if you cannot upload your compilation because "Lost Device after reset, assuming prod_id was incremented by oneNo DFU capable USB device found", change "sleep 1" value to higher one like "sleep 2". tufane on "Eclipse - quick start" http://forums.leaflabs.com/topic.php?id=681&page=2#post-23961 Thu, 28 Mar 2013 10:54:07 +0000 tufane 23961@http://forums.leaflabs.com/ Hi, I've just bought Maple_R5 and tried to compile using Eclipse according to given information by forum members and wiki page. Finally I've successfully done it in Win7 64 bit. I have to tell you, I didn't know anything about Linux or Unix based systems. But I made some google search and I found followings which must be installed to Windows system. 1- WinAvr (Actually you need only "x:\WinAVR-20100110\utils\bin" directory and must be added to "System varibles PATH" or install WinAvr which sets PATH automatically) 2- Python33 >>> <a href="http://www.python.org/download" rel="nofollow">http://www.python.org/download</a> "Python 3.3.0 Windows X86-64 MSI Installer" (install it) 3- pyserial 2.6 (serial port enabler for pyhton) >>> pypi.python.org/pypi/pyserial (install it as described in the web page) 4- Eclipse "eclipse IDE for C/C++ developers" >>> <a href="http://www.eclipse.org/downloads" rel="nofollow">http://www.eclipse.org/downloads</a> 5- Apply given information "wiki.leaflabs.com/Edit_sketches_with_Eclipse" 6- Change some lines in libmaple\support\scripts\reset.py; #!/usr/bin/env python >>>> #!x:/Python33/python.exe (where pyhton33 installed) import _winreg as reg >>>> import winreg as reg x: drive that has Python33 folder 7- Change Makefile; --------------------------------------- # Target upload commands # USB ID for DFU upload -- FIXME: do something smarter with this BOARD_USB_VENDOR_ID := 1EAF BOARD_USB_PRODUCT_ID := 0003 UPLOAD_ram := $(SUPPORT_PATH)/scripts/reset.py && \ sleep 1 && \ $(DFU) -a0 -d $(BOARD_USB_VENDOR_ID):$(BOARD_USB_PRODUCT_ID) -D $(BUILD_PATH)/$(BOARD).bin -R UPLOAD_flash := $(SUPPORT_PATH)/scripts/reset.py && \ sleep 1 && \ $(DFU) -a1 -d $(BOARD_USB_VENDOR_ID):$(BOARD_USB_PRODUCT_ID) -D $(BUILD_PATH)/$(BOARD).bin -R # Conditionally upload to whatever the last build was install: INSTALL_TARGET = $(shell cat $(BUILD_PATH)/build-type 2>/dev/null) install: $(BUILD_PATH)/$(BOARD).bin @echo "Install target:" $(INSTALL_TARGET) $(UPLOAD_$(INSTALL_TARGET)) ------------------------------- to this one; ------------------------------- # Target upload commands # USB ID for DFU upload -- FIXME: do something smarter with this BOARD_USB_VENDOR_ID := 1EAF BOARD_USB_PRODUCT_ID := 0003 UPLOAD_ram := $(SUPPORT_PATH)/scripts/reset.py && sleep 1 && $(DFU) -a0 -d $(BOARD_USB_VENDOR_ID):$(BOARD_USB_PRODUCT_ID) -D $(BUILD_PATH)/$(BOARD).bin -R UPLOAD_flash := $(SUPPORT_PATH)/scripts/reset.py && sleep 2 && $(DFU) -a1 -d $(BOARD_USB_VENDOR_ID):$(BOARD_USB_PRODUCT_ID) -D $(BUILD_PATH)/$(BOARD).bin -R INSTALL_TARGET = $(shell cat $(BUILD_PATH)/build-type 2>/dev/null) # Conditionally upload to whatever the last build was # install: INSTALL_TARGET = $(shell cat $(BUILD_PATH)/build-type 2>/dev/null) # $(BUILD_PATH)/$(BOARD).bin install: @echo "Install target:" $(INSTALL_TARGET) $(UPLOAD_$(INSTALL_TARGET)) ------------------------------- 8- Copy "dfu-util.exe" from maple-ide directory to "x:\WinAVR-20100110\utils\bin" x: drive that has WinAvr folder 9- Optionally modify build-target.mk which does not report object file sizes and give more information about compilation; # @echo " " # @echo "Object file sizes:" # @find $(BUILD_PATH) -name *.o | xargs $(SIZE) -t > $(BUILD_PATH)/$(BOARD).sizes # @cat $(BUILD_PATH)/$(BOARD).sizes $(BUILD_PATH)/$(BOARD).bin: $(BUILD_PATH)/$(BOARD).elf $(SILENT_OBJCOPY) $(OBJCOPY) -v -Obinary $(BUILD_PATH)/$(BOARD).elf $@ 1>/dev/null $(SILENT_DISAS) $(DISAS) -d $(BUILD_PATH)/$(BOARD).elf > $(BUILD_PATH)/$(BOARD).disas @echo " " @echo "Final Size:" @$(SIZE) -A $< @echo "Build Successfull." @echo $(MEMORY_TARGET) > $(BUILD_PATH)/build-type MSG_INFO: @echo "================================================================================" @echo "" @echo " Previous Build :" $(PREV_BUILD_TYPE) @echo " Build info :" @echo " BOARD: :" $(BOARD) @echo " MCU: :" $(MCU) @echo " MEMORY_TARGET: :" $(MEMORY_TARGET) @echo " USB_PRODUCT_ID :" $(BOARD_USB_PRODUCT_ID) @echo " USB_VENDOR_ID :" $(BOARD_USB_VENDOR_ID) @echo "" @echo " See 'make help' for all possible targets" @echo "" @echo "================================================================================" @echo "" Finally you can have alternative IDE for development. Best wishes..... mconners on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-20394 Sun, 21 Oct 2012 19:28:41 +0000 mconners 20394@http://forums.leaflabs.com/ 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 ahunter10@gmail.com on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-20393 Sun, 21 Oct 2012 19:16:01 +0000 ahunter10@gmail.com 20393@http://forums.leaflabs.com/ 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. mconners on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-20391 Sun, 21 Oct 2012 12:56:54 +0000 mconners 20391@http://forums.leaflabs.com/ 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 mconners on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-20368 Fri, 19 Oct 2012 13:57:03 +0000 mconners 20368@http://forums.leaflabs.com/ 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 <a href="http://www.kunen.org/uC/gnu_tool.html">instructions</a> 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 mconners on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-20346 Thu, 18 Oct 2012 21:29:58 +0000 mconners 20346@http://forums.leaflabs.com/ 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 ahunter10@gmail.com on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-20320 Tue, 16 Oct 2012 21:03:25 +0000 ahunter10@gmail.com 20320@http://forums.leaflabs.com/ 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 $ feurig on "Compiling for maple on raspberry pi" http://forums.leaflabs.com/topic.php?id=9201#post-20309 Tue, 16 Oct 2012 00:11:01 +0000 feurig 20309@http://forums.leaflabs.com/ 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.