• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 466 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CMEM overview for Windows CE

Kuzmin Alexey
Intellectual 430 points

Hello,

Please, make more available and actial information about CMEM state. Brief from here http://processors.wiki.ti.com/index.php/CMEM_Overview looks like uncompleted version without updates for the long time.

--

BW, AK.

  • 0
    TI__Genius 17205 points

    Hm.  What are you looking for?  Lack of activity doesn't imply incorrectness.

    The last WinCE Utils release was Nov 2010.  That CMEM Overview article has been updated several times since then.

    Chris

  • 0 in reply to Chris Ring
    Intellectual 430 points

    Hello, Chris.

    Thank you for reply.

    The incompletion is one type of incorrectness.

    We modifying memory mapping for Windows CE 6.0 BSP provided by Adeneo. It's not easy task and we should be well prepared to avoid side effects. When I found CMEM memory region DSP used I looked to more info about it, but \packages\ti\sdo\winceutils\cmem\readme.txt us not complete source and http://processors.wiki.ti.com/index.php/CMEM_Overview is not too (but with more details).

    Can you provide links with more information about Windows CE reserved areas and its mapping? I didnt found it for this moment.

    ---

    BW,

    AK.

     

  • 0 in reply to Kuzmin Alexey
    TI__Genius 17205 points

    K, thanks for the details.  I personally don't have your answer - often the memory map must take several things into account:

    • DSP-side code/data memory usage (e.g. what memory is the DSP-side code/data statically linked into?)
    • DSP-side cache constraints (e.g. cache alignment and MAR configuration if your DSP app needs _some_ memory DSP-side cached and _some_ not, it needs to span MAR address ranges)
    • WinCE OS memory needs
    • Data buffers which must be shared between ARM and DSP (e.g. CMEM)

    CMEM can be used in many environments, and that article describes how to reserve memory specifically for CMEM.  But memory partitioning for the system is bigger than CMEM.  Someone more familiar with your system-wide environment (maybe Adeneo if they're your BSP provider?) can hopefully help understand your system needs and how best to partition and set up the memory.

    Chris

  • 0 in reply to Chris Ring
    Intellectual 430 points

    Hello, Chris,

    Thank you for answer. Your advices are helpful and I will use it. Adn i will also ask Adeneo.

  • 0 in reply to Kuzmin Alexey
    Mastermind 9310 points

    Hi Alexey

    You can check the following link that explains a little bit about how the memory is mapped and the different memory sections in WinCE 6: http://blogs.msdn.com/b/ce_base/archive/2006/09/01/understanding-memory-sections-in-config.bib_2c00_-boot.bib_2c00_-and-oemaddresstable-in-windows-ce-5.0-and-6.0.aspx

  • 0 in reply to Adeneo Embedded support team
    Intellectual 430 points

    I already read this good blogpost about 3-4 years ago, but it more applicable for my current tasks, not for the then tasks.

    Great thank for your remind, will read.