.hex export option

[GoogleCodeExporter]

What change would like to see?
The possibility to export compiled .hex from temp directory directly from gui.

Why?
For programming no bootloaded chip or put into an emulator.

Would this cause any incompatibilities with previous versions?  If so, how
can these be mitigated?

Original issue reported on code.google.com by skywodd on 4 Mar 2011 at 4:05

[GoogleCodeExporter]

Arduino 1.0 will include the ability to select a programmer and uploading using 
a programmer directly from within the IDE, which I think will eliminate much of 
the need for a .hex export function.  Still, it's something I'd like to add at 
some point.

Original comment by dmel...@gmail.com on 7 Mar 2011 at 4:00

• Changed state: Accepted
• Added labels: Milestone-Post-1.0

[GoogleCodeExporter]

+1 to the above. 

But May I add that exporting the .o's and .elf would be helpful too for 
debugging (eg via jtag) and real time coding where you sometimes need to look 
at the asm generated.

Original comment by chris.ta...@gmail.com on 19 Mar 2011 at 8:34

[GoogleCodeExporter]

Issue 261 has been merged into this issue.

Original comment by dmel...@gmail.com on 15 Aug 2011 at 8:37

[GoogleCodeExporter]

As long as the result of one click in the IDE is a compiled hex file in my 
project directory, I will be happy. Right now having to hunt the file down in 
temp folders is incredibly annoying. 

Original comment by madsci1...@gmail.com on 13 Sep 2011 at 10:17

[GoogleCodeExporter]

Issue 641 has been merged into this issue.

Original comment by dmel...@gmail.com on 13 Sep 2011 at 11:48

[GoogleCodeExporter]

I do want to add an "export .hex file" option at some point, which would 
probably try to do something nice like give it a name that reflects the 
compilation options (e.g. include MCU and CPU speed, like 
blink_atmega328p_16.hex or similar).  But the actual build process will 
probably stay in a temporary directory.

Original comment by dmel...@gmail.com on 13 Sep 2011 at 11:49

[GoogleCodeExporter]

When you say "Export hex file option" I envision 3-4 mouse clicks: 
Compile(verify) then File -> Export hex -> (save hex file location dialog) then 
save. This is worse even then the current situation, and I'll try to explain 
why instead of sounding like a nit-pick. 

I use the Arduino IDE and libraries at work for one or few-off system rapid 
prototyping, mostly to take advantage of the large preexisting collection of 
hardware libraries. The custom AVR boards are usually encased inside pressure 
vessels that can't be easily opened, so I push firmware updates to the onboard 
computer and it updates the AVR via the bootloader. 

Some days during dev, I will compile and test 100 times in one day. Right now 
my day is usually goes : Compile once, find temp folder. Keep temp folder open, 
every time I hit verify copy new hex file over. Every once in a while, temp 
folder gets wiped, find new temp folder. repeat. 

Your suggestion of 3-4 mouse clicks each time will actually add time to this 
situation as I would have to click export every time. I would rather deal with 
the randomly changing temp folder instead of adding the mouse clicks. 

Instead, my suggestion is to turn back the clock to when the IDE used to 
compile to the projects temp folder, as this eliminates the randomly hoping 
temp folder without adding mouse clicks and more wasted time. A setting in the 
config that will either always skip the temp folder and compile directly to the 
project folder, or at least keep a copy in the project folder. 

Does that make sense to you?

Original comment by madsci1...@gmail.com on 14 Sep 2011 at 4:36

[GoogleCodeExporter]

Makes sense to me.  I would love extra functionality that is available to the 
advanced user.  All of the requests in this issue sound useful.  I think the 
developers want enough people requesting it though to justify the time to 
implement and maintain it.  Add my vote for direct programmer support, .O, .ELF 
and .HEX file exporting to the project directory.

Original comment by emailbr...@gmail.com on 14 Sep 2011 at 6:11

[GoogleCodeExporter]

OH, it is SO important to have the ability to get the hex file without having 
to chase the temp folders.

Add my plea

Ken H>

Original comment by sailing...@gmail.com on 22 Sep 2011 at 10:57