[SOLVED] RT105x problem with thumb_crt0 on NXP RT1052 Eval board

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

  • [SOLVED] RT105x problem with thumb_crt0 on NXP RT1052 Eval board

    I am trying to get a build for the NXP eval board with a RT1052 processor on it.
    I am using In thumb_crt0 there are some undefined variables, I think they would be define in ld script
    • __data_load_start__ // I think this should be __data_run_load_start__
    • __data_start__
    • __data_end__
    • __text_load_start // I think this should be __text_run_load_start__
    • __text_start__
    • __text_end__
    • __fast_load_start__ // I think this should be __fast_run_load_start__
    • __fast_start__
    • __fast_end__
    • __ctors_load_start__ // I think this should be __ctors_run_load_start__
    • __ctors_start__
    • __ctors_end__
    • __dtors_load_start__ // I think this should be __dtors_run_load_start__
    • __dtors_start__
    • __dtors_end__
    • __rodata_load_start__ // I think this should be __rodata_run_load_start__
    • __rodata_start__
    • __rodata_end__
    • __tdata_load_start__ // I think this should be __tdata_run_load_start__
    • __tdata_start__
    • __tdata_end__
    • __data2_load_start__ // I think this should be __data2_run_load_start__
    • __data2_start__
    • __data2_end__
    • __text2_load_start__ // I think this should be __text2_run_load_start__
    • __text2_start__
    • __text2_end__
    • __rodata2_load_start__ // I think this should be __rodata2_run_load_start__
    • __rodata2_start__
    • __rodata2_end__
    • __data_tcm_load_start__
    • __data_tcm_start__
    • __data_tcm_end__
    • __text_tcm_load_start__
    • __text_tcm_start__
    • __text_tcm_end__
    • __rodata_tcm_load_start__
    • __rodata_tcm_start__
    • __rodata_tcm_end__
    Is this correct, do you guys have a updated linker script to supply these variables
  • Hello,

    Thank you for your inquiry.
    Which linker file are you using for your setup?
    Keep in mind that the imxRT series does not have internal Flash so you would need to use the ram_placement.xml section placement when setting up the project.
    There .data .text .ctors etc. are all placed in RAM and can be referenced.
    Are you using the CPU Support Packages when setting up for that device?
    You can install it under: Tools->Package Manager..->NXP->MIMXRT1052 CPU Support Package
    When creating a new project you can now select the support package for the device specific base files. The generated project should be working out of the box on any imxRT1052 device.

    Does that solve the issue?

    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.
  • Hi Nino

    I am using this targeting a NXP eval board with QSPI flash on it.
    It sounds like there is no support on JLink QSPI at this time.
    I am considering using a LPC-Link2, which it looks like it make itself look like a JLink

    The eval board has 32MB of sdram on it so, that I could use.
    But when we load code the sdram has not been initialized.
    Is there a workaround for that.

    I created a sdram_placement.xml to place everything into sdram.
    By looking at the map file it looks to have worked.

    I am using the MIMXRT1052 CPU Support Package


    Thanks
    Paul
  • Hi Paul,

    QSPI Flash support is no available yet for this device as already writte in oyur other post: forum.segger.com/index.php?page=Thread&threadID=4881

    I am considering using a LPC-Link2, which it looks like it make itself look like a JLink

    This should be possible. Keep in mind that the LPC-Link2 will have some limited functionality compared to a full J-Link.

    The eval board has 32MB of sdram on it so, that I could use.
    But when we load code the sdram has not been initialized.
    Is there a workaround for that.


    J-Link will not initialize any external memories automatically. Only memory that is available internally after reset will be available.
    To enable external memory JLinkScripts can be used. More information can be found in the J-Link user manual in section J-Link script files.

    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.