New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output compiled size and static memory usage with 'platformio run' #59

Closed
aphelps opened this Issue Feb 3, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@aphelps

aphelps commented Feb 3, 2015

(This just an enhancement request)

One minor feature I find useful from the Arduino IDE is that it outputs the size of the program being updated and (in the 1.5 branch) the total size of static variables. These are both useful both to be careful about approaching the limits, but also for optimizing code during development.

'platformio run -t upload' already outputs the size, but since I'm not always uploading it would be useful if that was output for each environment during a build.

For the static variable usage, I have a recollection that theres a tool in the avr tool chain that produces this info, but I'm not immediately seeing it. Regardless this sort of info is hugely valuable when developing for a chip that may only have 1k of memory.

@aphelps

This comment has been minimized.

aphelps commented Feb 3, 2015

Actually, I found the command for the memory size: avr-size -C -x .pioenvs/arduino_nano/firmware.elf

If this is a fairly easy change to make, if you point me to the right areas of the code I'd be happy to make the change myself.

@ivankravets ivankravets added this to the 0.11.0 milestone Feb 4, 2015

@ivankravets

This comment has been minimized.

Member

ivankravets commented Feb 9, 2015

@aphelps Thanks a lot for idea! You can try it in the latest develop branch 👍

@ivankravets ivankravets modified the milestones: 0.11.0, 1.0.0 Feb 9, 2015

@aphelps

This comment has been minimized.

aphelps commented Feb 9, 2015

That works great, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment