-
My ToshibaSemicon
- General Top View
-
SEMICONDUCTOR View
-
ApplicationsAutomotive
Body Electronics
xEV
In-Vehicle Infotainment
Advanced Driver-Assistance Systems (ADAS)
Chassis
IndustrialInfrastructure
BEMS/HEMS
Factory Automation
Commercial Equipment
Consumer/PersonalIoT Equipment
Healthcare
Wearable Device
Mobile
Computer Peripherals
-
Products
Products
-
Design & Development
-
Knowledge
Knowledge
- Where To Buy View
-
- STORAGE View
- COMPANY View
- Part Number Search
- Cross Reference Search
- Keyword Search
- Parametric Search
- Stock Check & Purchase
This webpage doesn't work with Internet Explorer. Please use the latest version of Google Chrome, Microsoft Edge, Mozilla Firefox or Safari.
require 3 characters or more.
The information presented in this cross reference is based on TOSHIBA's selection criteria and should be treated as a suggestion only. Please carefully review the latest versions of all relevant information on the TOSHIBA products, including without limitation data sheets and validate all operating parameters of the TOSHIBA products to ensure that the suggested TOSHIBA products are truly compatible with your design and application.
Please note that this cross reference is based on TOSHIBA's estimate of compatibility with other manufacturers' products, based on other manufacturers' published data, at the time the data was collected.
TOSHIBA is not responsible for any incorrect or incomplete information. Information is subject to change at any time without notice.
require 3 characters or more.
Overall Configuration of the CPU: Stack and Stack Pointer
When an interrupt request occurs, the stack is used as a place to temporarily save the flags of the program and the value of the PC that were running until just before the interrupt occurred.
After the interrupt processing is completed, the information such as the flags saved in the stack is restored, and the continuation of the suspended program is executed.
The stack pointer manages the stack, and indicates the address where the PC and the flag are saved.
The data to be put in and out of the stack is managed using the FILO (First-in Last-out) method, in which the data stored first is taken out later.
Storing the data in this stack is called "Push", and reading the data from this stack is called "Pop".
The stack pointer is advanced by "Push", and returned by "Pop".
