General. 48Pro2 programmer offers the same advanced features as 48Pro+ programmer but with much higher programming speeds (20-75%) for high-capacity memories. FPGA based totally reconfigurable 48 powerful TTL pindrivers provide H/L/pullup/pulldown and read capability for each pin of socket. Advanced pindrivers incorporate high-quality high-speed circuitry to deliver signals without overshoot or ground bounce for all supported devices.
Improved pin drivers operate down to 1.8V so you'll be ready to program the full range of tomorrows advanced low-voltage devices. The programmer performs device insertion and contact tests before programming each device. These capabilities, supported by overcurrent protection and signature-byte check help prevent chip damage due to operator error. The selftest capability allows diagnostics included in the software to thoroughly check the health of the programmer. Built-in protection circuits eliminate damage to the programmer and/or programmed devices due to environment or operator failure. All the inputs of the 48Pro2 programmer, including ZIF socket, connection to PC and power supply input are protected against ESD up to 15kV.
48Pro2 programmer performs programming verification at the marginal level of supply voltage, improving programming yield and guarantying long data retention. Various socket converters are available to handle device in PLCC, JLCC, SOIC, SDIP, SOP, PSOP, SSOP, TSOP, TSOPII, TSSOP, QFP, PQFP, TQFP, VQFP, QFN (MLF), SON, BGA, EBGA, FBGA, VFBGA, UBGA, FTBGA, LAP, CSP, SCSP, LQFP, MQFP, HVQFN, QLP, QIP and other packages. User Interface. Programmer is driven by an easy-to-use control program with pull-down menus, hot keys and on-line help. Selecting of device is performed by its class, by manufacturer or simply by typing a fragment of vendor name and/or part number. Standard device-related commands (read, blank check, program, verify, erase) are enhanced by test functions (insertion test, signature-byte check) and additional special functions (auto-increment, production mode - programming starts immediately once chip inserted into socket).
All known data formats are supported. Automatic file format detection and conversion during loading of file. The versatile auto-increment function allows each programmed device to be assigned an individual or incrementing serial number. This function also enables the operator to read serial numbers or device identification signatures from a file. The software provides extensive information about programmable devices including detailed drawings of all available packages. The software also provides explanations of chip labelling (prefixes and suffixes) for each of the supported chips.
The software provides full information for ISP implementation: Description of ISP connector pins, recommended target design and other necessary information. The remote control feature allows the software to be flow controlled by another application - either using.BAT file commands or DLL file (C/PAS/VBASIC/.NET). Jam files of JEDEC standard JESD-71 are interpreted by Jam Player.
Jam files are generated by design software which is provided by the manufacturer of respective programmable device. Chips are programmed in-ZIF or through ISP connector (IEEE 1149.1 Joint Test Action Group (JTAG) interface). VME files are interpreted by VME Player. VME file is a compressed binary variation of SVF file and contains high-level IEEE 1149.1 bus operations.
VME files are generated by design software which is provided by the manufacturer of respective programmable device. Chips are programmed in-ZIF or through ISP connector (IEEE 1149.1 Joint Test Action Group (JTAG) interface). Multiple devices can be programmed and tested via JTAG chain: JTAG chain (ISP-Jam), JTAG chain (ISP-VME), JTAG chain (ISP-SVF) or JTAG chain (ISP-STP). Multiple 48Pro2 programmers can be connected to the same PC (via USB port) achieving an extremely powerful multi-programming system, supporting as many devices as a single 48Pro2 programmer and without a noticeable decrease in programming speed.
Concurrent multi-programming is also supported allowing each programmer to work independently increasing throughput. Keeping your programmer software up to date can be a costly business with some programmers. Dataman offers completely FREE software updates whenever you need them.
The latest software is always available from our website. Device Support The Dataman 48Pro2 supports over 110,000 of the most popular devices in use today - with future devices being added monthly. Dataman 48Pro2 coverage includes the following device types ZIF Socket. NAND Flash: Samsung K9xxx, KFxxx, SK Hynix (ex Hynix) HY27xxx, H27xxx, Toshiba TC58xxx, TH58xxx, Micron MT29Fxxx, (ex Numonyx ex STM) NANDxxx, Spansion S30Mxxx, S34xxx, 3D-Plus 3DFNxxx, ATO Solution AFNDxxx, Fidelix FMNDxxx, Eon Silicon Sol. Dataman 48Pro2 Super Fast Universal ISP Production Programmer. Dimensions: 195 x 140 x 55mm (7.7 x 5.5 x 2.2inches).
Weight: 0.9Kg (1.98lbs). Operating voltage: 100-240V AC.
Power consumption: max. 20W active / approx. 2W sleep. Power Cable. Moulded USB Cable. ISP Cable. Diagnostic POD for selftest of the programmer.
Diagnostic POD for selftest of the ISP connector. Anti-dust cover for ZIF socket. User Manual.
Software. Compatible with Windows XP, Windows Server 2003, Windows Vista, Windows 7, Windows 8 and Windows 10. Please see our for more information. Optional range of adapters and socket converters also available The Dataman 48Pro2 super fast universal programmer comes with:. 30 Day Money Back Guarantee.
If you don't like it, send it back. Three Year Guarantee - Three years parts and labour warranty, on the 48Pro2 universal device programmer. Life-Time Technical Support - 48Pro2 technical support is available free via our website and telephone helpdesk for life. Life-Time Software Updates - 48Pro2 software updates are available free via our website for life.Applies to orders from UK/US offices only.
17 Aug 04 - 26 Apr 15 ISP Flash Microcontroller Programmer Ver 3.0a Mohammad Asim Khan, Introduction This ISP Programmer can be used either for in-system programming or as a stand-alone spi programmer for Atmel ISP programmable devices. The programming interface is compatible to STK200 ISP programmer hardware so the users of STK200 can also use the software which can program both the 8051 and AVR series devices. Hardware Figure 1 shows the circuit diagram of the in-system programmer interface, the power to the interface is provided by the target system. The 74HCT541 ic isolate and buffer the parallel port signals.
It is necessary to use the HCT type ic in order to make sure the programmer should also work with 3V type parallel port. Figure 1: Circuit Diagram of the ISP Programmer Interface Figure 2 shows the circuit diagram of the stand-alone spi programmer, the power to the interface is provided by the PC USB port which can supply a max of 100mA current.
Get a cheap USB cable, cut the cable other end connector and attach a crimp shell connector to this end, red wire is 5V and black is 0V. The printer port buffer interface is same as shown in figure 1. For the u-controller a 40 pin ZIF socket can be used.
This programmer circuit can be use to program the 89S series devices and the AVR series devices which are pin compatible to 8051, like 90S8515. For other AVR series devices the user can make an adapter board for 20, 28 and 40 pin devices. The pin numbers shown in brackets correspond to PC parallel port connector. Figure 2: Circuit Diagram of the SPI Programmer Software The ISP-30a.zip file contains the main program and the i/o port driver. Place all files in the same folder. The main screen view of the program is shown in figure 3.
Also make sure do not program the RSTDISBL fuse in ATmega8, ATtiny26 and ATtiny2313 otherwise further spi programming is disable and you will need a parallel programmer to enable the spi programming. For the fuses setting consult the datasheet of the respective device. For the auto hardware detection it is necessary to short pin 2 and 12 of DB25 connector, otherwise the software uses the default parallel port i.e.
Following are the main features of this software,. Read and write the Intel Hex file. Read signature, lock and fuse bits. Clear and Fill memory buffer.
Verify with memory buffer. Reload current Hex file. Display buffer checksum.
Program selected lock bits & fuses. Auto detection of hardware Note: The memory buffer contains both the code data and the eeprom data for the devices which have eeprom memory. The eeprom memory address in buffer is started after the code memory, so it is necessary the hex file should contains the eeprom start address after the end of code memory last address i.e. For 90S2313 the start address for eeprom memory is 0x800.
The software does not provide the erase command because this function is performed automatically during device programming. If you are required to erase the controller, first use the clear buffer command then program the controller, this will erase the controller and also set the AVR device fuses to default setting. Download ISP-Flash Programmer Software Figure 3: Main screen of the program ISP-Pgm Ver 3.0a Contribution to Asim's ISP Loader Schematics and PCB Files including PDF layouts for all layers designed by from Iran using Eagle cadsoft. Updated 8-Sep-2005 Single side layout made by from Egypt. Single Side PCB files in Post Script and PDF Format made by from India. Layout made by Mehrdad Mahboudy from Iran.
The ISP-Flash Programmer was designed. Revised 14.August.2004 Any bug report or suggestion of using the ISP-Flash Programmer are welcome.
6- and 10-pin AVR ISP headers In-system programming (ISP), also called in-circuit serial programming (ICSP), is the ability of some, and other to be programmed while installed in a complete system, rather than requiring the chip to be programmed prior to installing it into the system. There are several mutually-incompatible in-system programming protocols for programming devices, including, and the.
ICSP has been primarily implemented by for programming PIC and dsPIC devices. The primary advantage of this feature is that it allows manufacturers of electronic devices to integrate programming and testing into a single production phase, and save money, rather than requiring a separate programming stage prior to assembling the system. This may allow manufacturers to program the chips in their own system's production line instead of buying preprogrammed chips from a manufacturer or distributor, making it feasible to apply code or design changes in the middle of a production run. Microcontrollers are typically soldered directly to a printed circuit board and usually do not have the circuitry or space for a large external programming cable to another computer. Typically, chips supporting ISP have internal circuitry to generate any necessary programming voltage from the system's normal supply voltage, and communicate with the programmer via a serial protocol.
Most programmable logic devices use a variant of the protocol for ISP, in order to facilitate easier integration with automated testing procedures. Other devices usually use proprietary protocols or protocols defined by older standards. In systems complex enough to require moderately large, designers may implement a JTAG-controlled programming subsystem for non-JTAG devices such as and microcontrollers, allowing the entire programming and test procedure to be accomplished under the control of a single protocol. An example of devices using ISP is the line of micro-controllers by such as the series. Contents. Microchip ICSP For most Microchip microcontrollers, ICSP programming is performed using two pins, clock (PGC) and data (PGD), while a high voltage (12 V) is present on the Vpp/MCLR pin.
Low voltage programming (5 V or 3.3 V) dispenses with the high voltage, but reserves exclusive use of an I/O pin. However, for newer microcontrollers, specifically PIC18F6XJXX/8XJXX microcontrollers families, entering into ICSP modes is a bit different. Entering ICSP Program/Verify mode requires the following three steps:. Voltage is briefly applied to the MCLR (master clear) pin. A 32-bit key sequence is presented on PGD.
Voltage is reapplied to MCLR. Microchip ICSP programmer A separate piece of hardware, called a programmer is required to connect to an I/O port of a PC on one side and to the PIC on the other side.
A list of the features for each major programming type are:. Parallel port - large bulky cable, most computers have only one port and it may be inconvenient to swap the programming cable with an attached printer. Most laptops newer than 2010 do not support this port.
All cheat sheets, round-ups, quick reference cards, quick reference guides and quick reference sheets in one page. Cheat sheet sports.
Parallel port programming is very fast. Serial port (COM port) - At one time the most popular method. Serial ports usually lack adequate circuit programming supply voltage.
Most computers and laptops newer than 2010 lack support for this port. Socket (in or out of circuit) - the CPU must be either removed from circuit board, or a clamp must be attached to the chip making access an issue. USB cable - Small and light weight, has support for voltage source and most computers have extra ports available. The distance between the circuit to be programmed and the computer is limited by the length of USB cable - it must usually be less than 180 cm. This can make programming devices deep in machinery or cabinets a problem.
ICSP programmers have many advantages, with size, computer port availability, and power source being major features. Due to variations in the interconnect scheme and the target circuit surrounding a micro-controller, there is no programmer that works with all possible target circuits or interconnects. Provides a detailed ICSP programming guide Many sites provide programming and circuit examples. PICs are programmed using five signals (a sixth pin 'aux' is provided but not used). The data is transferred using a two wire synchronous serial scheme, three more wires provide programming and chip power. The clock signal is always controlled by the programmer. Typical chip connections.
Vpp - Programming mode voltage. This must be connected to the MCLR pin, or the Vpp pin of the optional ICSP port available on some large-pincount PICs.
To put the PIC into programming mode, this line must be in a specified range that varies from PIC to PIC. For 5 V PICs, this is always some amount above Vdd, and can be as high as 13.5 V. The 3.3 V only PICs like the 18FJ, 24H, and 33F series use a special signature to enter programming mode and Vpp is a digital signal that is either at ground or Vdd. There is no one Vpp voltage that is within the valid Vpp range of all PICs.
In fact, the minimum required Vpp level for some PICs can damage other PICs. Vdd - This is the positive power input to the PIC. Some programmers require this to be provided by the circuit (circuit must be at least partially powered up), some programmers expect to drive this line themselves and require the circuit to be off, while others can be configured either way (like the Microchip ICD2). The Embed Inc programmers expect to drive the Vdd line themselves and require the target circuit to be off during programming. Vss - Negative power input to the PIC and the zero volts reference for the remaining signals.
Voltages of the other signals are implicitly with respect to Vss. ICSPCLK - Clock line of the serial data interface. This line swings from GND to Vdd and is always driven by the programmer. Data is transferred on the falling edge. ICSPDAT - Serial data line.
The serial interface is bi-directional, so this line can be driven by either the programmer or the PIC depending on the current operation. In either case this line swings from GND to Vdd. A bit is transferred on the falling edge of PGC.
Fast Flash Programmer
AUX/PGM - Newer PIC controllers use this pin to enable low voltage programming (LVP). By holding PGM high, the micro-controller will enter LVP mode.
PIC micro-controllers are shipped with LVP enabled - so if you use a brand new chip you can use it in LVP mode. The only way to change the mode is by using a high voltage programmer.
If you program the micro controller with no connection to this pin, the mode is left unchanged. RJ11 pinout.
RJ11 to ICSP PIC programmer An industry standard for using with an ICSP programmer is supported by Microchip. The illustration represents information provided in their data sheets. However, there is room for confusion. The PIC data sheets show an inverted socket and do not provide a pictorial view of pinouts so it is unclear what side of the socket Pin 1 is located on. The illustration provided here is untested but uses the phone industry standard pinout (the RJ11 plug/socket was original developed for wired desktop phones). References.
This new version uses an SMD 5x2 header. This is a simple to use USB AVR programmer. It is low cost, easy to use, works great with, and is tested extensively on a Windows desktop. Based on Dick Streefland’s and Limor Fried’s. This is a low-cost programmer designed for those on a tight budget. This programmer works really well for ATmega168 and ATmega328 and should work with all the AVR micros supported by AVRDUDE.
The microcontroller-to-be-programmed can be any AVR with 64K or less of flash. The ATmega328 on an Arduino Uno or RedBoard works perfectly, but the ATmega2560 of an Arduino Mega does not. This board is buffered and power protected so that you can do some really evil things to the programmer without killing it. One of the greatest features of this board is the ability to power the target (up to 500mA) from the programmer. Note: This product is a collaboration with Limor Fried. A portion of each sales goes back to them for product support and continued development. Note: The drivers link has been updated below to be Windows 7 compatible.
—————— Tech Support Tips/Troubleshooting/Common Issues —————— Hardware Setup The Pocket AVR Programmer can be used with one of our old tutorials “ Lecture 2 - How to Get Code Onto a Microcontroller”. The tutorial was originally referring to two other programmers and not the AVR Pocket programmer. The circuit had to be modified a little to get it working. First, you need to build the circuit on the breadboard.
I didn’t need to add the voltage regulator to my setup since the AVR Pocket Programmer can provide the 5V. Make sure that you flip the switch to “ Power Target.” I did use two 0.1uF decoupling capacitors in the circuit, LED for blink, LED for power, reset button, and associated resistors as explained in the tutorial.
One thing I did was to add a 16MHz crystal on pins 9 and 10 of the Atmega328p. Install Driver and WinAVR Make sure that you install the driver for your Pocket AVR Programmer. They can be found in the documents section under the Windows Driver link. After installing, the Pocket AVR Programmer will come up as a new tree under libusb-win32devices - USBtiny.
Also, make sure that you are installing the latest version of WinAVR. For more information on Downloading, Installing, and Configuring WinAVR, check out this pdf =. Installing Pocket AVR Programmer Driver on Windows 8 If customers are using Windows 8, they would need to disable the driver enforcement =. The tutorial talks about it. Alternative Pocket AVR Programmer Driver Installation with Signed Drivers An easier method is to do, point your computer to a driver package that has all of the drivers that are digitally signed. Codebender has packaged a nice digitally signed installer that gets us through all of this headache. Brian (from SFE Education) tried this on his Windows without the need to disable drivers and download their specific driver file.
Go through Codebender’s getting started walkthrough to install the drivers in step 3. Modifying the Make File I had to do some modifications in order to use the Pocket AVR Programmer in the old tutorial. I was using the ConText editor instead of Programmer’s Notepad or JFE that was explained in the tutorial to modify the Make File. The code in the ConText editor was highlighted using the C/C option to read the file easier. Under the section that says “Programming Options (avrdude),” I had to modify two lines to get the Pocket AVR programmer working: 1.) In line 200, change: AVRDUDE-Programmer = stk200 to AVRDUDE-Programmer = usbtiny 2.) In line 207, change: AVRDUDEWRITEFLASH = -U flash:w:$(TARGET).hex to AVRDUDEWRITEFLASH = -F -U flash:w:$(TARGET).hex. The first modification was to set the programmer to use the Pocket AVR Programmer.
The second line is to override a certain check by avrdude. I found this in the comments but didn’t run into this issue before and after modifying line 207. Keep in mind that # comments out a line. Compiling Hex File Open up the Command Prompt. I placed the blink1MHz on my desktop but you can place it anywhere in your computer. Just make sure that you are in the same directory in the Command Prompt.
Make sure that you know how to navigate through folders =. After entering the correct directory, type make all to compile the hex file. This will output a lot of files in the blink1MHz folder. The most important is the.hex file. If you want to change the c file, you must modify the c file, type make clean in the command prompt, and type make all again. Setting Fuse Bits, Uploading Hex File, and Setting Lock Bit You should try looking at the tutorial for installing an Arduino bootloader =. This will help in getting the correct connections from the programming cable to your breadboard Arduino.
I double checked with a multimeter to check the wiring under the continuity setting. Also, the section under “Uploading Code - Hard Way” will be useful when in the Command Prompt to set the fuse bits, upload the hex file, and set the lock bits. The syntax is sensitive and you can have problems if you don’t write the correct commands. Since you are in the same directory already from compiling the hex file in the Command Prompt, you just need to type the two lines as stated in the tutorial to set the fuse bits and then upload the hex file and set the lock bit. Make sure that you change the hex file in the line flash:w: hexfilename.hex to flash:w: blink1MHz.hex For more information, I recommend checking out the avrdude manual on the other options =.
After doing all this setup, I was able to get the Atmega 328P microcontroller to blink with the Pocket AVR Programmer. Hope this helps. Powering Your Target Microcontroller Make sure that you power your target AVR microcontroller.
Normal AVR programmers don’t have this option. Luckily, the AVR programmer is able to power your target by flipping the switch to the silkscreen that says “Power Target.” The voltage is 5V. The No Power option is so that the USB is not providing power directly from the VCC pin on the USB port. When flipping the switch over, there is still some power coming partly from the ATtiny2313 pin connected to CTL.
CTL is pulled high by the programmer when in a non-programming state (in order to tri-state the buffer IC). The power should be low enough where it won’t harm the target. The Atmel chips that I have been using when switched to the No Power is within its voltage range so I do not see any issues. I would usually need to power the target board using a separate power supply and with the switch flipped to No Power. Using my multimeter set to a measure current, I did notice that there wasn’t a lot of power being sent to the Atmega328P. After flipping the switch to the Power Target, I noticed that it was pulling a lot more current because the USB’s port was powering the target. If you are using this to flash 3.3V microcontrollers, you should use a logic level controller or resistors for voltage division.
Even by flipping the switch to No Power, there is some power that leaks through to the target device. Measuring with a multimeter it is around 4.46V. This is normal and the programmer was designed that way. The target will not be directly connected to the 5V pin when the switch flipped to the No Power side. It’s also normal the that D-, Stat, and Power LEDs are on. Speaking from experience, you will not be able to flash code to your target when the switch is in that position since you are not powering the target device with an external power supply. Errors 1.) Using a USB hub cable with the programmer, it might not work properly if the cable is damaged.
You might get this error through your serial terminal: Could not find USB device 0x1781/0xc9f Try using a dedicated mini-B USB cable or a different USB cable to prevent this error. 2.) If you are seeing this error: avrdude: initialization failed, rc=-1 Double check connections and try again, or use -F to override this check it is due to a few reasons. I recommend checking pin connections. There might be the reset pin that is not connected sufficiently (I had problems when reprogramming an ATtiny with the reset and pin not connecting correctly).
You need to to disconnect components attached to microcontroller before you can upload a new program to the chip. This is explained with the ATtiny’s in this tutorial = ) This error usually means that the programmer is OK but it could not find the chip. Check the wiring connections and see if your target AVR microcontroller is powered. 3.) If you are seeing this error with the byte location varying on each attempt when flashing code: avrdude: verification error, first mismatch at byte 0x0080 0x80!= 0x58 avrdude: verification error; content mismatch It has something to do with the bitclock rate used by the programmer.
A customer had a similar issue and found it through some of the resources that I had provided him. Most likely the original bitclock setting was too fast for the chip which would cause a failure to write/read the chip’s memory correctly. Just open a command line interface and specify the -B50 in the avrdude command line in order to slow down the bitclock rate in the programmer (sck) to 50 microseconds. Programming via Arduino with a modified “avrdude.conf” Certain Arduino IDE’s like v1.0.1 has the avrdude’s command line hardcoded so it cannot be “changed.” You can view this by using the IDE into verbose mode. To modify the “hardcoded” avrdude used with the Arduino IDE, go to your avrdude.conf file and modify the bitclock rate variable. The customer that resolved his case by using to change the'defaultbitclock' at line 319 of the avrdude.conf for his ATtiny85: defaultbitclock = 50; The customer was able to compile the Blink.ino sketch file through the Arduino IDE in order to upload code to the Attiny85. There were no verification errors.
By changing the bitclock rate, this would naturally cause the code to upload noticeably more slowly. Hello, In the last 2 years I have bought two of these devices. One didn’t work anymore after a month. It would return a random device ID no matter what deivce I used it on (I attempted several custom devices and several arduino uno’s and mega’s). I bought a new one soon after, and that worked up till a few days ago where it started showing the exact same behaviour.
Can one of you tell me if this is an error in the device or if it is fixable? I tried to get a replacement from the reseller where I bought them, but they need confirmation that this means that they broke. Kind regards, Sybren Zwetsloot.
I was going to write a review in the Reviews section on this product but it will not allow me to for some reason. So I’ll post it here.
I purchased this product as a programmer for the Atmel ATMEGA328P. I had a little difficulty figuring out the USB driver installation, but finally got it to install. So far I’ve used to to reload the Arduino boot loader as well as with AVRdude and Atmel Studio. This thing works flawlessly! Very nice solution and the price is perfect.
Would highly recommend this wonderful low cost programmer to anyone interested in getting into the Atmel AVR (I’m a PIC & MCS-51 guy just getting into AVR’s). A proper solution for running under Windows 7, including 64 bit, without turning off driver signing.
Download the windows driver from sparkfun, and unzip it somewhere. Download a recent libusb release from sourceforge: and unzip it somewhere. Take the libusb0.dll and libusb0.sys files from the sourceforge bin amd64 directory, rename them to libusb0x64.dll and libusb0x64.sys, and replace those files in the sparkfun driver directory. Replace the sparkfun libusb0.sys and libusb0.dll with copies from the sourceforge bin x86 directory (renaming the sourceforge libusb0x86.dll to libusb0.dll). Your driver is now ready to go. Windows will complain during the install that the drivers aren’t signed, but they actually are. Once installation is done, Windows will happily load the new drivers.
Sparkfun: please update those four files in driver zip file. That will fix it for everyone. WARNING - TARGET BOARD DESTROYED: It is my opinion that the PCB differs from the circuit diagram on a critical point. The ‘Power Target’ switch (on my board) is NOT wired as per the diagram. It removes VCC from both the ISP connector AND the 74LC125 buffer IC. This means that your target device still gets 5 Volts via an internal path through the 74LC125.
No big deal, except if you plug in a target which uses 3 Volts only. My $50 Seeeduino Film was instantly destroyed!!! Not very happy at all. It’s been a long time since looking at hardware specs, but in case someone is searching for the same information I am, I’d agree with TravisF, based on looking at the schematic/board layout (may2013) it seems sensitive 3.3V targets are ill-advised.I do not own this board currently, so I can’t verify the below, it comes from looking at the design docs. 1 - Cutting the trace between JP1 pins might work (disconnects from USB 5V power so entire board could be 3.3V powered, but you lose fuse protection on VCC, and a target may not be able to supply enough current) However only 74AC125 buffers are spec’d to operate at 3.3V (schematic has 74ACT, while picture shows 74AC) Additionally, this presumes USB data signals will not cause issues on ATTINY if they end up at 5VI found a reference that they were supposed to be 3V? 2 - Moving the switch to “not-powered” does not seem to prevent issues.
Specifically as noted by TravisF/AffordableTechnology, CTL when driven from a 5V powered ATTINY will may either damage the 3.3V powered 74xx125 or leak through the 74xx125 & 22k (R10) to the target. If your device is 5V tolerant while running at 3V or not leaking much current through R10 you may not see problems.
Really what “not-powered” means in this context is USB power is not directly providing power to a target, and the 74xx125 buffer is powered by the target’s VCC. I would presume this is to avoid USB current limits more than to allow 3V compatibility. 3 - FYI if you’re considering cutting the CTL trace keep in mind that the 74xx125 is only spec’d to allow inputs VCC+0.5 so it could still be damaged by running it at 3V while the ATTINY is at 5V So in short it seems to me that if you need to program a 3V sensitive device, you may wish to use a logic level shifter. In fact, if you want to fix your programmer yourself, you can, but it requires hacking the board a bit.
It’s not for the faint of heart. Look at the bottom of the board. About 1/8' below the “COM” in “sparkfun.com” there’s a straight horizontal trace between two vias. Cut that trace. Now, back on the top of the board, tack a 1N4148 diode between pin 8 of the 2313 (the big chip), and pin 1 of the 74HC125 (the small chip).
Note that the two chips are opposite-oriented. Pin 1 of the 74HC125 is bottom right (with the USB to the left), and pin 8 of the 2313 is 3rd from the bottom-left. The cathode of the diode is on the 2313 end, and the anode on the 74HC125 end. That done, you should find that with the target power switch turned off that you can safely program 3.3 volt systems, provided they’re self-powered during programming.
Isp Flash Programmer
The one note is that you are still feeding 5 volt logic into the 74HC’s pins from the 2313. The 74HC’s datasheet shows diodes on the input pins to Vcc, which are intended to protect the 74HC from excess voltage on the inputs. It’s conceivable, I suppose, that that might wind up raising Vcc on the target, but I haven’t actually tried it.
64bit Win7 Solution!!! I am running Win7 x64 ultimate and trying to program some ATTiny84/5s with Ardiuno 1.0.1. After much frustration, stumbled upon this updated driver today and it just plain worked for me, no workarounds, no hassle.
I unzipped the archive and updated the ‘failed’ earlier driver install attempt - once update was complete, shows as USBtiny in Device Manager. I was expecting a com port to show up but figured out all I had to do in Arduino was select USBtinyISP as the “Programmer”.
Man am I pumped! Thought I was going to have to dance around all the other nonsense I was reading about to make this (now) super cool programmer work in Win7x64. Hope this helps others out there!! This thing is freaking AWESOME! I had some problems in the beginning, when I first started using this programmer.
I used my Arduino Uno SMD as an ISP programmer for a while to program ATMEGA’s and ATTINY’s while trying to get this thing to work properly. I had used it many times with Arduino 0022, but it was time consuming trying to find the.cpp and.hex files after compiling. But with the release of Arduino 1.0, it’s a breeze to program AVR chips. You don’t even need to use the command window. Just select ‘USBtiny’ from the list of programmers under ‘Tools’.
I’ve personally programmed the following with this programmer: ATTINY85, ATTINY84, and ATMEGA328P (both factory fresh and preprogrammed w/ bootloader). It works every time.
Device Search tip The names of the programmable devices in our database don't contain all characters, shown at the top of the chip or mentioned in a datasheet section part numbering. The names of the chips in our database contain all characters necessary for identification of the device, but don't contain such codes, that have no influence to the programming, for example temperature code, speed code, packing type code, etc. If such code letter is at the end of the name, it should be omitted (Ex. If such code letter is in the middle of the name, it should be replaced by character ' x' (Ex. Examples:.
devices Am27C512-150, Am27C512-200 and Am27C512-250 should be searched as Am27C512. device S29GL064N11TF1010 should be searched as S29GL064N xxT xx01. Elnec fully understand needs of customers programming high volumes for which cost of adapters is one of most important component of costs. Therefore Elnec policy is to offer:.
fixed discount when buying 4+ adapters of particular type,. individual discount for quantities 8+ according to type of adapter and demanded quantity. To get Quotation 8+ please click here: Short description:.
110441 from 356 by 3.38 version of SW (1. 2018). extremely fast programming, one of the fastest programmers in this category. Sustainable programming speed greater than 5 MBytes per second. Features GENERAL. BeeProg2 is next member of USB/LPT-compatible, MS Windows (from Windows XP to Windows 10 32-bit and 64-bit) based ELNEC universal programmers, built to meet the strong demand of the small manufacturing and developers community for the fast and reliable universal programmer.
BeeProg2 programmer is the improvement of programmer, difference is much higher programming speed (up to 10x) of high-capacity memories, due to more powerful programming core (FPGA) inside. Supports all kinds of types and silicon technologies of today and tomorrow programmable devices without family-specific module. You have freedom to choose the optimal device for your design.
Using built-in in-circuit serial programming ( ISP) connector, the programmer is able to program ISP capable chips in circuit. BeeProg2 isn't only a programmer, but also a tester of TTL/CMOS logic ICs and memories. Furthermore, it allows generation of user-definable test pattern sequences. Provides very competitive price coupled with excellent hardware design for reliable programming. Probably best 'value for money'programmer in this class.
Extremely fast programming due to high-speed FPGA driven hardware and execution of time-critical routines inside of the programmer. As a result, when used in manually-operated production, this one-socket-programmer in most cases waits for an operator. BeeProg2 interfaces with any IBM PC compatible personal computers, running MS Windows OS, through USB (2.0 HigSpeed) port or any standard parallel (printer) port. Support of both USB/LPT port connection gives you the choice to connect the BeeProg2 programmer to any PC, from latest notebook to older desktop without USB port.
HARDWARE. FPGA based totally reconfigurable 48 powerful TTL pindrivers provide H/L/pullup/pulldown and read capability for each pin of socket.
Advanced pindrivers incorporate high-quality high-speed circuitry to deliver signals without overshoot or ground bounce for all supported devices. Improved pin drivers drivers operate down to 1.8V so you'll be ready to program the full range of today's advanced low-voltage devices. The programmer performs device insertion test based on the check of proper signal path between the programmer and programmed device before it programs each device. In dependence on programming configuration it identifies missed or poor contact between programmed device and the ZIF socket of the programming adapter (or the programmer directly), missed or poor contact between the programming adapter and the programmer and it's also able to indicate wrong position of device in the ZIF socket of the programmer / the programming adapter (moved, rotated, backward oriented). These capabilities, supported by overcurrent protection and signature-byte check help prevent chip damage due to operator error. The selftest capability allow to run diagnostic part of software to thoroughly check the health of the programmer.
Built-in protection circuits eliminate damage of programmer and/or programmed device due to environment or operator failure. All the inputs of the BeeProg2 programmer, including the ZIF socket, connection to PC and power supply input, are protected against ESD up to 15kV. When programming specification require, the (BeeProg2) programmer performs programming verification at the marginal level of supply voltage, which, obviously, improves programming yield, and guarantees long data retention. Various programming adapters are available to handle device in PLCC, JLCC, SOIC, SDIP, SOP, PSOP, SSOP, TSOP, TSOPII, TSSOP, QFP, PQFP, TQFP, VQFP, QFN (MLF), SON, BGA, EBGA, FBGA, VFBGA, UBGA, FTBGA, LAP, CSP, SCSP, LQFP, MQFP, HVQFN, QLP, QIP and other packages. SOFTWARE.
Programmer is driven by an easy-to-use control program with pull-down menu, hot keys and on-line help. Selecting of device is performed by its class, by manufacturer or simply by typing a fragment of vendor name and/or part number. Tensorflow checkpoint file. Standard device-related commands (read, blank check, program, verify, erase) are boosted by some test functions (insertion test, signature-byte check), and some special functions (autoincrement, production mode - start immediately after insertion of chip into socket). All known data formats are supported.
Automatic file format detection and conversion during loading of file. The rich-featured auto-increment function enables one to assign individual serial numbers to each programmed device - or simply increments a serial number, or the function enables one to read serial numbers or any programmed device identification signatures from a file. The software also provide a many information about programmed device. As a special, the drawings of all available packages are provided. The software provide also explanation of chip labelling (the meaning of prefixes and suffixes at the chips) for each supported chip.
The software provide a full information for ISP implementation: Description of ISP connector pins for currently selected chip, recommended target design around in-circuit programmed chip and other necessary information. The remote control feature allows to be PG4UW software flow controlled by other application – either using.BAT file commands or using DLL file. DLL file, examples (C/PAS/VBASIC/.NET) and manual are part of standard software delivery.
Jam files of JEDEC standard JESD-71 are interpreted by Jam Player. Jam files are generated by design software which is provided by manufacturer of respective programmable device. Chips are programmed in-ZIF or through ISP connector (IEEE 1149.1 Joint Test Action Group (JTAG) interface). VME files are interpreted by VME Player. VME file is a compressed binary variation of SVF file and contains high-level IEEE 1149.1 bus operations. SVF files are interpreted by SVF Player. SVF file (Serial Vector Format) contains high-level IEEE 1149.1 bus operations.
SVF files are generated by design software which is provided by manufacturer of respective programmable device. Chips are programmed in-ZIF or through ISP connector (IEEE 1149.1 Joint Test Action Group (JTAG) interface).
VME files are generated by design software which is provided by manufacturer of respective programmable device. Chips are programmed in-ZIF or through ISP connector (IEEE 1149.1 Joint Test Action Group (JTAG) interface). Multiple devices are possible to program and test via JTAG chain: JTAG chain (ISP-Jam), JTAG chain (ISP-VME), JTAG chain (ISP-SVF) or JTAG chain (ISP-STP). Care for the customers.
New Device Request. It is important to remember, that a support of most of the new devices requires only a software update, because the BeeProg2 is truly a universal programmer. With our prompt service you can have new device added to the list of supported devices within hours! See (Algorithm On Request) service and software for details. This service is almost in all cases free. Please note that we can ask customer to share the cost if development cost is too high. Free life-time.
Most current version of Elnec programmers software with support of newly added devices is available for free. Free. Elnec provide customers technical support (WebForm/e-mail based) available usually within few hours, at the latest next working day. service means, that ELNEC ships the latest version of programmer software and updated user documentation (Keep-Current package) to customer. The Keep-Current service is your hassle-free guarantee that you achieving the highest quality programming on ELNEC programmers, at minimal cost. Prompt delivery.
Combination of extensive stock, flexible manufacturing and shipping of Elnec products by world class carriers (like DHL) warrants customers very fast and secure delivery of ordered Elnec products. Products ordered before 10 a.m. (CET) will be dispatched the same working day (if products are in stock and the payment is done by Online payment (CardPay, PayPal). Warranty. Advanced design of the BeeProg2 universal programmer, including protective circuits, original brand components, careful manufacturing and burning-in allow us to provide a three-year warranty on parts and workmanship of the programmer (limited 25 000-cycle warranty on ZIF sockets).
Elnec provides free shipping of programmer repaired under warranty back to customer world wide. Warranty is valid from the date of purchase. Preferential handling of repair requests ensures registration of the product that should be done within 60 days from the date of purchase. Software. Algorithms: only manufacturer approved or certified algorithms are used. Custom algorithms are available at additional cost.
Flash Memory Programmer
Algorithm updates: software updates are available regulary, approx. Every 4 weeks, free of charge. OnDemand version of software is available for highly needed chips support and/or bugs fixes. Available nearly daily. Main features: revision history, session logging, on-line help, device and algorithm information. Device support Programmer, in ZIF socket. NAND FLASH: Samsung K9xxx, KFxxx, SK Hynix (ex Hynix) HY27xxx, H27xxx, Toshiba TC58xxx, TH58xxx, Micron MT29Fxxx, (ex Numonyx ex STM) NANDxxx, Spansion S30Mxxx, S34xxx, 3D-Plus 3DFNxxx, ATO Solution AFNDxxx, Fidelix FMNDxxx, Eon Silicon Sol.
Notes:. It is important to say, we always use random numbers data pattern for programming speed testing. Some our competitors use 'sparse' data pattern, where only few non-blank data are programmed or there are used data with only few 0 bits (FE, EF, etc.). This cheating approach can 'decrease' programming time considerable. If you plan to compare, ask always which pattern they use.
The programming speed depends on PC speed only slightly, of course at condition the CPU usage is below 100%. If the programmer attached to PC through LPT port, the programming of high-capacity memories will take considerable longer time. Device Size bits Operation Time K8P6415UQB (parallel NOR Flash) 400100hx16 bit (64 Mega) programming and verify 13 sec.
MT29F1G08ABAEAWP (parallel NAND Flash).2 8400000Hx8 (1 Giga) programming and verify 51 sec. THGBM3G4D1FBAIG (eMMC NAND Flash).2 2048 MB x8 (16 Giga) programming.1 363 sec. QB25F640S33 (serial Flash) 800200hx8 (64 Mega) programming and verify 30.7 sec. AT89C51RD2 (microcontroller) 10000Hx8 programming and verify 14.4 sec.
PIC32MX360F512L (microcontroller) 80000hx8 programming and verify 8.9 sec. Conditions: Intel Core2Duo 6300 1.86GHz, 1GB RAM, USB 2.0 HS, Win XP, software PG4UW v3.03. Notes:.1 - implementation is the same as in card readers. Verification of programming is performed by internal controller, where internal controller confirm the proper programming using status register.2 - the programming time is for active.
General PC system requirements. Programmer hardware related requirements:. either one USB port, 2.0 compatible.
or one (parallel) printer port with nothing attached, the IEEE 1284 compatible printer port (ECP/EPP) on PCI bus recommended Operation. operating voltage 100-240V AC rated, 90-264 VAC max., 47-63 HZ. power consumption max.