[SOLVED] Correct typing of Thumb functions for "SEGGER_THUMB_Startup.s "

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Correct typing of Thumb functions for "SEGGER_THUMB_Startup.s "

    Hello,

    after update to last version of SES v5.10a, i have some trouble with creation projects.

    I wrote earlier about the problem in the post forum.segger.com/index.php/Thr…elocation-R-ARM-THM-CALL/ and got some solution.

    after that I ran into a similar problem again, but for the file "SEGGER_THUMB_Startup.s"

    Source Code

    1. relocation R_ARM_THM_CALL to Arm-mode function not supported on this core, from .text.libc.__aeabi_errno_addr+2 (libc2.o (libc_v7em_fpv4_sp_d16_hard_t_le_eabi.a)) to __aeabi_read_tp (SEGGER_THUMB_Startup.o)
    2. See https://wiki.segger.com/Correct_typing_of_Thumb_functions for help on correcting this
    3. relocation R_ARM_THM_CALL to Arm-mode function not supported on this core, from .text.libc.__aeabi_errno_addr+2 (libc2.o (libc_v7em_fpv4_sp_d16_hard_t_le_eabi.a)) to __aeabi_read_tp (SEGGER_THUMB_Startup.o)
    4. See https://wiki.segger.com/Correct_typing_of_Thumb_functions for help on correcting this
    5. relocation R_ARM_THM_CALL to Arm-mode function not supported on this core, from .text.libc.__aeabi_errno_addr+2 (libc2.o (libc_v7em_fpv4_sp_d16_hard_t_le_eabi.a)) to __aeabi_read_tp (SEGGER_THUMB_Startup.o)
    6. See https://wiki.segger.com/Correct_typing_of_Thumb_functions for help on correcting this
    7. relocation R_ARM_THM_CALL to Arm-mode function not supported on this core, from .text.libc.__aeabi_errno_addr+2 (libc2.o (libc_v7em_fpv4_sp_d16_hard_t_le_eabi.a)) to __aeabi_read_tp (SEGGER_THUMB_Startup.o)
    8. See https://wiki.segger.com/Correct_typing_of_Thumb_functions for help on correcting this
    9. relocation R_ARM_THM_CALL to Arm-mode function not supported on this core, from .text.libc.__aeabi_errno_addr+2 (libc2.o (libc_v7em_fpv4_sp_d16_hard_t_le_eabi.a)) to __aeabi_read_tp (SEGGER_THUMB_Startup.o)
    10. See https://wiki.segger.com/Correct_typing_of_Thumb_functions for help on correcting this

    Based on the errors in the file, you yourself have broken the rule described in your wiki.

    I am attaching a file with corrections, I hope it helps someone.
    SEGGER_RTT_SES.7z

    I also hope that the Segger team will treat with understanding and make the required fixes in the new version.

    Let's make this product better together!

  • Hello,

    Thank you for your inquiry.
    The startup.s shipped with V5.10a is already in the correct format so you can simply use that.
    A general guide on how to migrate your projects from V4 to V5 is described here:
    wiki.segger.com/Migrating_proj…_Embedded_Studio_V4_to_V5

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • I'm sorry, my mistake.

    in the next branch you wrote that you expect support from Nordic for integration new assembler startup.
    For STM32 the new project is generated as expected.

    thanks for your patience and clarification.

  • Hello,

    No worries, and yes, the nRF package does not come with the correct startup yet. But an update is planned shortly.
    All other packages that are not transformed yet will also be updated by us.
    But if you generate a generic project for your target device without any CPU support package, the project generator will use the generic files from the /samples folder in the ES installation path which are in the correct form for the new SEGGER tool chain.

    You can also do this manually as explained in the Wiki article linked earlier.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.