Post Go back to editing

Inquiry on UART-Based Bootloader Development for ADuC7061

Thread Summary

The user inquired about loading firmware over UART for the ADuC7061. The built-in ROM loader requires the BM pin to be pulled low during reset or power-up to enter serial download mode. For products where BM and RESET pins are not accessible, implementing a custom bootloader in flash is recommended, using the UART protocol from AN-724 or a custom protocol. The user successfully developed a custom IAP with a Python GUI for firmware updates.
AI Generated Content
Category: Software
Product Number: ADUC7061
Software Version: N/A

Hi There,

I have a question regarding bootloader development for the ADuC7061.

I’d like to understand whether it is possible to load firmware over UART and, if so, how this can be done. I would really appreciate any guidance, documentation, or example regarding bootloader development for this MCU.

Best,
Farshid

Parents
  • Hi Karl,

    Thanks for pointing me to AN-724, it was very helpful.

    I’d like to clarify my understanding and make sure I’m interpreting the capabilities correctly for a real product use case.

    From AN-724, it seems that the ADuC7061’s built-in serial download (ROM loader) can load firmware over UART, but it requires the device to enter serial download mode by pulling the BM pin low during reset or power-up.

    My questions:

    1. Is it correct that the built-in UART downloader cannot be invoked purely by software (e.g., via a command from a running application), and always requires BM + reset?

    2. In a typical product where BM and RESET pins are not accessible to the end user, is the recommended approach to:
     - implement a custom bootloader in flash, and
     - use the UART protocol defined in AN-724 (or a custom protocol) to update firmware?

    3. Is there any documented or recommended method to:
     - trigger entry into the ROM loader from firmware (e.g., via watchdog/reset tricks or special registers), or
     - is hardware control of BM during reset strictly required?

    4. For production systems that support field firmware updates over UART (via USB-to-UART converters), what is the recommended architecture from ADI’s perspective?
     - Use the ROM loader with external hardware control of BM/RESET?
     - Or implement a custom bootloader?

    5. Are there any example projects or reference designs (even for other ADuC70xx devices) that demonstrate a customer-facing firmware update mechanism?

    I just want to make sure I choose the right approach early; especially since our end users will not have physical access to BM/RESET pins.

    Thanks again for your guidance.

Reply
  • Hi Karl,

    Thanks for pointing me to AN-724, it was very helpful.

    I’d like to clarify my understanding and make sure I’m interpreting the capabilities correctly for a real product use case.

    From AN-724, it seems that the ADuC7061’s built-in serial download (ROM loader) can load firmware over UART, but it requires the device to enter serial download mode by pulling the BM pin low during reset or power-up.

    My questions:

    1. Is it correct that the built-in UART downloader cannot be invoked purely by software (e.g., via a command from a running application), and always requires BM + reset?

    2. In a typical product where BM and RESET pins are not accessible to the end user, is the recommended approach to:
     - implement a custom bootloader in flash, and
     - use the UART protocol defined in AN-724 (or a custom protocol) to update firmware?

    3. Is there any documented or recommended method to:
     - trigger entry into the ROM loader from firmware (e.g., via watchdog/reset tricks or special registers), or
     - is hardware control of BM during reset strictly required?

    4. For production systems that support field firmware updates over UART (via USB-to-UART converters), what is the recommended architecture from ADI’s perspective?
     - Use the ROM loader with external hardware control of BM/RESET?
     - Or implement a custom bootloader?

    5. Are there any example projects or reference designs (even for other ADuC70xx devices) that demonstrate a customer-facing firmware update mechanism?

    I just want to make sure I choose the right approach early; especially since our end users will not have physical access to BM/RESET pins.

    Thanks again for your guidance.

Children