• State TI Thinks Resolved
  • Locked Locked
  • Replies 10 replies
  • Answers 1 answer
  • Subscribers 100 subscribers
  • Views 2832 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.

AM5728: ARM cross compiler for windows environment

Koichiro Tashiro
Mastermind 22945 points

Part Number: AM5728

Hi,

My customer is using Kernel4.19 in AM572x SDK 06.02.00.81.
According to below URL, corresponding toolchain is ARM GCC 8.3 2019.03 hard-float toolchain.
http://software-dl.ti.com/processor-sdk-linux-rt/esd/AM57X/latest/index_FDS.html


Customer is using Windows machine, so they tried to find cross compiler at ARM website, but they could not find it.
https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads/8-3-2019-03

Which toolchain customer should use?

Thanks and regards,
Koichiro Tashiro

  • 0
    TI__Guru**** 393215 points

    Hi,

    The AM57x Processor SDK Linux is supported only on Linux Host machines. This is clearly stated on the download link you refer above.

  • 0 in reply to Biser Gatchev-XID
    TI__Mastermind 22945 points

    Hi Biser,

    For old SDKs (i.e. Kernel4.4 in SDK3.3.0.4), we provided cross compiler for Windows.
    Linaro GCC 5.3 2016.02 hard-float toolchain


    Cross compiler for windows:

    It does not sound reasonable for customers we do not have it anymore.
    Customer cannot develop their Linux application on Windows machines.
    Could you double check there is any compatible cross compilers?

    Thanks and regards,
    Koichiro Tashiro

  • 0 in reply to Koichiro Tashiro
    TI__Mastermind 30986 points

    Tashiro-san,

    The Linaro toolchain referred to above is not for Windows, it is for Linux. The fact that it is a tar.xz file, which Windows does not natively support indicates that. We switched from Linaro to ARM, but they are both Linux toolchains. We only support doing Linux development from a Linux host. 

    I hope this is helpful and clear. Please let us know if you have any concerns.

    Thank you.

  • 0 in reply to RonB
    Prodigy 40 points

    Dear Mr. RonB,

    Please let me join this thread.
    I’m Masayoshi Sudoh who is a customer of Tashiro-san.
    I asked him to post this topic.
    Although you explained that “gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf.tar.xz” is for Linux, I’m afraid it is not true.
    Please take a look at the below screenshot.
    You can see files whose extension is “exe”, which is for Windows.
    In addition, we use this tool chain on Windows.
    So please introduce any compatible tool chain.
    Otherwise we cannot develop any applications.
    Thank you for your understanding and cooperation.

    Best regards,
    Masayoshi SUDOH

  • 0 in reply to user6299836
    Prodigy 40 points

    please check the files in gcc-linaro-5.3-2016.02-i686-mingw32_arm-linux-gnueabihf.tar.xz.

    you can get it from below URL.

    releases.linaro.org/.../

  • 0 in reply to user6299836
    TI__Mastermind 30986 points

    Hello,

    It seems that the later release of the ARM tools has added this support back:

    https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads

    Please see if this will meet your needs. We will be switching to this new version in a future SDK.

    Thank you.

  • 0 in reply to RonB
    TI__Mastermind 22945 points

    Hi Ron,

    Is the new version (ARM gcc 9.2 2019. 12 hard-float toolchain) compatible with TI RT Linux Kernel 4.19?

    Thanks and regards,
    Koichiro Tashiro

  • 0 in reply to Koichiro Tashiro
    TI__Mastermind 30986 points

    We tested our v4.19 kernel with the older version of GCC that didn't have the Windows support. It may still work in order to continue development. We will move to the newer toolchain as part of a migration for the SDKs in the middle of the year. That is when the new tooolchain would be validated.

  • 0 in reply to RonB
    Prodigy 40 points

    Dear Mr. RonB,

    Thank you for the information.

    We found that the tool chain which is included in PROCESSOR-SDK-LINUX-RT-AM57X  06_02_00_81 is arm-linux-gnueabihf (gcc-arm-8.3-2019.03-x86_64-arm-linux-gnueabihf.tar.xz).

    On the other hand, the name of the latest version (gcc-arm-9.2-2019.12) is arm-"none"-linux-gnueabihf.

    Can you say that the compatibility is guaranteed between arm-linux-gnueabihf and arm-"none"-linux-gnueabihf?

    We are thinking about another candidate.

    It is Linaro arm-linux-gnueabihf tool chain.

    releases.linaro.org/.../

    Would you please advise me which is better "gcc-arm-9.2-2019.12-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz" or "gcc-linaro-7.5.0-2019.12-i686-mingw32_arm-linux-gnueabihf.tar.xz"?

    Best regards,

    Masayoshi SUDOH

  • 0 in reply to user6299836
    TI__Mastermind 30986 points

    Would you please advise me which is better "gcc-arm-9.2-2019.12-mingw-w64-i686-arm-none-linux-gnueabihf.tar.xz" or "gcc-linaro-7.5.0-2019.12-i686-mingw32_arm-linux-gnueabihf.tar.xz"?

    As I stated earlier, our SDK will use 9.2 in the near future. While we have no plans to test it with the current SDK, you could plan to move to that SDK and use the supported toolchain.

    As to the change in naming, I found a quote on the ARM website in the release notes which helps explain the difference:

    "Changed toolchain naming convention to match standard target triplet naming convention, with vendor name being none. For example, arm-eabi is arm-none-eabi."

    Source is Release Notes for 9.2:

    https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads

    I hope this is helpful to you. 

    Thank you.