Shared memory architecture
First Claim
1. A memory architecture comprising:
- a non-volatile, application memory block having first application code for application functions capable of being called by a first application;
a non-volatile, launcher memory block having second application code for application functions capable of being called by a second application, the second application code being launcher code that is operable to initialize the first application code;
a non-volatile, shared memory block having shared code for shared functions; and
fixed memory locations dedicated within the shared memory block to store shared function pointers; and
volatile memory storing callback pointers, at least one associated with each one of the shared functions, wherein the callback pointers point to callback function code stored within the non-volatile, application memory block having first application code when the first application is executing and to callback function code stored within the non-volatile, launcher memory block having second application code when the second application is executing.
3 Assignments
0 Petitions
Accused Products
Abstract
A memory architecture includes a non-volatile, application memory block having first application code for application functions capable of being called by first application, a non-volatile launcher memory block having second application code for application functions capable of being called by a second application, a non-volatile, shared memory block having shared code for shared functions, and a fixed memory locations dedicated within the shared memory block to store shared function pointers, and a volatile memory storing callback pointers. The second application code is launcher code that is operable to initialize the first application code. At least one volatile memory storing callback pointer is associated with each one of the shared functions. The callback pointers point to callback function code when the first application is executing and to callback function code when the second application is executing.
-
Citations
11 Claims
-
1. A memory architecture comprising:
-
a non-volatile, application memory block having first application code for application functions capable of being called by a first application; a non-volatile, launcher memory block having second application code for application functions capable of being called by a second application, the second application code being launcher code that is operable to initialize the first application code; a non-volatile, shared memory block having shared code for shared functions; and fixed memory locations dedicated within the shared memory block to store shared function pointers; and volatile memory storing callback pointers, at least one associated with each one of the shared functions, wherein the callback pointers point to callback function code stored within the non-volatile, application memory block having first application code when the first application is executing and to callback function code stored within the non-volatile, launcher memory block having second application code when the second application is executing. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. A battery monitoring system (BMS) controller comprising:
-
a non-volatile, application memory block having application code for an application operable to execute battery monitoring related functions; a non-volatile, launcher memory block having launcher code for a launcher operable for initializing the BMS; a non-volatile, shared memory block having shared code for shared functions; fixed memory locations dedicated within the shared memory block to store shared function pointers; and a volatile memory storing callback pointers, wherein the callback pointers point to code stored in the application memory block in the event the application is operating and to code stored in the launcher memory block in the event the launcher is operating. - View Dependent Claims (8, 9, 10, 11)
-
Specification