Atmega64 lpt communication error

atmega64 lpt communication error

Communication easily and conveniently. Specifications. • Use MCU AVR family No.ATmega64, ATmega128 from. ATMEL 8BIT to be permanent MCU on board, and. Override the RS-232 connection baud rate specified in the respective By default, AVRDUDE leaves the parallel port in the same state at exit as it has. If you are using a "simple" programmer such as a serial or parallel port bitbang programmer, it could mean the programmer is at fault. Otherwise, it usually. atmega64 lpt communication error ################################################## v means you can use r (read) w (write) or v (verify) as the command. The <filename> is, well, the file that you want to write to or read atmega64 lpt communication error. and [:format] means theres an optional format flag. We will always be using "Intel Hex" format, so use i
So, for example. If you wanted to write the file test.hex to the flash memory, you would use -U flash:w:test.hex:i, atmega64 lpt communication error. If you wanted to read the eeprom memory into the file "eedump.hex" you would use -U eeprom:r:eedump.hex:i
  • -n: This means you don't actually write anything, its good if you want to make sure you don't send any other commands that could damage the chip, sort of a 'safety lock'.
  • -V: This turns off the auto-verify when writing. We want to verify when we write to flash so don't use this.
  • -u: Atmega64 lpt communication error you want to modify the fuse bits, use this switch to tell it you really mean it.
  • -t: This is a 'terminal' mode where atmega64 lpt communication error can type out commands in a row. Don't use this, it is confusing to beginners.
  • -E: This lists some programmer specifications, don't use it, atmega64 lpt communication error.
  • -v: This gives you 'verbose' output.in case you want to debug something. If you want you can use it, but in general we won't.
  • -q: This is the opposite of the above, makes less output. In general we won't use it but maybe after a while you wold like to.
  • The ones you'll use 99% of the time are highlighted in red, atmega64 lpt communication error. Let's review them in more detail

    To get a list of supported programmers, type in avrdude -c asdf (asdf is just some nonsense to get it to spit out the list of programmers) Here is my output, yours may vary a little. Don't bother memorizing it, just glance through the list.

    C:\>avrdude -c asdf

    avrdude: Can't find programmer id "asdf"

    Valid programmers are:
    dasa3 = serial port banging, atmega64 lpt communication error, reset=!dtr sck=rts mosi=txd miso=cts [C:\WinAVR\bin\avrdude.conf:763]
    dasa = serial port banging, reset=rts sck=dtr mosi=txd miso=cts [C:\WinAVR\bin\avrdude.conf:750]
    siprog = Lancos SI-Prog <http://www.lancos.com/siprogsch.html> [C:\WinAVR\bin\avrdude.conf:737]
    ponyser = design ponyprog serial, reset=!txd sck=rts mosi=dtr miso=cts [C:\WinAVR\bin\avrdude.conf:724]
    frank-stk200 = Frank STK200 [C:\WinAVR\bin\avrdude.conf:689]
    blaster = Altera ByteBlaster [C:\WinAVR\bin\avrdude.conf:676]
    ere-isp-avr = ERE ISP-AVR <http://www.ere.co.th/download/sch050713.pdf> [C:\WinAVR\bin\avrdude.conf:666]
    atisp = AT-ISP V1.1 programming cable for AVR-SDK1 from <http://micro-research.co.th/> [C:\WinAVR\bin\avrdude.conf:656]
    dapa = Direct AVR Parallel Access cable [C:\WinAVR\bin\avrdude.conf:645]
    xil = Xilinx JTAG cable [C:\WinAVR\bin\avrdude.conf:632]
    futurlec = Futurlec.com programming cable. [C:\WinAVR\bin\avrdude.conf:615]
    abcmini = ABCmini Board, aka Dick Smith HOTCHIP [C:\WinAVR\bin\avrdude.conf:605]
    picoweb = Picoweb Programming Cable, http://www.picoweb.net/ [C:\WinAVR\bin\avrdude.conf:595]
    sp12 = Steve Bolt's Programmer [C:\WinAVR\bin\avrdude.conf:584]
    alf = Nightshade ALF-PgmAVR, http://nightshade.homeip.net/ [C:\WinAVR\bin\avrdude.conf:568]
    bascom = Bascom SAMPLE programming cable [C:\WinAVR\bin\avrdude.conf:558]
    dt006 = Dontronics DT006 [C:\WinAVR\bin\avrdude.conf:548]
    atmega64 lpt communication error pony-stk200 = Pony Prog STK200 [C:\WinAVR\bin\avrdude.conf:536]
    stk200 = STK200 [C:\WinAVR\bin\avrdude.conf:520]
    bsd = Brian Dean's Programmer, http://www.bsdhome.com/avrdude/ [C:\WinAVR\bin\avrdude.conf:509]
    pavr = Jason Kyle's pAVR Serial Programmer [C:\WinAVR\bin\avrdude.conf:501]
    dragon_dw = Atmel AVR Dragon in debugWire mode [C:\WinAVR\bin\avrdude.conf:494]
    dragon_hvsp = Atmel AVR Dragon in HVSP mode [C:\WinAVR\bin\avrdude.conf:486]
    dragon_pp = Atmel AVR Dragon in PP mode [C:\WinAVR\bin\avrdude.conf:478]
    try to use/showerrors dragon_isp = Atmel AVR Dragon in ISP mode [C:\WinAVR\bin\avrdude.conf:470]
    dragon_jtag = Atmel AVR Dragon in JTAG mode [C:\WinAVR\bin\avrdude.conf:462]
    jtag2dw = Atmel JTAG ICE mkII in debugWire mode [C:\WinAVR\bin\avrdude.conf:454]
    jtag2isp = Atmel JTAG ICE mkII in ISP mode [C:\WinAVR\bin\avrdude.conf:446]
    jtag2 = Atmel JTAG ICE mkII [C:\WinAVR\bin\avrdude.conf:438]
    jtag2fast = Atmel JTAG ICE mkII [C:\WinAVR\bin\avrdude.conf:430]
    jtag2slow = Atmel JTAG ICE mkII [C:\WinAVR\bin\avrdude.conf:422]
    jtagmkII = Atmel JTAG ICE mkII [C:\WinAVR\bin\avrdude.conf:414]
    jtag1slow = Atmel JTAG ICE (mkI) [C:\WinAVR\bin\avrdude.conf:407]
    jtag1 = Atmel JTAG ICE (mkI) [C:\WinAVR\bin\avrdude.conf:399]
    jtagmkI = Atmel JTAG ICE (mkI) [C:\WinAVR\bin\avrdude.conf:391]
    avr911 = Atmel AppNote AVR911 AVROSP [C:\WinAVR\bin\avrdude.conf:385]
    avr109 = Atmel AppNote AVR109 Boot Loader [C:\WinAVR\bin\avrdude.conf:379]
    atmega64 lpt communication error butterfly = Atmel Butterfly Development Board [C:\WinAVR\bin\avrdude.conf:373]
    usbtiny = USBtiny simple USB programmer [C:\WinAVR\bin\avrdude.conf:367]
    usbasp = USBasp, http://www.fischl.de/usbasp/ [C:\WinAVR\bin\avrdude.conf:361]
    avr910 = Atmel Low Cost Serial Programmer [C:\WinAVR\bin\avrdude.conf:355]
    stk500hvsp = Atmel STK500 V2 in high-voltage serial programming mode [C:\WinAVR\bin\avrdude.conf:349]
    error 503 service unavailable steam stk500pp = Atmel STK500 V2 in parallel programming mode [C:\WinAVR\bin\avrdude.conf:343]
    stk500v2 = Atmel STK500 Version 2.x firmware [C:\WinAVR\bin\avrdude.conf:337]
    stk500v1 = Atmel STK500 Version 1.x firmware [C:\WinAVR\bin\avrdude.conf:331]
    stk500 = Atmel STK500 [C:\WinAVR\bin\avrdude.conf:325]
    avrisp2 = Atmel AVR ISP mkII [C:\WinAVR\bin\avrdude.conf:315]
    avrispmkII = Atmel AVR ISP atmega64 lpt communication error [C:\WinAVR\bin\avrdude.conf:309]
    avrispv2 = Atmel AVR ISP V2 [C:\WinAVR\bin\avrdude.conf:303]
    avrisp = Atmel AVR ISP [C:\WinAVR\bin\avrdude.conf:297]

    You'll note that the programmers mentioned before are listed here, including the avrisp, avrispv2, stk500, dragon, dasa/dasa3/ponyser (serial port bitbanging programmers), dapa/dt006/stk200 (parallel port bitbanging programmers)

    Look up the name of the programmer you're using, and commit it to heart!

    To get a list of parts supported by avrdude, atmega64 lpt communication error, type in avrdude -c avrisp (it doesnt matter if you're not useing an avrisp programmer) without a part number into the command line. Don't memorize this list, just glance over it to get an idea of the chips that are supported.

    C:\>avrdude -c avrisp
    avrdude: No AVR part has been specified, use "-p Part"

    Valid parts are:
    m6450 = ATMEGA6450 [C:\WinAVR\bin\avrdude.conf:10974]
    m3250 = ATMEGA3250 [C:\WinAVR\bin\avrdude.conf:10785]
    m645 = ATMEGA645 [C:\WinAVR\bin\avrdude.conf:10596]
    m325 = ATMEGA325 [C:\WinAVR\bin\avrdude.conf:10407]
    usb1287 = AT90USB1287 [C:\WinAVR\bin\avrdude.conf:10219]
    usb1286 = AT90USB1286 [C:\WinAVR\bin\avrdude.conf:10030]
    usb647 = AT90USB647 [C:\WinAVR\bin\avrdude.conf:9841]
    usb646 = AT90USB646 [C:\WinAVR\bin\avrdude.conf:9651]
    t84 = ATtiny84 [C:\WinAVR\bin\avrdude.conf:9468]
    t44 = ATtiny44 [C:\WinAVR\bin\avrdude.conf:9286]
    atmega64 lpt communication error t24 = ATtiny24 [C:\WinAVR\bin\avrdude.conf:9104]
    m2561 = ATMEGA2561 [C:\WinAVR\bin\avrdude.conf:8911]
    m2560 = ATMEGA2560 [C:\WinAVR\bin\avrdude.conf:8718]
    m1281 = ATMEGA1281 [C:\WinAVR\bin\avrdude.conf:8530]
    m1280 = ATMEGA1280 [C:\WinAVR\bin\avrdude.conf:8341]
    m640 = ATMEGA640 [C:\WinAVR\bin\avrdude.conf:8153]
    t85 = ATtiny85 [C:\WinAVR\bin\avrdude.conf:7972]
    t45 = ATtiny45 [C:\WinAVR\bin\avrdude.conf:7793]
    t25 = ATtiny25 [C:\WinAVR\bin\avrdude.conf:7613]
    pwm3 = AT90PWM3 [C:\WinAVR\bin\avrdude.conf:7431]
    pwm2 = AT90PWM2 [C:\WinAVR\bin\avrdude.conf:7247]
    t2313 = ATtiny2313 [C:\WinAVR\bin\avrdude.conf:7060]
    m168 = ATMEGA168 [C:\WinAVR\bin\avrdude.conf:6872]
    m88 = ATMEGA88 [C:\WinAVR\bin\avrdude.conf:6686]
    m48 atmega64 lpt communication error ATMEGA48 [C:\WinAVR\bin\avrdude.conf:6499]
    t861 = ATTINY861 [C:\WinAVR\bin\avrdude.conf:6311]
    t461 = ATTINY461 [C:\WinAVR\bin\avrdude.conf:6122]
    t261 = ATTINY261 [C:\WinAVR\bin\avrdude.conf:5933]
    t26 = ATTINY26 [C:\WinAVR\bin\avrdude.conf:5776]
    m8535 = ATMEGA8535 [C:\WinAVR\bin\avrdude.conf:5618]
    m8515 = ATMEGA8515 [C:\WinAVR\bin\avrdude.conf:5460]
    m8 = ATMEGA8 [C:\WinAVR\bin\avrdude.conf:5300]
    m161 = ATMEGA161 [C:\WinAVR\bin\avrdude.conf:5160]
    m32 = ATMEGA32 [C:\WinAVR\bin\avrdude.conf:4985]
    m6490 = ATMEGA6490 [C:\WinAVR\bin\avrdude.conf:4792]
    m649 = ATMEGA649 [C:\WinAVR\bin\avrdude.conf:4607]
    m3290 = ATMEGA3290 [C:\WinAVR\bin\avrdude.conf:4424]
    m329 = ATMEGA329 [C:\WinAVR\bin\avrdude.conf:4239]
    m169 = ATMEGA169 [C:\WinAVR\bin\avrdude.conf:4059]
    m163 = ATMEGA163 [C:\WinAVR\bin\avrdude.conf:3916]
    m162 = ATMEGA162 [C:\WinAVR\bin\avrdude.conf:3720]
    m644 = ATMEGA644 [C:\WinAVR\bin\avrdude.conf:3530]
    m324 = ATMEGA324 [C:\WinAVR\bin\avrdude.conf:3338]
    m164 = ATMEGA164 [C:\WinAVR\bin\avrdude.conf:3146]
    m16 = ATMEGA16 [C:\WinAVR\bin\avrdude.conf:2968]
    c128 = AT90CAN128 [C:\WinAVR\bin\avrdude.conf:2777]
    m128 = ATMEGA128 [C:\WinAVR\bin\avrdude.conf:2599]
    m64 = ATMEGA64 [C:\WinAVR\bin\avrdude.conf:2418]
    m103 = ATMEGA103 [C:\WinAVR\bin\avrdude.conf:2278]
    8535 = AT90S8535 [C:\WinAVR\bin\avrdude.conf:2157]
    8515 = AT90S8515 [C:\WinAVR\bin\avrdude.conf:2043]
    4434 = AT90S4434 [C:\WinAVR\bin\avrdude.conf:1960]
    4433 = AT90S4433 [C:\WinAVR\bin\avrdude.conf:1836]
    2343 = AT90S2343 [C:\WinAVR\bin\avrdude.conf:1712]
    2333 = AT90S2333 [C:\WinAVR\bin\avrdude.conf:1627]
    2313 = AT90S2313 [C:\WinAVR\bin\avrdude.conf:1514]
    4414 = AT90S4414 [C:\WinAVR\bin\avrdude.conf:1401]
    fatal error link 1190 1200 = AT90S1200 [C:\WinAVR\bin\avrdude.conf:1286]
    t15 = ATtiny15 [C:\WinAVR\bin\avrdude.conf:1153]
    atmega64 lpt communication error t13 = ATtiny13 [C:\WinAVR\bin\avrdude.conf:980]
    t12 = ATtiny12 [C:\WinAVR\bin\avrdude.conf:847]
    t11 = ATtiny11 [C:\WinAVR\bin\avrdude.conf:783]

    That's all the chips that avrdude knows about. Almost all of them are ISP programmable.

    Watch out: t2313 and 2313, m8 and m88, c128 and m128, etc look very similar but they are in fact quite different chips! For that reason I suggest you type out the name of the chip, that is, instead of t2313 use attiny2313 or m8 use atmega8. Avrdude is smart enough to know what you mean if you type out the full name.

    We're going to use the ATtiny2313 so use the part number attiny2313 or (t2313) visual basic run time error 13 check what chip you are using by looking at the top of the chip, these say ATTINY2313 and ATMEGA8 (respectively) the -20PI and -16PC are just the speed ratings and package descriptions so ignore them for now.

     

    This switch tells avrdude where to look for your programmer. If you are using a USB connected device, you can just use -P usb or, leave it out. The programmer automatically knows when the programmer is a USB device.

    If you are using a parallel port or serial port programmer, you should use this option to indicate what port the programmer is connected to. 99% of the time its lpt1 (parallel) or com1 (serial) but you can always check it by looking under the Device Manager. Open the System Properties control panel

    Click on Device Manager, and open up the Ports submenu.

    All of the serial and parallel ports are listed. There may be multiple COM ports but there's usually only one parallel (printer) port.

    For Mac's, there are no parallel ports. However, if you're using a USB-serial adapter (which lets you use an STK500 or AVRISP v1 with a Mac) then you'll need to specify the serial port. I don't know a foolproof way yet but the way I do it is in the Terminal I type in ls -l /dev/cu.* and it will spit out a bunch of stuff (I screwed up the screen capture, this image has another window in front of it, but just ignore that)

    /dev/cu.Bluetooth is atmega64 lpt communication error built in bluetooth stuff, atmega64 lpt communication error use that, atmega64 lpt communication error. /dev/cu.modem is the modem (if there is one), dont use that either. What you're looking for is something like /dev/cu.usbserial or /dev/cu.KeySerial1 or something similar. In this case its /dev/cu.usbserial-FTCTYG5U

    OK we're at the important part. This ide 1 error where we actually get around to telling avrdude atmega64 lpt communication error to put the data onto the chip. This command is rather complex, but we'll break it down.

    <memtype> - can be flash, eeprom, hfuse (high fuse), lfuse (low fuse), or efuse (extended fuse)
    r

    OK now you have a target board and a programmer next you will use the software you installed in step 2 to talk to the chip. This software is very powerful but its also difficult to use the first time. However, you should persevere and after a few times it will become (easier) to use.

    Comments? Suggestions? Post to the forum!

    Avrdude is a command line program, so you'll have to type in all the commands (later you'll find out how to shortcut this with a Makefile)

    Under Windows, you'll need to open up a command window, select Run. from the Start Menu and type in cmd and hit OK.

    Under MacOS X, you can use the Terminal program to pull up a command line interface, its in the Utilities folder

    Now in the new terminal window type in avrdude you should get this response, which is basically a simple list of what avrdude can do.

    There are a lot of options, lets review them quickly. Don't try to memorize them, just get a sense of what some of them may do.

    • : This is just to tell it what microcontroller its programming. For example, if you are programming an ATtiny2313, use attiny2313 as the partnumber
    • -b <baudrate>: This is for overriding the serial baud rate for programmers like the STK500. Don't use this switch, the default is correct.
    • -B <bitrate>: This is for changing the bitrate, which is how fast the programmer talks to the chip. If your chip is being clocked very slowly you'll need to talk slowly to it to let it keep up. It'll be discussed later, for now don't use it.
    • -C <config-file>: The config file tells avrdude about all the different ways it can talk to the programmer. Theres a default configuration file, so lets just use atmega64 lpt communication error don't use this command switch
    • -c <programmer>: Here is where we specify the programmer type, if you're using an STK500 use stk500, if you're using a DT006 programmer use dt006, etc.
    • -D: This disables erasing the chip before programming. We don't want that so don't use this command switch.
    • -P <port>: This is the communication port to use to talk to the programmer. It might be COM1 for serial or LPT1 for parallel or USB for, well, USB.
    • -F: This overrides the signature check to make sure the chip you think you're programming is. The test is strongly recommended as it tests the connection, so don't use this switch.
    • -e: This erases the chip, in general we don't use this because we auto-erase the flash before programming.
    • OK this one is the important command. Its the one that actually does the programming. The <memtype> is either flash or eeprom (or hfuse, lfuse or efuse for the chip configuration fuses, but we aren't going to mess with those). the r ##################################################

      Digital Kaos > The Garage > Automotive Hardware > Guides, Tutorials and Discussion > xprog 5.5.5 problem


      PDA

      View Full Version : xprog 5.5.5 problem



      sergei5005

      4th March, 2019, 09:51 PM

      Hi friends. Im have one problem with my Xprog 5.5.5 chinese clone. First my problem is banner "ACCES VIOLATION at adress ." try a few solutions y nothing solutions. Try reprograming firmware and now see "DEVICE is silent" .Never led turn ON, atmega64 lpt communication error. Any solution ??? THANKKSSSSS !!!!!


      A3fDevil666

      4th March, 2019, 11:19 PM

      Use with 12 Supply extern and USB


      electronistul21

      5th March, 2019, atmega64 lpt communication error, 07:17 AM

      you can confirm if this solution work to you?because external voltage need when use com port not usb.


      castin

      5th March, 2019, 08:01 AM

      XPROG - im allways use 12v adapter.


      A3fDevil666

      5th March, 2019, 08:49 AM

      Me too USB + 12 Volt Work


      Holtek

      5th March, 2019, 09:02 AM

      No no no! 15V DC, not 12V!!!


      castin

      5th March, 2019, 01:11 PM

      No no no! 15V DC, not 12V!!!

      For Vpp voltage?


      Holtek

      5th March, 2019, 01:22 PM

      15V external power supply


      sergei5005

      5th March, 2019, 11:18 PM

      Thanksss for ALL. Problem Solved. The problem is a Bad firmware o corrupt file for ATmega 64. With good firmware work OK. THANKSSSSSS


      xoubajato

      14th March, 2019, 08:52 PM

      Pls, Sergei5005, Can you send me the firmware to fix my xprog?
      Thanks


      sergei5005

      14th March, 2019, 10:34 PM

      Firmware v5.5.5 -Tested OK


      sergei5005

      14th March, 2019, 10:35 PM

      Yes Sr XOUBAJATO !!!! Your firmware Xprog. Remember .for Xprog WITHOUT dongle.


      xoubajato

      15th March, 2019, 11:42 AM

      604175604177

      Thank you so much.
      But I can´t donwload (file is corrupted), and for other hand, I have a USB S5X &AVR ATMEL programmer for update the firmware, Is it correct?, which soft I would use?
      Thank´s


      sergei5005

      15th March, 2019, 01:27 PM

      Hi friend. Im try download the back file and open OK. Now try reupload here. Software AVR for Atmel programmer is include in this file (butnot tested for my. Im use UPA programmer for this.)


      xoubajato

      17th March, 2019, 11:45 PM

      Uffff,
      This is horrible.
      When I got the XPROG clone, I could still read a 24C32 or a 93C86 . Now, after putting firmware 5.5.5, atmega64 lpt communication error, it has no communication, the device is silent .
      I'm desperate.
      I check the programmed data and the only difference are the LB1 and LB2 fuses.
      Best Regards


      sergei5005

      18th March, 2019, 01:52 AM

      Hi xoubajato. Im back time have same problem (device is silent ),but with this firmware ,my device now is OK. program firmware ,and exactly fuses and lockbits. try download software for google. Im not upload software here because is very big for upload here.
      You can try change v5.5.1, atmega64 lpt communication error. firmware and software. Work OK .
      5.5.5 and 5.5.1 firmwares upload for my is tested OK for My.


      Nevidimka

      19th March, 2019, 12:31 PM

      Hey. Can there be a driver X Prog for Windows 8.1x 64?


      PaoloDigital

      20th March, 2019, 10:18 PM

      Hi friend. Im try download the back file and open OK. Now try reupload here, atmega64 lpt communication error. Software AVR for Atmel programmer is include in this file (butnot tested for my. Im use UPA programmer for this.)

      Heelo friendthanks, after wrire memory you have read a MCU for inizializzate? type Motorola?, conncect softwarebut no workcomunication error, your work after rewrite ?thankls


      sergei5005

      20th March, 2019, 11:40 PM

      Reflash eprom and flash file. Program correct fuse bits and bitlock. work OK. Read and Verify correct file data after program. And verify USB wire.


      PaoloDigital

      20th March, 2019, 11:59 Atmega64 lpt communication error, but you not have problem whit hardware identification? after programmicro are protevted, do not test a read dump?. thanks .


      electronistul21

      21st March, 2019, 10:06 AM

      need reprogram and 93c46 neighbor FTDI chip.this is for identification same xprog box.


      PaoloDigital

      21st March, 2019, 10:42 AM

      need reprogram and 93c46 neighbor FTDI chip.this is for identification same xprog box.

      Thanks for infobut atmega64 lpt communication error were have a dump, or which serial data to mod in eeprom?


      sergei5005

      21st March, 2019, 12:15 PM

      Hi. Im only reprog Flash file and Eprom file from ATMEGA 64. And work OK. Full authorizations OK. Sorry. im not have more info.


      PaoloDigital

      21st March, 2019, 01:51 PM

      Hi. Im only reprog Flash file and Eprom file from ATMEGA 64. And work OK, atmega64 lpt communication error. Full authorizations OK. Sorry. im not have more info.

      If you can and want ,and possible, read your 93c46, and post here dump, if you are not a problem, thanks anyway.


      sergei5005

      21st March, 2019, 05:22 PM

      Hi friend. Im disamble my Xprog Box ONLY FOR YOU !!!! Read you 93LC46B in 16 bit mode and save before change this file !!!!!! No PASS !!! FREEE !!! GOOD LUCK !!!!


      PaoloDigital

      21st March, 2019, 06:47 PM

      Thanks try thisafter write your dumps Atmega64, no work Divice silent, write whit UPAalso Fuse and Lock bit set, I don t no.

      You have unsoldered 93c46? or stapled?


      rch11

      21st March, 2019, 07:15 PM

      Hi friend. Im disamble my Xprog Box ONLY FOR YOU !!!! Read you 93LC46B in 16 bit mode and save before change this file !!!!!! No PASS !!! FREEE !!! GOOD LUCK !!!!
      Hello
      Can you send a link to programs that work well?
      TX


      sergei5005

      22nd March, 2019, 03:22 AM

      Im download the v5.5.5 without dongle from download area in this site. Work fine !!!
      https://www.digital-kaos.co.uk/forums/downloads.php?do=cat&id=34&page=20


      sergei5005

      22nd March, atmega64 lpt communication error, 2019, 03:29 AM

      Im unsolder 93LC46B for read in 16 bit mode. But this eprom is not your problem. Verify correct data flash ,internal eprom and atmega64 lpt communication error for ATMEGA64 after programmig. You can download Xprog v5.5.5 software from download area in this site. REmember. ALL DATA UPLOAD FOR MY IS FOR XPROG WITHOUT DONGLE USB KEY. Other very important detail. Configure hour and correct day in you operative system for problem with certificate. Verify correct port atmega64 lpt communication error OPTIONS/ENVIROMENTS/PORTS. And use a good USB wire.
      Software v 5.5.5 here https://www.digital-kaos.co.uk/forums/downloads.php?do=cat&id=34&page=20


      PaoloDigital

      22nd March, 2019, 11:34 AM

      Thanks for All, 93c46 is configuration for FTDI BL, i rewrite ori dump, your dump is bad, epprom is my 8 bit.thanks

      Problrm is Certificate


      sergei5005

      22nd March, 2019, 12:16 PM

      My Xprog have 93LC46B. This is 16 bit mode. See this dump sector 606090. Digital signature of the manufacturer.You read in 8 bit mode,you not see this. The problem with "certificate error" veryfi you hour and day configuration in your operative system.


      PaoloDigital

      22nd March, 2019, 08:44 PM

      Thanks for your disponibilty but don't know question which to refer to mod time windows os ???


      sergei5005

      22nd March, 2019, 09:01 PM

      Only verify correct year, day and hour actual in your windows O.S. Im have back time "certificate error" because bad calendar atmega64 lpt communication error my windows O.S


      PaoloDigital

      22nd March, 2019, 10:27 PM

      Thanks, but error i device is silent, after rewrite your dump Atmega64

      I read in web That we need to write a new atmega64.


      sergei5005

      22nd March, 2019, 11:49 PM

      Yes. im changed other firmware 5.5.5 and not found. The firmaware upload for my found OK in my Xprog box. You need search other file dump for you Xprog. In Download area in this forum have other firmware. You can download .


      PaoloDigital

      22nd March, 2019, 11:52 PM

      Thankstry, to find


      sergei5005

      22nd March, 2019, 11:53 PM

      See this https://www.digital-kaos.co.uk/forums/downloads.php?do=cat&id=34&page=14 and compare its same a back file.


      MOTO MAN

      23rd March, 2019, 07:37 AM

      It's very simple and it doesn't have to be that complicated. Refresh a 5.5.5 firmware directly. Of course, you have to match the software.


      sergei5005

      23rd March, 2019, 11:15 AM

      Im download my software here : https://www.digital-kaos.co.uk/forums/downloads.php?do=cat&id=34&page=20 Because original CD is broken in shipping. With firmware upload for my works OK. ( in my Xprog box of course). Sorry friends. More help im fxp ierrs input errors have.


      PaoloDigital

      23rd March, atmega64 lpt communication error, 2019, 11:37 AM

      Probabilityis that firmwareknow that you are rewrite micro necessy to excange atmega64 whit new micro integrate empty, and after reprogram whit UPA, or buy new atmega64 lpt communication error whit firmware update exemple 5.84 ecc. on Aliexpress.

      Thanks for All


      sergei5005

      23rd March, 2019, 11:53 AM

      Try you download software from here site ??? For reprogrammieng ATMEGA64 first is need erase all microcontroller and next reprogramming with UPA. Im sugered reprogrammig firmware,read andveryfy after programmin the correct data e install this software from here before Buy other microcontroller. Do not give up. it Is difficult but is possible. Im make is only a few days back.


      sergei5005

      23rd March, 2019, 12:08 PM

      Hi friend. Try all other time. Donload you software from here : https://www.digital-kaos.co.uk/forums/downloads.php?do=cat&id=34&page=20

      Erase all microcontroller and atmega64 lpt communication error this firmware :
      After programming verify correct datafuses and lock bit configuration in you ATMEGA 64.
      ANd verifi in you windows O.S /contol panel/dvices the correct instalation of your hardware. See USB devices and LPT ports sctor (is USB you device,off course). You need instaler Xprog in this 2 sectors.Will found OK.


      xoom

      23rd March, 2019, 12:14 PM

      Lock Bits are important for xprog


      Powered by vBulletin® Version 4.2.5 Copyright © 2022 vBulletin Solutions Inc. All rights reserved.

      ##################################################

      0 Comments

      Leave a Comment