• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 287 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.

EK-TM4C129EXL: ROM Bootloader via Ethernet

Hairy Lee
Prodigy 200 points
Part Number: EK-TM4C129EXL
Other Parts Discussed in Thread: EK-TM4C1294XL

SW-TM4C-BOOTLDR-UG-2.2.0.295 states:

  1. When the user application is running, it can still invoke the ROM boot loader to force an update of the firmware through a chosen interface.

  2. Before calling the ROM boot loader API, the application must configure and enable the chosen interface and disable all processor interrupts.

I have the enet_tcpecho_server examle (provided in TivaWare_C_Series-2.2.0.295) running which has been modified to call ROM_UpdateEMAC(SYSCLK) when a message is receieved. I have called MAP_SysTickIntDisable, MAP_EMACIntDisable, and IntMasterDisable prior to calling the bootloader, but unable to download a new application via LM Flash Programmer once the bootloader has been entered.

Can you advise as to what I'm missing please.

Thanks

HL

  • 0
    TI__Guru**** 184346 points

    Hi Hairy,

      There is a example in C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c1294xl\boot_demo_emac_rom that calls the ROM_UpdateEMAC. Can you please refer to this example. I think what happens is that the ROM Ethernet bootloader is based on UDP protocol and your application is setup for TCP protocol. The lwIP does not allow both TCP and UDP at the same time as far as I know. 

  • 0 in reply to Charles Tsai
    Prodigy 200 points

    Sorry, I dont know how I missed that example.