Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [threadx-dev] ThreadX non-contiguous RAM support
  • From: Bill Lamie <blamie@xxxxxxxxxxx>
  • Date: Thu, 23 May 2024 18:48:59 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=px5rtos.com; dmarc=pass action=none header.from=px5rtos.com; dkim=pass header.d=px5rtos.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=dwk37vP66vbYkmd06We1nElXpT70YTtIBZb/Loi83eo=; b=HEsb9Zz692sXTBEJL+qIxE6yJe1WuLsvfl4/ZsmSjr6RQGcyUBzXgsuKdXb6nMQwUpnvVxuFsaiTGlJzA7K6wX1CTXc2LfAQ3O8hr9jfLJW9u6lNCmQK9IXft3hu7i6ChDJPrO48vF7dD28UJts6yCAFa/nXRa6uaItPuLLVCmjxLszdOqQYHtSh/VIowcdukFR0v8203dMh7qKEPDhDXqXTidq9VxQnnXLCmLAOeWbNp4f7Kltw4xWv0kfnMKxT7zTfjz/CzAplkUvr0wbh/R0ElCY1V8aUMLcxGb/wp7DWESaqFtiGeCTdqVBcbDp2gewoFpkyCH76OGZwU7FDMQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kn6Om/6CNIHn9x6/B7ceXgxv+w6nJMPiXhrQyFsH8ZL7M39aSYwaqW+0gcYJpQIi1BcJDRtOWvGXkzc3kBx5XsaL9BL7Al0qhaQxTgiLNg6yR3xQZhnIXLYSUBa461F+RyBRfURUt7dJ86Si41T5K17Fd93MjCIUgYimDI7g4EmKPuN21fNdI9FiqGc/PJRw4Peg9mEKxl7E6DaywukUUdhyCcB07XeiSZVuaPi0AmeVPohx6t1dkUxmgY/C90DZt5Cv4vR7hN0bCVMCGiRnGR/m+4L9bmzPYN6Mn/HonFf9C3oiO+A7e4iV/GH07KCcRXKciMYgUxjss27wJ6dC8Q==
  • Delivered-to: threadx-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/threadx-dev/>
  • List-help: <mailto:threadx-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/threadx-dev>, <mailto:threadx-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/threadx-dev>, <mailto:threadx-dev-request@eclipse.org?subject=unsubscribe>
  • Msip_labels: MSIP_Label_724d29b2-602f-4b77-ba15-b7b42511c7c5_Enabled=True; MSIP_Label_724d29b2-602f-4b77-ba15-b7b42511c7c5_SiteId=ee2cd48b-958f-4be4-9852-b8f104c001b9; MSIP_Label_724d29b2-602f-4b77-ba15-b7b42511c7c5_SetDate=2024-05-23T08:38:21.369Z; MSIP_Label_724d29b2-602f-4b77-ba15-b7b42511c7c5_Name=Internal; MSIP_Label_724d29b2-602f-4b77-ba15-b7b42511c7c5_ContentBits=0; MSIP_Label_724d29b2-602f-4b77-ba15-b7b42511c7c5_Method=Standard;
  • Thread-index: AQHarOwi189Mh7u6FkK7Envc0vnIx7GlIjEg
  • Thread-topic: ThreadX non-contiguous RAM support

Hi Konstantin,

 

The txm_module_manager_absolute_load API might help. It allows you to link/locate the module code to absolute addresses in your memory area—both ROM and RAM. However, it still allocates stack space from the module manager memory pool for a couple of threads created on behalf of the module. In any case, this does provide some sense of non-contiguous module RAM usage.

 

I believe you will have to update to the latest Module code, since this feature was not in the ThreadX Modules 5.7.5 release.

 

Please let me know if you have additional questions. My e-mail is blamie@xxxxxxxxxxx

 

Best regards,

 

Bill

 

 

From: threadx-dev <threadx-dev-bounces@xxxxxxxxxxx> On Behalf Of Bilozor, Konstantin via threadx-dev
Sent: Thursday, May 23, 2024 1:38 AM
To: threadx-dev@xxxxxxxxxxx
Cc: Bilozor, Konstantin <Konstantin.Bilozor@xxxxxxxxxxxxx>
Subject: [threadx-dev] ThreadX non-contiguous RAM support

 

Hello,

 

In our project we have an MCU which has non-contiguous RAM. We are using ThreadX 5.7.5 version and have modular approach. The problem what we are facing is shortage of RAM for one of the modules. I have 2 following questions:

  • Currently we use txm_module_manager_in_place_load functions to load the modules. As soon, as the object in the code is placed into RAM, all instances which are taking this object need to be in RAM as well. Is it possible with latest version of ThreadX to mix RAM and ROM objects? Will txm_module_manager_absolute_load solve the problem?

 

  • Is it possible to use non-contiguous RAM for the modules in latest ThreadX? In the version 5.7.5 it is not supported.

Best,

Konstantin

 

P PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS EMAIL.

This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.


Back to the top