[SOLVED] BTL_ImageCreator can combine multiple binaries?

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] BTL_ImageCreator can combine multiple binaries?

    Hi,

    In our custom hardware, we are using EMLOAD for flashing the FW Images. Other than EMLOAD, we are having 3 more Binaries, in which 2 binaries reside in internal Flash memory and another Binary reside in external NAND Flash.

    We are checking how we can combine all these 3 Binaries along with the EMLOAD Image, so that we can flash all these Images in production setup, using KEIL in a single step.

    Our queries are:

    1. Does BTL_ImageCreator can combine 4 Images including EMLOAD?
    2. Is the CRC residing in FWInfoArea is calculated considering the non-filled areas in Flash excluding EMLOAD area and FWInfoArea? As we are having the external NAND Flash memory, the CRC calculation includes this memory too?


    Regards,
    Pratheesh

  • Hi Pratheesh,

    Sorry for the delay but I think you already received my vacation note from one of my colleagues.

    Pratheesh P wrote:

    1. Does BTL_ImageCreator can combine 4 Images including EMLOAD?

    The purpose of the BTL Image Creator is to prepare ONE firmware image for direct flashing instead of updating via emLoad. Optional it can be combined with emLoad itself for direct flashing. It is not meant to combine multiple firmware images.

    Of course you can first combine multiple firmware images or parts of one large image that has different addresses into one big firmware file using other tools like J-Flash (merge command). These commands are avaulable on command line as well and do not even need a J-Flash license.

    Pratheesh P wrote:

    2. Is the CRC residing in FWInfoArea is calculated considering the non-filled areas in Flash excluding EMLOAD area and FWInfoArea? As we are having the external NAND Flash memory, the CRC calculation includes this memory too?

    The CRC is built over all firmware areas that emLoad is able to update. This means it also includes your NAND, or at least the portions of the NAND that you have declared to be part of any emLoad firmware area. Empty bytes here are expected to be 0xFF .

    Best regards,
    Oliver
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.