Re: [bug #61624] [Feature request] Serial/UART UPDI programmers

Hey, Sorry for going AWOL for a while, but as I wrote last time, I was waiting for tinyAVR chips. They have arrived, and in the meantime I worked a bit on the USERROW functionality. It works, but let’s discuss it another time, it’s another one of these rabbit holes. Anyway, I still want to

Re: [bug #61624] [Feature request] Serial/UART UPDI programmers

As Dawid Buchwald wrote: > There is, however, one more thing that mcudude mentioned - at the > end of programming AVRDUDE would list values of lfuse/hfuse/efuse in > its goodbye message. It is pretty irrelevant to the modern chips, > since they don’t really have any of these, they just have array

Re: [bug #61624] [Feature request] Serial/UART UPDI programmers

Thanks for the detailed explanation. This use case (lousy parallel port connection) makes sense, and indeed, this is not applicable to the SerialUPDI implementation. In fact, with how the NVM model works it’s actually impossible to change fuses by accident (like writing to flash at incorrect

Re: [bug #61624] [Feature request] Serial/UART UPDI programmers

On Wed, Dec 15, 2021 at 7:18 AM Joerg Wunsch wrote: > > As Dawid Buchwald wrote: > > > After some more investigation I concluded that there are actually > > different scenarios where Safemode is disabled, so I would really > > leave that for now. > > Just as a side-note, and since there is also

Re: [bug #61624] [Feature request] Serial/UART UPDI programmers

As Dawid Buchwald wrote: > After some more investigation I concluded that there are actually > different scenarios where Safemode is disabled, so I would really > leave that for now. Just as a side-note, and since there is also one large patch regarding safemode which I decided to not apply

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #24, bug #61624 (project avrdude): Let me start with reply, followed by status update. > Makes me wonder why they didn't just come up with one mode to rule them all, instead of three. I suppose this is because they are in process of finalising the design? I have no idea, but I

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #23, bug #61624 (project avrdude): > Not a noob question, it's really confusing. According to sources of pymcuprog there are actually three families: 0 (tiny), 2 (AVR Dx) and 3 (AVR EA). Family 1 has never been mentioned there. Makes me wonder why they didn't just come up with

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #22, bug #61624 (project avrdude): > I only own tiny1-series chips, so I tested on ATtiny416 and ATtiny817. Thanks for confirmation. I will get myself the other types as well then. > Probably a noob question, but does there exist an NVM 1 family? Not a noob question, it's

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #21, bug #61624 (project avrdude): > What attiny0 chips are you using? Sorry, I forgot to tell you. I only own tiny1-series chips, so I tested on ATtiny416 and ATtiny817. >So yeah, plenty to do, but I'm glad the basic use cases (burning flash, setting fuses, writing to

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #20, bug #61624 (project avrdude): Hello again! I'm really happy to hear that it works fine with other chips as well. At this point I will focus on some code refactoring and cleanup, because some of the code written today was just a quick and dirty implementation. For the other

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #19, bug #61624 (project avrdude): Hello again Dawid! I can confirm that I can correctly read and write to flash on both devices (I've just tested a couple of blink programs). I can also confirm that writing fuses and reading them back also works perfectly. I've also tried to

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #18, bug #61624 (project avrdude): I just tested reading from and writing to EEPROM on an ATmega4808 and ATmega4809, and it seems to work just fine. I've loaded various hex files, and the content read from EEPROM is always correct. It's also very fast, reading and writing take

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #17, bug #61624 (project avrdude): Hey, thanks a lot for your help! I'm happy to hear that it's working now. For the EEPROM issue - I found it and the fix is already in the version you have (svn update/svn info should give you revision 1520 or later). I was able to write/read

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #16, bug #61624 (project avrdude): Hi! I have now tested your latest version on ATmega4809, 3209, 4808, and 3208, and everything seems to be working fine. All fuses are set and read back correctly, and I'm not getting any segment errors anymore. I also have some tinyAVRs lying

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #15, bug #61624 (project avrdude): Hey, I have just posted another fix that should take care of the fuse write. Sorry for all the inconvenience. I would really appreciate if you could check it and let me know if it works correctly now. I just noticed another issue, related to

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #14, bug #61624 (project avrdude): > Yeah, I just checked and the same issue occurs when trying to save to AVR128DB28 fuses. I think I know what this is, working on a fix now, should have it ready in a moment. Will let you know when it's ready. Great! I'm about to leave for

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #13, bug #61624 (project avrdude): Yeah, I just checked and the same issue occurs when trying to save to AVR128DB28 fuses. I think I know what this is, working on a fix now, should have it ready in a moment. Will let you know when it's ready.

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #12, bug #61624 (project avrdude): I can confirm that the uploaded program works as expected. It looks like it's reading incorrect fuses on ATmega4809 as well. Tri's trying to write 0xCD, but reads back 0x40. And now I'm getting a segmentation fault when trying to set fuses on

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #11, bug #61624 (project avrdude): Hey, I'm glad to hear that at least flash programming works correctly now. I assume that once uploaded, programs work as expected? Could you confirm this? As for the atmega4808 failure during fuse setting, there are actually two problems

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #10, bug #61624 (project avrdude): Thanks Dawid, reading from flash now works in the ATmega4809! Just for curiosity and since I have all megaAVR-0 series chips, I decided to try them all. Uploading and fuse read/write works on ATmega4809, ATmega3208, ATmega1608, and ATmega808.

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #9, bug #61624 (project avrdude): Thanks a lot for your support, I really appreciate the time and effort. I think I have a fix for you. What you have to do is: svn update make clean all You expect following output: ➜ avrdude> svn update Updating '.': Userialupdi.c

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #8, bug #61624 (project avrdude): > First of all, thank you A LOT for your time and I'm really sorry it didn't work for you. Unfortunately, I don't own any other UPDI based MCUs, and there are apparently three different programming models for those, so I need to do some shopping

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #7, bug #61624 (project avrdude): First of all, thank you A LOT for your time and I'm really sorry it didn't work for you. Unfortunately, I don't own any other UPDI based MCUs, and there are apparently three different programming models for those, so I need to do some shopping

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #6, bug #61624 (project avrdude): No worries! I was able to build after following your instructions. It would be really nice if the DTR/RTS pulse could stay low during the entire Avrdude session. At the moment there seem to be two short (250us) pulses, one at the start and one

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #5, bug #61624 (project avrdude): Sorry, should have been clearer. You should do the following: svn co svn://svn.savannah.nongnu.org/avrdude/branches/serialupdi/avrdude cd avrdude ./bootstrap ./configure make all ./avrdude -C ./avrdude.conf -p avr128db28 -b 230400 -c

Re: [bug #61624] [Feature request] Serial/UART UPDI programmers

As mcudude wrote: > One issue though. I've been using git for years, but never ever touched svn. > Embarrassing question, how do I clone your repo/fork? I've tried various > commands, but I always end up with an empty serialupdi folder. You do not "clone" it, you "checkout" (or just "co") it. In

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #4, bug #61624 (project avrdude): Hi David! I'd love to try it out on various targets. I have lots of different chips I can try it out on. One issue though. I've been using git for years, but never ever touched svn. Embarrassing question, how do I clone your repo/fork? I've

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #3, bug #61624 (project avrdude): Hello, I have some good news for you - I have first alpha version of the SerialUPDI programmer. I hope you can give it a spin and let me know if it works for you. I'm using FT232RL chip with a diode between Rx and Tx, 1K resistor between Tx and

[bug #61624] [Feature request] Serial/UART UPDI programmers

Follow-up Comment #2, bug #61624 (project avrdude): Sorry for not creating this issue with my actual account. I totally forgot that I had one! Anyways, I'm very excited about this, but also for the fact that there finally is some work done to Avrdude. It is after all an invaluable tool for SO

[bug #61624] [Feature request] Serial/UART UPDI programmers

Update of bug #61624 (project avrdude): Status:None => In Progress Assigned to:None => dawidbuchwald ___ Follow-up Comment #1: Dawid already

[bug #61624] [Feature request] Serial/UART UPDI programmers

URL: Summary: [Feature request] Serial/UART UPDI programmers Project: AVR Downloader/UploaDEr Submitted by: None Submitted on: Mon 06 Dec 2021 11:57:08 AM UTC Category: None