KEIL生成的HEX文件的记录不能被PSoC编程识别

让我看看我能想出什么办法。在这一点上，我确认PSoC程序员失败了，正如Keil HEX文件所描述的那样。我需要把这个例子移植到Keil中，看看我是否可以复制你的十六进制文件。
吉姆



     以下为原文
  Let me see what I can figure out. At this point I confirm that PSoC Programmer fails as described with the Keil hex file. I need to port the example into Keil and see if I can replicate your HEX file.
 
Jim

只是一个快速跟进。我们正在探索。我会随时通知你的。



     以下为原文
  Just a quick follow up. We are exploring. I'll keep you posted.

你好，JCUI，
我检查了KEIL生成的HEX文件。与Creator生成的HEX文件的主要区别在于，有一行记录类型“0x05”，用于指定对象文件的执行起始地址。
例如，使用下面的行，执行起始地址是0x100000 0C1。
：040000 05100000 0C126
我认为PSoC程序员应该忽略“0x05”的记录类型。
郝



     以下为原文
  Hi JCUI,
 
I checked the hex file generated by Keil. The main difference with hex file generated by Creator is there is one line with record type '0x05' which means for specifying execution start address for the object file.
 
For example with the following line, the execution start address is 0x100000C1.
:04000005100000C126
 
I think PSoC programmer should ignore record type of '0x05'.
 
Hao

谢谢郝！我很欣赏更新。代码示例作者将在星期一看一看——他目前正在商务旅行。



     以下为原文
  Thanks Hao! I appreciate the update. The code example author is going to take a look on Monday - he's on business travel at the moment.

事实证明，这是预期的行为。我对PSoC程序员的内部设计有了一些了解。它不是设计为使用纯十六进制文件。CyPress工具（PSoC Creator）生成标准的HEX文件，加上一些附加信息来标识预期的目标，并提供快速校验和。实际上，它使标准的HEX文件更加健壮——它不能终止在错误的芯片上并导致失败。
因此，由第三方IDE创建的十六进制文件，使用该方的程序员。
我将研究支持标准HEX文件的想法，但是它有很多潜在的影响。PSoC程序员多年来一直这样工作，它是一个脚本化工具。我们无法知道谁已经建立了依赖于解析PSoC程序员HEX文件的脚本或命令行工具（这是有据可查的）。
所以现在，它就是这样运作的。我很欣赏这份报告和学习机会，并向你道歉，因为它并不像你预期的那样有效。
我要标记这个答案。如果你还有其他问题，请告诉我。



     以下为原文
  As it turns out, this is expected behavior. I've learned a little about the internal design of PSoC Programmer. It is not designed to use a pure hex file. Cypress tools (PSoC Creator) generate a standard hex file plus some additional information to identify the intended target, and to provide a quick checksum. In effect, it makes the standard hex file more robust - it can't end up on the wrong chip and cause failure.
 
So, a hex file created by a 3rd party IDE, use that party's programmer.
 
I will look into the idea of ALSO supporting standard hex files, but that has lots of potential repercussions. PSoC Programmer has worked like this for years, and it is a scriptable tool. We have no way of knowing who has built what scripts or command line tools that rely on parsing the PSoC Programmer hex file (which is well documented).
 
So for now, that's how it works. I appreciate the report, and the learning opportunity, and apologize that it did not work the way you expected.
 
I'm going to mark this answered. Let me know if you have any other questions.