Re: [avrdude-dev] JTAG ICE mkI support added

[Brian Dean]

On Sat, Nov 26, 2005 at 07:53:22AM +0100, Joerg Wunsch wrote:

> > I hope to do some testing with your new code this
> > weekend.
> 
> Yes, please do.  I don't have a mkI device anymore, so all my tests
> have been run against a quick'ndirty clone built up from an STK500.

Avrdude cannot seem to initialize the JTAGICE from a cold power-on.
Here's what I get when attempting to access it from a power-on reset
of the JTAGICE:

address@hidden:/obj- ./avrdude -p m128 -c jtag1 -P /dev/cu.USA19Hb11P1.1 -v -v 
-v -v

avrdude: Version 5.0cvs
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/

         System wide configuration file is "/opt/local/etc/avrdude.conf"
         User configuration file is "/Users/bsd/.avrduderc"

         Using Port            : /dev/cu.USA19Hb11P1.1
         Using Programmer      : jtag1
avrdude: jtagmkI_open()
avrdude: jtagmkI_open(): trying to sync at baud rate 19200:
avrdude: jtagmkI_resync()
avrdude: jtagmkI_resync(): Sending sync command: avrdude: Send:   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: jtagmkI_resync(): Sending sync command: avrdude: Send:   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: jtagmkI_resync(): Sending sync command: avrdude: Send:   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: jtagmkI_resync(): Sending sync command: avrdude: Send:   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: jtagmkI_resync(): Sending sync command: avrdude: Send:   [20] 
avrdude: ser_recv(): programmer is not responding
avrdude: jtagmkI_resync(): timeout/error communicating with programmer
avrdude: jtagmkI_open(): trying to sync at baud rate 115200:
avrdude: jtagmkI_resync()

.... cycle throught 115200, 9600, 38400, and 57600 with the same result as above

avrdude: ser_recv(): programmer is not responding
avrdude: jtagmkI_resync(): timeout/error communicating with programmer
avrdude: jtagmkI_open(): failed to synchronize to ICE
avrdude: jtagmkI_close()

avrdude done.  Thank you.


But if I first access it with my old copy of avarice, that works OK.
Then if I use avrdude, it works with the device as normal.  If I then
power cycle the JTAGICE and try again first with avrdude, I get the
same as above - failed to synchronize to ICE.

However, if I use my ECROS ICE-Cube (third party JTAGICE clone),
avrdude works fine in all cases - no initialization problems.

So there seems to be an initialization problem with avrdude.
Connecting to it first with avarice seems to work.  If I follow that
with avrdude without power-cycling the JTAGICE, avrdude can then talk
to it OK.  Here's what avrdude says about the JTAG firmware once it is
talking:

         Programmer Type : JTAGMKI
         Description     : Atmel JTAG ICE (mkI)
         ICE hardware version: 0xc0
         ICE firmware version: 0x7e
         Vtarget         : 5.1 V
         JTAG clock      : 1 MHz (1.0 us)

  avrdude: jtagmkI_initialize(): warning: OCDEN fuse not programmed, 
single-byte EEPROM updates not possible
  avrdude: AVR device initialized and ready to accept instructions


This matches what avarice reports:

        address@hidden:/diag- avarice -j  /dev/cu.USA19Hb11P1.1    
        AVaRICE version 2.2.20041125, Dec  2 2004 22:30:41

        Defaulting JTAG bitrate to 1 MHz. Make sure that the target
        frequency is at least 4 MHz or you will likely encounter failures
        controlling the target.

        JTAG config starting.
        Hardware Version: 0xc0
        Software Version: 0x7e
        Reported JTAG device ID: 0x9702
        Configured for device ID: 0x9702 atmega128
        JTAG config complete.


Once avrdude is talking, it does program and verify the flash
correctly, at least on a few of my firmwares that I tested.

-Brian
-- 
Brian Dean
ATmega128 based MAVRIC controllers
http://www.bdmicro.com/