• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 242 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.

Getting Started with TMS570LS12x + GCC + CCS + HALCoGen

Akmal Khan
Prodigy 30 points
Part Number: TMS570LS1227
Other Parts Discussed in Thread: HALCOGEN,

Tool/software:

Hello everyone,

I am starting a new project with the TMS570LS12x microcontroller series and would like some guidance on setting up and working with this platform. I’m using GCC as the compiler and Code Composer Studio (CCS) for development. I also plan to use HALCoGen for peripheral initialization.

Could anyone provide some advice or steps on the following?

  1. Setup and Configuration:

    • How do I configure Code Composer Studio (CCS) to work with GCC for the TMS570LS12x?
    • Are there any specific settings or plugins needed to integrate GCC with CCS?

  2. HALCoGen Integration:

    • How do I generate and integrate HALCoGen code with my GCC project in CCS?
    • What are the best practices for using HALCoGen to configure peripherals and initialize the microcontroller?

  3. Basic Example:

    • Is there a simple example project or tutorial available that demonstrates the use of HALCoGen with GCC and CCS for the TMS570LS12x?

  4. Troubleshooting:

    • What common issues might I encounter when setting up this environment, and how can I resolve them?

Any insights or resources would be greatly appreciated. Thank you!

Best regards,
Akmal Khan

  • 0
    TI__Guru 62905 points

    Hi Akmal Khan,

    My suggestion would be start from below FAQ:

    (+) [FAQ] TMS570LC4357: Examples and Demos available for Hercules Controllers (E.g. TMS570x, RM57x and RM46x etc) - Arm-based microcontrollers forum - Arm-based microcontrollers - TI E2E support forums

    In above thread i linked getting started examples:

    In above FAQ, that LED video tutorial have all the basic steps of installation tools required and they also mentioned the configuration procedure.

    --
    Thanks & regards,
    Jagadish.

  • 0 in reply to jagadish gundavarapu
    Prodigy 30 points

    Hi Jagadish,

    Thank you for your suggestion.I successfully worked with TI + HalCoGen.

    I am now seeking support for using GCC in CCS with HalCoGen for the TMS570LS1227.

    Here is what I have tried:

    1. I followed the suggestion from the TI E2E forum:

      -mcpu=cortex-r4 -march=armv7-r -mfloat-abi=hard -mfpu=vfpv3-d16 -I"C:/ti/ccsv6/tools/compiler/gcc-arm-none-eabi-4_8-2014q3/arm-none-eabi/include" -g -gdwarf-3 -c -mlittle-endian -r

      Source

    2. I also tried using the toolchain suggested by Linaro for ARM big endian systems:

      https://releases.linaro.org/components/toolchain/binaries/

      Source

    However, I am encountering warnings after applying the first suggestion. Here are the details:

    Building target: "Project1_GNU_ThreadX.out" Invoking: GNU Linker "C:/ti/ccs1230/ccs/tools/compiler/gcc-arm-none-eabi-9-2019-q4-major/bin/arm-none-eabi-gcc-9.2.1.exe" -Og -g -gdwarf-3 -gstrict-dwarf -Wall -specs="nosys.specs" -mcpu=cortex-r4 -march=armv7-r -mfloat-abi=hard -mfpu=vfpv3-d16 -I"C:\ti\ccs1230\ccs\tools\compiler\gcc-arm-none-eabi-9-2019-q4-major\arm-none-eabi\include" -g -gdwarf-3 -c -mlittle-endian -r -Wl,-Map,"Project1_GNU_ThreadX.map" -o"Project1_GNU_ThreadX.out" "./source/dabort.o" "./source/errata_SSWF021_45.o" "./source/esm.o" "./source/gio.o" "./source/notification.o" "./source/pinmux.o" "./source/rti.o" "./source/sys_core.o" "./source/sys_dma.o" "./source/sys_intvecs.o" "./source/sys_main.o" "./source/sys_mpu.o" "./source/sys_pcr.o" "./source/sys_phantom.o" "./source/sys_pmm.o" "./source/sys_pmu.o" "./source/sys_selftest.o" "./source/sys_startup.o" "./source/sys_vim.o" "./source/system.o" -Wl,-T"../source/sys_link.ld" -Wl,--start-group -lc -Wl,--end-group arm-none-eabi-gcc-9.2.1.exe: warning: ./source/dabort.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/errata_SSWF021_45.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/esm.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/gio.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/notification.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/pinmux.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/rti.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_core.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_dma.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_intvecs.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_main.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_mpu.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_pcr.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_phantom.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_pmm.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_pmu.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_selftest.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_startup.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/sys_vim.o: linker input file unused because linking not done arm-none-eabi-gcc-9.2.1.exe: warning: ./source/system.o: linker input file unused because linking not done Finished building target: "Project1_GNU_ThreadX.out" **** Build Finished ****

    Could you please provide guidance on resolving these warnings and successfully building the project with GCC in CCS for the TMS570LS1227?

    Thanks & Regards,
    Akmal Khan

  • 0 in reply to Akmal Khan
    TI__Guru 62905 points

    Hi Akmal Khan,

    I never come through these warnings before.

    First i would like to know, ignore the warning whether your intended functionality was happening successfully. Did you execute the project and verified the functionality.

    --
    Thanks & regards,
    Jagadish.