> It looks like your error is being reported within the bss section, the
> pic32 compiler only relieves the limitation for the code size,
> is still limited to (I think it is) 32K. Use malloc to get storage
> large arrays / chunks.
> Tom Walsh - WN3L - Embedded Systems Consultant
> 'www.openhardware.net', 'www.cyberiansoftware.com'
> "Windows? No thanks, I have work to do..."
> This message resent by the email@example.com list server
Thanks, Tom. A quick confirmed all errors were for global static
I have been going through the archives and trying to understand all
the limitations but I still have a few questions. Sorry for all the
With the 32-bit PIC patch, the modified crt0.S and no recompilation
of libraries (still 16-bit PIC),
1) What is the limit on the total size of the binary - will recompiling
the libraries with 32-bit change this
2) What is the limit on the text segment
3) What is the limit on the data+bss
4) What exactly is bss (apologies for what is no doubt a stupid question)
Some preliminary hacking to drastically reduce the size of statically
allocated variables still didn't solve the problem. Linking modules
one by one seems to indicate that the errors start appearing when
the total binary size exceeds 64K. Is this still a limit ?
I am guessing that there may be something more to fix with the total
size or bss even after using malloc instead of large static data
Thanks once again very much for the help.
This message resent by the firstname.lastname@example.org list server http://www.uClinux.com/
This archive was generated by hypermail 2b30 : Sun Apr 07 2002 - 00:01:39 EST