I have reproduced the bug.
Typing "frama-c helloworld.i", I get the error message:
.\\helloworld.c:209:[kernel] failure: Using a wide string literal to initialize something other than a wchar_t array
The line is:
AECHAR text[10] = L"0.0";
where AECHAR is a typedef:
typedef uint16 AECHAR;
One possible continuation is to comment the line AECHAR text[10] = L"0.0"; in the .i file (the variable text is not used anyway). If you do that, you can continue the analysis for instance with the command:
frama-c-gui helloworld.i -lib-entry -main HelloWorld_HandleEvent -val
This does not produce very interesting results because too many functions are missing. If you want static analysis that works in these conditions in order to find obvious bugs, we recommend Clang (http://clang.llvm.org/ ).

I know, that problem is in this string(AECHAR text[10] = L"0.0";), I've added it to show error.
Problem is that my real project has lots of that kind of strings(I can't comment them all).
Does this mean that this error is "Work as designed" feature?
Anyway, thanks for advise, I'll try Clang.

We recognize that failing to parse the definition of text[10] is a bug or at least that parsing it is a desirable feature. We will look at the difficulty of supporting it and if it does not seem too complicated, we will change the parser. This is the meaning of the "Confirmed" status of this bug report.
Because we anticipate that the next step in your usage of Frama-C will disappoint you anyway, we will not do it urgently, though. If you want to produce useful results with Frama-C, you must either:
- using the value analysis, include in the analysis project the source code of the functions that are part of the SDK. This will make the project big, but the value analysis does not work well when the source code of some functions is missing.
- using Jessie for modular verification of only some functions, be ready to write ACSL specifications.