update signature row with tuned OSCCAL value

[nerdralph]

A few years ago I started working on a HV OSCCAL tuner that uses undocumented commands to modify the signature row calibration values. I got a prototype version working, and then started work to discover how to do it without HV. I was able to erase the signature page, but a couple attempts to brute force search for the write signature page command did not succeed.

I never got around to cleaning up the code, but after seeing your project I thought it would be a useful feature in HV mode to skip the use of EEPROM and just modify the OSCCAL value that gets loaded on reset. Here's the code:
https://github.com/nerdralph/piggy-prog/tree/master/PiggyTune

[wagiminator]

That would of course be fantastic. I was annoyed that the calibration bytes cannot be written to. When I find a little more time again, I try to understand your code and implement it for the calibrator.

[wagiminator]

I can't get it to work. If you have some time, please have a look:

`
// HVSP load flash page
void HVSP_loadPage(uint8_t addr_low, uint8_t data_low, uint8_t data_high) {
HVSP_sendInstr(addr_low, 0x0C); // Instr1: address low byte
HVSP_sendInstr(data_low, 0x2C); // Instr2: data low byte
HVSP_sendInstr(data_high, 0x3C); // Instr3: data high byte
HVSP_sendInstr(0x00, 0x7D); // Instr4
HVSP_sendInstr(0x00, 0x7C); // Instr5
}

// HVSP write signature page
void HVSP_writeSigPage(void) {
// erase signature page
HVSP_sendInstr(0x80, 0xCC); // Instr1: modified chip erase command
HVSP_sendInstr(0x00, 0x64); // Instr2
HVSP_sendInstr(0x00, 0x6C); // Instr3
HVSP_BUSY_WAIT(); // wait for erase cycle to finish
HVSP_sendInstr(0x00, 0x4C); // no operation command to finish erase

// load flash page
HVSP_sendInstr(0x10, 0x4C); // command to enter flash programming mode
HVSP_loadPage(0x00, signature >> 16, outCALIB0); // write signature 0 and calibration 0
HVSP_loadPage(0x01, signature >> 8, outCALIB1); // write signature 1 and calibration 1
HVSP_loadPage(0x02, signature, 0xFF); // write signature 2

// flush signature page
HVSP_sendInstr(0x93, 0x55); // Instr1
HVSP_sendInstr(0x00, 0x45); // Instr2
HVSP_sendInstr(0x00, 0x35); // Instr3
HVSP_BUSY_WAIT(); // wait for write cycle to finish
HVSP_sendInstr(0x00, 0x4C); // no operation command to finish erase
}
`

[nerdralph]

I can't see anything obvious. I'll have to set up my HV programmer to re-test the code. I had a t13 that had its signature page accidentally erased, and I was able to restore it, so I'm confident that part works. It looks like I didn't test the erase sig before I set the project aside for other priorites. There's some old AVRfreaks discussions about the undocumented commands. I'll check my bookmarks and add them to the code comments.

…

On Wed, Feb 3, 2021, 15:35 Stefan Wagner ***@***.***> wrote: I can't get it to work. If you have some time, please have a look: ` // HVSP load flash page void HVSP_loadPage(uint8_t addr_low, uint8_t data_low, uint8_t data_high) { HVSP_sendInstr(addr_low, 0x0C); // Instr1: address low byte HVSP_sendInstr(data_low, 0x2C); // Instr2: data low byte HVSP_sendInstr(data_high, 0x3C); // Instr3: data high byte HVSP_sendInstr(0x00, 0x7D); // Instr4 HVSP_sendInstr(0x00, 0x7C); // Instr5 } // HVSP write signature page void HVSP_writeSigPage(void) { // erase signature page HVSP_sendInstr(0x80, 0xCC); // Instr1: modified chip erase command HVSP_sendInstr(0x00, 0x64); // Instr2 HVSP_sendInstr(0x00, 0x6C); // Instr3 HVSP_BUSY_WAIT(); // wait for erase cycle to finish HVSP_sendInstr(0x00, 0x4C); // no operation command to finish erase // load flash page HVSP_sendInstr(0x10, 0x4C); // command to enter flash programming mode HVSP_loadPage(0x00, signature >> 16, outCALIB0); // write signature 0 and calibration 0 HVSP_loadPage(0x01, signature >> 8, outCALIB1); // write signature 1 and calibration 1 HVSP_loadPage(0x02, signature, 0xFF); // write signature 2 // flush signature page HVSP_sendInstr(0x93, 0x55); // Instr1 HVSP_sendInstr(0x00, 0x45); // Instr2 HVSP_sendInstr(0x00, 0x35); // Instr3 HVSP_BUSY_WAIT(); // wait for write cycle to finish HVSP_sendInstr(0x00, 0x4C); // no operation command to finish erase } ` — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKNZ6R5R7KGRVH2GEVUQPTS5GQR7ANCNFSM4W3MVNHQ> .

[nerdralph]

Here's one of the avrfreaks discussions about the signature commands.
https://www.avrfreaks.net/comment/165751#comment-165751

[wagiminator]

These are exactly the same instructions. I would agree with you that the first problem is with erasing the signature page. Since that does not work, writing to the page cannot work either.

[nerdralph]

I recall testing the AC C0 00 00 command to erase the signature page which is mentioned here:
https://www.avrfreaks.net/forum/undocumented-signature-row-contents?name=PNphpBB2&file=viewtopic&t=140556

It's been a while since I was working on this. The couple of files I found have dates from the summer of 2018. I'm certain I was able to erase and then re-program the signature page, but it's possible I was using the ICSP (low-voltage) command to erase the page, and then using the HV command to re-write the page.

I still plan to re-assemble my HV programming circuit, though I'm not sure how much more work I'll do on the OSCCAL tuning. As you probably have noticed, it's primarily the t13 that needs OSCCAL tuning. All my t85's have been within 1-2% of spec. And for people that want a simple way to tune the speed, I wrote picoboot-lib, which is an Arduino compatible serial bootloader with automatic OSCCAL tuning.

[wagiminator]

This is obviously an ICSP command. I will test it, but it will take a while, because I have to deal with the ICSP protocol first.
In fact, the ATtiny13 in particular needs OSCCAL tuning, but as you may have noticed, I like to use it a lot ;-)

[wagiminator]

So, I quickly implemented the ICSP protocol (it's even easier than HVSP), but unfortunately I still can't erase the signature page ;-(

[nerdralph]

So, I quickly implemented the ICSP protocol (it's even easier than HVSP), but unfortunately I still can't erase the signature page ;-(

That's interesting. I didn't have these problems, and I had found at least 2 other people on avrfreaks that had tested the undocumented commands. That leads me to two explanations:

1. Atmel/Microchip changed the method of factory programming the signature row.
2. You have a clone MCU which implements the documented functionality, but not the undocumented functionality.

Have you ever used debugWire on these t13s? Although it is documented in the datasheet that debugWire is supported, the actual protocol was never documented by Atmel. This would make it difficult for a clone to properly implement debugWire.
dwprog is my preferred debugWire tool:
https://github.com/nerdralph/dwprog

[wagiminator]

Aha, the second point might apply. I bought 50 ATtiny13A for € 10 on aliexpress. I'll try that with a few other chips (hopefully my ATtiny85 are original). However, if that is the problem, then either it makes no sense to implement this feature in the calibrator, or I would have to run a test before calibrating.

[nerdralph]

I agree. The mere presence of clones that don't work diminishes the value of the technique. And at the same time, it probably increases the need for tuning as a clone manufacturer is less likely to tune and program each die.

[wagiminator]

I have now tried it with several ATtiny13/25/85 in DIP and SMD packages, unfortunately still without success. But as far as I can remember, I bought all of them on Aliexpress, so that doesn't mean a lot. Of course, there is also the possibility that I have a mistake somewhere.

[nerdralph]

I started playing with HV programming again yesterday. Partially killed one of my t13s. I have an updated circuit with a PNP+NPN (similar to your pFET + NPN setup). Over the next few days I hope to at least have a schematic + code that works, so you can try to duplicate it.

The fact that you've tried multiple different parts leads me to believe there's something different in your setup than mine. I wouldn't rule out one batch of your AVRs being clones, but it seems unlikely all of them are. I think about half of my 8-pin AVRs were purchased from Asia.

It may be a red herring, but I had found the HVSP wasn't as simple as following the datasheet instructions, and the t13s I tested had significantly different timing than the t85s.
http://nerdralph.blogspot.com/2018/05/piggyfuse-hvsp-avr-fuse-programmer.html

[nerdralph]

I'm not able to get the "0xAC 0xC0 0 0" to erase the signature page either. I tried 2 t13s (SOIC & DIP), a t85, and a DIP t88 that I bought from Newark/Element14. However I know there is a way to erase the signature page because I built the HV programmer and re-wrote the signature page after I accidentally erased the signature page during regular programming when I forgot to connect VCC and ended up powering the target AVR through the protection diodes on the SCK and MOSI lines. The signature and calibration all read as 0xFF, and with the HV command I was able to restore the signature and OSCCAL.

Back in the summer of 2018, I wrote a program to try to find the LV serial programming command to write the calibration page by partial brute force. I was guessing what the first command byte would likely be, and the program runs through all 16.8 million possibilities for the next 3 bytes.

I think I'll move on to testing the HV commands. Once I get that working again I'll document my exact hardware & firmware setup so you can try to duplicate it.

[wagiminator]

Then I wish you maximum success! It remains exciting.