⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
5 posts / 0 new
Last post
pvmellor
Offline
Last seen:1 year 8 months ago
Joined:2017-04-27 20:30
Out of Memory Error

We have good working code for the PAN1740 incorporating BASS, DISS, and a custom profile CUSTS1.
We have recently added support for SUOTA and now have an out of memory error at run time.
Program Size: Code=23964 RO-data=3032 RW-data=1096 ZI-data=8156

We're a little disappointed that such a small app (our customer profile is fairly simple) is already running up against resource constraints.

Can you advise on best steps to take to resolve this situation?

The compiler is set to "C99 mode" and optimise Level 3 (-O3) - would anything else here help?
Can we manually change the heap/stack etc. in a safe way? How?
我们可以删除任何调试stuf吗f?
What are the veneers? They seem to take up a fair bit of room.
Can we move stuff into different RAM areas? We boot the PAN from code held remotely on a controller MCU via SPI. How do we monitor the sizes of these? What's already in them?
I'm sure there are lots of other things...

Thanks,
Paul.

Keywords:
Device:
pvmellor
Offline
Last seen:1 year 8 months ago
Joined:2017-04-27 20:30
Looking a bit deeper, in the

Looking a bit deeper, in the map file I find
Total ROM Size (Code + RO Data + RW Data) 28092 ( 27.43kB)
So I'm thinking this should fit as it is under the 32k limit.

I have an external processor and I send messages back and forth via a GTL.
At initialization time there is a message containing the bondDB sent that is just over 100 bytes.
If EXCLUDE_DLG_SPOTAR = (1) and SPOTAR is excluded, then the GTL init message is correctly