pert:
This will set the fuses and also burn the bootloader. I know you don't need the bootloader since you're uploading via Sketch > Upload Using Programmer but the bootloader will just be erased the next time you upload so it doesn't make a difference other than taking a little more time to set the fuses, that's just the way the Arduino IDE it set up to work. You can use the same process to adjust any of the fuse setting you like.
TQVM on the detail explanation!
Will setting the high fuse (EESave) via board.txt will help me to maintain the EEPROM value after new program upload?
Prior to this, I developed my program using Arduino Uno board. First I upload the program with eeprom_put function to burn the initial EEPROM value, and then I upload my actual program. Now that I have a custom board and upload the program using USBtinyISP, this method doesnt work anymore because the EEPROM is cleared.
Sorry for the noob question...
pert:
If you end up wanting to keep a customized boards.txt file separate from the Arduino AVR Boards boards.txt it's fairly easy to install one at {sketchbook folder}/hardware. This file will not be affected by any IDE or Arduino AVR Boards updates. I can provide more information if you want to do that.
Yes, I would like to learn how to create customized board.txt. However I'm using macbook, is the steps going to be similar?
Thanks in advance for all ur help!