[bug #14212] can't read atmega128 eeprom with Beta5.0

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[bug #14212] can't read atmega128 eeprom with Beta5.0

anonymous-27

URL:
  <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14212>

                 Summary: can't read atmega128 eeprom with Beta5.0
                 Project: AVR Downloader/UploaDEr
            Submitted by: None
            Submitted on: jeu 18.08.2005 � 10:05
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: Bernard Fouch�
        Originator Email:
             Open/Closed: Open

    _______________________________________________________

Details:

Hi.
Even with my patch that makes beta5.0 able to write to an atmega64/128 and
verify that the write is good, I just came to see that a single eeprom read
does not work.

For instance -U eeprom:r:/tmp/eeprom:i gives an hex file with only one line
:

:00000001FF

  Bernard






    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14212>

_______________________________________________
  Message post� via/par Savannah
  http://savannah.nongnu.org/



_______________________________________________
avrdude-dev mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

Re: [bug #14212] can't read atmega128 eeprom with Beta5.0

Joerg Wunsch
As anonymous wrote:

> Even with my patch that makes beta5.0 able to write to an atmega64/128 and
> verify that the write is good,

Btw., can you please upload that patch as an attachment to the bug tracker?

> I just came to see that a single eeprom read
> does not work.

I can confirm this, and this appears to be completely independent of
bug #13693 as I can observe similar behaviour through a JTAG ICE
connection.  Funny enough, it only affects EEPROM reads, other reads
(like the signature or calibration space) do work as expected.

--
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)


_______________________________________________
avrdude-dev mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

Re: [bug #14212] can't read atmega128 eeprom with Beta5.0

Bernard Fouché
Joerg Wunsch wrote:

>
>I can confirm this, and this appears to be completely independent of
>bug #13693 as I can observe similar behaviour through a JTAG ICE
>connection.  Funny enough, it only affects EEPROM reads, other reads
>(like the signature or calibration space) do work as expected.
>
>  
>
Are you able to flash and verify a bootloader with the JTAG ICE? There
is another bug that I saw with avrispv2/stk500v2 and that bug forbids
one to verify a bootloader.I think that it forbids to verify anything
not starting at 0x0000 but I wonder if it's avrispv2/stk500v2 related.

I'll upload the patch later this day and make a report for the 'can't
verify bootloader' problem if I did not yet. I'll also upload the patch
that offers device locking on Linux. I did it because once I forgot a
'minicom' in a background window and I went mad not understanding why I
was not able to reflash my target. It was on a portable PC and I had
only one USB/RS232 cable, to flash and to check the output of the target ;-)

 Bernard


_______________________________________________
avrdude-dev mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

Re: [bug #14212] can't read atmega128 eeprom with Beta5.0

Joerg Wunsch
As Bernard Fouché wrote:

> Are you able to flash and verify a bootloader with the JTAG ICE?

Yes, I've been successfully programming bootloaders into an ATmega128
via the JTAG ICE recently as part of my job.

--
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)


_______________________________________________
avrdude-dev mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

[bug #14212] can't read atmega128 eeprom with Beta5.0

anonymous-27
In reply to this post by anonymous-27

Follow-up Comment #1, bug #14212 (project avrdude):

Joerg confirms the this bug: (posted on avrdude-dev list 18/08):

"I can confirm this, and this appears to be completely independent of
bug #13693 as I can observe similar behaviour through a JTAG ICE
connection.  Funny enough, it only affects EEPROM reads, other reads
(like the signature or calibration space) do work as expected."

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14212>

_______________________________________________
  Message post� via/par Savannah
  http://savannah.nongnu.org/



_______________________________________________
avrdude-dev mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

[bug #14212] can't read atmega128 eeprom with Beta5.0

anonymous-27

Update of bug #14212 (project avrdude):

        Originator Email:                         =>
<[hidden email]>

    _______________________________________________________

Follow-up Comment #2:

I tried that with the recently suggested serial bit-bang
device I've still got lying around, and with an STK500v1
device and it works there.

So somehow, that problem is restricted to certain programmers
only, perhaps only stk500v2 and jtag2.  Note that the latter
has partially been cloned from the stk500v2 code, so it's
possible that a bug has been cloned as well.

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14212>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/



_______________________________________________
avrdude-dev mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev
Reply | Threaded
Open this post in threaded view
|

[bug #14212] can't read atmega128 eeprom with Beta5.0

anonymous-27

Update of bug #14212 (project avrdude):

                  Status:                    None => Fixed                  
             Assigned to:                    None => bdean                  
             Open/Closed:                    Open => Closed                


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?func=detailitem&item_id=14212>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/



_______________________________________________
avrdude-dev mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/avrdude-dev