| ??? 11/20/07 11:12 Read: times |
#147242 - Problem found no stack overflow ... Responding to: ???'s previous message |
Thank you for all the good ideas and God bless Logic analysers.
After I was sure it is not Stack overflow, placed overall PIN toggling flags and found the problem. As Stefan already supposed it seems to be in a specific digital ASIC block (nothing to do with the 8051), one flag is not set even it should and than a while blocked the whole CPU in the interrupt. The strange thing was that this flag was changing according the SW timing and at the first look it seemd to be a stack problem. But, Attila, if you are going to provide the closed-source library and API as a method of using the chip, I'd say, it's your responsibility to tell at least the "time" and stack (and other resources) usage, so that the user can estimate how far he/she can go when writing the application... Jan's point is very good about the stack and resource usage with the closed library. Will go in this direction and collect this info for all the modules. |
| Topic | Author | Date |
| Stack overflow checking method | 01/01/70 00:00 | |
| stack overflow check | 01/01/70 00:00 | |
| KISS - would be nice to have but.. | 01/01/70 00:00 | |
| long interrupts are not taboo... | 01/01/70 00:00 | |
| stack overflow | 01/01/70 00:00 | |
Problem found no stack overflow ... | 01/01/70 00:00 |