Go Down

Topic: Arduino on Xcode Project — Official Thread (Read 159835 times) previous topic - next topic

avenue33

#495
Nov 05, 2013, 10:08 pm Last Edit: Nov 05, 2013, 10:12 pm by avenue33 Reason: 1
Arduino 1.5.x is still in beta, hence some issues with the libraries.

By default, embedXcode compiles all the libraries. It seems the latest release of Arduino includes libraries with issues.

Proceed as follow:
  • Create a new embedXcode project.

  • Edit the makefile with

Code: [Select]
APP_LIBS_LIST = 0
USER_LIBS_LIST = 0

  • Launch Build


Please refer to chapter 4 Build and Upload the Project section 2 Manage the Libraries for Compilation for more details.

As I don't own an Arduino Due, I can't conduct the tests myself but the issue has been reported on other boards.

colinbes

Thanks that helped.

I still had to manually setup the project after creating a new project, making changes to makefile and first build as the automatic updates didn't happen.

Otherwise it's compiling and executing on target.

I am still battling with differences between options of 'ALL' and 'BUILD' as both seem to compile, download to target and execute code - will play around a bit more.

~Colin


Arduino 1.5.x is still in beta, hence some issues with the libraries.

By default, embedXcode compiles all the libraries. It seems the latest release of Arduino includes libraries with issues.

Proceed as follow:
  • Create a new embedXcode project.

  • Edit the makefile with

Code: [Select]
APP_LIBS_LIST = 0
USER_LIBS_LIST = 0

  • Launch Build


Please refer to chapter 4 Build and Upload the Project section 2 Manage the Libraries for Compilation for more details.

As I don't own an Arduino Due, I can't conduct the tests myself but the issue has been reported on other boards.

avenue33

Strange you have to battle with manual changes on the makefiles...

It should work fine right away out-of-the-box.

colinbes

Yes, it is a bit strange. I even tried creating a new project seeing as the automated procedure is a once only affair.

I created a new project, manually edited lib lines in make file and then click the run icon to build.

Build was successful, but .ino file was still associated as a plain text file, plus I had to set up other items as outlined in manual procedure.

Colin

colinbes

I was wondering if my embedXcode/xcode setup is correct. I am running Arduino 1.5x, Xcode 5.01 and embedXcode 1.11 on OSX Mavericks as it is building/downloading very slowly (can take a minute to compile for small code base).

When viewing navigator I notice that under "Utilities" and "Product" I have embedXcode_prepare and "Index" showing in red - is this correct/okay?

As reported in my earlier post that I had to manually setup Xcode as the automated procedure doesn't work so am concerned I have not configured my setup correctly.

Please see attached showing the navigator.

~Colin

avenue33

#500
Nov 08, 2013, 09:33 pm Last Edit: Nov 08, 2013, 09:44 pm by avenue33 Reason: 1

When viewing navigator I notice that under "Utilities" and "Product" I have embedXcode_prepare and "Index" showing in red - is this correct/okay?


The embedXcode_prepare program prepares the project and runs only once, during the first compilation. It is deleted after.

The Index target is a proxy target used solely for code-sense.

Please find excerpts from the User Manual.

avenue33

#501
Nov 08, 2013, 09:48 pm Last Edit: Nov 11, 2013, 04:36 pm by avenue33 Reason: 1
Please find a new release of embedXcode.

  • embedXcode  • Nov 08, 2013 release 112 • Stability enhancement for Digispark
  • embedXcode+ • Nov 08, 2013 release 112 • Support for Protostack 28-pin AVR board, USBtinyISP and USBASP programmers


Mac OS X 10.9 Mavericks allows to read the User Manual as an e-book on a Mac.

embedXcode+ supports new boards and programmers: Adafruit Atmega32u4 Breakout and Protostack 28-pin AVR boards, Adafruit USBtinyISP and Protostack USBASP programmers.

Happy coding :)

Download

jimaobian

Hi,
I've just updated to embedXcode+113 in Mavericks. However when I try to create a new project ,set the USER_LIBS_LIST = 0, and build it. After successfully compile the project, all the files in the left project navigator disappear except the project file. If I click this project file ,an error diagram pops up "The file couldn't be opened".
If I remove all the user library away, this problem will no longer exist. However if there is any library in the library folder, this problem remains.
I turn back to the ver.110. There is no such problem in it.

avenue33


Hi,
I've just updated to embedXcode+113 in Mavericks. However when I try to create a new project ,set the USER_LIBS_LIST = 0, and build it. After successfully compile the project, all the files in the left project navigator disappear except the project file. If I click this project file ,an error diagram pops up "The file couldn't be opened".
If I remove all the user library away, this problem will no longer exist. However if there is any library in the library folder, this problem remains.
I turn back to the ver.110. There is no such problem in it.


The utility in charge of preparing the project hasn't changed between release 110 and 113. The issue you're reporting is due to non-standard names for the folders and files of the user library --like spaces, +, ...

jimaobian

I've dealt with this problem by moving the incompatible user library before. However at this time, whatever user library I put into the library folder, the project will be lost.
Since there is no such problem in ver.110 ,I can maintain use this version. But can you figure out the reason why?

avenue33


I've dealt with this problem by moving the incompatible user library before. However at this time, whatever user library I put into the library folder, the project will be lost.
Since there is no such problem in ver.110 ,I can maintain use this version. But can you figure out the reason why?


With so few elements, it is just impossible.

jimaobian

I resolved it by uninstalling it using the app under the document.

PS:
Perhaps you lost an 's' in the "document" folder. A new folder named "Document" is in my home folder after installation.


Namaan

Hi,

I haven't read all the thread, and the search function turns up nothing. I hope this question hasn't been asked already.

I have to small issues using embedXcode:

- I develop an RS-485 communication for my board (duemilanove). So naturally, I have an RS-485/USB converter plugged into my MAC. Unfortunately, wen the converter is plugged, I can't upload code to my board. embedXcode thinks the converter is my board. So I have to unplug, compile, upload, re-plug the RS-485 converter. That, in turn breaks the connection with my MAC application that I use to communicate with the board… and so on.
Question: how do I tell embedXcode which port to use to communicate with the board?

- I would like to test several boards (uno with ATMEGA, due with ARM processor and chip kit with PIC32). How do I add targets such as "ALL for uno", "ALL for due", and "ALL for chipkit"?

Thank you for reading me.

avenue33


I have to small issues using embedXcode:

- I develop an RS-485 communication for my board (duemilanove). So naturally, I have an RS-485/USB converter plugged into my MAC. Unfortunately, wen the converter is plugged, I can't upload code to my board. embedXcode thinks the converter is my board. So I have to unplug, compile, upload, re-plug the RS-485 converter. That, in turn breaks the connection with my MAC application that I use to communicate with the board… and so on.
Question: how do I tell embedXcode which port to use to communicate with the board?


On the main makefile, uncomment the line with [font=Courier]BOARD_PORT[/font] and set the exact USB port, as [font=Courier]/dev/tty.usbmodem1421[/font] in the example

Code: [Select]
# BOARD_PORT is optional
# If not defined, BOARD_PORT = /dev/tty.usb* (default)
#
BOARD_PORT = /dev/tty.usbmodem1421


- I would like to test several boards (uno with ATMEGA, due with ARM processor and chip kit with PIC32). How do I add targets such as "ALL for uno", "ALL for due", and "ALL for chipkit"?

Thank you for reading me.


Just select the board according to chapter 3 Use the Project section 3 Manage the Code for Multiple Plaforms sub-section 1 Change the Board of the User Manual.

Go Up