none
WEC7: support multi-language, but limitation of physical RAM. RRS feed

  • Question

  • Hello,

    I built NK.bin with English support. The size of NK.bin is about 56MB. It worked good on a 128MB memory hardware. Memory setting for my WEC7 BSP:

    NK--60MB

    RAM--40MB

    Display--26MB

    Now after enable other locales (German and Japanese), the size of NK.bin increases to 70MB. I changed memory setting:

    NK--75MB

    RAM--25MB

    Display--26MB.

    OS boots up and application launches, but the application will crash for some operations. I wonder why application crashes, because application should still run, it allocates memory from virtual memory manager on a lower memory hardware. 

    Do I need to enable any setting for virtual memory support on WEC7 BSP for limited memory hardware(128MB)? 

    Thanks!


    • Edited by kyan91 Monday, November 4, 2019 10:26 PM
    Monday, November 4, 2019 10:26 PM

Answers

  • If it's normal that image increases about 15MB when include Japanese locale (or other Asia language)? 

    Yes, that is normal. The asian fonts are all huge.

    if there is any strategy to reduce the EC7 size?

    WEC7 has an f'ed up dependency checker. WEC2013 is slightly better, but CE6 was the best in that respect. You can reduce the WEC7 image size a lot, but you'll have to force-exclude a lot of auto-included components. Definitely don't include any browser components if you don't have to and stay away from multimedia if you don't have to. Also don't include any ActiveStink components if you don't have to. They all pull in a lot of other components and thereby blowing up kernel size.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Tuesday, November 5, 2019 4:44 AM
    Moderator

All replies

  • You probably made some mistakes in config.bib causing CE to crash, or you forgot to update some header file containing memory location definitions. Review your config.bib settings (or post "before changes" and "after changes" versions here so we can review) and look through your BSP code to see if there are any other files that need updating for the new situation. Also provide more information about the "crash", as that word can mean a lot of things.

    To answer your question: No, not specific for low memory hardware, but you do need to make sure you change whatever is needed everywhere correctly.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Tuesday, November 5, 2019 12:52 AM
    Moderator
  • Thanks Michel,

    I will review config.bib tomorrow.

    questions regarding to image size:

    If it's normal that image increases about 15MB when include Japanese locale (or other Asia language)? 

    With English, German and Japanese support, The CE6 has only 25MB image, while when the BSP ported into EC7, the image size increases to 75MB. I tried my best to keep OS core catalog as similar as possible in 6 and 7, but I am wondering how to limit image size increasing significantly when we want to support multi-language, or in general, if there is any strategy to reduce the EC7 size?

    Tuesday, November 5, 2019 4:32 AM
  • If it's normal that image increases about 15MB when include Japanese locale (or other Asia language)? 

    Yes, that is normal. The asian fonts are all huge.

    if there is any strategy to reduce the EC7 size?

    WEC7 has an f'ed up dependency checker. WEC2013 is slightly better, but CE6 was the best in that respect. You can reduce the WEC7 image size a lot, but you'll have to force-exclude a lot of auto-included components. Definitely don't include any browser components if you don't have to and stay away from multimedia if you don't have to. Also don't include any ActiveStink components if you don't have to. They all pull in a lot of other components and thereby blowing up kernel size.


    Good luck,

    Michel Verhagen, eMVP
    Check out my blog: https://guruce.com/blog

    GuruCE
    Microsoft Embedded Partner
    NXP Proven Partner
    https://guruce.com
    Consultancy, training and development services.

    Interested in WEC on i.MX6?
    Get the only 100% stable and best performing i.MX6 BSP for WEC7 and WEC2013 here: https://guruce.com/imx6

    Tuesday, November 5, 2019 4:44 AM
    Moderator
  • Hi Michel,

    Thanks for the suggestions on image size reduce. I removed ActiveSync, browser and multimedia in catalog, and the image size reduced from 75MB to 43MB. Thus, I can use the old memory setting and the system is working fine now.

    Tuesday, November 5, 2019 9:04 PM