Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
12/01/08 08:19
Read: times


 
#160445 - stack and preview..
Responding to: ???'s previous message
"Btw. You did not understand what "...insert code here" means now did you? And you probably didn't look at the preview either, right?"

You ar right. I was a bit confused. When I pressed the button, I was expecing a pop-up window that was going to ask me for the .c or txt file. But then I found the 'insert your code here' line. That made me think that the whole think will be converted to html or the code part might be parsed separately and formatted into an html table or something. Since I didn'y find any html tags that could do it, I assumed that it would be inserted here. And preview button : I am not sure that I saw it. But then it must be my mistake. But then I am worried that, if I do it again, I might make the same mistake!!

Regarding the suggestions, thanks to every one. It is not the watchdog. It is definitely something to do with stack, since I can make the problem disappear by playing with the variables- like moving some to xdata, explicitly declaring variables with location etc.

I am using keil. I can change the start up code. But in startup code, they define stack for reentrant functions only!! I am a bit confused. Why is a regular stack location not initialised? In assembly, we always do it.
How do I know where variables are initialised? Is it there in a map file?
Is it better to explicitly place variables in specific locations, after ceating the map, like the way we do in assembly? We face this issue only in database oriented projects, where there are lot of pointers to strings. How do I know the stack usage of functions? Do functions use stack to pass the values? Like, does printf call use stack to pass the string? That will be lot of pushes and pops. Please guide...

Regarding



List of 21 messages in thread
TopicAuthorDate
Program hangs at one point - 8051F340            01/01/70 00:00      
   Assembly window            01/01/70 00:00      
   hyper terminal interface            01/01/70 00:00      
      Stack size?            01/01/70 00:00      
         Stack size            01/01/70 00:00      
            Stack Management            01/01/70 00:00      
   Watchdog            01/01/70 00:00      
      stack and preview..            01/01/70 00:00      
         Limited stack            01/01/70 00:00      
      Where is the UART ISR?            01/01/70 00:00      
         ISR for UART            01/01/70 00:00      
            ISR for UART?            01/01/70 00:00      
               why "TI0=1;" is required            01/01/70 00:00      
            No, it isn't            01/01/70 00:00      
               Solved - I guess            01/01/70 00:00      
                  'polling' is NOT "standard C"            01/01/70 00:00      
                     You are right Erik..            01/01/70 00:00      
      Thought I will thank you individually..            01/01/70 00:00      
   Disable watchdog            01/01/70 00:00      
      and in Keil it is:            01/01/70 00:00      
         Status : WDT disabling in the status worked            01/01/70 00:00      

Back to Subject List