PSoC3->PSoC5 funny problem

Maybe this might shed some light on the problem -

          http://www.psocdeveloper.com/forums/viewtopic.php?f=48&t=11266

Regards, Dana.

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 :)

Some more information in Wikipedia: https://en.wikipedia.org/wiki/Byte_order_mark

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...