- Posts: 18
- Thank you received: 0
Modular clock problems
7 months 2 weeks ago #12366
by tgibbs99
Replied by tgibbs99 on topic Modular clock problems
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
Bootloader:
7E00: 0x11 0x24 0x84 0xB7 0x14 0xBE 0x81 0xFF 0xF0 0xD0 0x85 0xE0 0x80 0x93 0x81 0x00
7E10: 0x82 0xE0 0x80 0x93 0xC0 0x00 0x88 0xE1 0x80 0x93 0xC1 0x00 0x86 0xE0 0x80 0x93
7E20: 0xC2 0x00 0x80 0xE1 0x80 0x93 0xC4 0x00 0x8E 0xE0 0xC9 0xD0 0x25 0x9A 0x86 0xE0
7E30: 0x20 0xE3 0x3C 0xEF 0x91 0xE0 0x30 0x93 0x85 0x00 0x20 0x93 0x84 0x00 0x96 0xBB
7E40: 0xB0 0x9B 0xFE 0xCF 0x1D 0x9A 0xA8 0x95 0x81 0x50 0xA9 0xF7 0xCC 0x24 0xDD 0x24
7E50: 0x88 0x24 0x83 0x94 0xB5 0xE0 0xAB 0x2E 0xA1 0xE1 0x9A 0x2E 0xF3 0xE0 0xBF 0x2E
7E60: 0xA2 0xD0 0x81 0x34 0x61 0xF4 0x9F 0xD0 0x08 0x2F 0xAF 0xD0 0x02 0x38 0x11 0xF0
7E70: 0x01 0x38 0x11 0xF4 0x84 0xE0 0x01 0xC0 0x83 0xE0 0x8D 0xD0 0x89 0xC0 0x82 0x34
7E80: 0x11 0xF4 0x84 0xE1 0x03 0xC0 0x85 0x34 0x19 0xF4 0x85 0xE0 0xA6 0xD0 0x80 0xC0
7E90: 0x85 0x35 0x79 0xF4 0x88 0xD0 0xE8 0x2E 0xFF 0x24 0x85 0xD0 0x08 0x2F 0x10 0xE0
7EA0: 0x10 0x2F 0x00 0x27 0x0E 0x29 0x1F 0x29 0x00 0x0F 0x11 0x1F 0x8E 0xD0 0x68 0x01
7EB0: 0x6F 0xC0 0x86 0x35 0x21 0xF4 0x84 0xE0 0x90 0xD0 0x80 0xE0 0xDE 0xCF 0x84 0x36
7EC0: 0x09 0xF0 0x40 0xC0 0x70 0xD0 0x6F 0xD0 0x08 0x2F 0x6D 0xD0 0x80 0xE0 0xC8 0x16
7ED0: 0x80 0xE7 0xD8 0x06 0x18 0xF4 0xF6 0x01 0xB7 0xBE 0xE8 0x95 0xC0 0xE0 0xD1 0xE0
7EE0: 0x62 0xD0 0x89 0x93 0x0C 0x17 0xE1 0xF7 0xF0 0xE0 0xCF 0x16 0xF0 0xE7 0xDF 0x06
7EF0: 0x18 0xF0 0xF6 0x01 0xB7 0xBE 0xE8 0x95 0x68 0xD0 0x07 0xB6 0x00 0xFC 0xFD 0xCF
7F00: 0xA6 0x01 0xA0 0xE0 0xB1 0xE0 0x2C 0x91 0x30 0xE0 0x11 0x96 0x8C 0x91 0x11 0x97
7F10: 0x90 0xE0 0x98 0x2F 0x88 0x27 0x82 0x2B 0x93 0x2B 0x12 0x96 0xFA 0x01 0x0C 0x01
7F20: 0x87 0xBE 0xE8 0x95 0x11 0x24 0x4E 0x5F 0x5F 0x4F 0xF1 0xE0 0xA0 0x38 0xBF 0x07
7F30: 0x51 0xF7 0xF6 0x01 0xA7 0xBE 0xE8 0x95 0x07 0xB6 0x00 0xFC 0xFD 0xCF 0x97 0xBE
7F40: 0xE8 0x95 0x26 0xC0 0x84 0x37 0xB1 0xF4 0x2E 0xD0 0x2D 0xD0 0xF8 0x2E 0x2B 0xD0
7F50: 0x3C 0xD0 0xF6 0x01 0xEF 0x2C 0x8F 0x01 0x0F 0x5F 0x1F 0x4F 0x84 0x91 0x1B 0xD0
7F60: 0xEA 0x94 0xF8 0x01 0xC1 0xF7 0x08 0x94 0xC1 0x1C 0xD1 0x1C 0xFA 0x94 0xCF 0x0C
7F70: 0xD1 0x1C 0x0E 0xC0 0x85 0x37 0x39 0xF4 0x28 0xD0 0x8E 0xE1 0x0C 0xD0 0x85 0xE9
7F80: 0x0A 0xD0 0x8F 0xE0 0x7A 0xCF 0x81 0x35 0x11 0xF4 0x88 0xE0 0x18 0xD0 0x1D 0xD0
7F90: 0x80 0xE1 0x01 0xD0 0x65 0xCF 0x98 0x2F 0x80 0x91 0xC0 0x00 0x85 0xFF 0xFC 0xCF
7FA0: 0x90 0x93 0xC6 0x00 0x08 0x95 0x80 0x91 0xC0 0x00 0x87 0xFF 0xFC 0xCF 0x80 0x91
7FB0: 0xC0 0x00 0x84 0xFD 0x01 0xC0 0xA8 0x95 0x80 0x91 0xC6 0x00 0x08 0x95 0xE0 0xE6
7FC0: 0xF0 0xE0 0x98 0xE1 0x90 0x83 0x80 0x83 0x08 0x95 0xED 0xDF 0x80 0x32 0x19 0xF0
7FD0: 0x88 0xE0 0xF5 0xDF 0xFF 0xCF 0x84 0xE1 0xDE 0xCF 0x1F 0x93 0x18 0x2F 0xE3 0xDF
7FE0: 0x11 0x50 0xE9 0xF7 0xF2 0xDF 0x1F 0x91 0x08 0x95 0x80 0xE0 0xE8 0xDF 0xEE 0x27
7FF0: 0xFF 0x27 0x09 0x94 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x04 0x04
MD5 sum of bootloader = 0xFB 0xF4 0x9B 0x7B 0x59 0x73 0x7F 0x65 0xE8 0xD0 0xF8 0xA5 0x08 0x12 0xE7 0x9F
Bootloader name: optiboot_atmega328
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.
Tim
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
Bootloader:
7E00: 0x11 0x24 0x84 0xB7 0x14 0xBE 0x81 0xFF 0xF0 0xD0 0x85 0xE0 0x80 0x93 0x81 0x00
7E10: 0x82 0xE0 0x80 0x93 0xC0 0x00 0x88 0xE1 0x80 0x93 0xC1 0x00 0x86 0xE0 0x80 0x93
7E20: 0xC2 0x00 0x80 0xE1 0x80 0x93 0xC4 0x00 0x8E 0xE0 0xC9 0xD0 0x25 0x9A 0x86 0xE0
7E30: 0x20 0xE3 0x3C 0xEF 0x91 0xE0 0x30 0x93 0x85 0x00 0x20 0x93 0x84 0x00 0x96 0xBB
7E40: 0xB0 0x9B 0xFE 0xCF 0x1D 0x9A 0xA8 0x95 0x81 0x50 0xA9 0xF7 0xCC 0x24 0xDD 0x24
7E50: 0x88 0x24 0x83 0x94 0xB5 0xE0 0xAB 0x2E 0xA1 0xE1 0x9A 0x2E 0xF3 0xE0 0xBF 0x2E
7E60: 0xA2 0xD0 0x81 0x34 0x61 0xF4 0x9F 0xD0 0x08 0x2F 0xAF 0xD0 0x02 0x38 0x11 0xF0
7E70: 0x01 0x38 0x11 0xF4 0x84 0xE0 0x01 0xC0 0x83 0xE0 0x8D 0xD0 0x89 0xC0 0x82 0x34
7E80: 0x11 0xF4 0x84 0xE1 0x03 0xC0 0x85 0x34 0x19 0xF4 0x85 0xE0 0xA6 0xD0 0x80 0xC0
7E90: 0x85 0x35 0x79 0xF4 0x88 0xD0 0xE8 0x2E 0xFF 0x24 0x85 0xD0 0x08 0x2F 0x10 0xE0
7EA0: 0x10 0x2F 0x00 0x27 0x0E 0x29 0x1F 0x29 0x00 0x0F 0x11 0x1F 0x8E 0xD0 0x68 0x01
7EB0: 0x6F 0xC0 0x86 0x35 0x21 0xF4 0x84 0xE0 0x90 0xD0 0x80 0xE0 0xDE 0xCF 0x84 0x36
7EC0: 0x09 0xF0 0x40 0xC0 0x70 0xD0 0x6F 0xD0 0x08 0x2F 0x6D 0xD0 0x80 0xE0 0xC8 0x16
7ED0: 0x80 0xE7 0xD8 0x06 0x18 0xF4 0xF6 0x01 0xB7 0xBE 0xE8 0x95 0xC0 0xE0 0xD1 0xE0
7EE0: 0x62 0xD0 0x89 0x93 0x0C 0x17 0xE1 0xF7 0xF0 0xE0 0xCF 0x16 0xF0 0xE7 0xDF 0x06
7EF0: 0x18 0xF0 0xF6 0x01 0xB7 0xBE 0xE8 0x95 0x68 0xD0 0x07 0xB6 0x00 0xFC 0xFD 0xCF
7F00: 0xA6 0x01 0xA0 0xE0 0xB1 0xE0 0x2C 0x91 0x30 0xE0 0x11 0x96 0x8C 0x91 0x11 0x97
7F10: 0x90 0xE0 0x98 0x2F 0x88 0x27 0x82 0x2B 0x93 0x2B 0x12 0x96 0xFA 0x01 0x0C 0x01
7F20: 0x87 0xBE 0xE8 0x95 0x11 0x24 0x4E 0x5F 0x5F 0x4F 0xF1 0xE0 0xA0 0x38 0xBF 0x07
7F30: 0x51 0xF7 0xF6 0x01 0xA7 0xBE 0xE8 0x95 0x07 0xB6 0x00 0xFC 0xFD 0xCF 0x97 0xBE
7F40: 0xE8 0x95 0x26 0xC0 0x84 0x37 0xB1 0xF4 0x2E 0xD0 0x2D 0xD0 0xF8 0x2E 0x2B 0xD0
7F50: 0x3C 0xD0 0xF6 0x01 0xEF 0x2C 0x8F 0x01 0x0F 0x5F 0x1F 0x4F 0x84 0x91 0x1B 0xD0
7F60: 0xEA 0x94 0xF8 0x01 0xC1 0xF7 0x08 0x94 0xC1 0x1C 0xD1 0x1C 0xFA 0x94 0xCF 0x0C
7F70: 0xD1 0x1C 0x0E 0xC0 0x85 0x37 0x39 0xF4 0x28 0xD0 0x8E 0xE1 0x0C 0xD0 0x85 0xE9
7F80: 0x0A 0xD0 0x8F 0xE0 0x7A 0xCF 0x81 0x35 0x11 0xF4 0x88 0xE0 0x18 0xD0 0x1D 0xD0
7F90: 0x80 0xE1 0x01 0xD0 0x65 0xCF 0x98 0x2F 0x80 0x91 0xC0 0x00 0x85 0xFF 0xFC 0xCF
7FA0: 0x90 0x93 0xC6 0x00 0x08 0x95 0x80 0x91 0xC0 0x00 0x87 0xFF 0xFC 0xCF 0x80 0x91
7FB0: 0xC0 0x00 0x84 0xFD 0x01 0xC0 0xA8 0x95 0x80 0x91 0xC6 0x00 0x08 0x95 0xE0 0xE6
7FC0: 0xF0 0xE0 0x98 0xE1 0x90 0x83 0x80 0x83 0x08 0x95 0xED 0xDF 0x80 0x32 0x19 0xF0
7FD0: 0x88 0xE0 0xF5 0xDF 0xFF 0xCF 0x84 0xE1 0xDE 0xCF 0x1F 0x93 0x18 0x2F 0xE3 0xDF
7FE0: 0x11 0x50 0xE9 0xF7 0xF2 0xDF 0x1F 0x91 0x08 0x95 0x80 0xE0 0xE8 0xDF 0xEE 0x27
7FF0: 0xFF 0x27 0x09 0x94 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0xFF 0x04 0x04
MD5 sum of bootloader = 0xFB 0xF4 0x9B 0x7B 0x59 0x73 0x7F 0x65 0xE8 0xD0 0xF8 0xA5 0x08 0x12 0xE7 0x9F
Bootloader name: optiboot_atmega328
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.
Tim
Attachments:
Please Log in or Create an account to join the conversation.
- Ty_Eeberfest
-
- Offline
- Administrator
-
7 months 2 weeks ago #12367
by Ty_Eeberfest
Look into it later when the dust is clearing off the crater.
Replied by Ty_Eeberfest on topic Modular clock problems
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.
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.
Please Log in or Create an account to join the conversation.
7 months 2 weeks ago #12368
by tgibbs99
Replied by tgibbs99 on topic Modular clock problems
Yes, I understand I could that with old or factory chips. These are brand new blank chips.
I have been known to do things the hard way in the past, however.
Thanks
Tim
I have been known to do things the hard way in the past, however.
Thanks
Tim
Please Log in or Create an account to join the conversation.
- Ty_Eeberfest
-
- Offline
- Administrator
-
7 months 2 weeks ago #12369
by Ty_Eeberfest
Look into it later when the dust is clearing off the crater.
Replied by Ty_Eeberfest on topic Modular clock problems
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.
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.
Please Log in or Create an account to join the conversation.
- Ty_Eeberfest
-
- Offline
- Administrator
-
7 months 2 weeks ago #12370
by Ty_Eeberfest
Look into it later when the dust is clearing off the crater.
Replied by Ty_Eeberfest on topic Modular clock problems
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.
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.
Please Log in or Create an account to join the conversation.
- Ty_Eeberfest
-
- Offline
- Administrator
-
7 months 2 weeks ago #12371
by Ty_Eeberfest
Geez, so many typos in my post.
I want to re-state one thing: Preserve EEPROM through erase = NO appears to be normal and not anything to worry about.
Look into it later when the dust is clearing off the crater.
Replied by Ty_Eeberfest on topic Modular clock problems
Ty_Eeberfest wrote: Okay then....
Geez, so many typos in my post.
I want to re-state one thing: Preserve EEPROM through erase = NO appears to be normal and not anything to worry about.
Look into it later when the dust is clearing off the crater.
Please Log in or Create an account to join the conversation.
Time to create page: 0.101 seconds