Hi,
I get the following error when building:
1 304 Handler table size exceeded allowed size (max. 200 handler vectors allowed) Handler table size exceeded allowed size (max. 200 handler vectors allowed)
When I comment out one call (in the main program file) to a subroutine in an included module, the
error goes away.
With the call commented out, memory usage is:
0 1144 Static RAM (bytes): 1769 Dynamic RAM (bytes): 12610 Static RAM (bytes): 1769 Dynamic RAM (bytes): 12610
0 1144 HEAP RAM (bytes): 2000 HEAP RAM (bytes): 2000
0 1144 Used ROM (bytes): 43585 (49%) Free ROM (bytes): 44479 (51%) Used ROM (bytes): 43585 (49%) Free ROM (bytes): 44479 (51%)
I use the v5.40 compiler version compiling for a dspic33FJ128GP804
Any way to get around this 200 limit?
regards peter
Error: max. 200 handler vectors allowed
-
- Posts: 174
- Joined: 31 Aug 2009 22:44
Error: max. 200 handler vectors allowed
Last edited by peterverkaik on 20 Mar 2012 12:59, edited 1 time in total.
-
- Posts: 174
- Joined: 31 Aug 2009 22:44
Re: Error: max. 200 handler vectors allowed
Hi,
I moved the code with the call to a subroutine in module X, from main program
file to a module Y. Uncommenting the call I still get the 200 limit.
Then I moved the called subroutine also to module Y, but I still get
the 200 limit.
I surely hope this 200 limit is not absolute because that would make
the compiler useless.
Please provide a solution or workaround ASAP.
regards peter
I moved the code with the call to a subroutine in module X, from main program
file to a module Y. Uncommenting the call I still get the 200 limit.
Then I moved the called subroutine also to module Y, but I still get
the 200 limit.
I surely hope this 200 limit is not absolute because that would make
the compiler useless.
Please provide a solution or workaround ASAP.
regards peter
- janko.kaljevic
- Posts: 3565
- Joined: 16 Jun 2011 13:48
Re: Error: max. 200 handler vectors allowed
Hello,
Please can you post a code that generate this error message.
From this point of view i can not tell what could cause this.
Or if it is more convenient for you send it on my e-mail:
janko.kaljevic@mikroe.com
Best regards.
Please can you post a code that generate this error message.
From this point of view i can not tell what could cause this.
Or if it is more convenient for you send it on my e-mail:
janko.kaljevic@mikroe.com
Best regards.
-
- Posts: 174
- Joined: 31 Aug 2009 22:44
Re: Error: max. 200 handler vectors allowed
Hi,
I was clearing subroutines (to not disclose source code) but keeping
the program stucture. At some point the limit error disappeared but
the error Not enough ROM space appeared.
So it looks like the source code is larger than the dspic can handle.
I can now uncomment the call and noticed a ROM usage increase
from 37153 (42%) to 87356 (99%).
regards peter
I was clearing subroutines (to not disclose source code) but keeping
the program stucture. At some point the limit error disappeared but
the error Not enough ROM space appeared.
So it looks like the source code is larger than the dspic can handle.
I can now uncomment the call and noticed a ROM usage increase
from 37153 (42%) to 87356 (99%).
regards peter
-
- Posts: 174
- Joined: 31 Aug 2009 22:44
Re: Error: max. 200 handler vectors allowed
Hi,
I commented out all the printf() debug statements
from the code, and codesize is now reduced to 89%.
I can uncomment the call and everything compiles fine.
So the source of the error was too much code.
The compiler should have generated "Not enough ROM space"
rather than the 200 limit error.
regards peter
I commented out all the printf() debug statements
from the code, and codesize is now reduced to 89%.
I can uncomment the call and everything compiles fine.
So the source of the error was too much code.
The compiler should have generated "Not enough ROM space"
rather than the 200 limit error.
regards peter
- janko.kaljevic
- Posts: 3565
- Joined: 16 Jun 2011 13:48
Re: Error: max. 200 handler vectors allowed
Hello,
Thanks for reporting.
And it would still be very helpful if you could send us your code that demonstrates this behavior.
Best regards.
Thanks for reporting.
And it would still be very helpful if you could send us your code that demonstrates this behavior.
Best regards.