avr-size is known to have issues too on Linux. Search this forums for more on that. If you don't give the MCU model, the tool can't determine (and warn you) if the RAM or FLASH consumption of your program has exceeded what's on the device.
My makefile automatically runs my game in the after a build, but I occasionally get weird problems which I've tracked down to overflowing the 4k RAM limit as I don't have a makefile check for this. If it helps anyone else, here is a way of using gawk to detect when my program data exceeds 3800 bytes:
My makefile automatically runs my game in the after a build, but I occasionally get weird problems which I've tracked down to overflowing the 4k RAM limit as I don't have a makefile check for this. If it helps anyone else, here is a way of using gawk to detect when my program data exceeds 3800 bytes and bail out of the makefile:
Avr-size for Linux won't let me set the mcu, I'm guessing it's the same for OS X.
I made this hacky OS check based on uzem's Makefile, I haven't tested it on Windows, but (assuming uzem's Makefile doesn't have any problems) it should work:
I was going to put forward that you go to the Build menu and "Export Makefile" then edit the Studio generated Makefile and back in Project-Config then set this as an outside makefile to be used (and I know you'd have to re-do this every time you add files to the project - so it's not the best answer) but it won't work anyway as the chant of avr-size does not appear in that Makefile anyway. Presumably Studio invokes make on the auto-Makefile and then unconnectedly runs avr-size? As such I don't think there's going to be anyway to change it's behavior (short, maybe, of using a binary editor on the avr-gcc plugin DLL file, ruling the avr-size invocation and changing it there)
I did a fresh install of AVR Studio 4.18SP3 and now the call in the generated makefile from studio to avr-size isn't there anymore. I didn't get any memory usage information. On older studio versions everything works fine ...
Last edited by kipfow on Fri Jun 22, 2012 8:23 am, edited 3 times in total.
Hmmm interesting. However we don't use generated makefiles for the Uzebox projects. Just start from the makefile in one of the demo projects and everything will be fine again.
I was rebuilding my tool chain on Windows and ran in this problem again, so I decided to document the fix and make a patched version of avr-make available. In case someone search for this issue in the futur...here is a patched version of avr-size for Windows that support the -C and --mcu switches.
Replace the old version under your win-avr/bin directory with this one and you are good to go.