Aug 10, 2017. Serial eeprom programmer 93c56 diagram. Xhorse VVDI2 Commander Key Programmer Full Version Including PSA functions VVDI 2 Updated to V V Download link pass: vvdi2 full manual. Software modules description and prices Transponder.

In many circumstances it is desirable to work with an 8 pin serial eeprom or Motorola microcontroller while it remains connected to the circuit assembly. The less desirable task of completely unsoldering the part from the board so that it can be attached to the programming instrument is far more likely to cause problems. Issues such as chip damage due to heat, lifting a board trace or dislodging of near by surface mount components all make chip removal a far more risky process. Cleaning the chip pins and attaching a clip or probes to the in-circuit part allows for a faster, safer procedure with much less risk of assembly damage. THE CHALLENGES OF IN-CIRCUIT READING AND PROGRAMMING In-circuit access to an 8 pin serial eeprom or microcontroller poses a challenge to product designers as the part is not only soldered to the circuit assembly but is also connected to existing components on the assembly itself. The challenge is to make the part appear to the programming instrument as though it is an unconnected device. In other words make a part which is already connected to other components look like it is not.

Andromeda Research products are designed to work with eeproms and microcontrollers in-circuit. The AR-32A programming instrument, when used with adapters specifically designed for in-circuit work, provides the best opportunity for successful part communication without removal from the assembly. Andromeda Research is know for providing an excellent in-circuit reading and programming solution for applications where unsoldering the part from the circuit assembly is not the desired approach. OBSTACLES TO SUCCESS - There are two primary obstacles or conditions which can interfere with successful in-circuit eeprom work. These are existing circuit loading and existing circuit activity.

EXISTING CIRCUIT LOADING - The part shown in the photo on the right is a 95320 serial eeprom. The hi-lited (yellow) circuit traces show how the part is connected to other components on the assembly. When the programming instrument is attached to the part and instructed to read the data two fundamental conditions must occur. First the part must have power applied in order to operate.

Second, each pin on the part which is required for successful communication must be driven to a valid logic level while the part is being read. A logic level is the voltage necessary for the part to interpret the applied signal as a logic 0 (low) or logic 1 (high).

If the part does not see a valid logic level on all pins necessary for communication then the part will not respond. The programming instrument must have sufficient drive capability to overcome the load presented by the existing module circuitry (yellow traces) to allow the application of valid logic levels. EXISTING CIRCUIT ACTIVITY - The second condition which affects successful in-circuit programming is caused by power backfeeding into the circuit assembly. The backfeed occurs because the power pins on the chip to which the programming unit is connected are also connected to the common power bus which feeds the entire module circuit assembly. If the power (voltage) applied to the eeprom chip is the same level as the standard assembly operating voltage, then the entire module will power up and become active (see photo right). When this happens the processor (microcontroller) will begin communicating with the eeprom at the same time the programming instrument is attempting to read data from the chip.

The resulting data collision causes invalid or incorrect data to be read by the programming instrument. Also, in some cases, the collision can cause data corruption within the eeprom itself as the chip is trying to process and respond to commands from two different sources (processor and programmer). CIRCUIT LOADING - The issue of circuit loading is addressed by incorporating push-pull pin driver circuitry in the programming instrument and adapters. A push-pull pin driver operates by forcing current to flow in both directions (in and out) with respect to the target pin and desired logic level. The driver circuit incorporates a two transistor output stage where the top transistor will source (push) a positive current into the device pin for a logic 1 (high). For a logic 0 the bottom transistor will conduct and (sink or pull) current from the device pin forcing it to a low voltage level.

Because there are individual transistors dedicated to driving the device pin to each logic level, a push-pull driver provides the best opportunity to overcome a pin load due to the pin being connected to existing components on the assembly. Also, due to the design of the push-pull circuit, the driver will limit the current applied to the pin to a level which prevents the attached circuitry and programming unit from being damaged.

CIRCUIT ACTIVITY - The issue of power backfeeding into the circuit which causes the entire assembly to become active is addressed with a special adaper which incorporates a variable voltage power selector. The in-circuit serial eeprom adapter allows the voltage which is applied to the assembly to be reduced when the eeprom is read or programmed. This is accomplished using two switches; VOLTAGE (LV-5V) and LV RANGE (3.0-3.6-4.2). Reducing the operating voltage to the assembly has two effects. The first is that the other components on the assembly, even though active, will present a reduced load.

This is because there is less current available to interfere with reading and programming the eeprom in-circuit allowing the push-pull driver to be more effective. The second is that the microcontroller (processor), which will normally start accessing the eeprom when the power is applied to the assembly, will not start at a reduced voltage. This means that invalid data resulting from processor interference does not occur. Using the voltage reduction technique provides excellent results when reading or programming eeproms in-circuit. WORKING WITH MICROCONTROLLERS IN-CIRCUIT - Microcontrollers present a similar but somewhat different challenge as compared to in-circuit work with eeproms. First, unlike the eeprom, microcontrollers cannot be operated at a reduced voltage. A microcontroller must operate at its specified voltage (usually 5 volts) to function properly.

In its normal operating mode the microcontroller performs the functions for which it was programmed (airbag module, digital cluster, immobilizer, etc.). This is the program that it runs when the module starts. When in-circuit reading and programming of a microcontroller is desired, the microcontroller must NOT run its standard program. It must run another program (special communication) or enter a mode which will allow the programming instrument to communicate with the microcontroller itself. This is much like a modem link between two computers except in this case it is between the programming instrument and the microcontroller. Neax 2000 Ips Matworx Download Movies more. In order for the microcontroller to enter the special communication mode certain pins (pin numbers) on the chip itself must be preset to specific logic or voltage levels.

Once the preset levels are established, the microcontroller will be reset by the programming instrument. When the microcontroller exits the reset condition it will test the logic state on the pins. Based on the pin logic levels the microcontroller will either run its standard program or enter the special communication mode. The illustration on the right shows a Motorola 68HC11E9 microcontroller. You can see from the top illustration the power pins (1 and 26), the communication pins (20 and 21), the reset pin (17), the clock input pin (7) and the mode pins (2 and 3). The logic levels on the mode pins determine which program the microcontroller will run after the part is reset. The lower photo shows the probes physically connected to the part.

In most cases connecting to the microcontroller is simply a matter of attaching the correct probes to the proper pins on the part. If, however, a pin on the part cannot be driven to the required logic level, the microcontroller will not run the communication program or enter the communication mode. TIPS AND TOOLS FOR IN-CIRCUIT MICROCONTROLLER WORK The pin connections on a microcontroller are subject to the same loading conditions which affect eeproms when working in-circuit. The microcontroller adapter () is designed with push-pull drivers which provide the best opportunity for successful in-circuit work. A condition which can occur with a microcontroller is that a pin which defines the chip operating mode (standard program or communication program) may be attached to an assembly power rail (directly to the power supply track). If the module design engineer chose to connect the pin directly to the power supply to present the desired logic level to the part, but the opposite logic level must be applied in order to enter communication mode, it is possible that a 'short-circuit' will result.

Progecad 2011 Professional Italiano Download Firefox on this page. In other words if a logic 1 (5 volts) is required for the standard program to run and a logic 0 (ground) is required for communication mode, when you attach the probe which forces the logic 0 on the pin you connect ground to 5 volts which creates a short. This does not damage the programming instrument or the part however it obviously will not allow the part to work. In this case the offending pin must be isolated from the assembly circuitry (disconnected from the board) in order for in-circuit work to be successful.

There are two techniques for isolating (disconnecting) a microcontroller pin which cannot be driven or forced to the required logic level. The first is to heat the pin with a low wattage soldering iron (top photo) until the solder melts. Once the solder is molten place a sharp object such as a dental pick (second photo) or x-acto knife blade behind the pin and carefully lever it up (about 45 degrees) or until the connection between the pin and assembly pad is open.

Once the pin is free connect the probe and perform your work. After you are finished bend the pin down until it contacts the pad then apply heat from the soldering iron. You may need to apply a small amount of solder. The second technique is to cut the track which connects to the pin. This only works if the pin is connected to a single track. If the track continues under the chip this will not work. To cut the track use an x-acto knife or other sharp object and very carefully cut across the width of the trace until there is a clear opening in the conductor.

You can confirm that the trace is open using an ohm meter or the LP-1 (see below). After you have performed your work carefully scrape the solder mask from each side of the cut then apply a small amount of solder across the cut to create a solder bridge. This reestablishes the connection.

LOGIC/TEST PROBE - The LP-1 Logic/Test probe is a tool designed to identify in-circuit programming issues before communication problems occur. The LP-1 allows you to determine if a pin on the target device can be driven to valid logic levels before you connect the programming instrument. This not only saves time but also eliminates the need to guess which pin to lift if communication is not successful. Use of the LP-1 also prevents the possibility of grounding a mode pin which may short out the power connection. The LP-1 works by injecting the same drive signal into the target device pin (microcontroller or eeprom) as is used by the programming instrument. If the LP-1 cannot drive the pin the LED indicator on the probe will stop flashing and lock at one level.

This indicates to you that the pin must be lifted. The LP-1 will also work (test mode) as a standard logic probe. In this mode the probe will indicate the logic level (high or low) on a specific pin.

Here’s how to reprogram your odometer after an instrument cluster swap. The vehicle this was demonstrated on is a 2004 Honda Accord. YouTube Video: DIY Honda Odometer Reprogramming Disclaimer: 1. The information provided should only be used to correct mileage information. While it is not illegal to change your odometer reading, it is illegal to falsify or misrepresent the actual mileage of the vehicle. The odometer display can be just as easily changed by swapping clusters to one of a lower mileage. This procedure requires disassembly of the cluster, and de-soldering of SMD components.

Use care and caution when dealing with delicate components, and practice first on a spare cluster. Step 1: Introduction. Let’s say you swapped an instrument cluster from a coupe to a sedan to change the look or color of the needles, or you’re replacing a defective cluster.

The mileage on most (Japanese) cars is stored on the instrument cluster itself, and not in the ECU. Therefore the mileage of the original vehicle that the cluster was from will be displayed on the dash. Odometer information is stored on a small EEPROM chip on the circuit board. The chip can be read and written to using a serial programmer. The information is coded in HEX characters. The odometer information can be copied over from the old cluster to the new cluster using Honda HDS, assuming the original cluster is operable.

What follows is a hack-around to using HDS, by programming the mileage directly to the chip. You can also opt to merely swap the chips, or copy and paste the program, rather than decode.' ' Tools and Parts Required: • Screwdrivers • Soldering iron, solder and a de-soldering pump • Computer with Windows XP and serial port • 8 pin DIP socket • Serial programmer - Breadboard - Hookup wire - Female serial port header - 5V from computer power supply - 4.7K ohm resistors - 5V Zener diodes o Wire strippers • Serial programming software (PonyProg freeware) • A spare instrument cluster in case you screw up Here's the original instrument cluster from my LX sedan, 314,622 km, and here’s my new cluster. It’s from an EX-L sedan with 211,150km.

Step 2: Disassemble the Instrument Cluster. Once the cluster is out of the vehicle, pull up on a few tabs to remove the front plastic cover and fascia. The needles will need to come off next.

Pull up on them carefully and they’ll come out. Take a photo of their home position before taking this apart so you know where to realign it upon reassembly.

Use gloves and don’t touch the black face of the gauges, it’s a fingerprint magnet. Once the gauge face is removed, remove the white backing plate revealing the circuit board, with the L56 EEPROM chip.

Step 3: Solder Hookup Wires. According to the datasheet, pins 1, 2, 3, 4, 5 and 8 will need to be connected for programming. To read the information off the chip, while it’s still in the cluster, we need to solder some hookup wires to the leads. If you use a multimeter you can trace the leads to the pads on the other side of the circuit board, and then solder some hookup wire.

Now before you can properly read from the chip, on board, you have to short the crystal, located to the top left of the EEPROM chip. Step 4: Programming Hardware Setup. This is the EEPROM programmer I built to connect the chip to my desktop computer. It interfaces through the RS232 serial port. All it is are three 5V zener diodes ($1) and three 4.7K ohm resistors ($1).

The rest is some 22 AWG hookup wire and a breadboard ($5). And here’s my programmer connected to the PC.

And the breadboard with the resistors and diodes. Now here’s where it got tricky. Using the PonyProg software, I was able to read and save the information from the odometer chip. But I wasn’t able to write to the chip.

The EEPROM must be removed from the board if you want to write to it, as it can’t be programmed in circuit. So off we went trying to desolder an SMD chip And SNAP!!! The leads broke off the chip. This is why you should use a hot air station so it heats all the pads evenly and you can just pick the chip off the board instead of prying it. Luckily, I had saved the EEPROM information I downloaded earlier. I found another replacement chip, the Microwire 93C56 chip from a car’s ECU I had laying around. The 93C56 chip is identical electronically to the L56 chip.

So I soldered wires to the “new” chip, and was able to connect it to the programmer directly, without having the board hamper the write function. The additional advantage is I could now quickly disconnect and reconnect my chip to the odometer board, and then test my new program out on the car as I decoded the odometer program. Step 5: Programming: Reading From the EEPROM.

I used PonyProg software, which is a free serial device programmer. It reads and writes to the COM port, which in my case is directly to the chip. If you don’t have a serial port on your computer, you can purchase an EEPROM programmer that connects via USB and emulates a serial port. First thing, head over to the setup menu under options; Make sure its set to read from the serial port, COM1, and SI Prog I/O. You can then Probe the port to make sure it detects your serial programmer.

Next head over to the device menu and select Microwire 93C56, which is compatible with the L56 EEPROM chip. Then click Device –>Read to read from the chip.

The information from the chip will be downloaded in HEX format in a 16 by 16 bit array. Step 6: Decoding the Odometer Dump. At this point you can merely save the odometer dump, and write it to your new cluster. Or if the engineer inside you is itching to make sense of 256 HEX characters, you can attempt to decode it.

Here’s a look at the HEX dump. Through a lot of trial and error, back and forth in the vehicle, and a few hours of hair pulling, calculating and note-taking, I was able to come up with a rough idea of how the odometer program works. The odometer has a major value in addition to a minor value that increments. Trip A and B are also stored in the EEPROM. The major value is what I’ll be focusing on, since that controls the thousands of kilometers which is more important. Knowing this, if we focus on the last few lines in the EEPROM dump, you’ll notice the characters 33 85 CC 7A repeated 8 times. This is the major odometer value in HEX.

The numbers are actually the HEX invert of each other, and act like a checksum. A HEX lookup table, which is 0-F and F-0 backward is used to determine the inverse of each character.

For example, a “3” will be inverted as “C”, and 8” inverted as “7” and “5” inverted as “A”. Therefore the only characters that store actual information are the first two HEX digits, 33 and 85. To decode, simply convert the number to decimal using a hex to decimal converter, and then multiply by 16 to give you the odometer reading in kilometers. I got 211,024km. Using this method of calculation, I need the new cluster to read 314K, so I can divide it by 16 and convert it to HEX to give me the base value in the odometer dump. This value, 4C CF will then have a checksum of B3 30, which I will write to the chip.

Now I know it’s not exactly accurate but close enough, because there is a minor incremental value that I haven’t decoded. I made an excel sheet to help me convert the numbers. Step 7: Writing Information to the EEPROM Chip. Now that we’ve got the corrected mileage value, head back to the PonyProg software and click Edit – Edit Buffer Enabled to enable writing to the HEX bits. Click on the bit you want to edit and type in the new value. In my case I replaced all “33 85 CC 7A” with “4C CF B3 30”.

Here’s what my modified odometer dump looks like with the bottom two rows edited for 314K. And that’s it, you can now disconnect the EEPROM from the programmer and hook it up to the odometer board to test it out. Step 8: Prototyping. Since I still had the hookup wire attached to the original odometer board, I use it to temporarily connect the EEPROM chip with the 314K program on it and test it in the car to see if it works.

I used alligator clips to connect the six hookup wires to the EEPROM. It looks ghetto, but this is only a test before re-soldering the chip! And start it up and it reads 314,543km, which is close enough to what I had on the old cluster. I’ve also gained the outside temperature display option on the EX-L cluster. Step 9: Closing Everything Back Up. Next, we can transfer the new programmed chip back onto the odometer board. In my case it was already soldered onto an ECU board, and it needed to be de-soldered.

A hot air station is highly recommend here, as we broke more pins taking this one off too! Then solder the new chip back onto the board. When removing the original chip, a few of the pads got damaged.

Thus a patch wire was soldered in to compensate for the lack of conductivity with the board beneath the lead. Now its time to reassemble the instrument cluster. Reinstall the needles, in the position that they originally came off in. They have a stopper that has to be adjusted. Good idea to refer to a photo of the cluster before you took things apart to get it aligned. Step 10: Results. Gauges can be calibrated by hand when the cluster is turned off.

Use an OBDII scanner to determine vehicle and engine speed and coolant temperature. Calibrate the gas gauge when the gas light turns on. The odometer does not roll over to 1 million kilometers. But the trip computer still works, as you can see here, I drove just over a kilometer to see what would happen. Once all the gauges are closed up, it’s interesting that Honda left a hole in the back of the cluster exactly behind where the EEPROM sits, where we soldered the hookup wire.

Remember though, even if you were able to solder hookup wire without taking apart the circuit board, you wouldn’t be able to write to the chip in circuit, just read from it. Just a thought.