为什么编译后会生成错误的CY8C3866AXI-040？

也许这会对这个问题有所启发。
HTTP://www. pSOCGooReR.COM/FUMRS/VIEW？PHP？F＝48和t＝11266
问候，Dana。



     以下为原文
  Maybe this might shed some light on the problem -
     
        
              http://www.psocdeveloper.com/forums/viewtopic.php?f=48&t=11266
     
    Regards, Dana.

我认为还有一件事：我在主开始看到代码   C EF BB BF。
MNI
8 K



     以下为原文
  I think there's something else:
I see code  EF  BB  BF at the beginning of main.c

•   main_as_bin.png 8.0 K
  
  

可能是在记事本（或其他编辑器）中打开了文件。字节序列0xEFBEF是UTF8中所谓的“字节顺序标记”，UTF8文件需要它来标记字节顺序（EndiaNess）。实际上是它的0xFFEF，但是在UTF8中它被重新编码。由于从PSoC3到5的切换改变了编译器（Keil对GCC），它也改变了字符编码的处理。对于UTF8，BOM是不需要的。
您可以尝试打开CyPress创建者中的文件，删除第一行，然后手动重新键入。这应该删除BOM。以后，尽量避免文件中的任何ULLUTT，这可能会导致编辑器切换到Unicode编码。避免记事本：



     以下为原文
  Probably you opened the file in Notepad (or some other editor). The byte sequence 0xefbbef is the so-called "byte order mark" in UTF8, which is needed for UTF16 file to mark the byte order (endianness). Actually its 0xfeff, but in UTF8 it gets re-encoded. Since switching from PSoC3 to 5 changes the compiler (Keil vs. gcc), it also changes the handling of character encoding. For UTF8 the BOM is not needed.
    You can try to open the file in Cypress Creator, delete the first line and then re-type it manually. That should remove the BOM. In the future, try to avoid any umlauts in your file, which might cause the editor to switcxh to a Unicode-encoding. And avoid notepad :)

谢谢您。也许你是对的。我尽量不要使用其他编辑器。但是我尝试用三个编辑器编辑Meave.C（PSoC5），PoSOC3不会出现WordPad、记事本、记事本+ +错误。并且删除第一行-无济于事。错误仍然存在。如果没有人，除了我没有问题，让我们希望这是我的电脑问题。



     以下为原文
  Thank you. Maybe you're right. I'll try not to use other editors.
But I tried to edit main.c (PSoC5) by three editors
WordPad, Notepad, NotePad + +    - error does not occur for PSoC3.
And removing the first row - does not help. The error remains.
If no one but me not had a problem then let's hope that this is the problem of my PC.
   
 

Windows记事本被称为添加BOM，只要它认为它保存在UTF8中（这可能是所有非英语版本的Windows的默认值）。如果更改第一行不起作用，则可能需要使用十六进制编辑器来修复该文件（或者将文件的第一部分（通常只是其注释）复制到新文件并使用该文件）。
KEIL编译器似乎很好地接受了BOM的输入，而GCC不喜欢。鉴于它没有为UTF8重新定义，我不能为此而犯错…



     以下为原文
  Windows notepad is known for adding the BOM whenever it thinks it shouds save in UTF8 (which might be the default for all non-english versions of Windows). If changing the first line doesn't help, you probably need to use a hex editor to fix that file (or copy anything except the first part of the file, usually its just comments, to a new file and use that one).
    The Keil compiler seems to fine in accepting input with a BOM, whereas gcc doesn't like it. And given that its not receommended for UTF8, I cannot fault it for that...