Maximum .PRG file size error

zlelik 7 days ago

I am trying to recompile one Application from github from one watch model to another. When I build it I get this error

ERROR: PRG generated exceeds the memory limit of app type 'watch-app' for device id 'instinct2x': 218282 bytes.

What does it exactly mean? Is it max file size of prg file 218282 bytes or it is bigger than maximum allowed by 218282 bytes or what?

When I build it I get 363980 bytes prg file.

Can I find somewhere the list of max oprg files for each watch?

Also, how can I decrease the size of prg file? Maybe change SDK version or some compiler option?

Top Replies

jim_m_58 6 days ago in reply to FlowState +2

Not true for a debug build, where the debug info doesn't get loaded. If you look at the prg in bin, that's a debug build, it's much larger than a release build due to all the debug info

With…

All Replies

zlelik 5 days ago in reply to FlowState

So, then it could be that instinct3 supports png natively and this is why prg file for instinct is small, but instinct2 supports only bitmaps and this is why the prg file is so big. Maybe I can try to play with png/bitmaps.

jim_m_58 5 days ago in reply to zlelik

The I3 devices have the graphics pool while the I2 devices don't, and everything need to fit in the apps memory instead of using the shared pool.

zlelik 5 days ago in reply to zlelik

I tried to convert one png to bmp but prg file size is still the same (did not change even 1 byte).

I will try https://github.com/pzl/ciqdb to see what is inside PRG file.

FlowState 5 days ago in reply to zlelik

zlelik said:
So, then it could be that instinct3 supports png natively and this is why prg file for instinct is small, but instinct2 supports only bitmaps and this is why the prg file is so big. Maybe I can try to play with png/bitmaps.

Yeah, but again, the part of the PRG that needs to be immediately loaded into memory shouldn't include resources either way, so I don't think that's the solution for the error you are seeing.

It seems to me that you need to reduce the amount of the code in the PRG.

Have you tried -O 3z (slow optimizations; optimize for space and not performance)? If that doesn't work, you might have to look at refactoring your code.

Do you have a lot of static data in big arrays? You could look at moving data like this from the source code to JSON resources, but that might just move the problem to runtime (depending on how much of the data you need to load at once).

zlelik 4 days ago in reply to FlowState

I tried to put

project.optimization = 3z

but PRG filesize is the same. I will check the code a bit more for static data and arrays.

jim_m_58 4 days ago in reply to zlelik

Have you contacted the dev that posted this on github? The dev knows their code. Maybe they can add the i2 and have a better incite into what's happening...

FlowState 4 days ago

Can you post a link to the github repo?

zlelik 4 days ago in reply to jim_m_58

It is good idea to contact the author of original code. I will.

zlelik 4 days ago in reply to FlowState

This is the link
github.com/.../main

zlelik 4 days ago in reply to FlowState

There is a large array in the code. 12000 items array. But if it is an array, then why it is not a problem for instinct3 and PRG file is relatively small with the same array?