| ??? 05/28/09 16:43 Read: times |
#165685 - back to the drawing board... Responding to: ???'s previous message |
The "slight" cut only works for the 8052 port. My own 8052 one derived port of CMON51 still has the linker error...and I didn't add any globals IIRC :(
Actualyl I don't think that memory allocation is so tight for CMON51. It banks all monitor data to XRAM for user applications so I think it should do well with the full 256bytes available. |
| Topic | Author | Date |
| SDCC Linker problem with CMON51 | 01/01/70 00:00 | |
| a wild, wild guess | 01/01/70 00:00 | |
| I already tried a typecast | 01/01/70 00:00 | |
| Why not take this to the SDCC forum? | 01/01/70 00:00 | |
| Already considered this... | 01/01/70 00:00 | |
| another possibility which is easy to check if ... | 01/01/70 00:00 | |
| I assume so... | 01/01/70 00:00 | |
| findings | 01/01/70 00:00 | |
| findings2 | 01/01/70 00:00 | |
| Temporary fix | 01/01/70 00:00 | |
| back to the drawing board... | 01/01/70 00:00 | |
| it's much less for DATA | 01/01/70 00:00 | |
| fix for --funsigned-char | 01/01/70 00:00 | |
| I'd like to but... | 01/01/70 00:00 | |
| how to patch | 01/01/70 00:00 | |
| Patch worked but SDCC doesn't compile anymore... | 01/01/70 00:00 | |
| HOW doesn't compile? | 01/01/70 00:00 | |
| Buffer cut | 01/01/70 00:00 | |
| not enough direct-addressable memory | 01/01/70 00:00 | |
| Nice idea but.... | 01/01/70 00:00 | |
| I can try with the versions I have here... | 01/01/70 00:00 | |
| Sure, why not | 01/01/70 00:00 | |
| Solution found | 01/01/70 00:00 | |
SDCC Linker problem with CMON51 | 01/01/70 00:00 |