• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 874 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.

Compiler/TMS320C6748: Build a executable file with a library which is not in the project

Tony Tang
Mastermind 30562 points

Part Number: TMS320C6748

Tool/software: TI C/C++ Compiler

Requirement:

My customer's product need to extend a feature with a software library which is developed by their end customer, the end customer can't delivery the library to my customer to build into one executable file before product delivery. My customer delivery product to their end customer with basic software, their end customer flash their library into flash, the basic software call it to implement the extend feature.

With this requirement, what I can thought:

#1. Refer TI's application notes on how to access ROM contents:()

But how to strip binary from a .lib for burning into flash

#2. Dynamic loader, I read wiki page: 

Still don't understand how to implement it. For example:

RIDL> base_image dl6x.6x
RIDL> load hello.dll
RIDL> execute
What is the RIDL, I don't think in a BIOS or bare metal stand alone system there is such s prompt console. 

I hope there is a simple bare metal example on how to using the dynamic link feature.
Or am I wrong on the dynamic feature for my customer's requirement? 
Please advise what is the right way to implement my customer's requirement.
  • 0
    TI__Guru**** 253410 points

    I think the best application note for your situation is ROMing Software Components: An RTS Use Case. Handle the customer's code like the RTS is handled in the application note, and the end customer's code like the final application.

    Please understand that I issue this recommendation with less than my usual confidence.  This application note takes you through many steps, unusual scripts, and so on.  It is impractical for me to try it all myself and somehow be certain it will work in your situation exactly as presented.  It is likely that you will have to make a few changes.  So long as you and your customer understand such changes may be needed, I think you will be okay.

    Thanks and regards,

    -George 

  • 0 in reply to George Mock
    TI__Mastermind 30562 points

    George,

    Thanks for pointing to the better application notes. I will study it.

    At the mean time, do you think dynamic link/load feature is suitable for my customer's requirement?  I would like to know the right person in BU for this feature, 

    if you know the window, would you please send me the information via email. Thanks.

  • 0 in reply to Tony Tang
    TI__Guru* 84285 points

    Tony Tang said:
    At the mean time, do you think dynamic link/load feature is suitable for my customer's requirement?

    Probably not.  Dynamic shared objects require a bit more support from the system than you'd need for ROM'd functions