You aren't.
Vikram vik76 wrote: > On reading Table 1-2, I found SRAM value for micaz to be 4kB. > I wrote a code wherein I declare two arrays of 30000 bytes each, and > then assign values to the elements to these two arrays. > The compilation looks like this: > compiled TestAppC to build/micaz/main.exe > 21418 bytes in ROM > 61722 bytes in RAM > avr-objcopy --output-target=srec build/micaz/main.exe build/micaz/main.srec > avr-objcopy --output-target=ihex build/micaz/main.exe build/micaz/main.ihex > writing TOS image > > Now if SRAM is 4kB, then for my array variables how am I getting 61722 > bytes in RAM? > > beyond this say at 63000 bytes it gives error: .bss is not within > region data > > > Thanks > > Vikram > > > > On Fri, Nov 13, 2009 at 12:10 PM, Paul Johnson <[email protected] > <mailto:[email protected]>> wrote: > > Vikram, > > Look at "Table 1-2. Mote Product Summary" in the link I provided. > It provides the exact information that you are asking about. > > As for your other question, Program Flash Memory is reserved > explicitly for your executable(so no, program size does directly > affect available data size). RAM (SRAM in this case) is used to > store any program variables that you might use, and any variables > tinyos uses internally, stack variables, etc. Measurement(Serial) > Flash is used to store whatever you want, measurement readings, > logs, etc. EEPROM is used to store configuration data that you burn > onto the device. This might be node ID's, private/public keys for > encryption, etc. > > -Paul > > > Vikram vik76 wrote: >> On examining the micaz datasheet I found >> Program Flash Memory - 128K bytes >> Measurement (Serial) Flash - 512K bytes >> Configuration EEPROM - 4K bytes >> I am not very clear about the purpose of all of the above. >> >> I would like to know where the program executable code resides, >> and where the data resides. From data I mean how many bytes of >> values can the variables in my program store. >> Does the program and data share the same memory? If yes, does >> this mean that if my program size increases, then the available >> data size decreases. >> My requirement is to use an array of uint8_t for a large number of >> elements whose values keep changing dynamically. >> >> Thanks >> >> Vikram >> >> >> On Fri, Nov 13, 2009 at 11:42 AM, Paul Johnson <[email protected] >> <mailto:[email protected]>> wrote: >> >> Vikram, >> >> Please examine the crossbow datasheet for the micaz or the >> crossbow's MPR-MIB User's Manual for this information. >> >> >> http://www.xbow.com/support/support_pdf_files/mpr-mib_series_users_manual.pdf >> >> -Paul >> >> >> Vikram vik76 wrote: >>> Hello, >>> >>> I would like to know how much memory is available in micaz >>> motes for the following. >>> 1. Data >>> 2. Program >>> >>> Thanks >>> >>> Vikram >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Tinyos-help mailing list >>> [email protected] >>> <mailto:[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 _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
