Question about printfs from the TCP/IP keepalives

The file where the printf comes from is under the path and I did find that file before I posted the question at the location:

CCS_Install\tirtos_2_16_00_08\products\NDK\stack\tcp\tcptime.c

I did try to modify the the source file and I still saw the printout so I think that code may be linked in or something anyway.

If modifying the file to not do the printf worked, that file is not part of the project or the source control for the project so changing the file would only work on the PC I modified the source file on if modifing the file did work.

Doug

Hi Doug,

I would guess its compiled in a library then and you need to recompile that library.

Can you check the list of linked libraries for your project? That might clue you in on which library includes these NDK elements.

Best Regards,

Ralph Jacobi

Ralph Jacobi said:

This specific line is coming from the tcptime.c file inside of the void TcpTimeoutKeep( TCPPROT *pt ) API where there is this line:

DbgPrintf(DBG_INFO,"TcpTimeoutKeep: Keep Timeout");

So if you removed that, that should solve the issue.

The TI Network Developer's Kit (NDK) API Reference Guide explains that the 1st argument to DbgPrintf() is a severity. There is a configuration parameter DbgPrintLevel Debug message print threshold which sets the lowest level of a system debug message which will be reported.

The default for DbgPrintLevel is DBG_INFO. Changing the DbgPrintLevel configuration parameter to the next highest level of DBG_WARN should suppress the reporting of TcpTimeoutKeep (and any other DBG_INFO messages in the network stack) without having to change the network stack code.

I haven't tried this myself.

in CCS Project properties I have the following:

Build->Include options:

"${workspace_loc:/${ProjName}}"

"${workspace_loc:/${ProjName}/inc}"

"${COM_TI_RTSC_TIRTOSTIVAC_INSTALL_DIR}/products/TivaWare_C_Series-2.1.1.71b"

"${COM_TI_RTSC_TIRTOSTIVAC_INSTALL_DIR}/products/bios_6_45_01_29/packages/ti/sysbios/posix"

"${CG_TOOL_ROOT}/include"

Build->ARM Linker:

                -mv7M4 --code_state=16 --float_support=FPv4SPD16 --abi=eabi -me -g --gcc --define=ccs="ccs" --define=TARGET_IS_TM4C129_RA1 --define=PART_TM4C1294NCPDT --define=ccs --define=TIVAWARE --diag_warning=225 --diag_warning=255 --diag_wrap=off --display_error_number --gen_func_subsections=on -z -m"ConformGen2.map" --stack_size=1024 --heap_size=0 -i"C:/ccs6p1p2/ccsv6/tools/compiler/ti-cgt-arm_5.2.7/lib" -i"C:/ccs6p1p2/ccsv6/tools/compiler/ti-cgt-arm_5.2.7/include" --reread_libs --diag_wrap=off --display_error_number --warn_sections --xml_link_info="ConformGen2_linkInfo.xml" --rom_model

Build->ARM Linker->File search path

"${COM_TI_RTSC_TIRTOSTIVAC_INSTALL_DIR}/products/TivaWare_C_Series-2.1.1.71b/driverlib/ccs/Debug/driverlib.lib"

The network was added via the RTOS config tool in the *.cfg file so do I have to check there for the linked in library?

Hi Doug,

I wouldn't think the .cfg has libraries too, but I was just thinking... there are usually two projects associated with the RTOS, the application and the kernel project. Have you re-built the kernel project as well? If not, try that.

Also would be an interesting test to see if you changed the output of that line, if you see that reflected at all. I searched through the RTOS files again and can't find any other references to TcpTimeoutKeep.

Best Regards,

Ralph Jacobi

I have never rebuilt a library, are there instructions on how to do that some place?

Hello Doug,

Wasn't meaning that the kernel project is a library - it's just the CCS project which should have the SYS/BIOS / Kernel configuration which is then used by the other RTOS application projects.

That said if were talking about a library like driverlib in TivaWare, we covered this in our new(ish) Getting Started Guide in Section 4.2! https://www.ti.com/lit/ug/spmu373a/spmu373a.pdf#page=20

Best Regards,

Ralph Jacobi