virtualdave
Well-known member
Question about HEX files.
I have an update to a sketch (via arduino) that I need to pass along to a client, however I don't want the client to have access to the sketch.
A little bit of sleuthing and I found buried deep inside the /private folder (I'm on a Mac, btw) the .hex file for the arduino sketch. It seems that via the Teensy app I can easily open this hex file and upload to the teensy (teensy 3.1 in case that matters). If I want my client to do the same, can I just send them this .hex file and the teensy app?
Also, how is it determined where the hex file gets stored when I compile on a mac? Right now the path is:
/private/var/folders/xx/m73qyzbj319cxpbjk9cl108m0000gp/T/build8890915754246587262.tmp/
Thanks in advance for any pointers!
Cheers,
David
I have an update to a sketch (via arduino) that I need to pass along to a client, however I don't want the client to have access to the sketch.
A little bit of sleuthing and I found buried deep inside the /private folder (I'm on a Mac, btw) the .hex file for the arduino sketch. It seems that via the Teensy app I can easily open this hex file and upload to the teensy (teensy 3.1 in case that matters). If I want my client to do the same, can I just send them this .hex file and the teensy app?
Also, how is it determined where the hex file gets stored when I compile on a mac? Right now the path is:
/private/var/folders/xx/m73qyzbj319cxpbjk9cl108m0000gp/T/build8890915754246587262.tmp/
Thanks in advance for any pointers!
Cheers,
David