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

Bootloader for Tiva Chip.

Evgeny7
Prodigy 220 points
Other Parts Discussed in Thread: TM4C123GH6PM

I need a bootloader for Tiva chip (TM4C123GH6PM).

I’ve read TivaWare Boot Loader manual, however the practical implementation has left obscured in the document.

After I compiled boot_serial demo should I download it with JTAG bootloader or I can do it with LM Flash Programmer with UART communication?

Should I explicitly set a bootloader address before downloading it into the chip?

Is there step by step manual for dummies explaining all details?

  • 0
    Guru 86765 points

    Hi,

        Do a search in the forum for the procedure of using boot_serial and boot_demo1.

    -kel

  • 0 in reply to Markel Robregado
    Prodigy 220 points

    Thank you for the answer.

  • 0
    Guru 117855 points

    Evgeny7 said:

    Should I explicitly set a bootloader address before downloading it into the chip?

    Find your post thoughtful - well constructed.

    In answer (beyond search, pray) might you need to specify the desired behavior of your bootloader?  Is it always to be present/functional/lurking - awaiting its "hoped for" launch command?  (and that is one method - used by many)

    Might you - instead - seek to devise one which may not be so aggressive - would instead not operate by default - but via some pre-arranged command handshake/exchange?  Perhaps worth your further thought, consideration.

    If you don't yet have access to "normal/customary" JTAG/SWD probe - urge you in that direction.  Such tools may better enable you to place code "exactly" where you seek - and may not undergo repeated "updates" - some which cause reasonably major changes in past behavior.

    There usually are 2 bootloader demo programs provided here - I'd read/re-read each several times.  Like you - we find that the vendor's detail does not quite rise to, "Airline Pilot, Pre-flight check list" caliber.  It may well be that those providing the guidelines are, "bit too close" to the topic - underestimate what they know (believe intuitive) - especially when compared to you/I. 

    Suggest that you employ your bootloader w/the smallest, simplest test program that you can devise.  (i.e. avoid interrupts, pointers, other items of complexity)  Via JTAG you should be able to record & observe the memory locations of both bootloader and your application program.  When that's stable/secure - you may wish to pass a 2nd (different) simple, application program - and confirm that the earlier app program has been replaced by the newer. 

    Believe that thorough read/review of all vendor, bootloader documentation, code examples - followed then by simple, basic program testing (as above) will best build your skills & confidence - in this aspect of MCU operation.  Bon chance, mon ami...