Menu
▾
▴
avr-eclipse-user — General discussions and support for the AVR Eclipse plugin
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
(5) |
Mar
(17) |
Apr
(8) |
May
(6) |
Jun
(5) |
Jul
(23) |
Aug
(22) |
Sep
(7) |
Oct
(8) |
Nov
(14) |
Dec
(16) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(15) |
Feb
(4) |
Mar
(8) |
Apr
(13) |
May
(12) |
Jun
|
Jul
(5) |
Aug
(3) |
Sep
(2) |
Oct
(15) |
Nov
(2) |
Dec
(3) |
| 2010 |
Jan
(12) |
Feb
(13) |
Mar
(8) |
Apr
(1) |
May
|
Jun
(8) |
Jul
(11) |
Aug
(12) |
Sep
(4) |
Oct
(7) |
Nov
(3) |
Dec
(4) |
| 2011 |
Jan
(2) |
Feb
(5) |
Mar
(6) |
Apr
|
May
|
Jun
(1) |
Jul
(4) |
Aug
|
Sep
|
Oct
(2) |
Nov
(3) |
Dec
(8) |
| 2012 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
|
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2015 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Thomas H. <th...@in...> - 2010-08-06 21:49:16
|
On 02.08.2010 02:53, Trevor Johansen wrote: > I recently switched over to Eclipse to work on my projects so i could > bounce between different operating systems. The main problem I am > having though is when debugging it is painfully slow to step through > the code. It takes 4s for each step in asm and at least 16s for a > single step in c/c++ and its just not useful at those speeds. I just tried some debugging with my Dragon, connected to a Butterfly. While it was certainly not instantaneous, both C and ASM single steps took usually only 2s, sometimes 4-5s. I don't know why it is running so slow on your system. First of all you should drop the '-d' on the avarice command line. While it is useful when avarice is not working, all the debug output does slow Eclipse down. Secondly you could experiment with the avarice '--jtag-bitrate'. It defaults to 250khz, good for debugging an 1MHz MCU, but if your MCU has a higher clock you could try in increase Bitrate up to 6400khz (for a 25MHz MCU) If that does not help I am afraid I am out of ideas. The current Eclipse/CDT Debugger is slow because it always updates all variables after each step. This could probably be improved by tweaking the debugger in CDT -- something which I have planned for some time now, but haven't had the time to do. If you really need fast debugging you can use AVR-Studio as a debugger. Just open the .elf file generated by Eclipse in AVR Studio and you can debug your program immediately. > > On a second note I see on the winavr website page that mentions > Eclipse their is a tab open called "AVR Device Explorer" that would be > really handy. I used the device info in avrstudio all the time as a > quick reference without the datasheets and it would be nice to do the > same here. Where do I enable it or is it a separate plugin or something? In Eclipse go to 'Window -> Show View -> Other... -> AVR' and click on 'AVR Device Explorer'. Cheers, Thomas |
|
From: SourceForge.net <no...@so...> - 2010-08-06 18:38:18
|
Bugs item #2872447, was opened at 2009-10-04 05:10 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=2872447&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Behavior Group: v2.3 Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Mitch Mitchell (mitchmitchell) Assigned to: Thomas Holland (innot) Summary: getWinAVRBasePath throws exception on Vista 64 Initial Comment: Whenever getWinAVRBasePath is called on my Windows Vista 64 system, I get the exception below. Creating an AVR project, trying to modify the paths under the AVR plugin etc. I think this is because the WinAVR registry key is not in HKML\Software\WinAVR but rather under HKML\Software\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\WinAVR java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:112) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:89) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:64) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.paths.AVRPathProvider.getPath(AVRPathProvider.java:63) at de.innot.avreclipse.core.toolinfo.AVRDude.getToolPath(AVRDude.java:152) at de.innot.avreclipse.core.toolinfo.AVRDude.loadProgrammersList(AVRDude.java:666) at de.innot.avreclipse.core.toolinfo.AVRDude.getProgrammersList(AVRDude.java:212) at de.innot.avreclipse.ui.preferences.AVRDudeConfigEditor.<init>(AVRDudeConfigEditor.java:137) at de.innot.avreclipse.ui.preferences.ProgConfigListFieldEditor.editButtonAction(ProgConfigListFieldEditor.java:468) at de.innot.avreclipse.ui.preferences.ProgConfigListFieldEditor.access$7(ProgConfigListFieldEditor.java:434) at de.innot.avreclipse.ui.preferences.ProgConfigListFieldEditor$4.widgetSelected(ProgConfigListFieldEditor.java:376) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-08-06 20:38 Message: OK, I'am about to give up... ... and upgrade to Window 7 64bit :-) (have this planned anyway for some time now) In the meantime I fixed the ArrayIndexOutOfBoundsException. Could you please try the version at: http://avr-eclipse.sourceforge.net/previews/avreclipse-p2-repository-2.3.4.20100806INT.zip This version probably won't find the paths automatically, but hopefully won't throw Exceptions either. Also, could you execute the following line from a command line and send me the output: reg query "HKLM\Software\WinAVR" /s and reg query "HKLM\Software\Wow6432Node\WinAVR" /s ---------------------------------------------------------------------- Comment By: A. Dewhurst (dagger2) Date: 2010-08-02 15:31 Message: It's still broken, now with java.lang.ArrayIndexOutOfBoundsException: 1 at de.innot.avreclipse.core.paths.win32.MyWindowsRegistry.executeKeyValueCommand(MyWindowsRegistry.java:269) at de.innot.avreclipse.core.paths.win32.MyWindowsRegistry.getKeyName(MyWindowsRegistry.java:204) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:126) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:92) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:63) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) Perhaps it should just fail on 64-bit systems? It looks like the problem is that CDT is broken on 64-bit, but this will get fixed at some point. As far as I'm aware, the only time you access registry keys is to fetch the path to WinAVR, and I already know what the path is (I had to pick it during the installation, after all). I'd be happy if it just failed nicely so I could supply it manually. ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-27 14:45 Message: I have once again tried to fix this problem. Before making a full release (which will be 2.3.4) I have uploaded a test version to: http://avr-eclipse.sourceforge.net/previews/avreclipse-p2-repository-2.3.4.20100727betaNGT.zip If anybody still monitoring this tracker item could please give it a try and see if the autodetection of paths now works on a 64bit Windows system. Your feedback would be appreciated. Thomas ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-22 22:32 Message: (Copied from Support Request 3031058) I thought I had this fixed (with 2.3.2), but I noticed that I never fully finished the fix. As I don't have a 64bit Windows I didn't test the fix before releasing it. I try to fix the bug over the weekend. In the meantime you could try the following workarounds: 1. Set the flag "Disable search for system paths at startup" on the AVR -> Paths preference page and manually set the paths. 2. If you can't set the flag due to NullPointerExceptions you could try to hack this flag. With Eclipse *not* running edit the file '{Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\de.innot.avreclipse.core.prefs' and add/edit the following line: 'avrpaths/NoScanAtStartup=true' Once you have done this you can restart Eclipse and again set the paths manually in the preferences. I have just tested this and it seems that with the workaround the offending code does not get called. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-14 04:28 Message: A simple failure mode that would allow me to manually enter the path to WinAVR would be all that is needed --- right now, the dialog to enter it gets the exception and nothing can be entered in the path field. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-14 04:26 Message: I am using Galileo on both machines. On the 32bit machine is Build id: 20090920-1017 Here is a copy of the exception on the 32bit machine -- I got to this one through a different path, but it is still in getWinAVRBasePath java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:112) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:89) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:60) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.preferences.AVRPathsPreferences$1.run(AVRPathsPreferences.java:168) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-14 00:56 Message: BTW what Eclipse version do you use? ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-14 00:55 Message: I have started to work on this Bug and the obvious culprit is not the AVR Plugin but the WindowRegistry Class from CDT. There is already a bug report that this class is not working on 64bit Windows. https://bugs.eclipse.org/bugs/show_bug.cgi?id=236330 To fix the Problem I will need to check the return value of WindowsRegistry.getRegistry() and if it is Null then either fail gracefully or try some other method of getting access to the registry. I have just contacted the author of the above mentioned bug report to see if I can use his patch as a fallback when getRegistry() fails. Why it also fails on your 32 bit XP I have currently no idea. Can you confirm that it is the same NullPointerException or maybe something other Exception? ---------------------------------------------------------------------- Comment By: Mitch Mitchell (mitchmitchell) Date: 2009-10-04 07:52 Message: I have now confirmed that this exception is also thrown on my 32bit Windows XP machine so the difference in the registry data is not the cause of the null pointer exception ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-04 07:11 Message: Thanks for the detailed description. I will fix this in the next release. ---------------------------------------------------------------------- Comment By: Mitch Mitchell (mitchmitchell) Date: 2009-10-04 05:12 Message: Should have read as HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\WinAVR Also under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Free Software Foundation\WinAVR-20090313 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=2872447&group_id=189165 |
|
From: Trevor J. <ice...@gm...> - 2010-08-02 00:53:37
|
I recently switched over to Eclipse to work on my projects so i could bounce
between different operating systems. The main problem I am having though is
when debugging it is painfully slow to step through the code. It takes 4s
for each step in asm and at least 16s for a single step in c/c++ and its
just not useful at those speeds.
My config:
External Tools Config:
Location: C:\WinAVR-20100110\bin\avarice.exe
Working Dir: ${workspace_loc}
Arg: --dragon --jtag usb :4242 --ignore-intr -d
Debug Configurations:
c/c++ application
Main Tab
Application: Debug\ILI9325.elf
Project: ILI9325
Build: Use Active, Disable auto build
Debugger Tab:
Debugger: gdbserver
Stop at: main
DGB Debugger: avr-gdb
Command set: Standard (Windows)
Protocol: mi
Verbose console mode
TCP localhost:4242
On a second note I see on the winavr website page that mentions Eclipse
their is a tab open called "AVR Device Explorer" that would be really handy.
I used the device info in avrstudio all the time as a quick reference
without the datasheets and it would be nice to do the same here. Where do I
enable it or is it a separate plugin or something?
|
|
From: SourceForge.net <no...@so...> - 2010-07-30 09:16:42
|
Feature Requests item #3036785, was opened at 2010-07-29 23:25 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928234&aid=3036785&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Additional Functionality Group: Consider For Next Release Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Grosche (texor) >Assigned to: Thomas Holland (innot) Summary: define files to be executed before and after upload-to-avr Initial Comment: Please add the option to choose a program/script to be executed before and (another) after the upload-to-avr-process. This would be nice when using one and the same RS232-port for output in a terminal on the PC and for programming the AVR. For example, you could execute a script before programming to close the terminal and release the RS232-port and execute a script to open the terminal again after programming completed. This would reduce a lot of clicks closing and opening the console ;-) Thanks a lot for this great plugin ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-07-30 11:16 Message: That sounds like a reasonable idea. But I think that this will require a bit of UI redesign so I will look at this once I restart development on the next major version. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928234&aid=3036785&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-30 09:07:04
|
Feature Requests item #2905839, was opened at 2009-11-30 07:07 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928234&aid=2905839&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface Improvements Group: None Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: MsJaye (msjaye) Assigned to: Thomas Holland (innot) Summary: Upload Project To Target Device from any point in Project Initial Comment: Having to explicitly select the top level project item in the Project Explorer to allow "Upload Project to Target Device" to work is rather irritating. Surely, if any element within a project is selected in the Project Explorer, then it's clear that the containing project is the one that's meant to be uploaded? It's a bit of a hassle having to bring up the Project Explorer and click on the project's top level item, especially when working on a small monitor when the Project Explorer isn't always visible. ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-07-30 11:07 Message: Fixed in SVN. Will be in the next release (2.3.4). ---------------------------------------------------------------------- Comment By: Matthew McDougal (mmdoogie) Date: 2010-07-08 06:09 Message: reassigning to current maintainer ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928234&aid=2905839&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-27 12:45:58
|
Bugs item #2872447, was opened at 2009-10-04 05:10 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=2872447&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Behavior Group: v2.3 Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: Mitch Mitchell (mitchmitchell) Assigned to: Thomas Holland (innot) Summary: getWinAVRBasePath throws exception on Vista 64 Initial Comment: Whenever getWinAVRBasePath is called on my Windows Vista 64 system, I get the exception below. Creating an AVR project, trying to modify the paths under the AVR plugin etc. I think this is because the WinAVR registry key is not in HKML\Software\WinAVR but rather under HKML\Software\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\WinAVR java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:112) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:89) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:64) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.paths.AVRPathProvider.getPath(AVRPathProvider.java:63) at de.innot.avreclipse.core.toolinfo.AVRDude.getToolPath(AVRDude.java:152) at de.innot.avreclipse.core.toolinfo.AVRDude.loadProgrammersList(AVRDude.java:666) at de.innot.avreclipse.core.toolinfo.AVRDude.getProgrammersList(AVRDude.java:212) at de.innot.avreclipse.ui.preferences.AVRDudeConfigEditor.<init>(AVRDudeConfigEditor.java:137) at de.innot.avreclipse.ui.preferences.ProgConfigListFieldEditor.editButtonAction(ProgConfigListFieldEditor.java:468) at de.innot.avreclipse.ui.preferences.ProgConfigListFieldEditor.access$7(ProgConfigListFieldEditor.java:434) at de.innot.avreclipse.ui.preferences.ProgConfigListFieldEditor$4.widgetSelected(ProgConfigListFieldEditor.java:376) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-07-27 14:45 Message: I have once again tried to fix this problem. Before making a full release (which will be 2.3.4) I have uploaded a test version to: http://avr-eclipse.sourceforge.net/previews/avreclipse-p2-repository-2.3.4.20100727betaNGT.zip If anybody still monitoring this tracker item could please give it a try and see if the autodetection of paths now works on a 64bit Windows system. Your feedback would be appreciated. Thomas ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-22 22:32 Message: (Copied from Support Request 3031058) I thought I had this fixed (with 2.3.2), but I noticed that I never fully finished the fix. As I don't have a 64bit Windows I didn't test the fix before releasing it. I try to fix the bug over the weekend. In the meantime you could try the following workarounds: 1. Set the flag "Disable search for system paths at startup" on the AVR -> Paths preference page and manually set the paths. 2. If you can't set the flag due to NullPointerExceptions you could try to hack this flag. With Eclipse *not* running edit the file '{Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\de.innot.avreclipse.core.prefs' and add/edit the following line: 'avrpaths/NoScanAtStartup=true' Once you have done this you can restart Eclipse and again set the paths manually in the preferences. I have just tested this and it seems that with the workaround the offending code does not get called. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-14 04:28 Message: A simple failure mode that would allow me to manually enter the path to WinAVR would be all that is needed --- right now, the dialog to enter it gets the exception and nothing can be entered in the path field. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-14 04:26 Message: I am using Galileo on both machines. On the 32bit machine is Build id: 20090920-1017 Here is a copy of the exception on the 32bit machine -- I got to this one through a different path, but it is still in getWinAVRBasePath java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:112) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:89) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:60) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.preferences.AVRPathsPreferences$1.run(AVRPathsPreferences.java:168) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-14 00:56 Message: BTW what Eclipse version do you use? ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-14 00:55 Message: I have started to work on this Bug and the obvious culprit is not the AVR Plugin but the WindowRegistry Class from CDT. There is already a bug report that this class is not working on 64bit Windows. https://bugs.eclipse.org/bugs/show_bug.cgi?id=236330 To fix the Problem I will need to check the return value of WindowsRegistry.getRegistry() and if it is Null then either fail gracefully or try some other method of getting access to the registry. I have just contacted the author of the above mentioned bug report to see if I can use his patch as a fallback when getRegistry() fails. Why it also fails on your 32 bit XP I have currently no idea. Can you confirm that it is the same NullPointerException or maybe something other Exception? ---------------------------------------------------------------------- Comment By: Mitch Mitchell (mitchmitchell) Date: 2009-10-04 07:52 Message: I have now confirmed that this exception is also thrown on my 32bit Windows XP machine so the difference in the registry data is not the cause of the null pointer exception ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-04 07:11 Message: Thanks for the detailed description. I will fix this in the next release. ---------------------------------------------------------------------- Comment By: Mitch Mitchell (mitchmitchell) Date: 2009-10-04 05:12 Message: Should have read as HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\WinAVR Also under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Free Software Foundation\WinAVR-20090313 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=2872447&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-27 12:41:15
|
Support Requests item #3031058, was opened at 2010-07-17 23:00 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3031058&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: Barry Burns (bsburns) Assigned to: Thomas Holland (innot) Summary: Project Creation Error Initial Comment: I have tried this on two computers and 2 different versions of eclipse (3.5 and 3.6). I am running on a Windows 7 x64 machine and i do have JRE installed and working (I have several other apps that rely on JRE). When I attempt to create a new project via the following steps: File->New->C++ Project In the pop-up dialog I provide a unique project name and select AVR Cross Target Application->Empty Project an then "Finish" At that time, I get a dialog message stating: "Project cannot be created Reason: Internal Error:" If I select details on the dialog message, it says: "java.lang.NullPointerException" What am I doing wrong? B2 ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-07-27 14:41 Message: Barry, I have uploaded a (hopefully) fixed version of the Plugin here: http://avr-eclipse.sourceforge.net/previews/avreclipse-p2-repository-2.3.4.20100727betaNGT.zip Could you please install this on your 64bit Windows, go to the AVR -> Paths preferences, click on one of the paths (e.g. AVR-GCC) and change its property back to "System". Hopefully this should work now, but I would really appreciate your feedback before making an official release. Thomas ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-22 22:17 Message: Thanks for the log, Barry. I have already found the problem. It is an inadequate fix for bug 2872447: "getWinAVRBasePath throws exception on Vista 64". I thought I had this fixed (with 2.3.2), but I noticed that I never fully finished the fix. As I don't have a 64bit Windows I didn't test the fix before releasing it. I try to fix the bug over the weekend. In the meantime you could try the following workarounds: 1. Set the flag "Disable search for system paths at startup" on the AVR -> Paths preference page and manually set the paths. 2. If you can't set the flag due to NullPointerExceptions you could try to hack this flag. With Eclipse *not* running edit the file '{Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\de.innot.avreclipse.core.prefs' and add/edit the following line: 'avrpaths/NoScanAtStartup=true' Once you have done this you can restart Eclipse and again set the paths manually in the preferences. I have just tested this and it seems that with the workaround the offending code does not get called. ---------------------------------------------------------------------- Comment By: https://www.google.com/accounts () Date: 2010-07-22 20:42 Message: !SESSION 2010-07-22 21:35:05.249 ----------------------------------------------- eclipse.buildId=I20100608-0911 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=ru_RU Framework arguments: -product org.eclipse.epp.package.cpp.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.cpp.product !ENTRY org.eclipse.ui.workbench 4 0 2010-07-22 21:35:07.963 !MESSAGE Unable to create view ID de.innot.avreclipse.views.supportedmcus: An unexpected exception was thrown. !STACK 0 java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:127) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:93) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:64) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.paths.AVRPathProvider.getPath(AVRPathProvider.java:63) at de.innot.avreclipse.core.toolinfo.GCC.getToolPath(GCC.java:79) at de.innot.avreclipse.core.toolinfo.GCC.runCommand(GCC.java:238) at de.innot.avreclipse.core.toolinfo.GCC.getNameAndVersion(GCC.java:198) at de.innot.avreclipse.ui.views.supportedmcu.MCUListColumn$2.getName(MCUListColumn.java:85) at de.innot.avreclipse.ui.views.supportedmcu.MCUListColumn.addColumn(MCUListColumn.java:250) at de.innot.avreclipse.ui.views.supportedmcu.MCUListView.createPartControl(MCUListView.java:132) at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:375) at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(WorkbenchPage.java:4218) at org.eclipse.ui.internal.WorkbenchPage$18.runWithException(WorkbenchPage.java:3277) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1566) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2537) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) !ENTRY org.eclipse.jface 4 2 2010-07-22 21:37:05.350 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:127) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:93) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:64) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.paths.AVRPathManager.getSystemPath(AVRPathManager.java:143) at de.innot.avreclipse.core.paths.AVRPathManager.getPath(AVRPathManager.java:101) at de.innot.avreclipse.core.paths.AVRPathManager.isValid(AVRPathManager.java:237) at de.innot.avreclipse.ui.preferences.AVRPathsFieldEditor.updateTableItem(AVRPathsFieldEditor.java:378) at de.innot.avreclipse.ui.preferences.AVRPathsFieldEditor.doLoad(AVRPathsFieldEditor.java:243) at org.eclipse.jface.preference.FieldEditor.load(FieldEditor.java:500) at org.eclipse.jface.preference.FieldEditorPreferencePage.initialize(FieldEditorPreferencePage.java:307) at org.eclipse.jface.preference.FieldEditorPreferencePage.createContents(FieldEditorPreferencePage.java:233) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501) at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:673) at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:867) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:865) at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1205) at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1230) at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:251) at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:245) at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:419) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-21 19:21 Message: Hi, please attach the Eclipse error log to this tracker item (or send it to me via email: th...@in...) I will have a look to determine where the NullPointerException is coming from. To get the error log in Helios (Eclipse 3.6): Help -> About Eclipse -> Installation Details -> Configuration -> View Error Log Thomas ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3031058&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-22 20:32:25
|
Bugs item #2872447, was opened at 2009-10-04 05:10 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=2872447&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Behavior Group: v2.3 Status: Open Resolution: Accepted Priority: 5 Private: No Submitted By: Mitch Mitchell (mitchmitchell) Assigned to: Thomas Holland (innot) Summary: getWinAVRBasePath throws exception on Vista 64 Initial Comment: Whenever getWinAVRBasePath is called on my Windows Vista 64 system, I get the exception below. Creating an AVR project, trying to modify the paths under the AVR plugin etc. I think this is because the WinAVR registry key is not in HKML\Software\WinAVR but rather under HKML\Software\HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\WinAVR java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:112) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:89) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:64) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.paths.AVRPathProvider.getPath(AVRPathProvider.java:63) at de.innot.avreclipse.core.toolinfo.AVRDude.getToolPath(AVRDude.java:152) at de.innot.avreclipse.core.toolinfo.AVRDude.loadProgrammersList(AVRDude.java:666) at de.innot.avreclipse.core.toolinfo.AVRDude.getProgrammersList(AVRDude.java:212) at de.innot.avreclipse.ui.preferences.AVRDudeConfigEditor.<init>(AVRDudeConfigEditor.java:137) at de.innot.avreclipse.ui.preferences.ProgConfigListFieldEditor.editButtonAction(ProgConfigListFieldEditor.java:468) at de.innot.avreclipse.ui.preferences.ProgConfigListFieldEditor.access$7(ProgConfigListFieldEditor.java:434) at de.innot.avreclipse.ui.preferences.ProgConfigListFieldEditor$4.widgetSelected(ProgConfigListFieldEditor.java:376) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3880) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3473) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-07-22 22:32 Message: (Copied from Support Request 3031058) I thought I had this fixed (with 2.3.2), but I noticed that I never fully finished the fix. As I don't have a 64bit Windows I didn't test the fix before releasing it. I try to fix the bug over the weekend. In the meantime you could try the following workarounds: 1. Set the flag "Disable search for system paths at startup" on the AVR -> Paths preference page and manually set the paths. 2. If you can't set the flag due to NullPointerExceptions you could try to hack this flag. With Eclipse *not* running edit the file '{Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\de.innot.avreclipse.core.prefs' and add/edit the following line: 'avrpaths/NoScanAtStartup=true' Once you have done this you can restart Eclipse and again set the paths manually in the preferences. I have just tested this and it seems that with the workaround the offending code does not get called. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-14 04:28 Message: A simple failure mode that would allow me to manually enter the path to WinAVR would be all that is needed --- right now, the dialog to enter it gets the exception and nothing can be entered in the path field. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2009-10-14 04:26 Message: I am using Galileo on both machines. On the 32bit machine is Build id: 20090920-1017 Here is a copy of the exception on the 32bit machine -- I got to this one through a different path, but it is still in getWinAVRBasePath java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:112) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:89) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:60) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.preferences.AVRPathsPreferences$1.run(AVRPathsPreferences.java:168) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-14 00:56 Message: BTW what Eclipse version do you use? ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-14 00:55 Message: I have started to work on this Bug and the obvious culprit is not the AVR Plugin but the WindowRegistry Class from CDT. There is already a bug report that this class is not working on 64bit Windows. https://bugs.eclipse.org/bugs/show_bug.cgi?id=236330 To fix the Problem I will need to check the return value of WindowsRegistry.getRegistry() and if it is Null then either fail gracefully or try some other method of getting access to the registry. I have just contacted the author of the above mentioned bug report to see if I can use his patch as a fallback when getRegistry() fails. Why it also fails on your 32 bit XP I have currently no idea. Can you confirm that it is the same NullPointerException or maybe something other Exception? ---------------------------------------------------------------------- Comment By: Mitch Mitchell (mitchmitchell) Date: 2009-10-04 07:52 Message: I have now confirmed that this exception is also thrown on my 32bit Windows XP machine so the difference in the registry data is not the cause of the null pointer exception ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-04 07:11 Message: Thanks for the detailed description. I will fix this in the next release. ---------------------------------------------------------------------- Comment By: Mitch Mitchell (mitchmitchell) Date: 2009-10-04 05:12 Message: Should have read as HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\WinAVR Also under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Free Software Foundation\WinAVR-20090313 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=2872447&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-22 20:17:34
|
Support Requests item #3031058, was opened at 2010-07-17 23:00 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3031058&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Accepted Priority: 5 Private: No Submitted By: Barry Burns (bsburns) Assigned to: Thomas Holland (innot) Summary: Project Creation Error Initial Comment: I have tried this on two computers and 2 different versions of eclipse (3.5 and 3.6). I am running on a Windows 7 x64 machine and i do have JRE installed and working (I have several other apps that rely on JRE). When I attempt to create a new project via the following steps: File->New->C++ Project In the pop-up dialog I provide a unique project name and select AVR Cross Target Application->Empty Project an then "Finish" At that time, I get a dialog message stating: "Project cannot be created Reason: Internal Error:" If I select details on the dialog message, it says: "java.lang.NullPointerException" What am I doing wrong? B2 ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-07-22 22:17 Message: Thanks for the log, Barry. I have already found the problem. It is an inadequate fix for bug 2872447: "getWinAVRBasePath throws exception on Vista 64". I thought I had this fixed (with 2.3.2), but I noticed that I never fully finished the fix. As I don't have a 64bit Windows I didn't test the fix before releasing it. I try to fix the bug over the weekend. In the meantime you could try the following workarounds: 1. Set the flag "Disable search for system paths at startup" on the AVR -> Paths preference page and manually set the paths. 2. If you can't set the flag due to NullPointerExceptions you could try to hack this flag. With Eclipse *not* running edit the file '{Workspace}\.metadata\.plugins\org.eclipse.core.runtime\.settings\de.innot.avreclipse.core.prefs' and add/edit the following line: 'avrpaths/NoScanAtStartup=true' Once you have done this you can restart Eclipse and again set the paths manually in the preferences. I have just tested this and it seems that with the workaround the offending code does not get called. ---------------------------------------------------------------------- Comment By: https://www.google.com/accounts () Date: 2010-07-22 20:42 Message: !SESSION 2010-07-22 21:35:05.249 ----------------------------------------------- eclipse.buildId=I20100608-0911 java.version=1.6.0_20 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=ru_RU Framework arguments: -product org.eclipse.epp.package.cpp.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.cpp.product !ENTRY org.eclipse.ui.workbench 4 0 2010-07-22 21:35:07.963 !MESSAGE Unable to create view ID de.innot.avreclipse.views.supportedmcus: An unexpected exception was thrown. !STACK 0 java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:127) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:93) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:64) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.paths.AVRPathProvider.getPath(AVRPathProvider.java:63) at de.innot.avreclipse.core.toolinfo.GCC.getToolPath(GCC.java:79) at de.innot.avreclipse.core.toolinfo.GCC.runCommand(GCC.java:238) at de.innot.avreclipse.core.toolinfo.GCC.getNameAndVersion(GCC.java:198) at de.innot.avreclipse.ui.views.supportedmcu.MCUListColumn$2.getName(MCUListColumn.java:85) at de.innot.avreclipse.ui.views.supportedmcu.MCUListColumn.addColumn(MCUListColumn.java:250) at de.innot.avreclipse.ui.views.supportedmcu.MCUListView.createPartControl(MCUListView.java:132) at org.eclipse.ui.internal.ViewReference.createPartHelper(ViewReference.java:375) at org.eclipse.ui.internal.ViewReference.createPart(ViewReference.java:229) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.WorkbenchPage$ActivationList.setActive(WorkbenchPage.java:4218) at org.eclipse.ui.internal.WorkbenchPage$18.runWithException(WorkbenchPage.java:3277) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803) at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1566) at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2537) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) !ENTRY org.eclipse.jface 4 2 2010-07-22 21:37:05.350 !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface". !STACK 0 java.lang.NullPointerException at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRBasePath(SystemPathsWin32.java:127) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getWinAVRPath(SystemPathsWin32.java:93) at de.innot.avreclipse.core.paths.win32.SystemPathsWin32.getSystemPath(SystemPathsWin32.java:64) at de.innot.avreclipse.core.paths.SystemPathHelper.getPath(SystemPathHelper.java:102) at de.innot.avreclipse.core.paths.AVRPathManager.getSystemPath(AVRPathManager.java:143) at de.innot.avreclipse.core.paths.AVRPathManager.getPath(AVRPathManager.java:101) at de.innot.avreclipse.core.paths.AVRPathManager.isValid(AVRPathManager.java:237) at de.innot.avreclipse.ui.preferences.AVRPathsFieldEditor.updateTableItem(AVRPathsFieldEditor.java:378) at de.innot.avreclipse.ui.preferences.AVRPathsFieldEditor.doLoad(AVRPathsFieldEditor.java:243) at org.eclipse.jface.preference.FieldEditor.load(FieldEditor.java:500) at org.eclipse.jface.preference.FieldEditorPreferencePage.initialize(FieldEditorPreferencePage.java:307) at org.eclipse.jface.preference.FieldEditorPreferencePage.createContents(FieldEditorPreferencePage.java:233) at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:232) at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1501) at org.eclipse.jface.preference.PreferenceDialog$14.run(PreferenceDialog.java:1258) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1252) at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:673) at org.eclipse.jface.preference.PreferenceDialog$10.run(PreferenceDialog.java:708) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.preference.PreferenceDialog$9.selectionChanged(PreferenceDialog.java:704) at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:867) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:865) at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1205) at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1230) at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:251) at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:245) at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:419) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211) at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:65) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4066) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3657) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) at org.eclipse.equinox.launcher.Main.run(Main.java:1407) at org.eclipse.equinox.launcher.Main.main(Main.java:1383) ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-21 19:21 Message: Hi, please attach the Eclipse error log to this tracker item (or send it to me via email: th...@in...) I will have a look to determine where the NullPointerException is coming from. To get the error log in Helios (Eclipse 3.6): Help -> About Eclipse -> Installation Details -> Configuration -> View Error Log Thomas ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3031058&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-08 07:41:36
|
Bugs item #3023718, was opened at 2010-07-01 11:16 Message generated for change (Comment added) made by simo1975 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Behavior Group: v2.3 Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Thomas Holland (innot) Summary: wrong part when invoking avrdude to read fuses/lockbits Initial Comment: When trying to read fuses or lockbits from AVRDude options page in project properties, the plugin outputs a wrong command line to invoke AVRDude: avrdude -cavrisp2 -Pusb -pm16 this command fails saying "avrdude: initialization failed, rc=-1" Since I'm using ATXMEGA128A1 mcu, the part specified in the command line doesn't reflects the project target hardware setting. I think the command line should be: avrdude -cavrisp2 -Pusb -px128a1 This behavior is present also when trying to load the "Flash memory erase cycle counter" in the "other" page of AVRDude options. P.S. My project is setup correctly as I can program my board and the fuses (when I set them manually). Please take a look at this. Xmega devices uses a different type of initialization than traditional MEGA. ---------------------------------------------------------------------- Comment By: Simone (simo1975) Date: 2010-07-08 09:41 Message: Yes, this works for me too! As I stated before, the only problem is that XMEGA uses a different protocol for the external programmer than the standard MEGA parts and AVRDude doesn't try automatically both protocols, it uses only the one for the part family you have specified in the command line. So I think your approach is optimal. This enhancement should go into the next release. Good job and many thanks for this great plugin! ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-06 20:09 Message: I think I have fixed this bug (and another XMega related bug that popped up once I had fixed this issue). Could you please try the fix to see if it works for you as well? I have uploaded the fixed plugin to the inofficial update site at avr-eclipse.sourceforge.net/previews or you could just use the following link to download the p2 repository which can be used as a local installation source. http://avr-eclipse.sourceforge.net/previews/avreclipse-p2-repository-2.3.4.20100706betaNGT.zip BTW the plugin still tries to determine the MCU automatically, it will just try an XMega typ if the a 'conventional' AVR MCU fails. Anything else would have meant a large rewrite of the plugin. ---------------------------------------------------------------------- Comment By: Simone (simo1975) Date: 2010-07-02 09:29 Message: This is the output log in CDT: ---------------------------------------------------------------------- Launching C:\Programmi\Atmel\WinAVR\bin\avrdude -cavrisp2 -Pusb -pm16 Output: avrdude: stk500v2_command(): command failed avrdude: stk500v2_command(): unknown status 0xc9 avrdude: stk500v2_program_enable(): cannot get connection status avrdude: initialization failed, rc=-1 Double check connections and try again, or use -F to override this check. avrdude execution aborted ---------------------------------------------------------------------- To help you, I tryed from command line to execute the command with xmega16a4 part and avrdude answers in the following way: ---------------------------------------------------------------------- avrdude -cavrisp2 -Pusb -px16a4 avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.02s avrdude: Device signature = 0x1e974c avrdude: Expected signature for ATXMEGA16A4 is 1E 94 41 Double check chip, or use -F to override this check. avrdude done. Thank you. ---------------------------------------------------------------------- and specifying the correct part (xmega128a1): ---------------------------------------------------------------------- C:\Documents and Settings\s.zamboni.ELTASRL>avrdude -cavrisp2 -Pusb -px128a1 avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.02s avrdude: Device signature = 0x1e974c avrdude done. Thank you. ---------------------------------------------------------------------- I think avrdude must know that the target hardware is a XMEGA part because MEGA and XMEGA series uses completely different protocols: ATMEGA is programmed over SPI and XMEGA uses the new PDI programming port. I know would be a better way to automatically recognize the device attached but wouldn't be simpler to just use the one specified by the user in the target page? If the user doesn't set any device he will receive an error. I can perform further test if you need extra informations. ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-01 15:43 Message: Some internal functions like "read fuses from MCU" try to automatically detect which MCU type is connected. This was done as a safeguard against user errors where the connected MCU is not the same as set for the project. They do this by passing -pm16 to avrdude and parsing the response from avrdude (which will report the correct MCU type) It seems that this autodetection fails with ATXmegas, but I don't have any ATXmegas to test this (I just ordered an XPlain board as a remedy :-). So, in the meantime could you please provide the full avrdude console output? (If you haven't done this already please select Window->Preferences...->AVR->AVRDude -> Log internal AVRDude output to console). This way I could already start to work on the bug while I wait for my XPlain board. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-06 18:09:58
|
Bugs item #3023718, was opened at 2010-07-01 11:16 Message generated for change (Settings changed) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Behavior Group: v2.3 Status: Open >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Thomas Holland (innot) Summary: wrong part when invoking avrdude to read fuses/lockbits Initial Comment: When trying to read fuses or lockbits from AVRDude options page in project properties, the plugin outputs a wrong command line to invoke AVRDude: avrdude -cavrisp2 -Pusb -pm16 this command fails saying "avrdude: initialization failed, rc=-1" Since I'm using ATXMEGA128A1 mcu, the part specified in the command line doesn't reflects the project target hardware setting. I think the command line should be: avrdude -cavrisp2 -Pusb -px128a1 This behavior is present also when trying to load the "Flash memory erase cycle counter" in the "other" page of AVRDude options. P.S. My project is setup correctly as I can program my board and the fuses (when I set them manually). Please take a look at this. Xmega devices uses a different type of initialization than traditional MEGA. ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-06 20:09 Message: I think I have fixed this bug (and another XMega related bug that popped up once I had fixed this issue). Could you please try the fix to see if it works for you as well? I have uploaded the fixed plugin to the inofficial update site at avr-eclipse.sourceforge.net/previews or you could just use the following link to download the p2 repository which can be used as a local installation source. http://avr-eclipse.sourceforge.net/previews/avreclipse-p2-repository-2.3.4.20100706betaNGT.zip BTW the plugin still tries to determine the MCU automatically, it will just try an XMega typ if the a 'conventional' AVR MCU fails. Anything else would have meant a large rewrite of the plugin. ---------------------------------------------------------------------- Comment By: Simone (simo1975) Date: 2010-07-02 09:29 Message: This is the output log in CDT: ---------------------------------------------------------------------- Launching C:\Programmi\Atmel\WinAVR\bin\avrdude -cavrisp2 -Pusb -pm16 Output: avrdude: stk500v2_command(): command failed avrdude: stk500v2_command(): unknown status 0xc9 avrdude: stk500v2_program_enable(): cannot get connection status avrdude: initialization failed, rc=-1 Double check connections and try again, or use -F to override this check. avrdude execution aborted ---------------------------------------------------------------------- To help you, I tryed from command line to execute the command with xmega16a4 part and avrdude answers in the following way: ---------------------------------------------------------------------- avrdude -cavrisp2 -Pusb -px16a4 avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.02s avrdude: Device signature = 0x1e974c avrdude: Expected signature for ATXMEGA16A4 is 1E 94 41 Double check chip, or use -F to override this check. avrdude done. Thank you. ---------------------------------------------------------------------- and specifying the correct part (xmega128a1): ---------------------------------------------------------------------- C:\Documents and Settings\s.zamboni.ELTASRL>avrdude -cavrisp2 -Pusb -px128a1 avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.02s avrdude: Device signature = 0x1e974c avrdude done. Thank you. ---------------------------------------------------------------------- I think avrdude must know that the target hardware is a XMEGA part because MEGA and XMEGA series uses completely different protocols: ATMEGA is programmed over SPI and XMEGA uses the new PDI programming port. I know would be a better way to automatically recognize the device attached but wouldn't be simpler to just use the one specified by the user in the target page? If the user doesn't set any device he will receive an error. I can perform further test if you need extra informations. ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-01 15:43 Message: Some internal functions like "read fuses from MCU" try to automatically detect which MCU type is connected. This was done as a safeguard against user errors where the connected MCU is not the same as set for the project. They do this by passing -pm16 to avrdude and parsing the response from avrdude (which will report the correct MCU type) It seems that this autodetection fails with ATXmegas, but I don't have any ATXmegas to test this (I just ordered an XPlain board as a remedy :-). So, in the meantime could you please provide the full avrdude console output? (If you haven't done this already please select Window->Preferences...->AVR->AVRDude -> Log internal AVRDude output to console). This way I could already start to work on the bug while I wait for my XPlain board. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-02 07:29:19
|
Bugs item #3023718, was opened at 2010-07-01 11:16 Message generated for change (Comment added) made by simo1975 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Behavior Group: v2.3 Status: Open Resolution: Accepted Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) Assigned to: Thomas Holland (innot) Summary: wrong part when invoking avrdude to read fuses/lockbits Initial Comment: When trying to read fuses or lockbits from AVRDude options page in project properties, the plugin outputs a wrong command line to invoke AVRDude: avrdude -cavrisp2 -Pusb -pm16 this command fails saying "avrdude: initialization failed, rc=-1" Since I'm using ATXMEGA128A1 mcu, the part specified in the command line doesn't reflects the project target hardware setting. I think the command line should be: avrdude -cavrisp2 -Pusb -px128a1 This behavior is present also when trying to load the "Flash memory erase cycle counter" in the "other" page of AVRDude options. P.S. My project is setup correctly as I can program my board and the fuses (when I set them manually). Please take a look at this. Xmega devices uses a different type of initialization than traditional MEGA. ---------------------------------------------------------------------- Comment By: Simone (simo1975) Date: 2010-07-02 09:29 Message: This is the output log in CDT: ---------------------------------------------------------------------- Launching C:\Programmi\Atmel\WinAVR\bin\avrdude -cavrisp2 -Pusb -pm16 Output: avrdude: stk500v2_command(): command failed avrdude: stk500v2_command(): unknown status 0xc9 avrdude: stk500v2_program_enable(): cannot get connection status avrdude: initialization failed, rc=-1 Double check connections and try again, or use -F to override this check. avrdude execution aborted ---------------------------------------------------------------------- To help you, I tryed from command line to execute the command with xmega16a4 part and avrdude answers in the following way: ---------------------------------------------------------------------- avrdude -cavrisp2 -Pusb -px16a4 avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.02s avrdude: Device signature = 0x1e974c avrdude: Expected signature for ATXMEGA16A4 is 1E 94 41 Double check chip, or use -F to override this check. avrdude done. Thank you. ---------------------------------------------------------------------- and specifying the correct part (xmega128a1): ---------------------------------------------------------------------- C:\Documents and Settings\s.zamboni.ELTASRL>avrdude -cavrisp2 -Pusb -px128a1 avrdude: AVR device initialized and ready to accept instructions Reading | ################################################## | 100% 0.02s avrdude: Device signature = 0x1e974c avrdude done. Thank you. ---------------------------------------------------------------------- I think avrdude must know that the target hardware is a XMEGA part because MEGA and XMEGA series uses completely different protocols: ATMEGA is programmed over SPI and XMEGA uses the new PDI programming port. I know would be a better way to automatically recognize the device attached but wouldn't be simpler to just use the one specified by the user in the target page? If the user doesn't set any device he will receive an error. I can perform further test if you need extra informations. ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-07-01 15:43 Message: Some internal functions like "read fuses from MCU" try to automatically detect which MCU type is connected. This was done as a safeguard against user errors where the connected MCU is not the same as set for the project. They do this by passing -pm16 to avrdude and parsing the response from avrdude (which will report the correct MCU type) It seems that this autodetection fails with ATXmegas, but I don't have any ATXmegas to test this (I just ordered an XPlain board as a remedy :-). So, in the meantime could you please provide the full avrdude console output? (If you haven't done this already please select Window->Preferences...->AVR->AVRDude -> Log internal AVRDude output to console). This way I could already start to work on the bug while I wait for my XPlain board. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-01 13:43:32
|
Bugs item #3023718, was opened at 2010-07-01 11:16 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Behavior Group: v2.3 Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Thomas Holland (innot) Summary: wrong part when invoking avrdude to read fuses/lockbits Initial Comment: When trying to read fuses or lockbits from AVRDude options page in project properties, the plugin outputs a wrong command line to invoke AVRDude: avrdude -cavrisp2 -Pusb -pm16 this command fails saying "avrdude: initialization failed, rc=-1" Since I'm using ATXMEGA128A1 mcu, the part specified in the command line doesn't reflects the project target hardware setting. I think the command line should be: avrdude -cavrisp2 -Pusb -px128a1 This behavior is present also when trying to load the "Flash memory erase cycle counter" in the "other" page of AVRDude options. P.S. My project is setup correctly as I can program my board and the fuses (when I set them manually). Please take a look at this. Xmega devices uses a different type of initialization than traditional MEGA. ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-07-01 15:43 Message: Some internal functions like "read fuses from MCU" try to automatically detect which MCU type is connected. This was done as a safeguard against user errors where the connected MCU is not the same as set for the project. They do this by passing -pm16 to avrdude and parsing the response from avrdude (which will report the correct MCU type) It seems that this autodetection fails with ATXmegas, but I don't have any ATXmegas to test this (I just ordered an XPlain board as a remedy :-). So, in the meantime could you please provide the full avrdude console output? (If you haven't done this already please select Window->Preferences...->AVR->AVRDude -> Log internal AVRDude output to console). This way I could already start to work on the bug while I wait for my XPlain board. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023718&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-07-01 08:37:01
|
Bugs item #3023252, was opened at 2010-06-30 10:30 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023252&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. >Category: Behavior >Group: v2.3 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Thomas Holland (innot) >Assigned to: Thomas Holland (innot) Summary: NullPointerException when opening the Project Properties Initial Comment: Version 2.3.2 will throw a NullPointerException when opening the Properties of a Makefile AVR-GCC Toolchain project. java.lang.NullPointerException at de.innot.avreclipse.core.ProjectTypeTester.test(ProjectTypeTester.java:90) at org.eclipse.core.internal.expressions.Property.test(Property.java:58) at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99) at org.eclipse.core.internal.expressions.NotExpression.evaluate(NotExpression.java:35) [...] This is due to a missing check in ProjectTypeTester.java: 86 if (KEY_STATIC_LIB.equalsIgnoreCase(property)) { 87 IManagedProject p = getManagedProject((IResource) receiver); 88 IBuildObjectProperties props = p.getBuildProperties(); 89 IBuildProperty prop = props.getProperty("org.eclipse.cdt.build.core.buildArtefactType"); 90 IBuildPropertyValue value = prop.getValue(); 91 if (value.getId().equals("de.innot.avreclipse.buildArtefactType.staticLib")) { 92 return true; 93 } ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-07-01 10:37 Message: Fixed in Release 2.3.3 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023252&group_id=189165 |
|
From: Zafi R. <zr...@ro...> - 2010-06-30 22:02:10
|
Hi Thomas, I confirm that I'm running a "Makefile project". Thanks for the support. Regards, Zafi. On 06/30/2010 10:36 AM, Thomas Holland wrote: > Hi Zafi, > > thank you for the bug report. I was able to reproduce the bug, but > only when creating a "Makefile project". There were no problems with > "AVR Cross Target Projects". Can you confirm this? > > I have opened a bug report > <https://sourceforge.net/tracker/?func=detail&aid=3023252&group_id=189165&atid=928231> > and as the fix should be trivial I will release it later today once I > have tested it sufficiently. > > brgds, > > Thomas > > On 30.06.2010 01:41, Zafi Ramarosandratana wrote: >> Hi all, >> >> I've just upgraded to Eclipse Galileo 3.5.2 and installed the last >> release of the AVR plugin. When selecting File -> Properties, no >> window appears. With Right-Click on a project, Properties does not >> appear in the menu list. >> >> See attached the corresponding log. >> >> In case it can help: I'm running Fedora 13, linux version 2.6.33.5-124. >> >> Regards, >> Zafi. >> > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > > > _______________________________________________ > avr-eclipse-user mailing list > avr...@li... > https://lists.sourceforge.net/lists/listinfo/avr-eclipse-user > |
|
From: Thomas H. <th...@in...> - 2010-06-30 09:02:01
|
Hi Zafi, thank you for the bug report. I was able to reproduce the bug, but only when creating a "Makefile project". There were no problems with "AVR Cross Target Projects". Can you confirm this? I have opened a bug report <https://sourceforge.net/tracker/?func=detail&aid=3023252&group_id=189165&atid=928231> and as the fix should be trivial I will release it later today once I have tested it sufficiently. brgds, Thomas On 30.06.2010 01:41, Zafi Ramarosandratana wrote: > Hi all, > > I've just upgraded to Eclipse Galileo 3.5.2 and installed the last > release of the AVR plugin. When selecting File -> Properties, no > window appears. With Right-Click on a project, Properties does not > appear in the menu list. > > See attached the corresponding log. > > In case it can help: I'm running Fedora 13, linux version 2.6.33.5-124. > > Regards, > Zafi. > |
|
From: SourceForge.net <no...@so...> - 2010-06-30 08:30:29
|
Bugs item #3023252, was opened at 2010-06-30 10:30 Message generated for change (Tracker Item Submitted) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023252&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Thomas Holland (innot) Assigned to: Nobody/Anonymous (nobody) Summary: NullPointerException when opening the Project Properties Initial Comment: Version 2.3.2 will throw a NullPointerException when opening the Properties of a Makefile AVR-GCC Toolchain project. java.lang.NullPointerException at de.innot.avreclipse.core.ProjectTypeTester.test(ProjectTypeTester.java:90) at org.eclipse.core.internal.expressions.Property.test(Property.java:58) at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99) at org.eclipse.core.internal.expressions.NotExpression.evaluate(NotExpression.java:35) [...] This is due to a missing check in ProjectTypeTester.java: 86 if (KEY_STATIC_LIB.equalsIgnoreCase(property)) { 87 IManagedProject p = getManagedProject((IResource) receiver); 88 IBuildObjectProperties props = p.getBuildProperties(); 89 IBuildProperty prop = props.getProperty("org.eclipse.cdt.build.core.buildArtefactType"); 90 IBuildPropertyValue value = prop.getValue(); 91 if (value.getId().equals("de.innot.avreclipse.buildArtefactType.staticLib")) { 92 return true; 93 } ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928231&aid=3023252&group_id=189165 |
|
From: Zafi R. <zr...@ro...> - 2010-06-29 23:41:22
|
Hi all, I've just upgraded to Eclipse Galileo 3.5.2 and installed the last release of the AVR plugin. When selecting File -> Properties, no window appears. With Right-Click on a project, Properties does not appear in the menu list. See attached the corresponding log. In case it can help: I'm running Fedora 13, linux version 2.6.33.5-124. Regards, Zafi. |
|
From: SourceForge.net <no...@so...> - 2010-06-14 21:04:20
|
Support Requests item #3012263, was opened at 2010-06-07 01:58 Message generated for change (Comment added) made by manfbraun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3012263&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: Fixed Priority: 5 Private: No Submitted By: mabra (manfbraun) Assigned to: Thomas Holland (innot) Summary: Adding pathes to libraries does not work Initial Comment: Hello ! I am trying to add a reference to the LUFA library in my project and I cannot make it work. Although I see it in the includes in the eclipses project directory, the compiler always complains: "Building file: ../Descriptors.c Invoking: AVR Compiler avr-gcc -Wall -g2 -gstabs -O0 -fpack-struct -fshort-enums -funsigned-char -funsigned-bitfields -mmcu=atmega16 -DF_CPU=1000000UL -MMD -MP -MF"Descriptors.d" -MT"Descriptors.d" -c -o"Descriptors.o" "../Descriptors.c" In file included from ../Descriptors.c:38: ../Descriptors.h:42:36: warning: LUFA/Drivers/USB/USB.h: No such file or directory" Astoundingly, making a clean, shows another path: "make clean rm -f ./Descriptors.o ./GenericHID.o ./LUFA/Drivers/USB/LowLevel/DevChapter9.o " [Regard the dot and ther backslash in the last line!!] I am attaching an image, how my includes looks like. I tried every permutation: - copying the LUFA lib into a subdir - put it onto the same disk - everything else ;-) Even it is not possible to get rid of the references, I had to delete an re-create the project. I tried this with adding "includes" and "source location" in different manners [not really clear, how to make them :-( ]. But nothing helps. I need help! I am using the latest updates to eclipse and the plugin. I am using "Windows Server 2008 R2" (this is always x64), en, all patches. Just mentioning:All my other [small] projects - using avr-include "standards" are working well! Thanks a lot! ++mabra ---------------------------------------------------------------------- >Comment By: mabra (manfbraun) Date: 2010-06-14 23:04 Message: Hello ! I want to thanks you, very, very much! You explained really all for me and this brings a new step to my initial adaption training! Unbelievable, that you even made that avr project, I cannot thank you enough! Although I made a complete CMP86 BIOS [30 years ago ;-) ], I am like a beginner currently and have to find my avr-way [I mostly use NET/C#]. I must study your other details so. But my simple sample is just running! Much, much thanks! ++mabra [My added comment does not appear - so I add this comment :-( ] ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-06-10 23:15 Message: Hi mabra, getting the LUFA Libraries to work with managed build is indeed a bit tricky, as this "library" is designed for use with makefiles. So you could just switch Eclipse to 'makefile' mode and edit the demo makefiles to suit your needs. But it can be used in managed mode as well with some tweaking. I have been able to successfully build the GenericHID example that you seem to be using. Here are the steps required to recreate this: Create a new AVR Project and import the 'LUFA' directory from the LUFA zip file as well as the four files from the demo (Descriptors.c/.h & GenericHID.c/.h) into it. The LUFA source code expects the GNU99 C Standard, so change this in the project properties under C/C++ Build -> Settings -> Tool Settings -> AVR Compiler -> Language Standard. Then you need to fix the include paths. Two options -- the correct one would be to replace the brackets in all '#include <LUFA/...>" lines in the .h files with quotes (i.e. #include "LUFA/...". The LUFA Author should learn that brackets are only used for system supplied header files) The other option is to add the new project in the 'Include Paths' of itself. Then we need to set the defines for the project. If you take a look at the makefile(s) supplied by LUFA, you will see something like this: # LUFA library compile-time options LUFA_OPTS = -D USB_DEVICE_ONLY LUFA_OPTS += -D FIXED_CONTROL_ENDPOINT_SIZE=8 LUFA_OPTS += -D FIXED_NUM_CONFIGURATIONS=1 LUFA_OPTS += -D USE_FLASH_DESCRIPTORS LUFA_OPTS += -D USE_STATIC_OPTIONS="(USB_DEVICE_OPT_FULLSPEED | USB_OPT_REG_ENABLED | USB_OPT_AUTO_PLL)" Add all of them to the AVR-Compiler -> Symbols properties (without the -D) Then you need to tell Eclipse which files from LUFA you need compiled. Again take a look at the makefile on which files are actually needed: $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/DevChapter9.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/Endpoint.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/Host.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/HostChapter9.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/LowLevel.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/Pipe.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/USBInterrupt.c \ $(LUFA_PATH)/LUFA/Drivers/USB/HighLevel/ConfigDescriptor.c \ $(LUFA_PATH)/LUFA/Drivers/USB/HighLevel/Events.c \ $(LUFA_PATH)/LUFA/Drivers/USB/HighLevel/USBTask.c \ $(LUFA_PATH)/LUFA/Drivers/USB/Class/Device/HID.c \ $(LUFA_PATH)/LUFA/Drivers/USB/Class/Host/HID.c \ $(LUFA_PATH)/LUFA/Drivers/USB/Class/Host/HIDParser.c \ All other parts of LUFA would just increase the size of the final program without doing anything. So in the project properties go to 'C/C++ General -> Paths and Symbols -> Source Location', click on 'Add Folder' and add the LUFA/Drivers/USB folder. The project will still not build, because the LUFA/Drivers/USB folder has some unneeded files that will cause errors. In the Project Explorer expand the LUFA/Drivers/USB/LowLevel folder, right click on 'Templates' and select 'Exclude from Build' The same with all .c files (except HID.c) in the LUFA/Drivers/USB/Class/Device folder. Now the project should build cleanly (it did for me) I have attached a zip file with the project I created. If you have problems with the steps above you can import it into Eclipse and take a look at it. brgds, Thomas ---------------------------------------------------------------------- Comment By: mabra (manfbraun) Date: 2010-06-07 02:01 Message: Hi again! I would like to add two more attachments, but sourceforge migrates more and more to a pain :-) You can notify me via source forge [I think], so I can upload the images via email?? ++mabra ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3012263&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-06-10 21:15:16
|
Support Requests item #3012263, was opened at 2010-06-07 01:58 Message generated for change (Comment added) made by innot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3012263&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Pending >Resolution: Fixed Priority: 5 Private: No Submitted By: mabra (manfbraun) >Assigned to: Thomas Holland (innot) Summary: Adding pathes to libraries does not work Initial Comment: Hello ! I am trying to add a reference to the LUFA library in my project and I cannot make it work. Although I see it in the includes in the eclipses project directory, the compiler always complains: "Building file: ../Descriptors.c Invoking: AVR Compiler avr-gcc -Wall -g2 -gstabs -O0 -fpack-struct -fshort-enums -funsigned-char -funsigned-bitfields -mmcu=atmega16 -DF_CPU=1000000UL -MMD -MP -MF"Descriptors.d" -MT"Descriptors.d" -c -o"Descriptors.o" "../Descriptors.c" In file included from ../Descriptors.c:38: ../Descriptors.h:42:36: warning: LUFA/Drivers/USB/USB.h: No such file or directory" Astoundingly, making a clean, shows another path: "make clean rm -f ./Descriptors.o ./GenericHID.o ./LUFA/Drivers/USB/LowLevel/DevChapter9.o " [Regard the dot and ther backslash in the last line!!] I am attaching an image, how my includes looks like. I tried every permutation: - copying the LUFA lib into a subdir - put it onto the same disk - everything else ;-) Even it is not possible to get rid of the references, I had to delete an re-create the project. I tried this with adding "includes" and "source location" in different manners [not really clear, how to make them :-( ]. But nothing helps. I need help! I am using the latest updates to eclipse and the plugin. I am using "Windows Server 2008 R2" (this is always x64), en, all patches. Just mentioning:All my other [small] projects - using avr-include "standards" are working well! Thanks a lot! ++mabra ---------------------------------------------------------------------- >Comment By: Thomas Holland (innot) Date: 2010-06-10 23:15 Message: Hi mabra, getting the LUFA Libraries to work with managed build is indeed a bit tricky, as this "library" is designed for use with makefiles. So you could just switch Eclipse to 'makefile' mode and edit the demo makefiles to suit your needs. But it can be used in managed mode as well with some tweaking. I have been able to successfully build the GenericHID example that you seem to be using. Here are the steps required to recreate this: Create a new AVR Project and import the 'LUFA' directory from the LUFA zip file as well as the four files from the demo (Descriptors.c/.h & GenericHID.c/.h) into it. The LUFA source code expects the GNU99 C Standard, so change this in the project properties under C/C++ Build -> Settings -> Tool Settings -> AVR Compiler -> Language Standard. Then you need to fix the include paths. Two options -- the correct one would be to replace the brackets in all '#include <LUFA/...>" lines in the .h files with quotes (i.e. #include "LUFA/...". The LUFA Author should learn that brackets are only used for system supplied header files) The other option is to add the new project in the 'Include Paths' of itself. Then we need to set the defines for the project. If you take a look at the makefile(s) supplied by LUFA, you will see something like this: # LUFA library compile-time options LUFA_OPTS = -D USB_DEVICE_ONLY LUFA_OPTS += -D FIXED_CONTROL_ENDPOINT_SIZE=8 LUFA_OPTS += -D FIXED_NUM_CONFIGURATIONS=1 LUFA_OPTS += -D USE_FLASH_DESCRIPTORS LUFA_OPTS += -D USE_STATIC_OPTIONS="(USB_DEVICE_OPT_FULLSPEED | USB_OPT_REG_ENABLED | USB_OPT_AUTO_PLL)" Add all of them to the AVR-Compiler -> Symbols properties (without the -D) Then you need to tell Eclipse which files from LUFA you need compiled. Again take a look at the makefile on which files are actually needed: $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/DevChapter9.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/Endpoint.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/Host.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/HostChapter9.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/LowLevel.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/Pipe.c \ $(LUFA_PATH)/LUFA/Drivers/USB/LowLevel/USBInterrupt.c \ $(LUFA_PATH)/LUFA/Drivers/USB/HighLevel/ConfigDescriptor.c \ $(LUFA_PATH)/LUFA/Drivers/USB/HighLevel/Events.c \ $(LUFA_PATH)/LUFA/Drivers/USB/HighLevel/USBTask.c \ $(LUFA_PATH)/LUFA/Drivers/USB/Class/Device/HID.c \ $(LUFA_PATH)/LUFA/Drivers/USB/Class/Host/HID.c \ $(LUFA_PATH)/LUFA/Drivers/USB/Class/Host/HIDParser.c \ All other parts of LUFA would just increase the size of the final program without doing anything. So in the project properties go to 'C/C++ General -> Paths and Symbols -> Source Location', click on 'Add Folder' and add the LUFA/Drivers/USB folder. The project will still not build, because the LUFA/Drivers/USB folder has some unneeded files that will cause errors. In the Project Explorer expand the LUFA/Drivers/USB/LowLevel folder, right click on 'Templates' and select 'Exclude from Build' The same with all .c files (except HID.c) in the LUFA/Drivers/USB/Class/Device folder. Now the project should build cleanly (it did for me) I have attached a zip file with the project I created. If you have problems with the steps above you can import it into Eclipse and take a look at it. brgds, Thomas ---------------------------------------------------------------------- Comment By: mabra (manfbraun) Date: 2010-06-07 02:01 Message: Hi again! I would like to add two more attachments, but sourceforge migrates more and more to a pain :-) You can notify me via source forge [I think], so I can upload the images via email?? ++mabra ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3012263&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-06-07 00:01:20
|
Support Requests item #3012263, was opened at 2010-06-07 01:58 Message generated for change (Comment added) made by manfbraun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3012263&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: mabra (manfbraun) Assigned to: Nobody/Anonymous (nobody) Summary: Adding pathes to libraries does not work Initial Comment: Hello ! I am trying to add a reference to the LUFA library in my project and I cannot make it work. Although I see it in the includes in the eclipses project directory, the compiler always complains: "Building file: ../Descriptors.c Invoking: AVR Compiler avr-gcc -Wall -g2 -gstabs -O0 -fpack-struct -fshort-enums -funsigned-char -funsigned-bitfields -mmcu=atmega16 -DF_CPU=1000000UL -MMD -MP -MF"Descriptors.d" -MT"Descriptors.d" -c -o"Descriptors.o" "../Descriptors.c" In file included from ../Descriptors.c:38: ../Descriptors.h:42:36: warning: LUFA/Drivers/USB/USB.h: No such file or directory" Astoundingly, making a clean, shows another path: "make clean rm -f ./Descriptors.o ./GenericHID.o ./LUFA/Drivers/USB/LowLevel/DevChapter9.o " [Regard the dot and ther backslash in the last line!!] I am attaching an image, how my includes looks like. I tried every permutation: - copying the LUFA lib into a subdir - put it onto the same disk - everything else ;-) Even it is not possible to get rid of the references, I had to delete an re-create the project. I tried this with adding "includes" and "source location" in different manners [not really clear, how to make them :-( ]. But nothing helps. I need help! I am using the latest updates to eclipse and the plugin. I am using "Windows Server 2008 R2" (this is always x64), en, all patches. Just mentioning:All my other [small] projects - using avr-include "standards" are working well! Thanks a lot! ++mabra ---------------------------------------------------------------------- >Comment By: mabra (manfbraun) Date: 2010-06-07 02:01 Message: Hi again! I would like to add two more attachments, but sourceforge migrates more and more to a pain :-) You can notify me via source forge [I think], so I can upload the images via email?? ++mabra ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3012263&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-06-06 23:58:07
|
Support Requests item #3012263, was opened at 2010-06-07 01:58 Message generated for change (Tracker Item Submitted) made by manfbraun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3012263&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: mabra (manfbraun) Assigned to: Nobody/Anonymous (nobody) Summary: Adding pathes to libraries does not work Initial Comment: Hello ! I am trying to add a reference to the LUFA library in my project and I cannot make it work. Although I see it in the includes in the eclipses project directory, the compiler always complains: "Building file: ../Descriptors.c Invoking: AVR Compiler avr-gcc -Wall -g2 -gstabs -O0 -fpack-struct -fshort-enums -funsigned-char -funsigned-bitfields -mmcu=atmega16 -DF_CPU=1000000UL -MMD -MP -MF"Descriptors.d" -MT"Descriptors.d" -c -o"Descriptors.o" "../Descriptors.c" In file included from ../Descriptors.c:38: ../Descriptors.h:42:36: warning: LUFA/Drivers/USB/USB.h: No such file or directory" Astoundingly, making a clean, shows another path: "make clean rm -f ./Descriptors.o ./GenericHID.o ./LUFA/Drivers/USB/LowLevel/DevChapter9.o " [Regard the dot and ther backslash in the last line!!] I am attaching an image, how my includes looks like. I tried every permutation: - copying the LUFA lib into a subdir - put it onto the same disk - everything else ;-) Even it is not possible to get rid of the references, I had to delete an re-create the project. I tried this with adding "includes" and "source location" in different manners [not really clear, how to make them :-( ]. But nothing helps. I need help! I am using the latest updates to eclipse and the plugin. I am using "Windows Server 2008 R2" (this is always x64), en, all patches. Just mentioning:All my other [small] projects - using avr-include "standards" are working well! Thanks a lot! ++mabra ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=3012263&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-04-29 22:34:41
|
Feature Requests item #2994430, was opened at 2010-04-29 22:34 Message generated for change (Tracker Item Submitted) made by radbrad You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928234&aid=2994430&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Additional Functionality Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: radbrad (radbrad) Assigned to: Matthew McDougal (mmdoogie) Summary: Add an AVR Calculator Initial Comment: A great yet simple improvement would be to add a few calculators for commonly used items: - Timers (for all their modes, etc.) - Baud rate calculator I'll look at adding this in myself, but if anyone has experience ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928234&aid=2994430&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-03-29 10:01:49
|
Support Requests item #2871692, was opened at 2009-10-02 05:18 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=2871692&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Install Problem (example) Group: None Status: Open Resolution: Accepted Priority: 5 Private: No Submitted By: Dan Bock (bock2911) Assigned to: Thomas Holland (innot) Summary: AVR Plugin problem with OS X Initial Comment: I am trying to install this on my MAC (intel chipset). And i am having a problem with the system not able to recognize the AVR Dragon that I have. I did find that paths it is not able to find the "ATmel part description files system". I have just reinstalled the Crosspack. Is that in there? Am I missing something also? One last thing, when I turn on the program, I do get the following error: Description Resource Path Location Type Error launching external scanner info generator (avr-gcc -E -P -v -dD /Users/danielbock/Eclipse development/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c) Test_1 Unknown C/C++ Problem Any help would be great. Thanks. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2010-03-29 10:01 Message: Okay, after some looking around I found the option 'Create Parser Log File'. When using this option on avr/io.h (this file includes the correct header files for a specific platform) I got the following: Scanner problems: #warning encountered with text: "device type not defined" in file: /usr/local/CrossPack-AVR-20100115/avr-4/include/avr/io.h:404 When doing the same with the file I actually need (avr/iox128a1.h) I get: Scanner problems: #error encountered with text: "Include <avr/io.h> instead of this file." in file: /usr/local/CrossPack-AVR-20100115/avr-4/include/avr/iox128a1.h:38 The rest of the files are parsed correctly. My guess is that during indexation the device type is not set (correctly), which would explain why auto-completion doesn't work. Sadly, I don't know how to fix this. P.S. I'm the poster of the previous post, something went wrong with openid. ---------------------------------------------------------------------- Comment By: https://www.google.com/accounts () Date: 2010-03-26 23:16 Message: I'm having the same problem with the warning messages. I've found one solution, which involves disabling the 'Automate discovery of paths and symbols' option in the default Discovery profile (Debug by default). Of course this only takes care of the warnings themselves, not the actual problem. Note that the building of source code succeeds, proper hex files are being generated and the uploading via avrdude works. (I'm using an ATXmega128A1 with the AVRIsp mkII programmer). The only thing that doesn't seem to work correctly is auto-completion for the AVR specific registers and such (I'm assuming this has to do with the warnings). Weird thing is that when I press 'Open Declaration' on, for example <avr/interrupt.h>, the correct header file is opened... So why isn't this indexed, maybe because the correct environment couldn't be determined? Running the avr-gcc command in a shell works, and gives the same output when run on a Windows machine with the same setup (same eclipse versions + WinAVR + AVR Studio). I'm using: MacOSX 10.6.2 Snow Leopard Eclipse Galileo - Build id: 20100218-1602 (latest) AVR Eclipse plugin - Version: 2.3.1.20081204PRD (latest) CrossPack-AVR-20100115 P.S. The Atmel part description files can easily be copied from an AVR Studio installation, just put them somewhere on your drive (I put them in '/usr/local/CrossPack-AVR') and set a custom path to it within Eclipse... It should be approximately 52MB. ---------------------------------------------------------------------- Comment By: jonny (schugabe) Date: 2010-03-11 23:38 Message: I also have the external scanner problem. If this seems to be a general problem would it still help if I debug the plugin? If yes what should I do? ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-02-28 23:00 Message: Ok, this seems to be a common Mac problem. Could someone with the problem ("Error launching external scanner info generator") please open a simple terminal and enter 'avr-gcc'. I am curious if 'avr-gcc' is in the standard system path on a Mac (with the avr-gcc toolchain installed of course) If it is, then I am out of ideas and for further troubleshooting I would need some OSX user who would be willing to debug the plugin (it is not very difficult, although a little bit of Java expertise would be helpful) BTW, some googleing for the error message showed that this problem does not seem to be limited to the AVR Plugin but also occurs with other toolchains. ---------------------------------------------------------------------- Comment By: Mikko Saarisalo (mikkosaarisalo) Date: 2010-02-20 19:38 Message: +1 on the second problem. I do have the same observation on my MAC installation. ---------------------------------------------------------------------- Comment By: Dan Bock (bock2911) Date: 2009-10-09 04:49 Message: Thanks for the help. However, I still have the same error as before: Description Resource Path Location Type Error launching external scanner info generator (avr-gcc -E -P -v -dD /Users/danielbock/Eclipse development/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c) Test_1 U nknown C/C++ Problem The output from running the gcc is as follows: Using built-in specs. Target: avr Configured with: ../configure --target=avr --program-prefix=avr- --enable-languages=c --disable-libssp --disable-nls --with-dwarf2 Thread model: single gcc version 4.2.0 /usr/local/libexec/gcc/avr/4.2.0/cc1 -E -quiet -v -P /Users/danielbock/Eclipse development/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c -dD ignoring nonexistent directory "/usr/local/lib/gcc/avr/4.2.0/../../../../avr/sys-include" #include "..." search starts here: #include <...> search starts here: /usr/local/lib/gcc/avr/4.2.0/include /usr/local/lib/gcc/avr/4.2.0/../../../../avr/include End of search list. #define __STDC__ 1 #define __STDC_HOSTED__ 1 #define __GNUC__ 4 #define __GNUC_MINOR__ 2 #define __GNUC_PATCHLEVEL__ 0 #define __SIZE_TYPE__ unsigned int #define __PTRDIFF_TYPE__ int #define __WCHAR_TYPE__ int #define __WINT_TYPE__ unsigned int #define __INTMAX_TYPE__ long long int #define __UINTMAX_TYPE__ long long unsigned int #define __GXX_ABI_VERSION 1002 #define __USING_SJLJ_EXCEPTIONS__ 1 #define __SCHAR_MAX__ 127 #define __SHRT_MAX__ 32767 #define __INT_MAX__ 32767 #define __LONG_MAX__ 2147483647L #define __LONG_LONG_MAX__ 9223372036854775807LL #define __WCHAR_MAX__ 32767 #define __CHAR_BIT__ 8 #define __INTMAX_MAX__ 9223372036854775807LL #define __FLT_EVAL_METHOD__ 0 #define __DEC_EVAL_METHOD__ 2 #define __FLT_RADIX__ 2 #define __FLT_MANT_DIG__ 24 #define __FLT_DIG__ 6 #define __FLT_MIN_EXP__ (-125) #define __FLT_MIN_10_EXP__ (-37) #define __FLT_MAX_EXP__ 128 #define __FLT_MAX_10_EXP__ 38 #define __FLT_MAX__ 3.40282347e+38F #define __FLT_MIN__ 1.17549435e-38F #define __FLT_EPSILON__ 1.19209290e-7F #define __FLT_DENORM_MIN__ 1.40129846e-45F #define __FLT_HAS_DENORM__ 1 #define __FLT_HAS_INFINITY__ 1 #define __FLT_HAS_QUIET_NAN__ 1 #define __DBL_MANT_DIG__ 24 #define __DBL_DIG__ 6 #define __DBL_MIN_EXP__ (-125) #define __DBL_MIN_10_EXP__ (-37) #define __DBL_MAX_EXP__ 128 #define __DBL_MAX_10_EXP__ 38 #define __DBL_MAX__ 3.40282347e+38 #define __DBL_MIN__ 1.17549435e-38 #define __DBL_EPSILON__ 1.19209290e-7 #define __DBL_DENORM_MIN__ 1.40129846e-45 #define __DBL_HAS_DENORM__ 1 #define __DBL_HAS_INFINITY__ 1 #define __DBL_HAS_QUIET_NAN__ 1 #define __LDBL_MANT_DIG__ 24 #define __LDBL_DIG__ 6 #define __LDBL_MIN_EXP__ (-125) #define __LDBL_MIN_10_EXP__ (-37) #define __LDBL_MAX_EXP__ 128 #define __LDBL_MAX_10_EXP__ 38 #define __DECIMAL_DIG__ 9 #define __LDBL_MAX__ 3.40282347e+38L #define __LDBL_MIN__ 1.17549435e-38L #define __LDBL_EPSILON__ 1.19209290e-7L #define __LDBL_DENORM_MIN__ 1.40129846e-45L #define __LDBL_HAS_DENORM__ 1 #define __LDBL_HAS_INFINITY__ 1 #define __LDBL_HAS_QUIET_NAN__ 1 #define __DEC32_MANT_DIG__ 7 #define __DEC32_MIN_EXP__ (-95) #define __DEC32_MAX_EXP__ 96 #define __DEC32_MIN__ 1E-95DF #define __DEC32_MAX__ 9.999999E96DF #define __DEC32_EPSILON__ 1E-6DF #define __DEC32_DEN__ 0.000001E-95DF #define __DEC64_MANT_DIG__ 16 #define __DEC64_MIN_EXP__ (-383) #define __DEC64_MAX_EXP__ 384 #define __DEC64_MIN__ 1E-383DD #define __DEC64_MAX__ 9.999999999999999E384DD #define __DEC64_EPSILON__ 1E-15DD #define __DEC64_DEN__ 0.000000000000001E-383DD #define __DEC128_MANT_DIG__ 34 #define __DEC128_MIN_EXP__ (-6143) #define __DEC128_MAX_EXP__ 6144 #define __DEC128_MIN__ 1E-6143DL #define __DEC128_MAX__ 9.999999999999999999999999999999999E6144DL #define __DEC128_EPSILON__ 1E-33DL #define __DEC128_DEN__ 0.000000000000000000000000000000001E-6143DL #define __REGISTER_PREFIX__ #define __USER_LABEL_PREFIX__ #define __VERSION__ "4.2.0" #define __GNUC_GNU_INLINE__ 1 #define __NO_INLINE__ 1 #define __FINITE_MATH_ONLY__ 0 #define __AVR 1 #define __AVR__ 1 #define AVR 1 #define __AVR_ARCH__ 2 Is it the directory error my problem that it says is nonexistent? ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-03 20:09 Message: Hi Dan, the path to the "Atmel part description files" is currently unused by the plugin and therefore not required. (The Atmel Part Description files are part of the Atmel AVR Studio IDE [Only available for Windows] and AFAIK not available separately) So the problem with recognizing your Dragon must be somewhere else. Maybe you can provide the console output to see where it is failing. For your second problem: I haven't seen this error message so I don't know where it comes from and what is causing it. But a few things you could try: check that the file "/Users/danielbock/Eclipse development/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c" exists and is just a empty file (except for one newline). Second: execute the whole command ("avr-gcc -E -P -v -dD /Users/.../specs.c") from a shell to check if there is any problem with that. BTW the "Test_1" in the output. Is that the name of a / the Project? Thomas ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=2871692&group_id=189165 |
|
From: SourceForge.net <no...@so...> - 2010-03-26 23:16:13
|
Support Requests item #2871692, was opened at 2009-10-02 05:18 Message generated for change (Comment added) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=2871692&group_id=189165 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Install Problem (example) Group: None Status: Open Resolution: Accepted Priority: 5 Private: No Submitted By: Dan Bock (bock2911) Assigned to: Thomas Holland (innot) Summary: AVR Plugin problem with OS X Initial Comment: I am trying to install this on my MAC (intel chipset). And i am having a problem with the system not able to recognize the AVR Dragon that I have. I did find that paths it is not able to find the "ATmel part description files system". I have just reinstalled the Crosspack. Is that in there? Am I missing something also? One last thing, when I turn on the program, I do get the following error: Description Resource Path Location Type Error launching external scanner info generator (avr-gcc -E -P -v -dD /Users/danielbock/Eclipse development/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c) Test_1 Unknown C/C++ Problem Any help would be great. Thanks. ---------------------------------------------------------------------- Comment By: https://www.google.com/accounts () Date: 2010-03-26 23:16 Message: I'm having the same problem with the warning messages. I've found one solution, which involves disabling the 'Automate discovery of paths and symbols' option in the default Discovery profile (Debug by default). Of course this only takes care of the warnings themselves, not the actual problem. Note that the building of source code succeeds, proper hex files are being generated and the uploading via avrdude works. (I'm using an ATXmega128A1 with the AVRIsp mkII programmer). The only thing that doesn't seem to work correctly is auto-completion for the AVR specific registers and such (I'm assuming this has to do with the warnings). Weird thing is that when I press 'Open Declaration' on, for example <avr/interrupt.h>, the correct header file is opened... So why isn't this indexed, maybe because the correct environment couldn't be determined? Running the avr-gcc command in a shell works, and gives the same output when run on a Windows machine with the same setup (same eclipse versions + WinAVR + AVR Studio). I'm using: MacOSX 10.6.2 Snow Leopard Eclipse Galileo - Build id: 20100218-1602 (latest) AVR Eclipse plugin - Version: 2.3.1.20081204PRD (latest) CrossPack-AVR-20100115 P.S. The Atmel part description files can easily be copied from an AVR Studio installation, just put them somewhere on your drive (I put them in '/usr/local/CrossPack-AVR') and set a custom path to it within Eclipse... It should be approximately 52MB. ---------------------------------------------------------------------- Comment By: jonny (schugabe) Date: 2010-03-11 23:38 Message: I also have the external scanner problem. If this seems to be a general problem would it still help if I debug the plugin? If yes what should I do? ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2010-02-28 23:00 Message: Ok, this seems to be a common Mac problem. Could someone with the problem ("Error launching external scanner info generator") please open a simple terminal and enter 'avr-gcc'. I am curious if 'avr-gcc' is in the standard system path on a Mac (with the avr-gcc toolchain installed of course) If it is, then I am out of ideas and for further troubleshooting I would need some OSX user who would be willing to debug the plugin (it is not very difficult, although a little bit of Java expertise would be helpful) BTW, some googleing for the error message showed that this problem does not seem to be limited to the AVR Plugin but also occurs with other toolchains. ---------------------------------------------------------------------- Comment By: Mikko Saarisalo (mikkosaarisalo) Date: 2010-02-20 19:38 Message: +1 on the second problem. I do have the same observation on my MAC installation. ---------------------------------------------------------------------- Comment By: Dan Bock (bock2911) Date: 2009-10-09 04:49 Message: Thanks for the help. However, I still have the same error as before: Description Resource Path Location Type Error launching external scanner info generator (avr-gcc -E -P -v -dD /Users/danielbock/Eclipse development/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c) Test_1 U nknown C/C++ Problem The output from running the gcc is as follows: Using built-in specs. Target: avr Configured with: ../configure --target=avr --program-prefix=avr- --enable-languages=c --disable-libssp --disable-nls --with-dwarf2 Thread model: single gcc version 4.2.0 /usr/local/libexec/gcc/avr/4.2.0/cc1 -E -quiet -v -P /Users/danielbock/Eclipse development/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c -dD ignoring nonexistent directory "/usr/local/lib/gcc/avr/4.2.0/../../../../avr/sys-include" #include "..." search starts here: #include <...> search starts here: /usr/local/lib/gcc/avr/4.2.0/include /usr/local/lib/gcc/avr/4.2.0/../../../../avr/include End of search list. #define __STDC__ 1 #define __STDC_HOSTED__ 1 #define __GNUC__ 4 #define __GNUC_MINOR__ 2 #define __GNUC_PATCHLEVEL__ 0 #define __SIZE_TYPE__ unsigned int #define __PTRDIFF_TYPE__ int #define __WCHAR_TYPE__ int #define __WINT_TYPE__ unsigned int #define __INTMAX_TYPE__ long long int #define __UINTMAX_TYPE__ long long unsigned int #define __GXX_ABI_VERSION 1002 #define __USING_SJLJ_EXCEPTIONS__ 1 #define __SCHAR_MAX__ 127 #define __SHRT_MAX__ 32767 #define __INT_MAX__ 32767 #define __LONG_MAX__ 2147483647L #define __LONG_LONG_MAX__ 9223372036854775807LL #define __WCHAR_MAX__ 32767 #define __CHAR_BIT__ 8 #define __INTMAX_MAX__ 9223372036854775807LL #define __FLT_EVAL_METHOD__ 0 #define __DEC_EVAL_METHOD__ 2 #define __FLT_RADIX__ 2 #define __FLT_MANT_DIG__ 24 #define __FLT_DIG__ 6 #define __FLT_MIN_EXP__ (-125) #define __FLT_MIN_10_EXP__ (-37) #define __FLT_MAX_EXP__ 128 #define __FLT_MAX_10_EXP__ 38 #define __FLT_MAX__ 3.40282347e+38F #define __FLT_MIN__ 1.17549435e-38F #define __FLT_EPSILON__ 1.19209290e-7F #define __FLT_DENORM_MIN__ 1.40129846e-45F #define __FLT_HAS_DENORM__ 1 #define __FLT_HAS_INFINITY__ 1 #define __FLT_HAS_QUIET_NAN__ 1 #define __DBL_MANT_DIG__ 24 #define __DBL_DIG__ 6 #define __DBL_MIN_EXP__ (-125) #define __DBL_MIN_10_EXP__ (-37) #define __DBL_MAX_EXP__ 128 #define __DBL_MAX_10_EXP__ 38 #define __DBL_MAX__ 3.40282347e+38 #define __DBL_MIN__ 1.17549435e-38 #define __DBL_EPSILON__ 1.19209290e-7 #define __DBL_DENORM_MIN__ 1.40129846e-45 #define __DBL_HAS_DENORM__ 1 #define __DBL_HAS_INFINITY__ 1 #define __DBL_HAS_QUIET_NAN__ 1 #define __LDBL_MANT_DIG__ 24 #define __LDBL_DIG__ 6 #define __LDBL_MIN_EXP__ (-125) #define __LDBL_MIN_10_EXP__ (-37) #define __LDBL_MAX_EXP__ 128 #define __LDBL_MAX_10_EXP__ 38 #define __DECIMAL_DIG__ 9 #define __LDBL_MAX__ 3.40282347e+38L #define __LDBL_MIN__ 1.17549435e-38L #define __LDBL_EPSILON__ 1.19209290e-7L #define __LDBL_DENORM_MIN__ 1.40129846e-45L #define __LDBL_HAS_DENORM__ 1 #define __LDBL_HAS_INFINITY__ 1 #define __LDBL_HAS_QUIET_NAN__ 1 #define __DEC32_MANT_DIG__ 7 #define __DEC32_MIN_EXP__ (-95) #define __DEC32_MAX_EXP__ 96 #define __DEC32_MIN__ 1E-95DF #define __DEC32_MAX__ 9.999999E96DF #define __DEC32_EPSILON__ 1E-6DF #define __DEC32_DEN__ 0.000001E-95DF #define __DEC64_MANT_DIG__ 16 #define __DEC64_MIN_EXP__ (-383) #define __DEC64_MAX_EXP__ 384 #define __DEC64_MIN__ 1E-383DD #define __DEC64_MAX__ 9.999999999999999E384DD #define __DEC64_EPSILON__ 1E-15DD #define __DEC64_DEN__ 0.000000000000001E-383DD #define __DEC128_MANT_DIG__ 34 #define __DEC128_MIN_EXP__ (-6143) #define __DEC128_MAX_EXP__ 6144 #define __DEC128_MIN__ 1E-6143DL #define __DEC128_MAX__ 9.999999999999999999999999999999999E6144DL #define __DEC128_EPSILON__ 1E-33DL #define __DEC128_DEN__ 0.000000000000000000000000000000001E-6143DL #define __REGISTER_PREFIX__ #define __USER_LABEL_PREFIX__ #define __VERSION__ "4.2.0" #define __GNUC_GNU_INLINE__ 1 #define __NO_INLINE__ 1 #define __FINITE_MATH_ONLY__ 0 #define __AVR 1 #define __AVR__ 1 #define AVR 1 #define __AVR_ARCH__ 2 Is it the directory error my problem that it says is nonexistent? ---------------------------------------------------------------------- Comment By: Thomas Holland (innot) Date: 2009-10-03 20:09 Message: Hi Dan, the path to the "Atmel part description files" is currently unused by the plugin and therefore not required. (The Atmel Part Description files are part of the Atmel AVR Studio IDE [Only available for Windows] and AFAIK not available separately) So the problem with recognizing your Dragon must be somewhere else. Maybe you can provide the console output to see where it is failing. For your second problem: I haven't seen this error message so I don't know where it comes from and what is causing it. But a few things you could try: check that the file "/Users/danielbock/Eclipse development/.metadata/.plugins/org.eclipse.cdt.make.core/specs.c" exists and is just a empty file (except for one newline). Second: execute the whole command ("avr-gcc -E -P -v -dD /Users/.../specs.c") from a shell to check if there is any problem with that. BTW the "Test_1" in the output. Is that the name of a / the Project? Thomas ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=928232&aid=2871692&group_id=189165 |
