Email Detail

HTTP 200 OK
Allow: GET, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "url": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/7GE2HM3LFN2UC2LPE2NSUO4FQYUGOHY4/?format=api",
    "mailinglist": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/?format=api",
    "message_id": "BY3PR13MB4788BEE64F776389CBE5C221EF732@BY3PR13MB4788.namprd13.prod.outlook.com",
    "message_id_hash": "7GE2HM3LFN2UC2LPE2NSUO4FQYUGOHY4",
    "thread": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/thread/7GE2HM3LFN2UC2LPE2NSUO4FQYUGOHY4/?format=api",
    "sender": {
        "address": "bstrick (a) N5BRG.COM",
        "mailman_id": "953542c988dd4c549175bb02a8a6a1ed",
        "emails": "https://mailman.amsat.org/hyperkitty/api/sender/953542c988dd4c549175bb02a8a6a1ed/emails/?format=api"
    },
    "sender_name": "Bob Stricklin",
    "subject": "[pacsat-dev] Re: Memory Problem on PacSatSW",
    "date": "2024-01-16T02:36:45Z",
    "parent": null,
    "children": [],
    "votes": {
        "likes": 0,
        "dislikes": 0,
        "status": "neutral"
    },
    "content": "OK will have a look at this.\r\n\r\n\r\nFound this note also which probably applies to us also:\r\nOn MSP430 (or other) devices with limited RAM, the linker may fail to allocate the .bss or other sections allocated to RAM. The .bss section is for uninitialized global variables, and goes into RAM, along with stack (.stack) and heap (.sysmem) sections . If the code has a large number of global variables, you may run out of RAM space. If this is the case, you may consider making some of the variables const so they go into the .const section instead (which gets placed in FLASH instead of RAM).\r\n\r\n\r\n\r\nFrom: Burns Fisher (AMSAT) via pacsat-dev <[email protected]>\r\nSent: Monday, January 15, 2024 6:38 PM\r\nTo: Jim McCullers <[email protected]>\r\nCc: Pacsat Dev <[email protected]>\r\nSubject: [pacsat-dev] Re: Memory Problem on PacSatSW\r\n\r\nWhen you mentioned the heap, you reminded me:\r\n\r\nFreeRTOS has a heap, which is essentially just a big array.  The only thing it gets used for is allocating task stacks and the structures that represent semaphores, queues, etc.  And they way that I have used the OS, they get allocated but never released.  But the thing I meant to say is that allocating smaller stacks does not use less memory from the linker's point of view because the array that the stacks are allocated from is not changed.   There is a routine you can use to ask how much heap is free.  After it is all booted up, unless the new code uses it differently than I did, any \"free heap\" is wasted.  I think the size of the heap is an OS parameter in one of the free rtos header files.\r\n\r\n73,\r\n\r\nBurns Fisher, WB1FJ\r\nAMSAT(R) Engineering -- Flight Software\r\n\r\n\r\nOn Mon, Jan 15, 2024 at 7:31 PM Jim McCullers via pacsat-dev <[email protected]<mailto:[email protected]>> wrote:\r\nMy version of CSS is either different or how did you turn on the green lines with summary data?\r\nI get a popup status message with similar info but not as stable or detailed as yours.\r\n\r\nOn my system, I’m showing 80% utilization.\r\nThe majority is in ucHeap (about 131k).\r\nI’ll bet on a function somewhere allocating a chunk of memory or repeatedly doing so and never using or releasing it.\r\nShould be ‘fun’ to find.\r\n\r\nJim McCullers\r\nWA4CWI\r\n\r\n\r\n\r\nLooks like we have an issue with memory usage in RAM\r\n\r\nIf you load up CCS with the current project PacSatSW and build it then you can select VIEW -> Memory Allocation  and look at the tab. You will see the package needs 154K or RAM and the Launpad has 191K.  In the case of the TMS570LS0914 we have 128K max.\r\nYou can expand RAM and the subfolders and see where the memory is being used.\r\n\r\nI worked for the last few days getting a HalCoGen setup for the LS0914 and then murging this HCG file with the code of the Launcpad project. After working through some issues it built but when it ran the linker it errored out with not enough memory. So faked it out and told the linker I had more memory. Then it would build and generate a .out file and the Memory Allocation info. It matches the launch pad build.\r\n\r\nProbably need to look for ways to reduce RAM needed. Reduce buffer sizes, move buffers to external memory, or take out code.\r\n\r\nI will be looking for things here to try and complete a basic build of the code for the LS0914. Please look for ideas and post any that you come up with. We probably should target RAM usage at about 80% of the max or about 100KB.  We could change processors later but that would need some study.\r\n\r\nBob\r\n\r\n[cid:[email protected]]\r\n\r\n-----------------------------------------------------------\r\n\r\npacsat-dev mailing list -- [email protected]<mailto:[email protected]>\r\nView archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/[email protected]\r\nTo unsubscribe send an email to [email protected]<mailto:[email protected]>\r\nManage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org\r\n\n\n",
    "attachments": [
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/7GE2HM3LFN2UC2LPE2NSUO4FQYUGOHY4/?format=api",
            "counter": 3,
            "name": "attachment.html",
            "content_type": "text/html",
            "encoding": "utf-8",
            "size": 11937,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/7GE2HM3LFN2UC2LPE2NSUO4FQYUGOHY4/attachment/3/attachment.html"
        },
        {
            "email": "https://mailman.amsat.org/hyperkitty/api/list/[email protected]/email/7GE2HM3LFN2UC2LPE2NSUO4FQYUGOHY4/?format=api",
            "counter": 4,
            "name": "image001.png",
            "content_type": "image/png",
            "encoding": null,
            "size": 367151,
            "download": "https://mailman.amsat.org/hyperkitty/list/[email protected]/message/7GE2HM3LFN2UC2LPE2NSUO4FQYUGOHY4/attachment/4/image001.png"
        }
    ]
}