• Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 577 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TI TMS470 compiler version 4.9.3 issue with ELF EABI complaincy

Pramod Kumar Swami
Genius 13630 points

We have an issue reported by our customer saying that the library generated by TI compiler on cortex-M3 is not EABI compliant and because of it once they use a non-TI compiler (gcc) for linking the library they find that the generated executable is not properly following ELF format. Because of this, ELF loader is not properly able to load the image on target processor.

Below is the statement from customer

We required hacking our loader. The relocation R_ARM_THM_JUMP24 needed a patch that hard-substitutes the target address (including odd thumb-mode address) into the relocated instruction rather than using regular relocation. This mode is used in the TI library files but appears not to be used by our compiler, so this patch was ‘safe’ for me to do

We have tried creating a smaller project to see the issue and we also observed that below generated executable if loaded in CCSV4 – the loaded image are inconsistent -  sometimes there appear correct but some time incorrect.

 

0363.sampleTest.zip


Generated Executable is part of zip file @ sampleTest\app\simpleapp_command.out
TI cortex-M3 compiler version number: 4.9.3
codesourcery compiler version number: 4.5.2
Source and make file for library  project: part of zip file @ sampleTest\lib
Source and build script for application project part of zip file @ sampleTest\app

Please look at the assembly code after loading in CCS for doMath function – it will have unexpected assembly. If you do reset of processor and then load, you will see mostly code being loaded as incorrect for this fucntion

Can you please help to conclude that whether it is an issue with TI tool chain (library) or codesourcery compiler (application) or loader?

Thanks,
With Regards,
Pramod

  • TI__Guru**** 244280 points

    I'll ask for some help on this one.  But I'm sure we will need these 2 things.  I'd appreciate if you would provide them.  One, a test case we can build ourselves.  I tried using the makefile in the lib directory with no success.  Second, a precise description of one instance where a R_ARM_THM_JUMP24 relocation is handled incorrectly.  Show what is encoded for it now, what you expect the encoding to be, and why.

    Thanks and regards,

    -George

  • in reply to George Mock
    TI__Genius 13630 points

    Thanks George for the response

    Regarding makefile it has some assumption that for path of CG tools and it is for windows machine. So instead of make file you can use these 2 lines on command line or any script based upon your OS. I assume that your path environment variable has included the CGTOOLS bin directory

    cl470  -mv7M3 -O3 -me --enum_type=packed --elf --gen_func_subsections --abi=eabi --signed_chars --auto_inline=200 library.c
    ar470 -r .\libsamplelib.a library.obj

    Now regarding R_ARM_THM_JUMP24 handled incorrectly - I am not sure that it is visible in this simple example. It is my hope that the issue being observed in this simple example and solution of this can lead to actual issue also. Otherwise if you need the actual occurance of this issue then I can share a library and example client project but to build the client project there are lot of dependencies and you might end up downloading couple of components hence I thought of starting with simple example

    Thanks,
    With Regards,
    Pramod

  • in reply to Pramod Kumar Swami
    TI__Guru**** 244280 points

    Unfortunately, the R_ARM_THM_JUMP24 relocation does not occur in that test case.  We will not be able to make progress on this issue until such a test case is provided.

    You can see the relocations with ofd470.  For example ...

    % ofd470 library.obj

    Will show lines like these ...

     Relocation Table 1/1 for Section 10 (".debug_info")

     id type offset sym name 
     -- ---- ------ --- ---- 
     0 R_ARM_ABS32 0x00000006 19 .debug_abbrev
    ...  
    You can search through that for the R_ARM_THM_JUMP24 relocation like this ...

    % ofd470 library.obj | find "JUMP24"

    You won't get any hits.

    Thanks and regards,

    -George