• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 29 subscribers
  • Views 675 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.

EK-LM4F232 Startup File for Summon ARM Toolchain

David Zemon
Prodigy 160 points


I finally got the summon arm toolchain working under Linux with my EK-LM4F120 (with these files: https://github.com/scompo/stellaris-launchpad-template-gcc) and am now ready to set it up for the 232. I tried copying the startup C source file and the linker script, but at least one of them is not working. Does anyone have a startup file and linker script that works for the LM4F232 and summon toolchain?

Thanks,

David

  • 0
    Guru 117855 points

    Have zero knowledge/experience w/toolchain you list.  That said - would not it prove useful to carefully review (and contrast) the treatment of Startup source and linker script - from the established IDE vendors such as Keil or IAR?  Any differences/accommodations between the relevant files for LX4F120 and LX4F232 may be noted - thus providing a "model" for your incorporation w/in your toolchain. 

    Most successful "pioneers" - employ some of the "proven," overlapped methods of others...

  • 0
    Guru 11940 points

    This toolchain is basically gcc, so you can try to "gut" a commercial gcc-based toolchain, say, it's free version. Startup code and linker script are usually closely intertwined. Toolchains like Keil disqualify, as they do not use the same assembler syntax.

    The STM32 version of s.a.t. did this with Atollic, CodeSourcery might be another candidate.

    Not sure how you manage debug support. There are some problem classes that just can't be covered with printf-style debugging.

  • 0 in reply to f. m.
    Guru 117855 points

    f. m. said:
    Toolchains like Keil disqualify, as they do not use the same assembler syntax.

    Perhaps - but one suspects that info of value can still be discerned.   I stand by the claim that a, "baseline" of key data can be thus acquired...

  • 0 in reply to cb1_mobile
    Guru 11940 points

    I stand by the claim that a, "baseline" of key data can be thus acquired...

    If one is willing to rewrite the Keil startup code in gcc syntax, then, of course. Or one may try the Keil-assemble -> objdump disassemble route.

    As stated the toolchain version for STM32 "robbed" everything from Atollic, including the gdb server...

  • 0 in reply to f. m.
    Guru 35565 points

    I don't think that looking at Keil or IAR would be of any help at all with the GCC Linker Script or makefile?

    But second f.m.'s motion that there are plenty of established GCC toolsets for Cortex-M3 - so that would be the place to start.

     

  • 0 in reply to Andy Neil
    Prodigy 160 points

    I was able to copy the linker script and startup code from the 120 - line for line.

    As for debugging, I'm using OpenOCD and gdb.