Closed Dlloydev closed 3 years ago
Yeah, already doing that for DxCore, planning to bring that back to megaTinyCore
On Sat, Oct 17, 2020 at 1:10 PM Dlloydev notifications@github.com wrote:
Can we get more options for Startup Time or a less aggressive minimum setting?
If using the ATtiny 0/1/2 parts as a HV programmer and the target has UPDI in GPIO mode, the HV pulse needs to be applied within 8.8ms after power-up. I find the 1ms option too aggressive and 8ms to close to the allowed limit. I've been measuring the power ramp-up of various circuits and find that it usually takes up to 2ms to get to > 90% of set voltage. In this case 2ms or 4ms are good options but unavailable.
MPLAB options:
[image: tempsnip] https://user-images.githubusercontent.com/63488701/96348850-cb21a880-1079-11eb-9f58-a52a5f1dde05.png
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/SpenceKonde/megaTinyCore/issues/251, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTXEWZJSGDJ4QAQG4ZMBMDSLHFXNANCNFSM4SUPP54Q .
--
Spence Konde Azzy’S Electronics
New products! Check them out at tindie.com/stores/DrAzzy GitHub: github.com/SpenceKonde ATTinyCore: Arduino support for almost every ATTiny microcontroller Contact: spencekonde@gmail.com
By the way, currently the 8ms option sets it to 4ms. I did a really lousy job on boards.txt in 2.1.0.....
Can we get more options for Startup Time or a less aggressive minimum setting?
If using the ATtiny 0/1/2 parts as a HV programmer and the target has UPDI in GPIO mode, the HV pulse needs to be applied within 8.8ms after power-up. I find the 1ms option too aggressive and 8ms to close to the allowed limit. I've been measuring the power ramp-up of various circuits and find that it usually takes up to 2ms to get to > 90% of set voltage. In this case 2ms or 4ms are good options but unavailable.
MPLAB options: