Hi Gary, You're both right and not. There are two images, one for the app (in the apps/Null/build/... directory), and one for the bootloader (in tos/lib/tosboot/build). On the avr platforms, the bootloader goes to the last 4k of the flash, therefor the bootloader image is 128kB, but the first 124kB is empty (this is achieved with the --section-start=.text=0x1f000 gcc flag). So programming goes like this: -install app after erasing ROM -install bootloader without erasing ROM
Andris On Sat, Sep 15, 2012 at 4:57 AM, Gary Lee <[email protected]> wrote: > Dear All, > > Here is what I do: > > 1. For the Null application, I run “make micaz”, the image needs > 608 byte of ROM and 4 byte of RAM; > > 2. Then in the Makefile, I add “BOOTLOADER=tosboot”, and I run > “make micaz”, the image still needs 608 byte of ROM and 4 byte of RAM; > > I think the image from 2) should be larger than the image from 1), because > 2) includes bootloader, right? > > > Thanks a lot, > > > Gary > > > > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
