Re: Separating Assembly data from code in Flash

Chris Musial wrote:

>Hello Group,
>
>I've got some interrupt routines written in assembly that increment counters
>stored in a java array of shorts.  When I install the interrupt, I pass the
>assembly routine the address of the java buffer and the assembly squirrels away
>the buffer address into an area reserved in assembly using db's.  Each time the
>interrupt service routine is entered, it grabs the buffer address, dereferences
>it, and increments the counters stored in the buffer.
>
>My question:  if I put this entire application into flash, do those data areas
>in my assembly also get put into slush, or do they get put into a separate data
>segment that gets mapped into SRAM when the application is run.  If not, are
>there any scratch data areas in SRAM that I can use (and hardcode) that won't
>get grabbed by the VM memory allocator?  (I'm making my application part of
>slush, so slush will be running at the same time).
>
When you call loadLibrary(...), your library is copied into a freshly 
allocated section of heap. Your native code is executed out of, and your 
DB-ed data lives in RAM. This is true for any application including a 
flashed application (e.g. slush).

>
>Chris Musial
>cmusial-cK+/[email protected]
>  
>


-- 
Thomas Chenot


_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini