EsotericLabs Posted June 18, 2012 Report Share Posted June 18, 2012 Hello, I'm new to Midibox, but i love the concept already. I'm putting together my firts LPC17 core but I got stuck setting up the programming environment. I'm on Mac with Lion OSX and XCode 4.3. I installed SDCC an GPUTILS with Mac Ports as in the Docu Wiki. I set up the environment variables as in http://www.midibox.org/dokuwiki/doku.php?id=macos_mios32_toolchain_core, I put the skeleton project in XCode (with only an app target), but when I build, Xcode does not see the environment variables, and ends with an error. What am I doing wrong? Thank you for helping me out. Quote Link to comment Share on other sites More sharing options...
TK. Posted June 18, 2012 Report Share Posted June 18, 2012 Hi, for LPC17 you need a different, gcc based toolchain - it's very different from the PIC setup. I'm unsure if this works in Xcode, normally I execute the Makefile directly with the command shell. A link to the precompiled toolchain + additional informations can be found here: http://www.ucapps.de/mios32_c.html (follow the Mac Link) Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
EsotericLabs Posted June 18, 2012 Author Report Share Posted June 18, 2012 Thank you very much Thorsten, I'm honored to hear from you in person. I had missed out the tool chain download, but I' m not sure it's downloaded correctly. It stops at 19.9m but says it has more. And then unzipping gives an error. Any other server to try? And if I figure out how to set up with Lion an Xcode, I will post it. Quote Link to comment Share on other sites More sharing options...
ultra Posted June 19, 2012 Report Share Posted June 19, 2012 plz do! i'm using xcode and make -s from the terminal. i'd love to see my errors highlighted among all those warnings that i ignore for now and will get to fixing later. :P ultra Quote Link to comment Share on other sites More sharing options...
EsotericLabs Posted June 19, 2012 Author Report Share Posted June 19, 2012 (edited) I will sure try, but judging from your status, this won't be easy? At my work, I managed to download the toolchain package. I'll try asap. Cannot I just put a make -s statement in the makefile for xcode? Edited June 19, 2012 by Martijn Quote Link to comment Share on other sites More sharing options...
ultra Posted June 19, 2012 Report Share Posted June 19, 2012 I'm kinda new to Mac and I haven't used xcode as anything but a basic editor. I have programmer's status, but my understanding of the toolchain isn't the greatest so I just follow the wiki instructions. ultra Quote Link to comment Share on other sites More sharing options...
EsotericLabs Posted June 19, 2012 Author Report Share Posted June 19, 2012 For me, Xcode is also new. I used to program in other environments. I now got to the point where I can use XCode for editing and compile from the terminal with make -s. I needed the toolchain and the command line tools (Xcode->Preferences->Downloads->Command Line Tools->install). But then I could compile 001_forwarding_midi without any problems. I now have a .hex file, that needs to be converted to .syx (once I finish the core), right? But I did not get xcode to properly understand the environment variables. It says /Users/martijneskinasi/Library/Developer/Xcode/DerivedData/MIOS_Skeleton-fbpmxsbgweoachcyuzoxednrxabu/Build/Intermediates/MIOS Skeleton.build/Debug/SkeletonApp.build/Script-E3BCCAE4158FB69A006D012B.sh: line 7: cd: /Users/martijneskinasi/Documents/Studio/XCode/MIOS: No such file or directory Makefile:50: /programming_models/traditional/programming_model.mk: No such file or directory Makefile:53: /modules/app_lcd//app_lcd.mk: No such file or directory Makefile:56: /include/makefile/common.mk: No such file or directory make: *** No rule to make target `/include/makefile/common.mk'. Stop. $MIOS32_PATH is properly set up in ~/.profile and is available in the terminal. I do not understand why a makefile should be a target. Quote Link to comment Share on other sites More sharing options...
ultra Posted June 19, 2012 Report Share Posted June 19, 2012 I'll try it later tonight and let you know what happens. The .hex itself is what you upload to the core. ultra Quote Link to comment Share on other sites More sharing options...
TK. Posted June 20, 2012 Report Share Posted June 20, 2012 I now got to the point where I can use XCode for editing and compile from the terminal with make -s. I needed the toolchain and the command line tools (Xcode->Preferences->Downloads->Command Line Tools->install). But then I could compile 001_forwarding_midi without any problems. I now have a .hex file, that needs to be converted to .syx (once I finish the core), right? No - you can upload the .hex file directly to the core by using MIOS Studio. A .syx file conversion is neither required, nor supported for MIOS32 (since the approach via MIOS Studio is more robust) Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
EsotericLabs Posted June 21, 2012 Author Report Share Posted June 21, 2012 No - you can upload the .hex file directly to the core by using MIOS Studio. A .syx file conversion is neither required, nor supported for MIOS32 (since the approach via MIOS Studio is more robust) Best Regards, Thorsten. Thank you! That makes life easier again. The Reichelt parts should arrive any moment now. I'm excited to put it all together and upload a .hex.. Quote Link to comment Share on other sites More sharing options...
EsotericLabs Posted June 21, 2012 Author Report Share Posted June 21, 2012 Hello Ultra, I found the trick in Xcode 4.3: see Enjoy! 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.