[=>GO TO HELP] Wafercard with PIC 16F84 and EEPROM 24C16 (Twostone-Wafercard)
[=>GO TO HELP] AVR-Yupiter-Card with AT90S2323 and EEPROM 24C16 (Twostone AVR)
[=>GO TO HELP] AVR-Yupiter-Card with AT90S2343 and EEPROM 24C16
[=>GO TO HELP] Funcard with AT90S8515 and EEPROM 24C64 (Twostone-Funcard)
[=>GO TO HELP] Jupiter 2 Card with AT90S8535 and EEPROM 24C64

ChipCat cooperates with a lot of passive Programmern. Presupposition are all passive Programmers which have AVR-and PIC-procedure. In addition still 3.5 or 6.0 Mhz Mouse must be existing. Both can be in a device or be connected in separated COM-interfaces.
Were tested: MasterCRD, AVR-Mouse, Multiprog Quadro, in 2001, 2001 XL, Card-maestro. Naturally also function a row other Programmer, I have not tested them(it), however, and therefore can give also no functional guarantee for it. Does not function with Multiprog in 2000.

With ChipCat describing the EEPROMs on the Smartcards goes very simple. Simply file for the controller [1] and the EEPROM [2] select, and program. Which procedure must be put with the Programmer,
is indicated by ChipCat. Also choices of the EEPROM are possible, however, in this connection, the original content of the controller is headed. ChipCat has firmly inserted a fitting Loader for every supported Smartcard-type. An external Loader is not necessary.
ChipCat can invite for the EEPROM .hex.bin and .crd-files. Unfortunately, there is with .crd-files no uniform (standardized) format, so that ChipCat tries independently to determine the fitting format. If the format of the file should not unambiguously be recognizable, the file can not be loaded. Weights You with the producer of this file... Not with me.
I don't want to give here any manual for "Dummies" how anybody programs a ticket(map) quickly. I think, all should experiment by find out how it functions. Only so You can learn from Your own mistakes.

Here only a few Tipps to the configuration.
The sliding regulator "Speed" determines the timing with the programming from AVR-and PIC-controllers. You try the best attitude(setting) yourself best, while You program a controller with Verify. Step during programming or with the Verify a mistake on, the regulator must farther be pushed to the right.
The COM-Port for the controllerprogramming (AVR-/PIC-Mode) and EEPROM-PROGRAMMING (Mouse-fashion) can be put separated, so that also two different Programmer can be used in separated Ports.

MISTAKE MESSAGES
Verify anus programming:
The content of the controller is checked night of taken place programming. *! * with the programmation of the EEPROMs in the Mouse-procedure a Verify is not always executed automatically, however, Loader-boarder is implemented and indicated.
Promptly before write and erase:
If a Smartcard is deleted or should be described, an indication appears.
Enable Warnings:
A warning appears if the controller-content should be headed by the Loader.
Auto file reload on startup and device change:
Letzen to used files are automatically invited if Chip-Cat is started or is changed the Smartcardtyp.
Clear all memory before loading:
The complete warehouse content is set on $FF, before a new file is invited. As a rule this option can be remain activated. However, before the shop of .crd-files this function can be switched off around a for example only part of the EEPROM-DATA by the .crd-file to change.
Don't write EEPROM if all addressing ares $FF:
If the whole EEPROM-STORAGE AREA is empty, the EEPROM mustn't  also be described. Through here can be forced, for example that only the controller is written again.

PS. Deleting a storage area takes place by pressing of the right mouse-key. In the appearing pop-up-menu can be chosen whether the storage area on $FF or 00 $ should be set.

[ Author/Programmer from the ChipCat] [Need you even more help? Click!]