Re: jtag3updi with attiny1604

[Doom]

Hi Andy,

Why this fork ?

Unfortunately, I encountered also problems while programming new component
in UPDI (ATmega4809).

So I found the repo of Martino Facchin (Senior Firmware Engineer @ Arduino)
on GitHub.
After some adjustment, it works for me. Unfortunately, my pull request was
not merged.

Then I changed of component to new AVR DA/DB family.
I encountered a lot of problems and find that UPDI component with page size
more that 256 were not supported.
Unfortunately I was unable to patch the problem.

But I found on official SVN a patch made by a guy of Microchip
(@janegilruud)
And I apply this patch to my fork (Apply svn patch #10000 from @janegilruud)

This is now merged in the Arduino repo : https://github.com/facchinm/avrdude

I gave you mine because I know this one works (changes have been done since
my pull request).

You can obviously open a pull request for adding your programmer.

D.




ᐧ

Le dim. 28 févr. 2021 à 17:10, Andy Bennett <andyjpb@ashurst.eu.org> a
écrit :

> Hi,
>
> > Maybe readsize  parameter is missing in the family.
> >
> > Can you tried the avrdude.conf (avrdude.conf.in) of the repo
> > : https://github.com/doom-fr/avrdude ?
> > You may override your current conf file with the -C option.
>
> Thanks. :-)
> That avrdude.conf.in file seems to work!
>
> ...but only after adding the definition for the jtag3updi progammer from
> the original avrdude.conf.in:
>
> -----
> programmer
>   id    = "jtag3updi";
>   desc  = "Atmel AVR JTAGICE3 in UPDI mode";
>   type  = "jtagice3_updi";
>   connection_type = usb;
>   usbpid = 0x2110, 0x2140;
> ;
> -----
>
>
>
> -----
> $ ~/project/.../avrdudue/installation/bin/avrdude -p t1604 -c jtag3updi -P
> usb -t
>
> avrdude: AVR device initialized and ready to accept instructions
>
> Reading |                                                    | 0%
> 0.00savrdude: bad response to read memory command: 0xa0
> Reading | ################################################## | 100% 0.01s
>
> avrdude: Device signature = 0x1e9425 (probably t1604)
> avrdude>
> -----
>
> I still get that "avrdude: bad response to read memory command: 0xa0"
> tho'.
> Do you know what that means?
>
>
>
> It seems to be able to read the flash, the fuses, prodsig and other
> regions
> too, which inspires some more confidence:
>
> -----
> avrdude> dump flash 0 200
> >>> dump flash 0 200
> 0000  00 00 81 81 00 00 04 04  00 00 00 00 00 00 00 00  |................|
> 0010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> 0020  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> 0030  00 00 00 00 00 00 00 00  00 00 00 00 00 00 3f 3f  |..............??|
> 0040  21 21 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |!!..............|
> 0050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> 0060  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> 0070  00 00 07 07 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> 0080  05 05 06 06 80 80 00 00  00 00 00 00 00 00 00 00  |................|
> 0090  00 00 0d 0d 00 00 00 00  00 00 00 00 00 00 00 00  |..  ............|
> 00a0  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> 00b0  21 21 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |!!..............|
> 00c0  00 00 00 00 00 00 00 00                           |........        |
>
> avrdude>
> -----
>
>
> > And if it does not work, you can also try the full avrdude
> > version of this repo.
>
> What's the main difference between the repos / reason for the fork? Which
> one is the official version?
>
>
>
> Thanks so much for your help!
>
> I really appreciate it. I'll try to program some parts now and see if I
> run
> into any more problems.
>
>
> Should I file a bug / send a patch for this?
>
>
>
>
> Best wishes,
> @ndy
>
> --
> andyjpb@ashurst.eu.org
> http://www.ashurst.eu.org/
> 0x7EBA75FF
>