-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
megaTinyCore optiboot_x issue with avrdude git main -- FALSE ALARM #1166
Comments
Now we need to revisit the following two, or avrdude.conf for the ATTiny1627 and other ATtiny 0/1/2 devices.
|
Just wondering if you can help checking on megaTinyCore and MegaCoreX. Thanks. |
@mcuee sure! I'm currently on vacation, and didn't brought the right hardware with me. @mcuee meanwhile, can you try to change Lines 762 to 772 in b569966
It is strange that it doesn't work with Avrdude 7.0, since no major changes to stk500.c was done after the project was migrated over to Github. Can you try with Avrdude 6.4? The follwing commit is present in Avrdude 6.4 and later, but not in 6.3. Can you try to revert this as well? If this doesn't help, please try to roll even further back to see if you can narrow it down to a single commit: |
@mcuee from the output you provided, It doesn't look like you actually tested
Also, you shouldn't use the |
Looks like a megaTinyCore issue to me now. I use Arduino IDE 2.0.1 and now it okay to burn the bootloader (no need to manually using avrdude) and upload the sketch. Take note I am using avrdude git master and not avrdude 6.3.
|
Howver, it is actually not working if I verify using the on-board pkobn_updi programmer.
|
I am going to close this one as invalid for now as the bootloader does not seem to work at all for the ATtiny1627 Curiosity Nano board. Arduino IDE 2.0.1 somehow can not display the menu option for I am using the other option However, sketch upload still fails. For Arduino 2.0.1, sketch uploading appears to pass but then verify using the on_board programmer shows that it fails in reality. |
I find it hard to believe that Optiboot doesn't work on the ATtiny1627. I believe Spence would have tested this. Since I don't have the correct hardware at hand, can you test this @mcuee?
Here's an
|
@MCUdude The Tiny2 series is supposed to be easier with optiboot_x and it indeed seem to be so (to configure PB4 as the alternative reset pin). I do not really need to use the 8s trick. The only problem is that it does not seem to write to the flash. Edit to add: |
Thanks for the advice, I think the issue is with And it works fine. I verified with the on-board pkobn_updi as well.
|
I'd like to see the possibility of using optiboot_x on the ATmega4808 based Nano 4808 board. I understand that you do not support it with optiboot_x in MegaCoreX. Just wondering what is the reason. Thanks. If I am willing to use PICKit 4 HV UPDI with the board (I have two boards now and another on-order, so I can sacrifice one just in case), is it possible to use optiboot_x? I see that you also do not support optiboot_x for Arduino Nano Every (ATmega4809), I believe it is based on the same reason. I have one official board. What about Microchip ATmega4809 Curiosity Nano board? I do not have the board but I may be able to get one in the future (out of stock as of now from local onlone shops). |
Thank you @mcuee for carrying out the test, even if it's a little boring and kinda time-consuming. Now we know that the upstream version of Avrdude works with optiboot_x for ATtinys, and that's a good thing! I'll perform the same tests on different ATtiny hardware when I'm back home, just to back your conclusion.
My "3rd party Arduino core philosophy" has always been to greatly extend the original Arduino AVR core in terms of features, performance, and hardware compatibility, but not to give the user a bunch of choices in the Arduino Tools menu that 99.9% of the users wouldn't really care about. I believe this is the reason most of my Arduino cores have become quite popular, while the number of reported issues/questions is quite low. Optiboot on the Nano 4808/4809 is on paper a good idea since the upload speed would be greatly improved. However, the last time I had a look at this, the IDE had a few quirks that made it difficult to implement bootloader upload while still maintaining a user interface the average user could make sense of. From the top of my head, here's one of the main obstacles I stumbled across:
However, I've compiled a bootloader binary with an 8-second timeout on power-on that you could use for Nano 4808/4809 optiboot testing. But I don't find the Nano 4808/4809 board to be convenient enough for bootloader use that I would give MegaCoreX users this option. (Suitable for the Nano Every 4809) (Suitable for the Nano 4808) |
@MCUdude Thanks a lot for the bootloaders. The one for Arduino Nano Every seems to work fine.
|
But the one for Mega4808 does not seem to work. I will need to double check if the fuse settings play a part or not.
|
In the end, it is due to the wrong fuse8 setting. Once I fixed the fuse8 setting, it works fine.
|
I have learned to choose the right hex file (
Ref: 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.
|
Interestingly I got a Nano4808 clone where the on-board jtag2updi does not work (only work once to upload the optiboot hex file and then can not talk the board). Luckily I used the PICkit4 to change the fuse settings and now it works okay. |
Could you also tell me how to build the hex file for ATmega4809 Curiosity Nano? I just got the board. The following command generated a bootloader (8s delay, UART3, LED is B5) which works only one time. After uploading the blink hex file it no longer works. The fuse should be correct.
Run log:
|
I can not get avrdude git main to work with megaTinyCore optiboot_x using ATtiny1627 Curiosity Nano board.
More details here.
avrdude 7.0 also does not work.
But avrdude 6.3 from megaTinyCore works fine, verified with the on-board pkobn_updi programmer as well.
The text was updated successfully, but these errors were encountered: