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.

TM4C1292NCPDT: TivaWare BootLoader with external Ethernet MII PHY

Part Number: TM4C1292NCPDT
Other Parts Discussed in Thread: TM4C1294NCPDT,

Hi,

we have been using TM4C1294NCPDT (with built-in Ethernet PHY) for many projects and always have used built-in (ROM) TivaWare bootloader to flash initial firmware trough Ethernet (we have our own PC software that serves firmware to TM4C once it sees it's BOOTP request).
Note that we need this only for initial firmware upload (future updates are done with our own Ethernet bootloader).

We are now working on a project that required external Ethernet PHY thus we selected TM4C1292NCPDT (basically same MCU with only difference that is has no internal PHY but rather has MII interface for external PHY).

We have confirmed that our board is functional as Ethernet communication works with our firmware loaded. Note that we had to make few modifications in code related to moving from internal PHY to external: main difference being the need to do GPIO Pin Mux for MII interface, but external PHY itself is functional without any additional steps.

Now issue lies in fact that when we power-on fresh board (with blank TM4C), we would expect it to go into TivaWare bootloader and send a BOOTP request over Ethernet - unfortunately we are not seeing this.

We can't find any additional documentation about TivaWare ROM bootloader besides this and it does't go into details:


Probably someone has experience with TM4C TivaWare bootloader and external PHY?

  • Hi Ainars,

    With the blank flash TM4C it means that the MCU will need to boot from the ROM-based bootloader. The ROM-base bootloader does not configure and interface (via MII) to the external PHY. I think this is the problem.
  • Charles,

    thank you for fast response.

    Unfortunately that is exactly what we suspected.

    I must say that this is due to unclear documentation about ROM bootloader, especially as TM4C1292NCPDT Data Sheet mentions Ethernet Boot Loader:

    For this project we will have to modify board to accept different method for initial programming.

    As we plan to continue using TM4C family and probably use other modifications, is there any documentation that would explain in detail behavior of ROM bootloader for different TM4C family devices?

    Is it safe to assume that ROM-based bootloader USB DFU mode will be available across all TM4C129x family?

  • Hi Ainars ,

      

    Ainars Pastars said:
    As we plan to continue using TM4C family and probably use other modifications, is there any documentation that would explain in detail behavior of ROM bootloader for different TM4C family devices?

     The TivaWare Bootloader user's guide is the best document we have as far as bootloading is concerned. We also have the ROM user's guide in case you in want to reference the ROM based driverlib.

    Ainars Pastars said:
    Is it safe to assume that ROM-based bootloader USB DFU mode will be available across all TM4C129x family?

    Yes, ROM-based bootloader USB DFU is available across all TM4C129x family.

  • Thank you for your help Charles!