Arm Community
Site
Search
User
Site
Search
User
Groups
Arm Research
DesignStart
Education Hub
Graphics and Gaming
High Performance Computing
Innovation
Multimedia
Open Source Software and Platforms
Physical
Processors
Security
System
Software Tools
TrustZone for Armv8-M
中文社区
Blog
Announcements
Artificial Intelligence
Automotive
Healthcare
HPC
Infrastructure
Innovation
Internet of Things
Machine Learning
Mobile
Smart Homes
Wearables
Forums
All developer forums
IP Product forums
Tool & Software forums
Support
Open a support case
Documentation
Downloads
Training
Arm Approved program
Arm Design Reviews
Community Help
More
Cancel
Developer Community
Tools and Software
Software Tools
Jump...
Cancel
Software Tools
Arm Development Studio forum
Cortex M3 - How detect stack overflow?
Tools, Software and IDEs blog
Forums
Videos & Files
Help
Jump...
Cancel
New
Replies
5 replies
Subscribers
126 subscribers
Views
13105 views
Users
0 members are here
Related
Cortex M3 - How detect stack overflow?
Offline
Andre Pereira
over 7 years ago
Note: This was originally posted on 12th January 2011 at http://forums.arm.com
Hi everybody,
I've started developing whit ARM few weeks a go and I have this doubt:
The Cortex-M3 have some hardware detection of stack overflow?
Let me explain:
I've used PIC24 for my last projects, and using as example, the PIC24 have the register "SPLIM" (Stack Pointer Limit) where you write the address of the last byte of your software stack and if your software try to write in more than the address wrote in the SPLIM register, the processor causes a "trap" (a kind of interruption with an dedicated vector).
Using this "trap" you can know if you have any stack overflow.
The ARM Cortex-M3 have something like that?
I've searched in the ARM v7 and the Cortex-M documentation and I just found something about BusFault in stacking but I don't understand very well.
Sorry for my poor english (I'm from Brazil) and thanks in advance.
André Rairan.
Parents
Offline
Joseph Yiu
over 7 years ago
Note: This was originally posted on 14th January 2011 at
http://forums.arm.com
First of all, in case you don't know, many compiler suites generate information about how much stack your program required.
For example, in Keil MDK, after you compile a project, you will find a html file in the project directory. Inside you can find something like this
main
(Thumb, 36 bytes, Stack size 8 bytes, hello.o(.text))
[Stack]
Max Depth = 128
Call Chain = main ⇒ __2printf ⇒ _printf_char_common ⇒ __printf
(it is a long file, but you should be able to locate this information easily).
From the same file, you should be able to locate the stack size required for your interrupt handlers.
For each level of interrupt, you need to reserved 9 words. (Depending on the stack pointer value when interrupt happen, a word of padding might be need so that the stack frame is double word aligned).
Now you can work out the maximum stack size you need by consider
the stack size required from main( )
+ the stack size required for interrupt handlers when nested
+ 9 words x number of interrupt level.
However, this will not check the situations when the stack pointer is modified manually inside the code.
If using MPU, you can define two regions (the MPU support 8 regions):
Region 0 cover the whole 4GB address space to allow the program to access program, data and I/O as usual.
Region 1 define a small memory block (minimum MPU region is 32 bytes) to be blocked from any accesses.
The rest of the regions (region 2 to region 7) remain disabled.
Then enable the MPU (MPU_CTRL set to 1).
When the block memory is accessed, a hardfault (or memoery management fault if you enable this exception) would take place.
By setting the blocked memory region to the limited of the stack memory, the hardfault will be triggered when your program use more stack then you expected.
Note:
1. A MPU region starting address must be aligned to the size of the MPU region.
2. By using this method, the values of registers pushed to the stack before hardfault is entered could be lost.
If you want to allow the program to be resumed, it is easier to use data watchpoint comparator in DWT to trigger debug monitor exception.
Cancel
Up
0
Down
Reply
Cancel
Reply
Offline
Joseph Yiu
over 7 years ago
Note: This was originally posted on 14th January 2011 at
http://forums.arm.com
First of all, in case you don't know, many compiler suites generate information about how much stack your program required.
For example, in Keil MDK, after you compile a project, you will find a html file in the project directory. Inside you can find something like this
main
(Thumb, 36 bytes, Stack size 8 bytes, hello.o(.text))
[Stack]
Max Depth = 128
Call Chain = main ⇒ __2printf ⇒ _printf_char_common ⇒ __printf
(it is a long file, but you should be able to locate this information easily).
From the same file, you should be able to locate the stack size required for your interrupt handlers.
For each level of interrupt, you need to reserved 9 words. (Depending on the stack pointer value when interrupt happen, a word of padding might be need so that the stack frame is double word aligned).
Now you can work out the maximum stack size you need by consider
the stack size required from main( )
+ the stack size required for interrupt handlers when nested
+ 9 words x number of interrupt level.
However, this will not check the situations when the stack pointer is modified manually inside the code.
If using MPU, you can define two regions (the MPU support 8 regions):
Region 0 cover the whole 4GB address space to allow the program to access program, data and I/O as usual.
Region 1 define a small memory block (minimum MPU region is 32 bytes) to be blocked from any accesses.
The rest of the regions (region 2 to region 7) remain disabled.
Then enable the MPU (MPU_CTRL set to 1).
When the block memory is accessed, a hardfault (or memoery management fault if you enable this exception) would take place.
By setting the blocked memory region to the limited of the stack memory, the hardfault will be triggered when your program use more stack then you expected.
Note:
1. A MPU region starting address must be aligned to the size of the MPU region.
2. By using this method, the values of registers pushed to the stack before hardfault is entered could be lost.
If you want to allow the program to be resumed, it is easier to use data watchpoint comparator in DWT to trigger debug monitor exception.
Cancel
Up
0
Down
Reply
Cancel
Children
No data
More questions in this forum
By title
By date
By reply count
By view count
By most asked
By votes
By quality
Descending
Ascending
All recent questions
Unread questions
Questions you've participated in
Questions you've asked
Unanswered questions
Answered questions
Questions with suggested answers
Questions with no replies
Suggested Answer
error encountered when try to connect FVP
0
1513
views
7
replies
Latest
11 days ago
by
fantim.zhang
Answered
Key difference between GCC arm-none-eabi and arm-eabi
0
compiler
GCC
Getting Started
parameters
GNU
eabi
52620
views
6
replies
Latest
13 days ago
by
Juvanta
Suggested Answer
Can anyone please help me on how evalution development studio 2020.1 work s and which compiler is needed and how it can be setup?
0
1103
views
3
replies
Latest
16 days ago
by
Ronan Synnott
Suggested Answer
Can anyone tell me the difference between DSTREAM and DSTREAM-ST?
0
1331
views
2
replies
Latest
21 days ago
by
Xiang
Not Answered
Would you be interested in a VScode extension to handle ARM toolchain?
0
1224
views
0
replies
Started
23 days ago
by
vix
<
>
View all questions in Arm Development Studio forum