Open GoogleCodeExporter opened 9 years ago
Check the auto-reset function again please. It seemed in 44 as if you had to
set the
auto-reset each time before uploading/connecting or else it wouldnt work.
One 'feature' i might suggest would be to add the option to 'reverse' the build
output so it writes from button to top - as well as the 'errors and warnings' -
that
way it's easier to keep track of whats happening as you could always see the
newest
item appearing.
Original comment by mamage...@gmail.com
on 22 Oct 2009 at 7:36
i'm not sure what is happening with the auto-reset, can you describe the
problem with
more detail? does the checkbox become magically unchecked?
I will reverse the ordering of the display
Original comment by frank.zhao.main@gmail.com
on 22 Oct 2009 at 12:54
Thanks for reversing the output - it is better that way (for me at least ;0))
The thing with auto-reset is like this. in V44 uploading to arduino didnt work,
you
had do decheck the reset, close the properties, open it up again, and recheck it
again. Then upload worked exactly one time (though you might have dont the
decheck/recheck thing again.)
Now in 47 even this seems not to work anymore. Checked it with a 328 and a
1280.. its
simply as if auto reset was turned off completely now.
Original comment by mamage...@gmail.com
on 24 Oct 2009 at 11:14
in 47 i can get autoreset working every time (i have a freeduino board to test),
might be a driver setting, try making sure "set RTS on close" is enabled
Original comment by frank.zhao.main@gmail.com
on 25 Oct 2009 at 4:34
There appears to be an issue with reading fuses/lock byte. Avrdude runs ok and
values get saved to a tempfile, but API nevertheless reports an error (there is
a
double slash between path and file name).
When using the "fuse calculator" and changing avrdude options/overrides
(including
part), the overrides are not used when calling avrdude. I've noticed that
you've
consistently avoided the Ok button (as a change commit) on dialogs - this
dialog
however would benefit from having one.
Original comment by bflaglie@c2i.net
on 27 Oct 2009 at 7:32
ok i see all the mistakes, will fix when i get home
i can add the ok button to all dialogs later
Original comment by frank.zhao.main@gmail.com
on 27 Oct 2009 at 12:48
fixed, and added option to discard changes on all dialogs
Original comment by frank.zhao.main@gmail.com
on 27 Oct 2009 at 11:14
I see that the double slash is gone, but the error remains (temporary file not
found). avrdude however writes lfuse/lock bytes
to "programdata\AVRProjectIDE\tempfuse.txt".
I used installer52 - Help/About shows Alpha51.
Original comment by bflaglie@c2i.net
on 28 Oct 2009 at 9:02
Quote
One 'feature' i might suggest would be to add the option to 'reverse' the build
output so it writes from button to top - as well as the 'errors and warnings
Unquote
This does not make sense to me at all. When we develop in C/C++, the compiler
works
its way from top to bottom and more often than not - an early error will
trigger
lots of followers. If you look to Visual Studio, the C/C++ compilers will even
abandon compile after a few errors in the same source file. Message being - fix
these first and I'll show you more. Top to bottom error reporting makes sense -
the
reverse does not.
Please change back or give us the option to choose.
Original comment by bflaglie@c2i.net
on 28 Oct 2009 at 1:40
added option to change build output behaviour
the bug with the fuse reading is really confusing, it works perfectly on my
computer,
i wonder what's going wrong on yours, i added the full expected file path to the
error messages
Original comment by frank.zhao.main@gmail.com
on 28 Oct 2009 at 10:39
Thanks again for the effort you out into this project.
As for fuse readings, the issue remains - temporary file not found.
"tempfile.txt"
does indeed exists and it will be created if I delete and run again. On your
trace
output there is an extra white space after the temp filename extension and the
full
stop (".. tempfuse.txt . Here is the .."), but this may of course come from
your
trace output formatting rather than the filename itself.
I've seen similar issues in the past on fast multicore CPU's when using
ShellExec.
The problem has been that you synchronize/wait on the shell rather that the
process
the shell invokes (avrdude in this case). To deal with this I've standardized
on
creating a small "RunCmd/MyExec" wrapper based on the .NET Process class
with "UseShellExec" set to false.
Original comment by bflaglie@c2i.net
on 29 Oct 2009 at 7:31
Fuse readings are working fine now - thanks.
There seems to be a small issue with the "Recent messages on top/bottom"
preference.
The setting is preserved between sessions (according to the peference dialog),
but
API still defaults to using "recent on top" unless I go into "Editor Settings"
and "Save Changes".
Original comment by bflaglie@c2i.net
on 5 Nov 2009 at 9:23
found the problem, fixed in 56
Original comment by frank.zhao.main@gmail.com
on 6 Nov 2009 at 1:10
Original issue reported on code.google.com by
frank.zhao.main@gmail.com
on 21 Oct 2009 at 1:13