[En-Nut-Discussion] Ethernut 2.1 and AVR studio
Thiago A. Corrêa
thiago.correa at gmail.com
Sun Jan 18 18:55:36 CET 2009
I would suggest that instead you build Nut/OS using the Nut
Configurator, then build your app with AVRStudio.
You can set AVR Studio to use an external makefile, the problem is
that you usually have to store your Nut enabled makefile in a
different folder (say build) because AVR Studio has the bad habit of
overwritting it with it's own.
Then you should be able to debug your code with AVR Studio and
JTAGICE MkII as you normally would.
That's what I do when I really need to use the debugger.
Also, make sure to your compiler to avr-gccdbg in Nut Configurator
if you want to debug the OS and/or use a makefile like those in the
Apps that inherits those settings from the Makedefs.avr-gccdbg and
friends in the main distribution of ethernut.
Thiago A. Correa
On Sat, Jan 17, 2009 at 6:39 PM, Xeeon <mbabik82 at gmail.com> wrote:
> Harald Kipp wrote:
>> You're obviously not using nutapp/http/Makefile. In your compiler call
>> at least option -DETHERNUT2 seems to be missing. This is required for
>> both, building the system libraries and the application.
>> Btw. don't try Nut/OS in the AVR Studio Simulator. I'm almost sure that
>> this will not work.
> Thanks a lot. But I am sure I use -DETHERNUT2 and also -D__HARDWARE_ARCH__,
> -D_MCU_enhaced. Also all libraries paths are set (correctly, I hope). I'll
> keep playing with that. BTW "make all" in cmd window works fine:)
> I don't use AVR studio simulator and I never did before. I have JTAGICE II
> from the beginning of my AVR experience.
> View this message in context: http://www.nabble.com/Ethernut-2.1-and-AVR-studio-tp21517392p21521025.html
> Sent from the MicroControllers - Ethernut mailing list archive at Nabble.com.
More information about the En-Nut-Discussion