Issues buring bootloader for ATtiny817 Xplained Mini and Xplained Pro #842
Labels
No Plans-or not viable
There are no plans to fix/change, and I do not even know that it can be
Not our bug
This is a bug in a third party tool and should be raised with the maintainers of that tool, if any.
Comments
|
Avrdude 7.0 will be used in some future version of the core. It categorically will not be going into 2.6.2 or DxC 1.5.0 and isn't going into anything until we have compile and upload working via the recommended method on all parts (including the DD-series parts on DxCore, which people are asking for constantly!!, all CI tests are passing, and nobody is screaming at me. A second rate microchip board based on substandard (small flash when larger flash is available, plus it's below the magic threshold that gets you a second whole adc, 2 more analog comparator, a full 2k of ram, etc? Not a priority. Especially since this is not is not a regression (at least not one that we can be blamed for) I would argue that rather than change avrdude to workaround their new bug, they should fix the bug in the new firmware.... |
|
I agree with delaying this to future. I think this board is not good for the bootloader. It works with the on-board programmer using avrdude-7.0. BTW, I do not have any issues to get the bootloader working with your DxCore for my AVR128DB48 Curiosity Nano board. |
|
BTW, just wondering if you have any concerns over ATtiny1616 issue mentioned here. I believe it is a user issue. But please help to confirm. Thanks. |
Apparently avrdude 7.0 and git main has an issue with optiboot_x. But megaTinyCore bundled version (avrdude 6.3 custom version by Arduino) works fine. |
|
It looks to me like a bug in 2.6.1 that I've partly fixed, thought your
logs suggest there's a bit more to it
2.6.2 is **very** close. I just need to finish a round of tweaks to wire
toget compile time errors I'd invalid values are passed to pins and swap.
It cand be made to worm perfectly, but it can be made to
BTW, I reiterate my offer of $25 in free merchandise from my store, shipped
for free within the US (international shipping charges have increased
six-fold since I started thst business, and I can't tank those on a whim -
at least not with stronger sales) for anyone who can make me a function
like badArg or badCall but which generates a warning if it is reachable
after constant folding.
…____________
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: ***@***.***
On Thu, Oct 6, 2022, 07:49 mcuee ***@***.***> wrote:
Two issues:
1. Arduino's avrdude 6.3 forks does not work with the latest FW of the
on-board debugger. It will even make the FW in a bad state.
Solution-- please upgrade to avrdude 7.0
Reference:
- avrdudes/avrdude#741 (comment)
<avrdudes/avrdude#741 (comment)>
C:\Users\xiaof\AppData\Local\Arduino15\packages\DxCore\tools\avrdude\6.3.0-arduino17or18/bin/avrdude -CC:\Users\xiaof\AppData\Local\Arduino15\packages\megaTinyCore\hardware\megaavr\2.6.1/avrdude.conf -v -pattiny817 -cxplainedmini_updi -Pusb -e -Ufuse0:w:0x00:m -Ufuse1:w:0x00:m -Ufuse5:w:0b1100010{bootloader.eesavebit}:m -Ufuse6:w:0x04:m -Ufuse8:w:0x00:m -Ufuse7:w:0x00:m -Uflash:w:C:\Users\xiaof\AppData\Local\Arduino15\packages\megaTinyCore\hardware\megaavr\2.6.1/bootloaders/hex/optiboot_XplainedPro817.hex:i
avrdude: Version 6.3-20201216
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch
System wide configuration file is "C:\Users\xiaof\AppData\Local\Arduino15\packages\megaTinyCore\hardware\megaavr\2.6.1/avrdude.conf"
Using Port : usb
Using Programmer : xplainedmini_updi
avrdude: Found CMSIS-DAP compliant device, using EDBG protocol
avrdude: jtag3_edbg_recv(): Inconsistent fragment number; expect 1, got 0
avrdude done. Thank you.
Error while burning bootloader.
1. There is still another issue from the above prompt: the menu is
missing for the {bootloader.eesavebit}.
—
Reply to this email directly, view it on GitHub
<#842>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTXEW2NI6FMH5XUOZCNJ73WB24DBANCNFSM6AAAAAAQ6Q5OBE>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
|
I think I will not worry about the bootloader for now. The work-around to use avrdude 7.0 or git main is to export the hex file from megaTinyCore. It works fine. |
SpenceKonde
added
No Plans-or not viable
|
FYI as well, from here. For those who are more adventurous, you can try the Windows binary mentioned in this thread. I have tested it with DxCore, megaTinyCore and MegaCoreX. It is based on avrdude git main (with many fixes over 7.0 release). I have also built Linux and macOS binaries here (32 bitLinux x86, 64bit macOS x86_64). |
|
You can also try the binaries here. I need to use the 64bit Linux binary under 64bit Linux (no 32bit compatibility layer installed). More discussions here. |
|
Choosing the other hex file works for ATtiny817 Xplained Mini (LED is PC0/Pin12). |
|
Same bootloader also works for ATtiny817 Xplained Pro (just the LED pin is different at PB4/Pin7 for the blink sketch). |
|
Fuse settings for reference: |
|
Basically just choose generic ATtiny817 board with optiboot and do not choose Microchip official board with optiboot. UART pins for the bootloader are PB2/PB3. |
|
Can someone summarize wtf is wrong with that bootloader file and whether it can be fixed? The only thing that should be different is which bloody pin it blinks? |
|
I will try to summarize.
|
mcuee
changed the title
|
Using avrdude git main to illustrate the problem. The default optiboot hex file Note to myself: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Three issues:
Solution-- please upgrade to avrdude 7.0
Reference:
There is still another issue from the above prompt: the menu is missing for the {bootloader.eesavebit}.
There is no hex file
bootloaders/hex/optiboot_XplainedPro817.hex, rather the hex file is justoptiboot_xplained817.hex.The text was updated successfully, but these errors were encountered: