This is user manual of the Original Launch EasyDiag Bluetooth OBDII Code Reade for IOS Android, incuding how to log in, register and pay for EasyDiag software.
Step 1 - Log in software
Note: before operating, you need to log in software first. If your Android phone’s Bluetooth is closed, a request for Bluetooth will be seen once open the software
Select “yes” to turn on Bluetooth; or you can not communicate with EasyDiag
Look through these illustrations for a general understanding for the software
some precautions and warnings about using, read it carefully
click “I’ve read it” to enter login interface
Click “Login” to open login interface
For existing users, input your account to login. For new users, click to register.
Input the necessary messages, and then click “Register and Login”
If you have a new connector need to registered, it is suggested to choose “Register Connector” item, once selected, the screen will jump into “Register Connector” page directly.
NOTE: When registration is successful, a confirm letter will be sent to your registered Email.
the interface after login
Click “read” to open quick start guide. And also you can open it in “More” item.
The software initial interface
1: Function selection list
2: Function extension button
3: Login button
4: Vehicle origin selection,
5: Car model selection area, the download icon means this car's diagnostic software has not been downloaded, if you want to diagnose it, click it to acquire the software.
6: Full screen display switch button
7: Partial display area
If you don’t have an EasyDiag, you can click DEMO icon to get into the demo function interface, and experience the vehicle diagnosis function
If you have already got a Lauch EasyDiag unit, please continue the registration.
Step 2 - Register connector
Plug the EasyDiag adapter into DLC socket and turn on the ignition switch.
Click “User Account” to enter the interface
Click “Register Connector”
Input Serial Number and verification code, then click “Register” to complete registration.
Note: the product Serial Number and verification code are available in the password envelope.
Step 3 - Acquire software
Before software download, please complete software acquisition
The download icon means the diagnostic software has not been downloaded, if you want to diagnose this car, please click it to acquire the diagnostic software.
Before purchase, you should select a product serial number
In the EasyDiag app, click the brand icon software which you want.
Take “ACURA” as an example.
Click “ACURA” icon
If only this software to be purchased, click “Add to cart”.
If you also want to add other software into the cart, close this page and select others add to shopping cart, also you can click “Software Package” to purchase software in packages or individually.
NOTE: Software package only supplies to individual regions.
Press “Create order” after software selection
Order list
After you click the space which marked in red circle, it would provide some useful information, such as diagnosis soft order name, order number, product serial number, total price, order status, and order time.
Please comfirm those information, and take a note about the order number which is the most important.
PAYMENT: You can select pay with PayPal or pay on website; here we choose the latter to illustrate how to pay. As for PayPal method, you can follow the on-screen instructions to complete.
After click button, the browser will automatic jump into LAUNCH user center login page.
Login with name and password, same as EasyDiag app login account.
order information, comfirm the order number
Click “PAY”
two options to pay, one is called “支付宝” for Chinese currency and the other one is “PayPal” for USD
a PayPal account is needed before you made the payment
login your PayPal account with your email address, and password, and click “continue”.
Pay sucess
DOWNLOAD: After made payment, please move back to EasyDiag application. And click the diagnosis software icon which have already paid
Take “DEMO” as an example, press “Check Download”.
Select HONDA, and start to download
Select “Download”.
Download until completed
Press”return” to back to the when diagnosis software download is completed, the download icon on the right bottom will disappear
Thursday, 31 March 2016
Friday, 25 March 2016
How to solve Kess V2 Bootloader adapter problems
Find a solution to fix Kess v2 clone bootloader adapter problems. Just put it here for sharing.
Device:
Kess v2 with ksuite 4.036 (China clone)
Symptom:
I am having problems with my bootloader adapter for Kess v2. Kess is reworked to 4.036 and works with OBD cable. I tried to use bootloader adapter and cable, but failed to read any ecu. I tried to connect EDC17CP14 (on the bench and without boot pin- obd mode on the bench), no luck with Kess (but my reworked Galletto worked with similar wiring ID + read OK).
I already checked the wiring in the cable connector- fixed some wires, but still nothing.
I think there may be something wrong in the bootloader unit.
4 steps to solve bootloader adapter problems:
Step 1- fixed the wiring
i fixed the wiring in the connector that goes into the bootloader module like in the picture (Ktag has the same) 4 wires were wrong in my connector.
Step 2- resoldered the mosfet
And I resoldered the mosfet (in the middle of the module- near the middle LED).
Step 3- read ECU without opening
I then got the power to the ecu. But it didnt read it, probably because I didn’t connect the boot pin (that needs to be soldered on the ecu pcb). I tried to read it without opening, because I borrowed the ecu.
Step 4- opened the ECU to read
So I finally got the time to test my bootloader module with all wiring (boot cable attached). Once I opened the ECU (edc17cp14) and connected the boot pin, I was able to succesfully Id and read the ECU.
Worked like a charm!
The main problem was the soldering of the mosfet transistor in the middle of bootloader pcb, and I remowed the extra wire that was on the other side of the pcb.
Hope this helps those with Kess V2 unit from China
(NOTE: This is a cutomer solution; please try and responsible for what you will do)
Device:
Kess v2 with ksuite 4.036 (China clone)
Symptom:
I am having problems with my bootloader adapter for Kess v2. Kess is reworked to 4.036 and works with OBD cable. I tried to use bootloader adapter and cable, but failed to read any ecu. I tried to connect EDC17CP14 (on the bench and without boot pin- obd mode on the bench), no luck with Kess (but my reworked Galletto worked with similar wiring ID + read OK).
I already checked the wiring in the cable connector- fixed some wires, but still nothing.
I think there may be something wrong in the bootloader unit.
4 steps to solve bootloader adapter problems:
Step 1- fixed the wiring
i fixed the wiring in the connector that goes into the bootloader module like in the picture (Ktag has the same) 4 wires were wrong in my connector.
Step 2- resoldered the mosfet
And I resoldered the mosfet (in the middle of the module- near the middle LED).
Step 3- read ECU without opening
I then got the power to the ecu. But it didnt read it, probably because I didn’t connect the boot pin (that needs to be soldered on the ecu pcb). I tried to read it without opening, because I borrowed the ecu.
Step 4- opened the ECU to read
So I finally got the time to test my bootloader module with all wiring (boot cable attached). Once I opened the ECU (edc17cp14) and connected the boot pin, I was able to succesfully Id and read the ECU.
Worked like a charm!
The main problem was the soldering of the mosfet transistor in the middle of bootloader pcb, and I remowed the extra wire that was on the other side of the pcb.
Hope this helps those with Kess V2 unit from China
(NOTE: This is a cutomer solution; please try and responsible for what you will do)
Tuesday, 22 March 2016
VVDI Prog Programmer 4.4.0 Test Results from Customers
The is customer feedback collections of VVDI Prog Programmer (2.2.0-4.4.0) at OBDexpress.
Feedback on http://www.obdexpress.co.uk/wholesale/vvdi-prog-vvdi-prog-super-programmer.html
VVDI Prog 4.4.0 on BMW cars
Cas 3 0L15Y read/write eep+flash ok
Cas 3+ 0M23S read/write eep+flash ok
Cas 2 2K79X read/write eep+flash ok
Program BMW CAS4+ All Key Lost...test ok
Read BMW CAS2, CAS3, CAS3+ and CAS4 ECU...test ok
Read BMW Engine ECU ISN...test ok
read out BMW 5 series CAS data
adds BMW CAS4 key
Can't find a way to read Cas 1 for E65 mask 0K50E
VVDI Prog on Mercedes Benz
W211 ezs 4L40K read/write eep+flash ok
VVDI PROG programmer 4.1.4 on Great Wall, Delphi
Read Great Wall Delphi EEPROM 93C66...test ok
Read 5M48H and common 8pin IC...test ok
VVDI Prog 2.2.0 on VW
The programmer read VW 44 IC EEPROM
Calculate password
VVDI Prog on MCU Motorola 912Xd256
MCU Motorola 912Xd256 unsecured it
read ok
eeprom and flash write ok
wont write new data on
always says erase error
eeprom flash not
VVDI Prog get PIN code of Ford, Nissan, Hyundai, VW
Ford password calculation (get Incode with Outcode)
calculate Nissan 20 digital PIN code
Calculate Hyundai PIN code by VIN
Load data to calculate VW PIN
Feedback on http://www.obdexpress.co.uk/wholesale/vvdi-prog-vvdi-prog-super-programmer.html
VVDI Prog 4.4.0 on BMW cars
Cas 3 0L15Y read/write eep+flash ok
Cas 3+ 0M23S read/write eep+flash ok
Cas 2 2K79X read/write eep+flash ok
Program BMW CAS4+ All Key Lost...test ok
Read BMW CAS2, CAS3, CAS3+ and CAS4 ECU...test ok
Read BMW Engine ECU ISN...test ok
read out BMW 5 series CAS data
adds BMW CAS4 key
Can't find a way to read Cas 1 for E65 mask 0K50E
VVDI Prog on Mercedes Benz
W211 ezs 4L40K read/write eep+flash ok
VVDI PROG programmer 4.1.4 on Great Wall, Delphi
Read Great Wall Delphi EEPROM 93C66...test ok
Read 5M48H and common 8pin IC...test ok
VVDI Prog 2.2.0 on VW
The programmer read VW 44 IC EEPROM
Calculate password
VVDI Prog on MCU Motorola 912Xd256
MCU Motorola 912Xd256 unsecured it
read ok
eeprom and flash write ok
wont write new data on
always says erase error
eeprom flash not
VVDI Prog get PIN code of Ford, Nissan, Hyundai, VW
Ford password calculation (get Incode with Outcode)
calculate Nissan 20 digital PIN code
Calculate Hyundai PIN code by VIN
Load data to calculate VW PIN
Friday, 18 March 2016
Thursday, 17 March 2016
V2016.3 MB SD C4 Newest Software Support Win 7/Win8 Released
V2016.3 MB SD C4 Connect Compact Software HDD With DELL D630 /External Format 500GB Supports WIN7/ WIN8,Works with MB SD Connect Compact C4, support latest Mercedes Benz car and truck models.
Software languages:
Chinese,English,Croatian,Czech,Danish,Dutch,Finish,French,German,Greek,Hungarian,Italian, Japanese,Korean,Polish,Portuguese,Romanian,Russian,Spanish,Swedish,Turkish
V2016.3 MB SD C4 Software FUNCTIONS:
1. 1989~up to now Car, Bus, Truck, Sprint, Smart
2. All electric system Diagnostic;(Do not include flash code)
3. reading trouble code
4. erasing trouble code
5. live-data
6. adaptation
7. component testing
8. maintenance
9. information consultation
10. component location diagram
11. wiring diagram
2016.3 MB SD C4 Software display:
Free Download 2016.3 MB Star SD C4 Activate Manual for reference.
How to activate 2016.3 mb star c3 c4 sd c4 software on win7
http://www.obdexpress.co.uk/wholesale/mb-star-series/
Software languages:
Chinese,English,Croatian,Czech,Danish,Dutch,Finish,French,German,Greek,Hungarian,Italian, Japanese,Korean,Polish,Portuguese,Romanian,Russian,Spanish,Swedish,Turkish
V2016.3 MB SD C4 Software FUNCTIONS:
1. 1989~up to now Car, Bus, Truck, Sprint, Smart
2. All electric system Diagnostic;(Do not include flash code)
3. reading trouble code
4. erasing trouble code
5. live-data
6. adaptation
7. component testing
8. maintenance
9. information consultation
10. component location diagram
11. wiring diagram
2016.3 MB SD C4 Software display:
Free Download 2016.3 MB Star SD C4 Activate Manual for reference.
How to activate 2016.3 mb star c3 c4 sd c4 software on win7
http://www.obdexpress.co.uk/wholesale/mb-star-series/
Wednesday, 16 March 2016
Tuesday, 15 March 2016
KTAG ECU Programming tool Using Tips
This post will answer all of following questions on Ktag master ECU programming tool including optional version, compatible vehicles, workable software, the difference among all available KTAG, tokens reset method and Ktag FAQ etc.
Ktag master ECU programming tool optional version
Following optional KTAG is compatible with most world-wide cars, and a little part of Motorcycle, truck, tractors and bikes. They are different in hardware version, price and the way to reset tokens.
Ktag ECU programming tool :
Item NO. SE80: FW V5.001, €74.99+shipping
Item NO. SE80-B: FW V6.007, €165.00+ shipping
Item No. SE80-C: FW V6.007, €119.00 free shipping
Item No. SE80-E: FW V5.001,€63.80+shipping
Item No. SE80-D: FW V7.003,€349.00+shipping
Tip on Ktag master ECU programming tool workable software:
So far, the compatible software version is as high as V2.11, if you run the higher software version on the hardware, you will find in the menu many gray icon and the function is not working, since higher software version requires higher hardware version.
Difference between SE80-B and SE80-C, they are same hardware version:
The distinct difference between Item No. SE80-B and SE80-C is that they use different method to reset tokens.
SE80-B token reset method: just press the “Token Reset” Button built-in on the side of machine, and meanwhile plug the power adapter to the power. You are free to get as much tokens as you can.
SE80-C token reset method:After tokens use up, connect the USB to the computer, use the token reset tool to write, then you can reset the tokens,
Note: Ktag is built in 30 tokens, after use up, you need to reset. The machine without tokens are built in 500 tokens which guaranty you can use Ktag for a long time.
KTM100 and KTAG have the same function, hardware version is V7.003,software version is V2.13.
KTM100 should pay attention:
A.K TM100 must not can use the original software, use original software might damage the equipment.
B.K TM100 buttons are all grey, there are two possible. A is a customer with the original software upgrades, and second, the TOKEN is used up.
KTM100 get TOKEN method:
Through the TOKEN RESET BUTTON to restore.
Must pay attention to is to hold down the button and turn on the power then you can reset TOKEN, just hold down the button is not used, and only two to do at the same time then you can reset token.
FAQ:
1.Q:If Ktag will burn the ECU?
A: No, even you wire the cable not correctly. By the way, if you use FGtech and wire the cable for incorrectly, it will easily burn the ECU.
2.Q:When Ktag deducts tokens?
A:1)Back up: when you back up the data, it will not deduct tokens.
2)Flash (map) tunning file: It will not deduct tokens when read but will deduct when write.
3)EEPROM: It will not deduct tokens when read but will deduct when write.
3.Q:If you can able the internet connection when using KTAG?
A:No, you are required to disconnect the network connection, otherwise Ktag may automatically connect the network connection to upgrade and damage the machine, or you get all the menu options gray and not working.
More information:http://www.obdexpress.co.uk/producttags/k-tag.html
Ktag master ECU programming tool optional version
Following optional KTAG is compatible with most world-wide cars, and a little part of Motorcycle, truck, tractors and bikes. They are different in hardware version, price and the way to reset tokens.
Ktag ECU programming tool :
Item NO. SE80: FW V5.001, €74.99+shipping
Item NO. SE80-B: FW V6.007, €165.00+ shipping
Item No. SE80-C: FW V6.007, €119.00 free shipping
Item No. SE80-E: FW V5.001,€63.80+shipping
Item No. SE80-D: FW V7.003,€349.00+shipping
Tip on Ktag master ECU programming tool workable software:
So far, the compatible software version is as high as V2.11, if you run the higher software version on the hardware, you will find in the menu many gray icon and the function is not working, since higher software version requires higher hardware version.
Difference between SE80-B and SE80-C, they are same hardware version:
The distinct difference between Item No. SE80-B and SE80-C is that they use different method to reset tokens.
SE80-B token reset method: just press the “Token Reset” Button built-in on the side of machine, and meanwhile plug the power adapter to the power. You are free to get as much tokens as you can.
SE80-C token reset method:After tokens use up, connect the USB to the computer, use the token reset tool to write, then you can reset the tokens,
Note: Ktag is built in 30 tokens, after use up, you need to reset. The machine without tokens are built in 500 tokens which guaranty you can use Ktag for a long time.
KTM100 and KTAG have the same function, hardware version is V7.003,software version is V2.13.
KTM100 should pay attention:
A.K TM100 must not can use the original software, use original software might damage the equipment.
B.K TM100 buttons are all grey, there are two possible. A is a customer with the original software upgrades, and second, the TOKEN is used up.
KTM100 get TOKEN method:
Through the TOKEN RESET BUTTON to restore.
Must pay attention to is to hold down the button and turn on the power then you can reset TOKEN, just hold down the button is not used, and only two to do at the same time then you can reset token.
FAQ:
1.Q:If Ktag will burn the ECU?
A: No, even you wire the cable not correctly. By the way, if you use FGtech and wire the cable for incorrectly, it will easily burn the ECU.
2.Q:When Ktag deducts tokens?
A:1)Back up: when you back up the data, it will not deduct tokens.
2)Flash (map) tunning file: It will not deduct tokens when read but will deduct when write.
3)EEPROM: It will not deduct tokens when read but will deduct when write.
3.Q:If you can able the internet connection when using KTAG?
A:No, you are required to disconnect the network connection, otherwise Ktag may automatically connect the network connection to upgrade and damage the machine, or you get all the menu options gray and not working.
More information:http://www.obdexpress.co.uk/producttags/k-tag.html
Thursday, 10 March 2016
New Genius Ktouch vs. Kess V2 ECU Tuning Tool
Hand-held New Genius & Flash Point has been released for decades. Here, obd2express list the main differences of the two ECU chip tuning tools- hand-held kess v2 and pc-based kess v2.
Product Name | New Genius/ Ktouch | Best Quality Kess V2 |
---|---|---|
Picture | ||
Language | English, Italian, German, French, Spanish, Portuguese,Hungarian |
English, German, Spanish, Italian, Portuguese, French |
Software | -- | V2.15 |
Hardware | V5.05 | V4.036 |
Tokens | No Tokens Limitation,30 Tokens come with device by default, you can press the tokens reset button on the back of hardware to get new Tokens |
No Tokens Limitation, there is renew button on the main unit. This button is used to charge tokens. Once your tokens run over, just click this button, then tokens will go back to 30 tokens. |
Update | via hardware | via hardware |
Support Protocols | CAN-BUS, KWP and J1850 protocols | Line, CAN, EDC17 and MED17 and Ford J1850 |
Vehicle coverage | Car, Bikes, LCV Support more new vehicle than Kess V2 New Genius vehicle list |
Car and Bike |
PC | Hand-held, no need PC; software is inside the machine already directly to use PC is needed when modify the data |
PC-based ECU Programmer; you need install the software by yourself |
OS | Windows XP system | most WIN7 and XP systems |
Method | Read and Write ECU via OBD2 directly | Read and Write ECU via OBD2 directly |
Conclusion | 1) Hand-held KESS V2 version- KTouch, more easily and convenient to use 2) Adds more new ECUs than KESS V2 |
Sunday, 6 March 2016
ATMEGA64 Repair Chip for Xprog-m User Manual
This is the user manual of ATMEGA64 Repair Chip which can help you update the XPROG-M programmer from V5.0 or V5.3 to V5.55, no dongle needed, full authorization support, including CAS4!
Main parts in the manual:
ATMEGA64 Repair Chip Features
Pin Configuration
ATmega103 and ATmega64 Compatibility
ATmega103 Compatibility Mode
Pin Descriptions
Register Summary
Instruction Set Summary
ATMEGA64 Repair Chip Features
• High-performance, Low-power AVR® 8-bit Microcontroller
• Advanced RISC Architecture
– 130 Powerful Instructions – Most Single Clock Cycle Execution
– 32 x 8 General Purpose Working Registers + Peripheral Control Registers
– Fully Static Operation
– Up to 16 MIPS Throughput at 16 MHz
– On-chip 2-cycle Multiplier
• Non-volatile Program and Data Memories
– 64K Bytes of In-System Reprogrammable Flash
Endurance: 10,000 Write/Erase Cycles
– Optional Boot Code Section with Independent Lock Bits
In-System Programming by On-chip Boot Program
True Read-While-Write Operation
– 2K Bytes EEPROM
Endurance: 100,000 Write/Erase Cycles
– 4K Bytes Internal SRAM
– Up to 64K Bytes Optional External Memory Space
– Programming Lock for Software Security
– SPI Interface for In-System Programming
• JTAG (IEEE std. 1149.1 Compliant) Interface
– Boundary-scan Capabilities According to the JTAG Standard
– Extensive On-chip Debug Support
– Programming of Flash, EEPROM, Fuses, and Lock Bits through the JTAG Interface
• Peripheral Features
– Two 8-bit Timer/Counters with Separate Prescalers and Compare Modes
– Two Expanded 16-bit Timer/Counters with Separate Prescaler, Compare Mode, and Capture Mode
– Real Time Counter with Separate Oscillator
– Two 8-bit PWM Channels
– 6 PWM Channels with Programmable Resolution from 1 to 16 Bits
– 8-channel, 10-bit ADC
8 Single-ended Channels
7 Differential Channels
2 Differential Channels with Programmable Gain (1x, 10x, 200x)
– Byte-oriented Two-wire Serial Interface
– Dual Programmable Serial USARTs
– Master/Slave SPI Serial Interface
– Programmable Watchdog Timer with On-chip Oscillator
– On-chip Analog Comparator
• Special Microcontroller Features
– Power-on Reset and Programmable Brown-out Detection
– Internal Calibrated RC Oscillator
– External and Internal Interrupt Sources
– Six Sleep Modes: Idle, ADC Noise Reduction, Power-save, Power-down, Standby and Extended Standby
– Software Selectable Clock Frequency
– ATmega103 Compatibility Mode Selected by a Fuse
– Global Pull-up Disable
• I/O and Packages
– 53 Programmable I/O Lines
– 64-lead TQFP and 64-pad MLF
• Operating Voltages
– 2.7 - 5.5V for ATmega64L
– 4.5 - 5.5V for ATmega64
• Speed Grades
– 0 - 8 MHz for ATmega64L
– 0 - 16 MHz for ATmega64
Pin Configuration
ATMEGA64 update chip pinout
ATMEGA64 for Xprog M ECU programmer pinout:
Block Diagram
The AVR core combines a rich instruction set with 32 general purpose working registers. All the 32 registers are directly connected to the Arithmetic Logic Unit (ALU), allowing two independent registers to be accessed in one single instruction executed in one clock cycle. The resulting architecture is more code efficient while achieving throughputs up to ten times faster than conventional CISC microcontrollers.
The ATmega64 provides the following features: 64K bytes of In-System Programmable Flash with Read-While-Write capabilities, 2K bytes EEPROM, 4K bytes SRAM, 53 general purpose I/O lines, 32 general purpose working registers, Real Time Counter (RTC), four flexible Timer/Counters with compare modes and PWM, two USARTs, a byte oriented Two-wire Serial Interface, an 8-channel, 10-bit ADC with optional differential input stage with programmable gain, programmable Watchdog Timer with internal Oscillator, an SPI serial port, IEEE std. 1149.1 compliant JTAG test interface, also used for accessing the On-chip Debug system and programming, and six software selectable power saving modes. The Idle mode stops the CPU while allowing the SRAM, Timer/Counters, SPI port, and interrupt system to continue functioning. The Powerdown mode saves the register contents but freezes the Oscillator, disabling all other chip functions until the next interrupt or Hardware Reset. In Power-save mode, the asynchronous timer continues to run, allowing the user to maintain a timer base while the rest of the device is sleeping. The ADC Noise Reduction mode stops the CPU and all I/O modules except asynchronous timer and ADC, to minimize switching noise during ADC conversions. In Standby mode, the crystal/resonator Oscillator is running while the rest of the device is sleeping. This allows very fast start-up combined with low power consumption. In Extended Standby mode, both the main Oscillator and the asynchronous timer continue to run.
The device is manufactured using Atmel’s high-density non-volatile memory technology. The On-chip ISP Flash allows the program memory to be reprogrammed In-System through an SPI serial interface, by a conventional non-volatile memory programmer, or by an On-chip Boot program running on the AVR core. The Boot Program can use any interface to download the Application Program in the Application Flash memory. Software in the Boot Flash section will continue to run while the Application Flash section is updated, providing true Read-While-Write operation. By combining an 8-bit RISC CPU with In-System Self-Programmable Flash on a monolithic chip, the Atmel ATmega64 is a powerful microcontroller that provides a highly-flexible and cost-effective solution to many embedded control applications.
The ATmega64 AVR is supported with a full suite of program and system development tools including: C compilers, macro assemblers, program debugger/simulators, In-Circuit Emulators, and evaluation kits.
ATmega103 and ATmega64 Compatibility
The ATmega64 chip is a highly complex microcontroller where the number of I/O locations supersedes the 64 I/O location reserved in the AVR instruction set. To ensure backward compatibility with the ATmega103, all I/O locations present in ATmega103 have the same location in ATmega64. Most additional I/O locations are added in an Extended I/O space starting from 0x60 to 0xFF (i.e., in the ATmega103 internal RAM space). These location can be reached by using LD/LDS/LDD and ST/STS/STD instructions only, not by using IN and OUT instructions. The relocation of the internal RAM space may still be a problem for ATmega103 users. Also, the increased number of Interrupt Vectors might be a problem if the code uses absolute addresses. To solve these problems, an ATmega103 compatibility mode can be selected by programming the fuse M103C. In this mode, none of the functions in the Extended I/O space are in use, so the internal RAM is located as in ATmega103. Also, the extended Interrupt Vectors are removed. The ATmega64 is 100% pin compatible with ATmega103, and can replace the ATmega103 on current printed circuit boards. The application note “Replacing ATmega103 by ATmega64” describes what the user should be aware of replacing the ATmega103 by an ATmega64.
ATmega103 Compatibility Mode
By programming the M103C Fuse, the ATmega64 will be compatible with the ATmega103 regards to RAM, I/O pins and Interrupt Vectors as described above. However,some new features in ATmega64 are not available in this compatibility mode,these features are listed below:
• One USART instead of two, asynchronous mode only. Only the eight least significant bits of the Baud Rate Register is available.
• One 16 bits Timer/Counter with two compare registers instead of two 16 bits Timer/Counters with three compare registers.
• Two-wire serial interface is not supported.
• Port G serves alternate functions only (not a general I/O port).
• Port F serves as digital input only in addition to analog input to the ADC.
• Boot Loader capabilities is not supported.
• It is not possible to adjust the frequency of the internal calibrated RC Oscillator.
• The External Memory Interface can not release any Address pins for general I/O,neither configure different wait states to different External Memory Address sections.
• Only EXTRF and PORF exist in the MCUCSR Register.
• No timed sequence is required for Watchdog Timeout change.
• Only low-level external interrupts can be used on four of the eight External Interrupt sources.
• Port C is output only.
• USART has no FIFO buffer, so Data OverRun comes earlier.
• The user must have set unused I/O bits to 0 in ATmega103 programs.
Pin Descriptions
VCC
Digital supply voltage.
GND
Ground.
Port A (PA7..PA0)
Port A is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port A output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port A pins that are externally pulled low will source current if the pull-up resistors are activated. The Port A pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port B (PB7..PB0)
Port B is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port B output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port B pins that are externally pulled low will source current if the pull-up resistors are activated. The Port B pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port C (PC7..PC0)
Port C is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port C output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port C pins that are externally pulled low will source current if the pull-up resistors are activated. The Port C pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port C also serves the functions of special features of the ATmega64. In ATmega103 compatibility mode, Port C is output only, and the port C pins are not tri-stated when a reset condition becomes active.
Port D (PD7..PD0)
Port D is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port D output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port D pins that are externally pulled low will source current if the pull-up resistors are activated. The Port D pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port E (PE7..PE0)
Port E is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port E output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port E pins that are externally pulled low will source current if the pull-up resistors are activated. The Port E pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port F (PF7..PF0)
Port F serves as the analog inputs to the A/D Converter. Port F also serves as an 8-bit bi-directional I/O port, if the A/D Converter is not used.Port pins can provide internal pull-up resistors (selected for each bit). The Port F output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port F pins that are externally pulled low will source current if the pull-up resistors are activated. The Port F pins are tri-stated when a reset condition becomes active, even if the clock is not running. If the JTAG interface is enabled, the pull-up resistors on pins PF7(TDI), PF5(TMS) and PF4(TCK) will be activated even if a reset occurs. The TDO pin is tri-stated unless TAP states that shift out data are entered. Port F also serves the functions of the JTAG interface.In ATmega103 compatibility mode, Port F is an input port only.
Port G (PG4..PG0)
Port G is a 5-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port G output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port G pins that are externally pulled low will source current if the pull-up resistors are activated. The Port G pins are tri-stated when a reset condition becomes active, even if the clock is not running. Port G also serves the functions of various special features. In ATmega103 compatibility mode, these pins only serves as strobes signals to the external memory as well as input to the 32 kHz Oscillator, and the pins are initialized to PG0 = 1, PG1 = 1, and PG2 = 0 asynchronously when a reset condition becomes active, even if the clock is not running. PG3 and PG4 are Oscillator pins.
RESET
Reset input. A low level on this pin for longer than the minimum pulse length will generate a reset, even if the clock is not running. The minimum pulse length is given in Table 19 on page 50. Shorter pulses are not guaranteed to generate a reset.
XTAL1
Input to the inverting Oscillator amplifier and input to the internal clock operating circuit.
XTAL2
Output from the inverting Oscillator amplifier.
AVCC
AVCC is the supply voltage pin for Port F and the A/D Converter. It should be externally connected to VCC, even if the ADC is not used. If the ADC is used, it should be connected to VCC through a low-pass filter.
AREF
AREF is the analog reference pin for the A/D Converter.
PEN
This is a programming enable pin for the SPI Serial Programming mode. By holding this pin low during a Power-on Reset, the device will enter the SPI Serial Programming mode. PEN has no function during normal operation.
Register Summary
Notes:
1. For compatibility with future devices, reserved bits should be written to zero if accessed. Reserved I/O memory addresses should never be written.
2. Some of the status flags are cleared by writing a logical one to them. Note that the CBI and SBI instructions will operate on all bits in the I/O Register, writing a one back into any flag read as set, thus clearing the flag. The CBI and SBI instructions work with registers 0x00 to 0x1F only
Instruction Set Summary
Main parts in the manual:
ATMEGA64 Repair Chip Features
Pin Configuration
ATmega103 and ATmega64 Compatibility
ATmega103 Compatibility Mode
Pin Descriptions
Register Summary
Instruction Set Summary
ATMEGA64 Repair Chip Features
• High-performance, Low-power AVR® 8-bit Microcontroller
• Advanced RISC Architecture
– 130 Powerful Instructions – Most Single Clock Cycle Execution
– 32 x 8 General Purpose Working Registers + Peripheral Control Registers
– Fully Static Operation
– Up to 16 MIPS Throughput at 16 MHz
– On-chip 2-cycle Multiplier
• Non-volatile Program and Data Memories
– 64K Bytes of In-System Reprogrammable Flash
Endurance: 10,000 Write/Erase Cycles
– Optional Boot Code Section with Independent Lock Bits
In-System Programming by On-chip Boot Program
True Read-While-Write Operation
– 2K Bytes EEPROM
Endurance: 100,000 Write/Erase Cycles
– 4K Bytes Internal SRAM
– Up to 64K Bytes Optional External Memory Space
– Programming Lock for Software Security
– SPI Interface for In-System Programming
• JTAG (IEEE std. 1149.1 Compliant) Interface
– Boundary-scan Capabilities According to the JTAG Standard
– Extensive On-chip Debug Support
– Programming of Flash, EEPROM, Fuses, and Lock Bits through the JTAG Interface
• Peripheral Features
– Two 8-bit Timer/Counters with Separate Prescalers and Compare Modes
– Two Expanded 16-bit Timer/Counters with Separate Prescaler, Compare Mode, and Capture Mode
– Real Time Counter with Separate Oscillator
– Two 8-bit PWM Channels
– 6 PWM Channels with Programmable Resolution from 1 to 16 Bits
– 8-channel, 10-bit ADC
8 Single-ended Channels
7 Differential Channels
2 Differential Channels with Programmable Gain (1x, 10x, 200x)
– Byte-oriented Two-wire Serial Interface
– Dual Programmable Serial USARTs
– Master/Slave SPI Serial Interface
– Programmable Watchdog Timer with On-chip Oscillator
– On-chip Analog Comparator
• Special Microcontroller Features
– Power-on Reset and Programmable Brown-out Detection
– Internal Calibrated RC Oscillator
– External and Internal Interrupt Sources
– Six Sleep Modes: Idle, ADC Noise Reduction, Power-save, Power-down, Standby and Extended Standby
– Software Selectable Clock Frequency
– ATmega103 Compatibility Mode Selected by a Fuse
– Global Pull-up Disable
• I/O and Packages
– 53 Programmable I/O Lines
– 64-lead TQFP and 64-pad MLF
• Operating Voltages
– 2.7 - 5.5V for ATmega64L
– 4.5 - 5.5V for ATmega64
• Speed Grades
– 0 - 8 MHz for ATmega64L
– 0 - 16 MHz for ATmega64
Pin Configuration
ATMEGA64 update chip pinout
Block Diagram
The AVR core combines a rich instruction set with 32 general purpose working registers. All the 32 registers are directly connected to the Arithmetic Logic Unit (ALU), allowing two independent registers to be accessed in one single instruction executed in one clock cycle. The resulting architecture is more code efficient while achieving throughputs up to ten times faster than conventional CISC microcontrollers.
The ATmega64 provides the following features: 64K bytes of In-System Programmable Flash with Read-While-Write capabilities, 2K bytes EEPROM, 4K bytes SRAM, 53 general purpose I/O lines, 32 general purpose working registers, Real Time Counter (RTC), four flexible Timer/Counters with compare modes and PWM, two USARTs, a byte oriented Two-wire Serial Interface, an 8-channel, 10-bit ADC with optional differential input stage with programmable gain, programmable Watchdog Timer with internal Oscillator, an SPI serial port, IEEE std. 1149.1 compliant JTAG test interface, also used for accessing the On-chip Debug system and programming, and six software selectable power saving modes. The Idle mode stops the CPU while allowing the SRAM, Timer/Counters, SPI port, and interrupt system to continue functioning. The Powerdown mode saves the register contents but freezes the Oscillator, disabling all other chip functions until the next interrupt or Hardware Reset. In Power-save mode, the asynchronous timer continues to run, allowing the user to maintain a timer base while the rest of the device is sleeping. The ADC Noise Reduction mode stops the CPU and all I/O modules except asynchronous timer and ADC, to minimize switching noise during ADC conversions. In Standby mode, the crystal/resonator Oscillator is running while the rest of the device is sleeping. This allows very fast start-up combined with low power consumption. In Extended Standby mode, both the main Oscillator and the asynchronous timer continue to run.
The device is manufactured using Atmel’s high-density non-volatile memory technology. The On-chip ISP Flash allows the program memory to be reprogrammed In-System through an SPI serial interface, by a conventional non-volatile memory programmer, or by an On-chip Boot program running on the AVR core. The Boot Program can use any interface to download the Application Program in the Application Flash memory. Software in the Boot Flash section will continue to run while the Application Flash section is updated, providing true Read-While-Write operation. By combining an 8-bit RISC CPU with In-System Self-Programmable Flash on a monolithic chip, the Atmel ATmega64 is a powerful microcontroller that provides a highly-flexible and cost-effective solution to many embedded control applications.
The ATmega64 AVR is supported with a full suite of program and system development tools including: C compilers, macro assemblers, program debugger/simulators, In-Circuit Emulators, and evaluation kits.
ATmega103 and ATmega64 Compatibility
The ATmega64 chip is a highly complex microcontroller where the number of I/O locations supersedes the 64 I/O location reserved in the AVR instruction set. To ensure backward compatibility with the ATmega103, all I/O locations present in ATmega103 have the same location in ATmega64. Most additional I/O locations are added in an Extended I/O space starting from 0x60 to 0xFF (i.e., in the ATmega103 internal RAM space). These location can be reached by using LD/LDS/LDD and ST/STS/STD instructions only, not by using IN and OUT instructions. The relocation of the internal RAM space may still be a problem for ATmega103 users. Also, the increased number of Interrupt Vectors might be a problem if the code uses absolute addresses. To solve these problems, an ATmega103 compatibility mode can be selected by programming the fuse M103C. In this mode, none of the functions in the Extended I/O space are in use, so the internal RAM is located as in ATmega103. Also, the extended Interrupt Vectors are removed. The ATmega64 is 100% pin compatible with ATmega103, and can replace the ATmega103 on current printed circuit boards. The application note “Replacing ATmega103 by ATmega64” describes what the user should be aware of replacing the ATmega103 by an ATmega64.
ATmega103 Compatibility Mode
By programming the M103C Fuse, the ATmega64 will be compatible with the ATmega103 regards to RAM, I/O pins and Interrupt Vectors as described above. However,some new features in ATmega64 are not available in this compatibility mode,these features are listed below:
• One USART instead of two, asynchronous mode only. Only the eight least significant bits of the Baud Rate Register is available.
• One 16 bits Timer/Counter with two compare registers instead of two 16 bits Timer/Counters with three compare registers.
• Two-wire serial interface is not supported.
• Port G serves alternate functions only (not a general I/O port).
• Port F serves as digital input only in addition to analog input to the ADC.
• Boot Loader capabilities is not supported.
• It is not possible to adjust the frequency of the internal calibrated RC Oscillator.
• The External Memory Interface can not release any Address pins for general I/O,neither configure different wait states to different External Memory Address sections.
• Only EXTRF and PORF exist in the MCUCSR Register.
• No timed sequence is required for Watchdog Timeout change.
• Only low-level external interrupts can be used on four of the eight External Interrupt sources.
• Port C is output only.
• USART has no FIFO buffer, so Data OverRun comes earlier.
• The user must have set unused I/O bits to 0 in ATmega103 programs.
Pin Descriptions
VCC
Digital supply voltage.
GND
Ground.
Port A (PA7..PA0)
Port A is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port A output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port A pins that are externally pulled low will source current if the pull-up resistors are activated. The Port A pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port B (PB7..PB0)
Port B is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port B output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port B pins that are externally pulled low will source current if the pull-up resistors are activated. The Port B pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port C (PC7..PC0)
Port C is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port C output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port C pins that are externally pulled low will source current if the pull-up resistors are activated. The Port C pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port C also serves the functions of special features of the ATmega64. In ATmega103 compatibility mode, Port C is output only, and the port C pins are not tri-stated when a reset condition becomes active.
Port D (PD7..PD0)
Port D is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port D output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port D pins that are externally pulled low will source current if the pull-up resistors are activated. The Port D pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port E (PE7..PE0)
Port E is an 8-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port E output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port E pins that are externally pulled low will source current if the pull-up resistors are activated. The Port E pins are tri-stated when a reset condition becomes active, even if the clock is not running.
Port F (PF7..PF0)
Port F serves as the analog inputs to the A/D Converter. Port F also serves as an 8-bit bi-directional I/O port, if the A/D Converter is not used.Port pins can provide internal pull-up resistors (selected for each bit). The Port F output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port F pins that are externally pulled low will source current if the pull-up resistors are activated. The Port F pins are tri-stated when a reset condition becomes active, even if the clock is not running. If the JTAG interface is enabled, the pull-up resistors on pins PF7(TDI), PF5(TMS) and PF4(TCK) will be activated even if a reset occurs. The TDO pin is tri-stated unless TAP states that shift out data are entered. Port F also serves the functions of the JTAG interface.In ATmega103 compatibility mode, Port F is an input port only.
Port G (PG4..PG0)
Port G is a 5-bit bi-directional I/O port with internal pull-up resistors (selected for each bit). The Port G output buffers have symmetrical drive characteristics with both high sink and source capability. As inputs, Port G pins that are externally pulled low will source current if the pull-up resistors are activated. The Port G pins are tri-stated when a reset condition becomes active, even if the clock is not running. Port G also serves the functions of various special features. In ATmega103 compatibility mode, these pins only serves as strobes signals to the external memory as well as input to the 32 kHz Oscillator, and the pins are initialized to PG0 = 1, PG1 = 1, and PG2 = 0 asynchronously when a reset condition becomes active, even if the clock is not running. PG3 and PG4 are Oscillator pins.
RESET
Reset input. A low level on this pin for longer than the minimum pulse length will generate a reset, even if the clock is not running. The minimum pulse length is given in Table 19 on page 50. Shorter pulses are not guaranteed to generate a reset.
XTAL1
Input to the inverting Oscillator amplifier and input to the internal clock operating circuit.
XTAL2
Output from the inverting Oscillator amplifier.
AVCC
AVCC is the supply voltage pin for Port F and the A/D Converter. It should be externally connected to VCC, even if the ADC is not used. If the ADC is used, it should be connected to VCC through a low-pass filter.
AREF
AREF is the analog reference pin for the A/D Converter.
PEN
This is a programming enable pin for the SPI Serial Programming mode. By holding this pin low during a Power-on Reset, the device will enter the SPI Serial Programming mode. PEN has no function during normal operation.
Register Summary
Notes:
1. For compatibility with future devices, reserved bits should be written to zero if accessed. Reserved I/O memory addresses should never be written.
2. Some of the status flags are cleared by writing a logical one to them. Note that the CBI and SBI instructions will operate on all bits in the I/O Register, writing a one back into any flag read as set, thus clearing the flag. The CBI and SBI instructions work with registers 0x00 to 0x1F only
Instruction Set Summary
Subscribe to:
Posts (Atom)