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.

TM4C123GH6PM: in circuit programming/release code?

Part Number: TM4C123GH6PM
Other Parts Discussed in Thread: SEGGER

Hello, 

    I have a few questions regarding the programmimg of the device in circuit. I was hoping someone could point me to the right docs. 

1. how to create the 'release version' of the code developed on a development board

2. how to actually program it into the device

      - is it as straight forward as bringing the 4 JTAG pins out on the target board using a connector or bed of nails,

      - then use a programmer like segger or lm flash that can write the release code (*.out ??)  into the device using the JTAG interface? 

      - does the board need to powered or is the JTAG enough. 

Thank You 

P

  • Hello Patrick,

    1. how to create the 'release version' of the code developed on a development board

    Not really sure I can offer much guidance here. Development vs Release code bases tend to be specific to customer needs - like maybe a development project as debug outputs that are omitted in the release version. Usually that is done with #define's and the like where the release and development versions have different defines.

      - does the board need to powered or is the JTAG enough. 

    Yes the board needs to be powered so the flash cells are powered and active to received program code.

      - is it as straight forward as bringing the 4 JTAG pins out on the target board using a connector or bed of nails,

    It can be! You can review our JTAG User's Guide for programming options in terms of connections / pinouts: https://www.ti.com/lit/pdf/spma075

    *.out or *.bin files are commonly used and the right programming software will depend on your debug probe of choice.

    Best Regards,

    Ralph Jacobi

  • hello ralph,

        thanks for the response. When I compile code as the release version I get a raft of errors. 

    just work through each? no other special considerations needed to make the device run on its own? 

    thanks

    p

  • Hello Patrick,

    There are no special considerations to make - but if you have a lot of error that would suggest you like have some sort of directive(s) defined in Debug compilation which are not defined in Release compilation which could either indicate you missed adding a directive which belongs in the Release compilation or there needs to be more care to limit lines of code intended only for the Debug compilation.

    If you want to post an image of the errors I may be able to give you some high level guidance on what is going on.

    Best Regards,

    Ralph Jacobi