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.
i want to update the firmware using ethernet i found this
but i have some question why we need boot_demo_emac and why the boot_emac_flash is not enough and what happen when i load the boot_emac_flash and boot_demo_emac and i want to load another application what happen to boot_demo_emac would it still exist or the bootloader write the new code on it
Hi,
I just answered your another post at https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1357975/tm4c1294ncpdt-ethernet-firmware-update
but i have some question why we need boot_demo_emac and why the boot_emac_flash is not enough and what happen when i load the boot_emac_flash and boot_demo_emac and i want to load another application what happen to boot_demo_emac would it still exist or the bootloader write the new code on it
boot_emac_flash is the bootloader. The bootloader is a tiny piece of program that is first loaded to the flash via JTAG interface. It has the code to setup Ethernet module and interact with the BootP and TFTP server to download your application firmware image. boot_demo_emac_flash is an example application firmware. You can create your own application but start with the example first. Once you are familiar with how everything works, you can adapt to your own application. In the current bootloader setup, you will overwrite the existing application firmware if you choose to update it again.
So i need the part of waiting for software update in demo_emac_flash and dont need the canavas part ? am i right ?
I have no idea what canavas part you are referring to? Please elaborate. I will suggest you run the example as is at least once and many things will clear up for you.