This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TI-RTOS and BSS size issues

Other Parts Discussed in Thread: SYSBIOS

Hi,

We've just switched over from using the NDK/NSP/SysBIOS individual packages to the new TI-RTOS combined package. Using the old stack, when I just have the usual Sys/BIOS features we are using enabled (BIOS, Task, Timer, HWI, Memory, Error Handling, Timestamp), compiling in Release mode and looking at the .map file, our BSS is of length 0x1794. 

With the new stack, in the same configuration, the BSS appears to be exactly the same size. So, it looks like everything is working so far. And then...

As soon as I enable any networking feature (TCP, UDP, or IP) my BSS balloons to 0xeca8. The funny thing to me is, if I enable IP and it grows to that size, and then I enable TCP and UDP both, the BSS size does not change. It is still of length 0xeca8. Not only does it seem like this might be pulling in all the NDK features regardless of whether I check the box or not, it is also quite large (our BSS total size is 0x8000 according to the linker).

I also get a message that the NIMUDeviceTable is undefined, which is apparently a symbol in the NDK (inside TI-RTOS). I am not sure if this is related.

I have a few questions:

1. Am I using the new TI-RTOS package correctly? Since this appears to be a collection of existing packages including Sys/BIOS and the NDK, I assumed it did not need much more configuration than those.

2. Why does enabling IP, TCP, UDP, or any other networking feature use the same amount of space, and so much space? As I noted, it seems quite large even considering the buffer sizes for something like TCP.

3. What can I do to reduce my BSS size so that I can get my project to compile?