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.
Tool/software: Code Composer Studio
Hi All,
We are using TM4C1294NCPDT to develop a project in Ti-RTOS. We configured UDP protocol for sending JSON Packets but facing some issues as mentioned below.
1.Getting Error if call a function "Board_initEMAC()" .
unresolved symbol SemPost, first referenced in C:/ti/tirtos_tivac_2_16_01_14/products/tidrivers_tivac_2_16_01_13/packages/ti/drivers/lib/drivers_tivaware.aem4f<EMACSnow.oem4f> UART_INT_0.0.13 C/C++ Problem
2. Our requirement is, to Send ADC samples over Ethernet in the JSON Format. Can we have any example related to JSON Packets?
3. Some times we face a common issue related to CCS IDE. When we take the backup of a project in the same workspace and try to debug( or load the program in the device), shows an error :
Texas Instruments XDS110 USB Debug Probe_0/CORTEX_M4_0 : Target must be connected before loading program.
Thank You,
Kashif Khan
Hi,
Did you have a chance to run the TI-RTOS UDP example. See below. When you run this example, do you see the same unresolved symbol message after you call the Board_initEMAC()?
We don't have any example on sending packets in JSON format. I hope you can so some Google search on this.
Which debug probe do you have? If you are manually launching a debug session then you will need to connect to the target prior to loading a program.
Hi Tsai,
We have already run the example code of 'UDP_echo' and It's working fine.
But if we call function "Board_initEMAC()" function in our project, it shows the above-mentioned error.
We are using "XDS110 USB Debug Probe_0/CORTEX_M4_0" to debug.
Hi,
The UDP_echo also calls the Board_initEMAC() in the beginning of the main. Please see below. If you were to start your project using the UDP_echo as a starting reference, will you see the same message?
int main(void) { /* Call board init functions */ Board_initGeneral(); Board_initGPIO(); Board_initEMAC(); /* Turn on user LED */ GPIO_write(Board_LED0, Board_LED_ON); System_printf("Starting the UDP Echo example\nSystem provider is set to " "SysMin. Halt the target to view any SysMin contents in" " ROV.\n"); /* SysMin will only print to the console when you call flush or exit */ System_flush(); /* Start BIOS */ BIOS_start(); return (0); }
About the XDS110 message, there is a similar question in the below post. Can you please follow the suggestion by Desouza from our CCS team? I will also suggest you manually create a target configuration file that is not located in your workspace and manually launch the target configuration to connect to the target and see if that makes a difference.
For that error, can you check the Project Properties under Debug -> Auto Run and Launch -> Launch Options to see if the "Connect to the target on debugger startup" option is ticked for the CORTEX_M4 core. See https://e2e.ti.com/support/microcontrollers/other/f/908/p/759209/2804781#2804781Kashif Khan said:3. Some times we face a common issue related to CCS IDE. When we take the backup of a project in the same workspace and try to debug( or load the program in the device), shows an error :
1Texas Instruments XDS110 USB Debug Probe_0/CORTEX_M4_0 : Target must be connected before loading program.
Hi Chester Gillon,
As you mentioned "Connect to the target on debugger startup" option isn't ticked. I ticked and now working fine.
Thank you very much for the quick support
Regards,
Kashif Khan