- pacsat-dev - mailman.amsat.org

Re: Memory Problem on PacSatSW
by Bob Stricklin 16 Jan '24

16 Jan '24

Here is the map file you were looking for. Bob From: Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org> Sent: Tuesday, January 16, 2024 12:04 PM To: Bob Stricklin <bstrick(a)n5brg.com> Cc: Pacsat Dev <pacsat-dev(a)amsat.org> Subject: [pacsat-dev] Re: Memory Problem on PacSatSW The MRAMmap that you sent has nothing to do with the linker complaining. MRAM is totally external and the linker knows nothing about it. I did not know about View/Memory that Jim pointed out. To me the most useful thing, and what I mean by the Link Map or Memory Map is under the Debug folder (or Release folder depending on which way you are building) and is called programname.map, for example PacSat.map. It shows how much each module is using in both code (flash memory) and RAM. Here is a section showing how much code (.text in Unix terms) is being used. SECTION ALLOCATION MAP output attributes/ section page origin length input sections -------- ---- ---------- ---------- ---------------- .intvecs 0 00000000 00000020 00000000 00000020 sys_intvecs.obj (.intvecs) .text 0 00000020 00048338 00000020 000046f4 Ax25Task.obj (.text) 00004714 00003d54 UplinkTask.obj (.text) 00008468 00003b14 PbTask.obj (.text) 0000bf7c 000033f0 ConsoleTask.obj (.text) 0000f36c 0000314c pacsat_header.obj (.text) 000124b8 00002b7c sys_selftest.obj (.text) 00015034 00002860 os_tasks.obj (.text) 00017894 000026b8 inodedata.obj (.text) 00019f4c 000020d0 nonvolManagement.obj (.text) 0001c01c 00002008 posix.obj (.text) ========================= And here is how much RAM is getting used. .bss 0 08001500 00024752 UNINITIALIZED 08001500 00020000 os_heap.obj (.bss:ucHeap) 08021500 00000acc Ax25Task.obj (.bss:data_link_state_machine) 08021fcc 00000a00 PbTask.obj (.bss:pb_list) 080229cc 0000067c buffer.obj (.bss:gBufCtx) 08023048 00000360 CommandTask.obj (.bss:UplinkCommandBuffer) 080233a8 00000320 posix.obj (.bss:gaHandle) 080236c8 00000200 UplinkTask.obj (.bss:ftl0_pfh_byte_buffer$2) 080238c8 00000200 pacsat_dir.obj (.bss:pfh_byte_buffer) 08023ac8 000001d4 UplinkTask.obj (.bss:ftl0_pfh_buffer$1) 08023c9c 000001d4 pacsat_dir.obj (.bss:pfh_buffer) 08023e70 00000128 (.common:gaRedCoreVol) 08023f98 00000120 rtsv7R4_T_be_v3D16_eabi.lib : trgmsg.c.obj (.bss:_CIOBUF_) 080240b8 00000118 UplinkTask.obj (.bss:ax25_event) 080241d0 00000118 Ax25Task.obj (.bss:ax25_received_event) 080242e8 00000118 Ax25Task.obj (.bss:lm_event) 08024400 00000118 Ax25Task.obj (.bss:send_event_buffer) 08024518 00000118 UplinkTask.obj (.bss:send_event_buffer) 08024630 00000118 Ax25Task.obj (.bss:timer_event) ========================= Notice that you can tell which is in flash and which is in memory by the address (080xxxxx is ram, 0004xxxx is flash). This is totally an output file. What you changed was the link command file sys_lnk.cmd which is input to the linker. You essentially "lied" to the linker so it would not complain, I think. Clever way to find out how much it really wanted! But if you can send the PacSat.map (or whatever it is called), that will tell exactly who is using the memory. 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software On Tue, Jan 16, 2024 at 12:30 PM Bob Stricklin via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Jim, Make sure you are looking at: View -> Memory Allocation And not Memory Browser Memory Allocation should open in a TAB in a window within CCS. My TAB is at the bottom of CCS along with a bunch more TABs. Bob From: Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> Sent: Monday, January 15, 2024 6:31 PM To: 'Pacsat Dev' <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> Subject: [pacsat-dev] Re: Memory Problem on PacSatSW My version of CSS is either different or how did you turn on the green lines with summary data? I get a popup status message with similar info but not as stable or detailed as yours. On my system, I’m showing 80% utilization. The majority is in ucHeap (about 131k). I’ll bet on a function somewhere allocating a chunk of memory or repeatedly doing so and never using or releasing it. Should be ‘fun’ to find. Jim McCullers WA4CWI Looks like we have an issue with memory usage in RAM If 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. You can expand RAM and the subfolders and see where the memory is being used. I 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. Probably need to look for ways to reduce RAM needed. Reduce buffer sizes, move buffers to external memory, or take out code. I 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. Bob [cid:image001.png@01DA4880.1BEE3260] ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Re: Memory Problem on PacSatSW
by Burns Fisher (AMSAT) 16 Jan '24

16 Jan '24

The MRAMmap that you sent has nothing to do with the linker complaining. MRAM is totally external and the linker knows nothing about it. I did not know about View/Memory that Jim pointed out. To me the most useful thing, and what I mean by the Link Map or Memory Map is under the Debug folder (or Release folder depending on which way you are building) and is called programname.map, for example PacSat.map. It shows how much each module is using in both code (flash memory) and RAM. Here is a section showing how much code (.text in Unix terms) is being used. SECTION ALLOCATION MAP output attributes/ section page origin length input sections -------- ---- ---------- ---------- ---------------- .intvecs 0 00000000 00000020 00000000 00000020 sys_intvecs.obj (.intvecs) .text 0 00000020 00048338 00000020 000046f4 Ax25Task.obj (.text) 00004714 00003d54 UplinkTask.obj (.text) 00008468 00003b14 PbTask.obj (.text) 0000bf7c 000033f0 ConsoleTask.obj (.text) 0000f36c 0000314c pacsat_header.obj (.text) 000124b8 00002b7c sys_selftest.obj (.text) 00015034 00002860 os_tasks.obj (.text) 00017894 000026b8 inodedata.obj (.text) 00019f4c 000020d0 nonvolManagement.obj (.text) 0001c01c 00002008 posix.obj (.text) ========================= And here is how much RAM is getting used. .bss 0 08001500 00024752 UNINITIALIZED 08001500 00020000 os_heap.obj (.bss:ucHeap) 08021500 00000acc Ax25Task.obj (.bss:data_link_state_machine) 08021fcc 00000a00 PbTask.obj (.bss:pb_list) 080229cc 0000067c buffer.obj (.bss:gBufCtx) 08023048 00000360 CommandTask.obj (.bss:UplinkCommandBuffer) 080233a8 00000320 posix.obj (.bss:gaHandle) 080236c8 00000200 UplinkTask.obj (.bss:ftl0_pfh_byte_buffer$2) 080238c8 00000200 pacsat_dir.obj (.bss:pfh_byte_buffer) 08023ac8 000001d4 UplinkTask.obj (.bss:ftl0_pfh_buffer$1) 08023c9c 000001d4 pacsat_dir.obj (.bss:pfh_buffer) 08023e70 00000128 (.common:gaRedCoreVol) 08023f98 00000120 rtsv7R4_T_be_v3D16_eabi.lib : trgmsg.c.obj (.bss:_CIOBUF_) 080240b8 00000118 UplinkTask.obj (.bss:ax25_event) 080241d0 00000118 Ax25Task.obj (.bss:ax25_received_event) 080242e8 00000118 Ax25Task.obj (.bss:lm_event) 08024400 00000118 Ax25Task.obj (.bss:send_event_buffer) 08024518 00000118 UplinkTask.obj (.bss:send_event_buffer) 08024630 00000118 Ax25Task.obj (.bss:timer_event) ========================= Notice that you can tell which is in flash and which is in memory by the address (080xxxxx is ram, 0004xxxx is flash). This is totally an output file. What you changed was the link command file sys_lnk.cmd which is input to the linker. You essentially "lied" to the linker so it would not complain, I think. Clever way to find out how much it really wanted! But if you can send the PacSat.map (or whatever it is called), that will tell exactly who is using the memory. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Tue, Jan 16, 2024 at 12:30 PM Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Jim, > > > > Make sure you are looking at: > > > > View -> Memory Allocation > > > > And not Memory Browser > > > > Memory Allocation should open in a TAB in a window within CCS. My TAB is > at the bottom of CCS along with a bunch more TABs. > > > > Bob > > > > > > *From:* Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org> > *Sent:* Monday, January 15, 2024 6:31 PM > *To:* 'Pacsat Dev' <pacsat-dev(a)amsat.org> > *Subject:* [pacsat-dev] Re: Memory Problem on PacSatSW > > > > My version of CSS is either different or how did you turn on the green > lines with summary data? > > I get a popup status message with similar info but not as stable or > detailed as yours. > > > > On my system, I’m showing 80% utilization. > > The majority is in ucHeap (about 131k). > > I’ll bet on a function somewhere allocating a chunk of memory or > repeatedly doing so and never using or releasing it. > > Should be ‘fun’ to find. > > > > Jim McCullers > > WA4CWI > > > > > > > > Looks like we have an issue with memory usage in RAM > > > > If 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. > > You can expand RAM and the subfolders and see where the memory is being > used. > > > > I 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. > > > > Probably need to look for ways to reduce RAM needed. Reduce buffer sizes, > move buffers to external memory, or take out code. > > > > I 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. > > > > Bob > > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Memory Problem on PacSatSW
by Bob Stricklin 16 Jan '24

16 Jan '24

Jim, Make sure you are looking at: View -> Memory Allocation And not Memory Browser Memory Allocation should open in a TAB in a window within CCS. My TAB is at the bottom of CCS along with a bunch more TABs. Bob From: Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org> Sent: Monday, January 15, 2024 6:31 PM To: 'Pacsat Dev' <pacsat-dev(a)amsat.org> Subject: [pacsat-dev] Re: Memory Problem on PacSatSW My version of CSS is either different or how did you turn on the green lines with summary data? I get a popup status message with similar info but not as stable or detailed as yours. On my system, I'm showing 80% utilization. The majority is in ucHeap (about 131k). I'll bet on a function somewhere allocating a chunk of memory or repeatedly doing so and never using or releasing it. Should be 'fun' to find. Jim McCullers WA4CWI Looks like we have an issue with memory usage in RAM If 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. You can expand RAM and the subfolders and see where the memory is being used. I 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. Probably need to look for ways to reduce RAM needed. Reduce buffer sizes, move buffers to external memory, or take out code. I 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. Bob [cid:image001.png@01DA486F.5D06AFE0]

1 0

Re: Memory Problem on PacSatSW
by Bob Stricklin 16 Jan '24

16 Jan '24

Chris, Your comments are the direction we need to move towards. I would like to just hack out what I can to make it build and load so I can test chip interface. Will be looking at doing this. I want to get to the point that when I take something out that green bar moves to the left. This bar is red when you exceed available memory and probably yellow just before you do. I worry the bar is based on inputs and not actual linker results. I agree constants want help much but if there are any tables of fixed data that can be helpful. The other thing to do is code with numbers and not use variables. Again, not much savings but just a coding style. The heap space and swap is set for 0x800 each. I tried making this 0x100 each and did not see a change in the Green bar. This seems like a problem. Bob From: Chris Thompson via pacsat-dev <pacsat-dev(a)amsat.org> Sent: Tuesday, January 16, 2024 10:39 AM To: Bob Stricklin <bstrick(a)n5brg.com> Cc: Pacsat Dev <pacsat-dev(a)amsat.org> Subject: [pacsat-dev] Re: Memory Problem on PacSatSW I expect the code could be drastically optimized to reduce memory usage. It's fairly complex and I opted for simple static memory allocation. But there is plenty of duplication. Each task makes a copy of the received packet in an RTOS queue and likely in a temp buffer as well. In theory we could collapse all of that into one shared queue/buffer. In the short term you can reduce the heap size as Burns said. You could also remove some of the tasks temporarily as they each have a stack. The stack sizes can also probably be trimmed back in some cases as no optimization has been done. Most of the Globals are in MRAM but get mirrored in RAM. We could stop doing that but I doubt it is a lot of space. Finally we keep an index of the directory in the heap which does increase its size. We could remove that and only iterate over MRAM but that requires some redesign as it needs to be sorted by upload time. 73 Chris the On Mon, Jan 15, 2024, 16:01 Bob Stricklin via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: Looks like we have an issue with memory usage in RAM. If 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. You can expand RAM and the subfolders and see where the memory is being used. I 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. Probably need to look for ways to reduce RAM needed. Reduce buffer sizes, move buffers to external memory, or take out code. I 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. Bob [cid:image001.png@01DA47C3.B189E4D0] ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0

Faking Memory Size
by Bob Stricklin 16 Jan '24

16 Jan '24

You can see the file I edited and the change I made to make CCS build the project so I could see how much memory it used. This file and info is initially supplied by HCG. I am getting exact same information I see in Launchpad code and I see no reason for it to be much different. Bob

1 0

Memory File Linker
by Bob Stricklin 16 Jan '24

16 Jan '24

Burns, Tied up with doctors visit here earlier. Going to forward a couple of files related to this. I do not see a MAP file generated by the Linker. I feel there should be one some place. The only thing I see related to this is the Memory Allocation relating memory use to code routines. Using the same input of code here used by Launchpad and PacSatSW project with HCG changes. I plan to put my code on GitHub today. Have not tried to manually modify the Memory Map file. I have project set for automatic and my understanding is CCS does this for you. I will send a second email showing changes I made to make CCS think I had more memory and build project. Bob

1 0

Re: Memory Problem on PacSatSW
by Burns Fisher (AMSAT) 16 Jan '24

16 Jan '24

Just a reminder, Chris, that if you are using the OS heap (as gets used for stacks) reducing what you request will not reduce the memory that the linker sees being used. You have to also reduce the heap size. 73, Burns Fisher, WB1FJ *AMSAT(R) Engineering -- Flight Software* On Tue, Jan 16, 2024 at 11:38 AM Chris Thompson via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > I expect the code could be drastically optimized to reduce memory usage. > It's fairly complex and I opted for simple static memory allocation. But > there is plenty of duplication. Each task makes a copy of the received > packet in an RTOS queue and likely in a temp buffer as well. In theory we > could collapse all of that into one shared queue/buffer. > > In the short term you can reduce the heap size as Burns said. You could > also remove some of the tasks temporarily as they each have a stack. The > stack sizes can also probably be trimmed back in some cases as no > optimization has been done. > > Most of the Globals are in MRAM but get mirrored in RAM. We could stop > doing that but I doubt it is a lot of space. > > Finally we keep an index of the directory in the heap which does increase > its size. We could remove that and only iterate over MRAM but that > requires some redesign as it needs to be sorted by upload time. > > 73 > Chris the > > > On Mon, Jan 15, 2024, 16:01 Bob Stricklin via pacsat-dev < > pacsat-dev(a)amsat.org> wrote: > >> Looks like we have an issue with memory usage in RAM. >> >> >> >> If 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. >> >> You can expand RAM and the subfolders and see where the memory is being >> used. >> >> >> >> I 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. >> >> >> >> Probably need to look for ways to reduce RAM needed. Reduce buffer sizes, >> move buffers to external memory, or take out code. >> >> >> >> I 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. >> >> >> >> Bob >> >> >> >> >> ----------------------------------------------------------- >> >> pacsat-dev mailing list -- pacsat-dev(a)amsat.org >> View archives of this mailing list at >> https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org >> To unsubscribe send an email to pacsat-dev-leave(a)amsat.org >> Manage all of your AMSAT-NA mailing list preferences at >> https://mailman.amsat.org >> > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Memory Problem on PacSatSW
by Chris Thompson 16 Jan '24

16 Jan '24

I expect the code could be drastically optimized to reduce memory usage. It's fairly complex and I opted for simple static memory allocation. But there is plenty of duplication. Each task makes a copy of the received packet in an RTOS queue and likely in a temp buffer as well. In theory we could collapse all of that into one shared queue/buffer. In the short term you can reduce the heap size as Burns said. You could also remove some of the tasks temporarily as they each have a stack. The stack sizes can also probably be trimmed back in some cases as no optimization has been done. Most of the Globals are in MRAM but get mirrored in RAM. We could stop doing that but I doubt it is a lot of space. Finally we keep an index of the directory in the heap which does increase its size. We could remove that and only iterate over MRAM but that requires some redesign as it needs to be sorted by upload time. 73 Chris the On Mon, Jan 15, 2024, 16:01 Bob Stricklin via pacsat-dev < pacsat-dev(a)amsat.org> wrote: > Looks like we have an issue with memory usage in RAM. > > > > If 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. > > You can expand RAM and the subfolders and see where the memory is being > used. > > > > I 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. > > > > Probably need to look for ways to reduce RAM needed. Reduce buffer sizes, > move buffers to external memory, or take out code. > > > > I 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. > > > > Bob > > > > > ----------------------------------------------------------- > > pacsat-dev mailing list -- pacsat-dev(a)amsat.org > View archives of this mailing list at > https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org > To unsubscribe send an email to pacsat-dev-leave(a)amsat.org > Manage all of your AMSAT-NA mailing list preferences at > https://mailman.amsat.org >

1 0

Re: Memory Problem on PacSatSW
by Bob Stricklin 16 Jan '24

16 Jan '24

I am working with CCS version 12.5. Bob From: Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org> Sent: Monday, January 15, 2024 6:31 PM To: 'Pacsat Dev' <pacsat-dev(a)amsat.org> Subject: [pacsat-dev] Re: Memory Problem on PacSatSW My version of CSS is either different or how did you turn on the green lines with summary data? I get a popup status message with similar info but not as stable or detailed as yours. On my system, I'm showing 80% utilization. The majority is in ucHeap (about 131k). I'll bet on a function somewhere allocating a chunk of memory or repeatedly doing so and never using or releasing it. Should be 'fun' to find. Jim McCullers WA4CWI Looks like we have an issue with memory usage in RAM If 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. You can expand RAM and the subfolders and see where the memory is being used. I 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. Probably need to look for ways to reduce RAM needed. Reduce buffer sizes, move buffers to external memory, or take out code. I 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. Bob [cid:image001.png@01DA47F2.CE257530]

1 0

Re: Memory Problem on PacSatSW
by Bob Stricklin 16 Jan '24

16 Jan '24

OK will have a look at this. Found this note also which probably applies to us also: On 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). From: Burns Fisher (AMSAT) via pacsat-dev <pacsat-dev(a)amsat.org> Sent: Monday, January 15, 2024 6:38 PM To: Jim McCullers <wa4cwi(a)bellsouth.net> Cc: Pacsat Dev <pacsat-dev(a)amsat.org> Subject: [pacsat-dev] Re: Memory Problem on PacSatSW When you mentioned the heap, you reminded me: FreeRTOS 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. 73, Burns Fisher, WB1FJ AMSAT(R) Engineering -- Flight Software On Mon, Jan 15, 2024 at 7:31 PM Jim McCullers via pacsat-dev <pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org>> wrote: My version of CSS is either different or how did you turn on the green lines with summary data? I get a popup status message with similar info but not as stable or detailed as yours. On my system, I’m showing 80% utilization. The majority is in ucHeap (about 131k). I’ll bet on a function somewhere allocating a chunk of memory or repeatedly doing so and never using or releasing it. Should be ‘fun’ to find. Jim McCullers WA4CWI Looks like we have an issue with memory usage in RAM If 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. You can expand RAM and the subfolders and see where the memory is being used. I 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. Probably need to look for ways to reduce RAM needed. Reduce buffer sizes, move buffers to external memory, or take out code. I 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. Bob [cid:image001.png@01DA47F2.8D773AF0] ----------------------------------------------------------- pacsat-dev mailing list -- pacsat-dev(a)amsat.org<mailto:pacsat-dev@amsat.org> View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/pacsat-dev@amsat.org To unsubscribe send an email to pacsat-dev-leave(a)amsat.org<mailto:pacsat-dev-leave@amsat.org> Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org

1 0