Extensions of the digispark IDE

[gogol]

Hi,

as one of the biggest problems of digispark beginners is the very limited SRAM. If you are not used to watch for each single byte, you are running very fast over the 512 byte limit.  Problems hard hard to debug. Last example: http://digistump.com/board/index.php/topic,1049.0.html

As there is allready an wrapper replacing avr-dude, that wrapper should be able to run avr-size before downloading, and give a warning, if the static allocation of SRAM is already  over the limit, and maybe give a warning, when static allocation is 400++ bytes.

Should be a small addition to the wrapper?

Regards

  Gogol

[Bluebie]

Here's the avrdude wrapper: https://github.com/digistump/avr-dummy


Want to have a go adding these bits?

[gogol]

I have added avr-size just as an additional information line

output looks like:

Code: [Select]

Please check output of avr-size, if .data and .bss exceeds 512 bytes
   text       data        bss        dec        hex    filename
      0        758          0        758        2f6    C:\Users\wmk\AppData\Local\Temp\build1690028270039706566.tmp\Start.cpp.hex
Running Digispark Uploader...
Plug in device now... (will timeout in 60 seconds)

I have attached my change and binaries for Linux and Windows

regards

  .g

[gogol]

I uploaded the windows binary to the wiki: http://digistump.com/wiki/?ns=%3A&image=%3Aavrdude.zip&do=media&tab_files=files&tab_details=view
as it is to big, to be uploaded here.


.g

[gogol]

I uploaded yesterday a 64bit Windows version Today the 32-bit: http://digistump.com/wiki/?ns=%3A&image=%3Aavrdude-32bit.zip&do=media&tab_files=files&tab_details=view

[digistump]

This is great thanks! I'll put it in the next official version