Menu

Can't Program Atmel devices

Rhonn
2011-04-28
2012-10-27
1 2 3 > >> (Page 1 of 3)
  • Rhonn

    Rhonn - 2011-04-28

    Hi,

    Just finished my programmer and also construct adapter for 28/40 pins PIC and
    it work flawlessly, but so frustrated with ATMEL..:(

    I tried several ATMega8 and AT90S2313 but only get this error:

    Synchronization error

    Device detected: vid=0x04D8 pid=0x0100
    Path: \?\hid#vid_04d8&pid_0100#6&24c088c1&0&0000#{4d1e55b2-f16f-11cf-
    88cb-001111000030}
    Programmer detected
    Firmware version 0.7.6
    Hardware ID: 0.0.1 (18F2550)

    Synchronization error

    What seems to be the problem??

     
  • Alberto Maccioni

    It means that the device doe snot respond to SPI commands.
    First of all: are you using the Atmel AVR adapter?

     
  • Rhonn

    Rhonn - 2011-04-29

    Yes sir I built the adapter for Atmel...Which PIN the SPI comes in??

     
  • Rhonn

    Rhonn - 2011-04-29

    is that from RB1? BTW I used PIC18F2455 instead of 2550...

     
  • Alberto Maccioni

    No, it's RB0, and RC7 the output.
    2455 or 2550 is the same, it's done in software.
    Try to read with Tiny2313, that uses a slower data rate.

     
  • Rhonn

    Rhonn - 2011-04-30

    Sir same error with Tiny2313..:(

    here is my programmer

     
  • ded6moroz

    ded6moroz - 2011-04-30

    Having the same error. Using PIC18F2550 and ATMEL adapter.

     
  • Alberto Maccioni

    You'r using the wrong socket, that one is for Tinyx61A; put your device on the
    upper socket with alignment to pin 1.

     
  • ded6moroz

    ded6moroz - 2011-05-02

    The upper socket is the only one that I used to program ATMega8A. It is the
    only 28-pin socket in this adapter.

     
  • Alberto Maccioni

    Ok, I thought the picture was referring to your test.
    Can you check the SPI communication with an oscilloscope?

     
  • ded6moroz

    ded6moroz - 2011-05-03

    I-ll try. But what should I see there?

     
  • ded6moroz

    ded6moroz - 2011-05-03

    Sorry, no need... As my friend say - Problem always being of two types - 1.
    Thereis a contact whereit shouldn-t be, or 2. There is no contact where it
    must be... Other is only variations of this two. So there was a contact
    between pins on that socket. Sorry again.

     
  • Rhonn

    Rhonn - 2011-05-03

    Nothing change...same error..even with ATMega8A plug on the 28pins socket..

    Synchronization error

     
  • Rhonn

    Rhonn - 2011-05-03

    Damn! I got it!

    Device detected: vid=0x04D8 pid=0x0100
    Path: \?\hid#vid_04d8&pid_0100#6&24c088c1&0&0000#{4d1e55b2-f16f-11cf-
    88cb-001111000030}
    Programmer detected
    Firmware version 0.7.6
    Hardware ID: 0.0.1 (18F2550)

    CHIP ID:1E9307
    Atmel ATmega8 8KB Flash
    LOCK bits: 0xFF
    FUSE bits: 0xE1
    FUSE HIGH bits: 0xD9
    Calibration bits: 0xBD,0xBC,0xB7,0xB8
    Reading code ... completed
    Reading EEPROM ... completed

    Code memory:
    (empty)

    EEPROM memory:
    (empty)

    End (3.06 s)

    this time im using ATmega8L...where should I put the AT90S2313? same socket
    with Mega8??

     
  • Rhonn

    Rhonn - 2011-05-03

    tried reading ATTiny12 and the device was set to ATTiny2313 here's what i
    get..

    CHIP ID:1E9005
    Atmel Unknown device
    1KB Flash
    LOCK bits: 0x86
    FUSE bits: 0x52
    FUSE HIGH bits: 0x86
    Extended FUSE bits: 0x52
    Calibration bits: 0x40,0xFF,0xFF,0xFF
    Reading code ... completed
    Reading EEPROM ... completed

    Code memory:
    03E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
    FF FF FF FF FF FF 40 FF
    07E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
    FF FF FF FF FF FF 40 FF

    EEPROM memory:
    0030: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 40 ...............@
    0070: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 40 ...............@

    End (1.94 s)

    I think you can just update the GUI adding ATTiny12 as well...:D

     
  • Alberto Maccioni

    So it was an hardware issue; just the shorted pins?
    90S2313 goes in the same 28 pin socket, aligned to pin 1.
    Regarding the tiny12 it would need HV programming to claim full support; now
    you can just read.

     
  • Rhonn

    Rhonn - 2011-05-04

    So it was an hardware issue; just the shorted pins? 90S2313 goes in the same
    28 pin socket, aligned to pin 1. Regarding the tiny12 it would need HV
    programming to claim full support; now you can just read.

    No I don't see any hardware issue or shorted pins..just plug in a new Mega8L
    and READ...do you think my other Atmel are defective??

     
  • Alberto Maccioni

    Serial programming can be disabled via fuse, so your other part might be
    locked.
    But you can only disable it with parallel programming, so it depends from what
    programmer was used before.

     
  • Rhonn

    Rhonn - 2011-05-04

    oh i see...so I need a HVPP for this...

     
  • Alberto Maccioni

    Not necessarily. Was it programmed with HVPP?

     
  • Rhonn

    Rhonn - 2011-05-04

    I don't have any idea...just pulled it out from one of my box..

     
  • ded6moroz

    ded6moroz - 2011-05-08

    Interesting... I can't program any PIC device... AVR works fine, but PIC's...
    It says Communication timeout. I found, that there is no 5v on CK, D, PGM
    outs. Could it be because i used LPT-programmer like Art-Joy to write main
    18F2550?

    By the way. When i performing hardware test i see the voltages on step 1, but
    after it (steps 2, 3, 4) i can't see any voltage on 20-pin socket.

     
  • Alberto Maccioni

    If the hardware test fails you cannot expect a correct operation.
    The programmer used to flash the main micro does not have any influence as
    long as it writes the firmware correctly.

     
  • ded6moroz

    ded6moroz - 2011-05-09

    Does it mean, that I need to check out only power regulator? Or I need to
    reflash the main micro again too? I checked written firmware twice before
    assembling open programmer.

    During hardware test GUI says "Communication timeout". Is it correct, or it
    shouldn't show this message in log window?

     
  • Alberto Maccioni

    Errors are not normal, as you may expect.
    If you are sure about your flashing process there's no need to repeat it; once
    you verify that the hardware is detected by your pc you can be reasonably sure
    that the firmware is working correctly.
    Check carefully your hardware looking for shorts, opens, or mounting errors.

     
1 2 3 > >> (Page 1 of 3)

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.