1MINIPRO(1) General Commands Manual MINIPRO(1)
2
6 minipro - programs various chips using the Minipro TL866XX series of
7 programmers.
8
10 minipro -l | -L search | -d device | -D | [-p device] [-c
11 code|data|config] [-o option ... ] [-r|-w filename]
12 [-e][-u][-P][-i|-I][-v][-s|-S][-x][-y][-V][-t] [-T] [-f ihex|srec] [-F
13 filename] [-h]
14 miniprohex [-p device] [-c code|data|config] [-r|-w filename]
16 [-e][-u][-P][-i|-I]
17
20 minipro is an Open Source tool intended to become a complete cross-
21 platform replacement for the proprietary utility from Autoelectric.
22 Currently it supports more than 13000 of target devices - including
23 AVRs, PICs as well as a huge number of other microcontrollers and vari‐
24 ous memory chips.
25
29 -l Get a list of supported devices.
30 -L <search>
33 List devices beginning with this string.
34 -d <device>
37 Show device information.
38 -D Just read the chip ID and do nothing else (like reading the
41 whole chip contents). This is for use in scripts where you have
42 for example several similar chips with different IDs and want to
43 check if the currently inserted chip is one in your list of al‐
44 lowed ones. Also useful to detect if a chip is inserted at all
45 when using the -y option.
46 -p <device>
49 Specify the device name. If the desired device name contains a
50 space, parenthesis, or at sign; the device name MUST be sur‐
51 rounded by quotes.
52 -c <type>
55 Optionally specify memory type. Possible values include "code",
56 "data", and "config". The "config" memory type is used to access
57 fuses, see FUSES below.
58 -o <option>
61 Specify various programming options. For multiple options use -o
63 multiple times. Valid options are:
64 • vpp=<value>
67 Set the programming voltage (10, 12.5, 13.5, 14, 16, 18,
69 21).
70 • vdd=<value>
73 Set the VDD write voltage (3.3, 4, 4.5, 5, 5.5, 6.25).
75 • vcc=<value>
78 Set the VCC verify voltage (3.3, 4, 4.5, 5, 5.5, 6.25).
80 • pulse=<value>
83 Set the programming pulse delay (0-65535 usec).
85 -r <filename>
88 Read from the device and write the contents to this file.
89 -w <filename>
92 Write to the device using this file.
93 -e Do NOT erase device.
96 -u Do NOT disable write-protect.
99 -P Do NOT enable write-protect.
102 -v Do NOT verify after write.
105 -i Use ICSP.
108 -I Use ICSP (without enabling Vcc).
111 -s Do NOT error on file size mismatch (only a warning).
114 -S No warning message for file size mismatch (can't combine with
117 -s).
118 -x Do NOT attempt to read ID (only valid in read mode). Avoids
121 sending high Chip ID read voltages to unknown pins.
122 -y Do NOT error on ID mismatch.
125 -T Run a logic IC test.
128 Errorneous states are reported with a "-" (minus) sign next to
130 the expected pin state.
131 -V Show version information.
134 -t Start hardware check.
137 -f <ihex | srec>
140 Specify the file format: either Intel ihex or Motorola srecord.
141 When writing chips, this is not necessary because the file for‐
143 mat is automatically detected. There is no need to specify the
144 exact Intex hex format (ihex8, ihex16, or ihex32) as the format
145 is automatically detected. If this option is not used, then the
146 file will be saved as a raw binary file.
147 When reading chips and the ihex format is chosen, if the data
149 size is up to 64Kb the file will be saved in ihex8 format. Just
150 plain hex records are used -- no segment/linear address records
151 are inserted. If the data size exceeds 64Kb then the ihex32
152 format is used. The ihex16 format is not used when reading
153 chips. The same strategy is used for the Motorola srecord for‐
154 mat.
155 -F <filename>
158 Update firmware (should be update.dat).
159 -h Show help and quit.
162
165 If -c is omitted and -r is specified then the code, data (if applica‐
166 ble) and config (if applicable) will be written to filename.$ext, file‐
167 name.eeprom.bin and filename.fuses.conf correspondingly. If -c is omit‐
168 ted and -w is specified, then -c code is assumed.
169 The -i and -I options enable use of ICSP port for TL866A and TL866II+
171 models. The former enables the voltage supply on the Vcc pin of the
172 ICSP port while the latter leaves it off. These options are of no use
173 for the TL866CS.
174 The Minipro TL866xx series of chip programmers is distributed by Auto‐
176 electric. Their website is http://www.autoelectric.cn.
177
180 Minipro supports reading and writing to standard input and output. To
181 do this, use a dash (-) as a filename for the -w or -r options.
182 For example:
184 head -c 256k < /dev/urandom | srec_cat - -bin -o - -intel -Ad‐
186 dress_Length=4 -obs=16 | minipro -p w49f002u -w-
187 This is how the hex/srec parsers were tested for reading from stdin.
189 256kb of random binary data is generated then converted from binary to
190 intel hex by the srec_cat utility. Finally the converted data is passed
191 to our minipro which will read this data, convert it to binary by de‐
192 coding the intel hex format from stdin and write it to the specified
193 chip. Note the -r- which tells to read from stdin instead from a regu‐
194 lar file. This is just a test command to test the ihex/srec parsers.
195 Don't use this in real life (convert from binary to ihex then from ihex
196 to binary).
197 You can also read a chip and write the data to the stdout like this:
199 minipro -p w49f002u -r- -f ihex.
201 You can then pass the output to another command line tool with | for
203 other processing, etc.
204
207 Fuses can be read and written with the -c config option. Fuse data is
208 exchanged in a text format. When writing fuses all fuses on your device
209 must be assigned a value. To see what fuses are supported by your de‐
210 vice use -r with -c config to get your current fuse values. This also
211 shows you what the text format looks like.
212
215 minipro -p 7404 -T
216 Check whether a 74(LS/HC/...)04 hex NOT gate chip.
217
220 minipro was written by Valentin Dudouyt and is copyright 2014. Many
221 others have contributed code and bug reports. Development is currently
222 coordinated by David Griffith.
223
226 The canonical repository for minipro is at Gitlab:
227 https://gitlab.com/DavidGriffith/minipro/
228 It is distributed under the GNU General Public License version 3 or (at
229 your option) any later version.
230 https://www.gnu.org/licenses/gpl-3.0.en.html
231 This software is offered as-is with no warranty or liability. If you
232 find a bug or would like minipro to do something it doesn't currently
233 do, please visit the above Gitlab website and report your concerns.
234 14 August 2018 (v0.3) MINIPRO(1)