• State Answer Suggested
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 1419 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.

TMS570LS1224 without HERCULIES tool

Arvind Upadhyay
Expert 1405 points
Other Parts Discussed in Thread: TMS570LS1224, HALCOGEN

Hi friends,

Can I use TMS570LS1224 launchpad without HERCULIES tool. If yes How??

I tried but getting wornning some init() and startup is not there... 

Regards,

Arvind.

  • 0
    Guru 15740 points

    Hercules doesn't do magic.

    It creates c and assembler source files, and a linker command file. All in readable (and compilable) format.

    When you are not using the tool, you will have to do the initialisation (and write driver code) yourself.

  • 0 in reply to Jan Cumps
    Expert 1405 points
    Hi Jan,
    when I am creating New CCS project of Hello world from Empty project, I am getting warring likes:
    -> Description Resource Path Location Type
    #10247-D creating output section ".bss" without a SECTIONS specification Hello Projext C/C++ Problem
    -> Description Resource Path Location Type
    #10247-D creating output section ".cinit" without a SECTIONS specification Hello Projext C/C++ Problem
    ->Description Resource Path Location Type
    #10247-D creating output section ".const" without a SECTIONS specification Hello Projext C/C++ Problem
    ->Description Resource Path Location Type
    #10247-D creating output section ".data" without a SECTIONS specification Hello Projext C/C++ Problem
    ->Description Resource Path Location Type
    #10247-D creating output section ".sysmem" without a SECTIONS specification Hello Projext C/C++ Problem
    ->Description Resource Path Location Type
    #10247-D creating output section ".text" without a SECTIONS specification Hello Projext C/C++ Problem

    Can you help me how to solve out this issues. I working on a project.

    Regards,
    Arvind
  • 0 in reply to Arvind Upadhyay
    Guru 15740 points
    Arvind, all of these things are set in the linker command file by HALCoGen (source/xxx.cmd).
    I will not be able to help you. I always use HALCoGen.

    If you want to do without HALCoGen, you'll have to study both the tool chain (assembler, compiler, linker, error correction code generator) and the controller TRM (including errata) very deeply.
    Or you can generate a project with HALCoGen, and copy from there (check the license please to see what you have to includ in your project when you copy from HALCoGen generated code).
  • 0 in reply to Jan Cumps
    Expert 1405 points
    Thank you Jan for reply. I understand.
  • 0 in reply to Arvind Upadhyay
    Guru 15740 points

    (It's not impossible though, so don't get demotivated by my reply :) . There's someone who is working on ADA development for the Hercules. He has also started from nothing
    source: github.com/.../gnat2015
    )

  • 0 in reply to Jan Cumps
    Expert 1405 points

    No problem Jan, I will take this as positively and spend sometime to expose this things.

  • 0 in reply to Arvind Upadhyay
    Guru 92251 points

    Arvind Upadhyay said:
    Can you help me how to solve out this issues.

    I think the issue is that the default linker command files in CCS for Hercules devices are missing the SECTION definitions for the sections which are expected by the compiler.

    I did query this in the past, and the response was that HALCoGen was expected to be used to create projects for Hercules devices - see Sections missing TMS570LS202x6SFlashLnk.cmd in CCS 5.1

    You need to remove the "creating output section "<section_name>" without a SECTIONS specification" warnings by adding sections to the linker command file, as otherwise the linker can assign sections to arbitrary memory regions which causes the program to fail at run time.

    See Linker Command File Primer for some background information.