This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

L6405E

I have the L6405E error and I don't know how to solve (lpc1788) please help me

  • I can see you are stuck - you seem to have missed that the Linker error message does mention much more information than the error code.

    Don't you get the name of a scatter file, and a region name and some object file name or symbol name?

    And how did you create your scatter file - and what does it look like? Because no reader on this forum can guess these things from you just posting an error code.

  • dear sir. i have following error messages in compiling process. please tell me about its solutions:

    D:\Users\Administrator\Desktop\gui5\Keil\Applications\VB92\VB92_Signal.c(1073) : GUI_SetAlpha(220);
    D:\Users\Administrator\Desktop\gui5\Keil\Applications\VB92\VB92_Signal.c(1086) : GUI_SetAlpha(0);
    D:\Users\Administrator\Desktop\gui5\Keil\Applications\VB92\VB92_Graphics.c(246) : GUI_SetAlpha(80);
    D:\Users\Administrator\Desktop\gui5\Keil\Applications\VB92\VB92_Graphics.c(274) : GUI_SetAlpha(0);
    D:\Users\Administrator\Desktop\gui5\Keil\Applications\VB92\VB92_Graphics.c(293) : GUI_SetAlpha(30);
    D:\Users\Administrator\Desktop\gui5\Keil\Applications\VB92\VB92_Graphics.c(296) : GUI_SetAlpha(0);

    Thanks

  • Interesting - now you posted new information. Information that still doesn't represent full error messages from compiler or linker. Is it a policy of yours, no never post complete information? Or is it that you, yourself, never want to read the complete information just to "save time"?

    If the compiler sees that you try to call functions that it doesn't know about, then it's reasonable for the compiler to complain. And it's then reasonable for you to spend time trying to figure out why the compiler doesn't know about these symbols. Have you forgot a header file? Have you included the wrong header file? Have you forgotten to set a #define?

    Maybe you should break the bank, and for once write a post where you tell us exactly what own work you have done to try to understand these error messages - and what own work you have then done to try to solve them.

    Google can give good explanations for most build errors - if you just specify the correct part of the error messages when searching.