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

Importing User Boot Loader (UBL) Project to CCSv5

Andrew Muehlfeld
Intellectual 720 points

I am developing software for the DM6467T, and need to recompile the User Boot Loader (UBL).  I downloaded the UBL source code from flash-utils-dm646x.tar.gz at http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_3_10/latest/index_FDS.html. It appears to be a CCSv2 project.  I would like to import it into CCSv5 running under Linux, and recompile the source code.  Is this possible?  If not, what are my options for recompiling?

  • 0
    TI__Genius 15640 points

    We currently do not support importing .pjt files (CCS 1.x-3.3 project format) directly into Linux. .You could import .pjt file on windows (this would covert .pjt file to CCS5 format and then you should be able to import v5 project into CCSv5 on linux).  pjt file format has evolved over the life of CCS 1 through 3.3, most of our testing has focused on 3.3 .pjt files, but in theory 2.x .pjt file should be simpler (i.e. less features) and hence it should still work. The other option that you could consider is opening .pjt file in a text editor (it is just a text file) and re-creating the project directly in CCSv5 on linux, by adding same sources and adding same compiler/linker options. The format of .pjt file should be pretty self explanatory once you open it. 

    Martin

     

  • 0 in reply to MartinS
    Intellectual 720 points

    I followed your suggestion, opened the .pjt file and recreated the project adding the sources and linker options.  A few notes in case anyone else tries this:

     

    1) Linux is case sensitive, and gets angry about capitals for some of the #include files.  You will have to change them to all lowercase.

     

    2) Not all the .c files in the source directories are used, be sure to only add the ones from the .pjt file to the project.

     

    3) There is a perl script which calls a Windows executable that must be run in Windows to post-process the result.  It is documented in ubl/docs/DM6467_Boot_Loader_UserGuide.doc.  It needs your <name>.out and <name>.map file, and generates <name>.bin.  You may have to rename all of these to ublDavinci.*