S,
http://www.fpga-faq.com/archives/33100.html#33108
对正在发生的事情进行了很好的讨论。
25年前,eeproms采用了舞台程序员编程,具有英特尔格式,摩托罗拉格式和各种其他格式。
英特尔和摩托罗拉制造的eeproms早已不复存在,程序员也是如此,但文件格式仍然存在,并成为事实上的标准。
.mcs,.rbt和其他是ASCII表示(ASCI 1 = 31H,ASCII 0 = 30H),带有标题,注释等。
.bin,.bit是二进制文件:所有单个位,1和0。
多年来,所有格式都在不断发展,并且仍然在使用。
新公司制作程序员,并支持所有旧格式。
因此.bin用于使用Impact编程电缆(JTAG或并行)对器件进行编程,而.rbt是执行averify Impact时的文件回读(还提供不等于.bin文件的.bin回读文件)
用来编程部分!)。
.mcd可能习惯于为最终板编程舞会,在开机时配置器件。
Austin Lesea主要工程师Xilinx San Jose
以上来自于谷歌翻译
以下为原文
s,
http://www.fpga-faq.com/archives/33100.html#33108
Is a good discussion of what is going on.
25 years ago, eeproms were programmed with prom programmers, that had Intel format, Motorola format, and various other formats. The eeproms made by Intel and Motorola are long gone, and so are the programmers, but the file formats remain, and became defacto standards.
The .mcs, .rbt, and others are ASCII representations (ASCI 1 = 31H, and ASCII 0=30H) with headers, comments, etc.
The .bin, .bit are binary files: all single bits, 1's and zeros.
All formats have evolved over the years, and are still used. New companies make programmers, and all the old formats get supported.
So a .bin is used to program the part using an Impact programming cable (JTAG or parallel), and a .rbt is the file readback when doing averify Impact (also provide a .bin readback file which is not equal to the .bin file used to program the part!).
The .mcd might get used to program a prom for the final board, to configure the part upon power on.
Austin Lesea
Principal Engineer
Xilinx San Jose
S,
http://www.fpga-faq.com/archives/33100.html#33108
对正在发生的事情进行了很好的讨论。
25年前,eeproms采用了舞台程序员编程,具有英特尔格式,摩托罗拉格式和各种其他格式。
英特尔和摩托罗拉制造的eeproms早已不复存在,程序员也是如此,但文件格式仍然存在,并成为事实上的标准。
.mcs,.rbt和其他是ASCII表示(ASCI 1 = 31H,ASCII 0 = 30H),带有标题,注释等。
.bin,.bit是二进制文件:所有单个位,1和0。
多年来,所有格式都在不断发展,并且仍然在使用。
新公司制作程序员,并支持所有旧格式。
因此.bin用于使用Impact编程电缆(JTAG或并行)对器件进行编程,而.rbt是执行averify Impact时的文件回读(还提供不等于.bin文件的.bin回读文件)
用来编程部分!)。
.mcd可能习惯于为最终板编程舞会,在开机时配置器件。
Austin Lesea主要工程师Xilinx San Jose
以上来自于谷歌翻译
以下为原文
s,
http://www.fpga-faq.com/archives/33100.html#33108
Is a good discussion of what is going on.
25 years ago, eeproms were programmed with prom programmers, that had Intel format, Motorola format, and various other formats. The eeproms made by Intel and Motorola are long gone, and so are the programmers, but the file formats remain, and became defacto standards.
The .mcs, .rbt, and others are ASCII representations (ASCI 1 = 31H, and ASCII 0=30H) with headers, comments, etc.
The .bin, .bit are binary files: all single bits, 1's and zeros.
All formats have evolved over the years, and are still used. New companies make programmers, and all the old formats get supported.
So a .bin is used to program the part using an Impact programming cable (JTAG or parallel), and a .rbt is the file readback when doing averify Impact (also provide a .bin readback file which is not equal to the .bin file used to program the part!).
The .mcd might get used to program a prom for the final board, to configure the part upon power on.
Austin Lesea
Principal Engineer
Xilinx San Jose
举报