• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 32 subscribers
  • Views 388 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

RTOS/EK-TM4C129EXL: continue to have problems with Linker

user5877900
Prodigy 30 points

Part Number: EK-TM4C129EXL

Tool/software: TI-RTOS

Hello everybody,

Unfortunately, I have not been able to implement the secure_iot demo running on the tm4c129exl board. I have tried it with various wolfssl and tirtos versions. Unfortunately, I can not get on my last post: "RTOS / EK-TM4C129EXL: secure_iot_demo problems with linker".

WolfSSL writes that I'm on the right track. They could not help me any further. The "settings.h" on which they point out, I have already adapted as described in the instructions included.

Is it possible to send me a zip containing the secure_iot demo with tirtos and wolfssl built in. So that I have to import it only in the ccs?
For Information: With Windows10, I come to the same point.

best regards

Mathias
  • 0
    TI__Guru**** 191886 points
    Hi Mathias,
    Looks like you had opened a similar thread e2e.ti.com/.../755430 a while back and our TI-RTOS team had made some suggestions. If WolfSSL cannot help you resolve your issue I'm not sure what additional help we can provide. Please clearly describe what your latest problem is and I will transfer your question to our TI-RTOS experts and see if they can provide some more comments.
  • 0 in reply to Charles Tsai
    TI__Guru* 96960 points

    Are you still trying to use a newer WolfSSL version? If so, we cannot really help with this. I was able to build using wolfssl-3.8.0-commercial with the out of the box example (TCP Echo + TLS) + changes specified in the example's readme.

    Todd

    [Update 1/22: Marking as TI Thinks Resolved due to no response from original poster.]