Ty,
Great! Let's tackle flashing the atmega328P. The setup I am using is "Arduino as ISP.
The wiring diagram and photo below.
I changed the code in file boot.txt but was not able to get that change to show up on the chip.
Using this sketch:// Atmega chip fuse detector
// Author: Nick Gammon
// Date: 19nd March 2017
// Version: 1.20
I now a chip with the following parameters:
Atmega chip detector.
Written by Nick Gammon.
Version 1.20
Compiled on Jan 30 2021 at 21:26:44 with Arduino IDE 10813.
Attempting to enter ICSP programming mode ...
Entered programming mode OK.
Signature = 0x1E 0x95 0x0F
Processor = ATmega328P
Flash memory size = 32768 bytes.
LFuse = 0xFF
HFuse = 0xDE
EFuse = 0xFD
Lock byte = 0xFF
Clock calibration = 0x95
Bootloader in use: Yes
EEPROM preserved through erase: No
Watchdog timer always on: No
Bootloader is 512 bytes starting at 7E00
So the lfuse is ok, hfuse OK, efuse reads 0xFD instead of Ox05.
EEPROM preserved through erase: No is this a problem.
I downloaded the V2 firmware. I adjust the #include to FWV2 or REV3 as appropriate for the board.
I place the atmega on an arduino board and flash the firmware.
Do you see any problems with the flash method?
More on the problems the chips display in the boards to follow. Thanks.
Is the chip you are trying to flash one of the ones that came with the clock kits??
If yes then you are working way to hard with that ICSP setup. All you have to do to flash a chip that already has a bootloader on it (as the ones from the clock kits do) is stick it in the socket on an UNO and flash it via USB from the IDE as you would any UNO. That's it.
Look into it later when the dust is clearing off the crater.
Okay then... but I wish you would just stick with the chips that came with your clocks for now so we can troubleshoot the clocks rather than troubleshooting ICSPs!
I got myself a copy of the Nick Gammon utilities just now. Ran it on a known good chip, compared it to your output. I see nothing glaringly wrong with what you got. Bootloader name and MD5 are the same. Fuses the same. Preserve EEPROM is set to No on mine but I do not think this is a big deal. Pretty sure yuo are better off with Preserev EEPROM Yes so once you get the clock firmware loaded and configure your settings can persist across uploads.
Look into it later when the dust is clearing off the crater.
I also just burned a bootloader onto a virgin 328P using the "Arduino_Board_Programmer" tool that was part of the Nick Gammon distribution I downloaded from github. So i guess you are on the right track with your setup.
Once the bootloader has been burned onto the new chip you should be able to proceed as per normal, i.e stick the new chip into an UNO and flash with the clock firmware in the normal USB manner.
Look into it later when the dust is clearing off the crater.