Comments on: AVR and Xcode http://davidbeckblog.com/2009/10/avr-and-xcode/ The ramblings of an obsessed programmer Sun, 25 Jul 2010 08:11:07 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Ethyl Riggsby http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-341 Ethyl Riggsby Sun, 25 Jul 2010 08:11:07 +0000 http://davidbeckblog.com/?p=130#comment-341 That was a fairly useful perception for me personally That was a fairly useful perception for me personally

]]> By: Allun http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-293 Allun Sat, 03 Jul 2010 23:33:42 +0000 http://davidbeckblog.com/?p=130#comment-293 Hi,   regarding YannickF's issue - I have solved this one and someone else might find the info useful. Here's my writeup from my personal notes: XCODE DOESN'T JUMP TO THE ERROR WHEN CLICKING ON IT IN THE BUILD WINDOW: This is because of a paths problem - the project settings make gcc compile the files in the "firmware" dir, and pipes the output back to xcode to show in the build window but gcc passes back a relative path, so unless the C files are in the same dir as the ".xcode" project file, xcode can't jump to the appropriate line in the editor. The fix for this is to a) just read the line number that is reported in the build window and manually go to that line in the editor (with line numbers turned on) b) put the xcode project file in the "firmware" dir then open the project and remove the references to the source and makefile, then re add them from their new location..... d) set the project settings so that the path for the custom build command is "./" i.e. the current directory. This does mean that you get your hex files and project files and source all in the same dir, but I am will to deal with this and be able to click on the build errors and jump to them automatically!   d) is the nest option of course, the others are just there to show what the problem is. Hi,
 
regarding YannickF’s issue – I have solved this one and someone else might find the info useful.
Here’s my writeup from my personal notes:
XCODE DOESN’T JUMP TO THE ERROR WHEN CLICKING ON IT IN THE BUILD WINDOW:
This is because of a paths problem – the project settings make gcc compile the files in the “firmware” dir, and pipes the output back to xcode to show in the build window but gcc passes back a relative path, so unless the C files are in the same dir as the “.xcode” project file, xcode can’t jump to the appropriate line in the editor.

The fix for this is to
a) just read the line number that is reported in the build window and manually go to that line in the editor (with line numbers turned on)
b) put the xcode project file in the “firmware” dir then open the project and remove the references to the source and makefile, then re add them from their new location…..
d) set the project settings so that the path for the custom build command is “./” i.e. the current directory. This does mean that you get your hex files and project files and source all in the same dir, but I am will to deal with this and be able to click on the build errors and jump to them automatically!
 
d) is the nest option of course, the others are just there to show what the problem is.

]]> By: Delicia Gord http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-275 Delicia Gord Tue, 22 Jun 2010 19:08:03 +0000 http://davidbeckblog.com/?p=130#comment-275 I am definitely bookmarking this page and sharing it with my acquaintances. You will be getting plenty of visitors to your website from me! I am definitely bookmarking this page and sharing it with my acquaintances. You will be getting plenty of visitors to your website from me!

]]> By: Jonathan http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-226 Jonathan Wed, 26 May 2010 08:40:33 +0000 http://davidbeckblog.com/?p=130#comment-226  Use this web site  http://www.engbedded.com/fusecalc/ It came up with this for our atmel -U lfuse:w:0xf9:m  Use this web site 
http://www.engbedded.com/fusecalc/
It came up with this for our atmel
-U lfuse:w:0xf9:m

]]> By: Daniel H http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-214 Daniel H Wed, 14 Apr 2010 02:18:51 +0000 http://davidbeckblog.com/?p=130#comment-214 Hi! Does anyone have any idea what should I have to replace the fuses line in order to program an ATMEL AT90S8515? FUSES      = -U hfuse:w:0xd9:m -U lfuse:w:0x24:m Thanks, Daniel Hi!
Does anyone have any idea what should I have to replace the fuses line in order to program an ATMEL AT90S8515?

FUSES      = -U hfuse:w:0xd9:m -U lfuse:w:0×24:m

Thanks,
Daniel

]]> By: Ruedi Heimlicher http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-213 Ruedi Heimlicher Wed, 07 Apr 2010 20:10:17 +0000 http://davidbeckblog.com/?p=130#comment-213 Hello I am programming my Atmega's with the USB-Programmer from www.tuxgraphics.org without any problems using the toolchain provided by CrossPack and a makefile from Tim Lott.  After upgrading to Snow Leopard and Xcode3.2, programming failed with the message that the data for the atmega328p could not be found although I hat inserted the code for it in the avrdude.conf. The problem was fixed after typing once the line avr-gcc-select-4 in the terminal. It is mentioned in the comments that gcc4 produces larger code than gcc3, but I didn't get it to work otherwise.   Hello
I am programming my Atmega’s with the USB-Programmer from http://www.tuxgraphics.org without any problems using the toolchain provided by CrossPack and a makefile from Tim Lott.  After upgrading to Snow Leopard and Xcode3.2, programming failed with the message that the data for the atmega328p could not be found although I hat inserted the code for it in the avrdude.conf. The problem was fixed after typing once the line
avr-gcc-select-4
in the terminal. It is mentioned in the comments that gcc4 produces larger code than gcc3, but I didn’t get it to work otherwise.
 

]]> By: makefile template http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-211 makefile template Sat, 03 Apr 2010 12:49:53 +0000 http://davidbeckblog.com/?p=130#comment-211 [...] columns to the right of the user area and the rows below the user area when I issue a template. ...David Beck's Blog AVR and XcodeThat isn't really necessary since Xcode has a built in template architecture. ... I didn't want to [...] [...] columns to the right of the user area and the rows below the user area when I issue a template. …David Beck's Blog AVR and XcodeThat isn't really necessary since Xcode has a built in template architecture. … I didn't want to [...]

]]> By: Michael Shimniok http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-188 Michael Shimniok Mon, 01 Mar 2010 04:48:19 +0000 http://davidbeckblog.com/?p=130#comment-188 Nice write-up, thanks for putting this info together!  Am referencing this writeup on my blog post re: programming Pololu Orangutans on the Mac. --Michael Nice write-up, thanks for putting this info together!  Am referencing this writeup on my blog post re: programming Pololu Orangutans on the Mac. –Michael

]]> By: YannickF http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-75 YannickF Mon, 02 Nov 2009 13:25:41 +0000 http://davidbeckblog.com/?p=130#comment-75 Hello   Thanks for information about AVR and Xcode. I was using AVRstudio without any problem (via Parallels desktop) but I want to use Xcode. I can now build with Xcode, but if the build fail, there isn't any information about the line (in source code) where the error appears. So, clicking on the error in build output window is not very useful (as it was in AVRstudio) The output of avr-gcc (WinAVR) version gives the line number. It seems that the CrossAVR version just indicate the error type, not the line where it occurs. How could I click on error and set the cursor on the appropriate line ? Thanks YannickF. Hello
 
Thanks for information about AVR and Xcode.
I was using AVRstudio without any problem (via Parallels desktop) but I want to use Xcode.
I can now build with Xcode, but if the build fail, there isn’t any information about the line (in source code) where the error appears. So, clicking on the error in build output window is not very useful (as it was in AVRstudio)
The output of avr-gcc (WinAVR) version gives the line number. It seems that the CrossAVR version just indicate the error type, not the line where it occurs.
How could I click on error and set the cursor on the appropriate line ?
Thanks
YannickF.

]]> By: David Beck http://davidbeckblog.com/2009/10/avr-and-xcode/comment-page-1/#comment-74 David Beck Fri, 30 Oct 2009 04:21:36 +0000 http://davidbeckblog.com/?p=130#comment-74 <p>Thanks, I will give that a try.</p> Thanks, I will give that a try.

]]>