Flashloader, Flash visible twice

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

  • Flashloader, Flash visible twice

    In the Fujitsu/Spansion/Cypress FCR4 family chips the internal flash is visible twice:
    once on the AXI "BUS" interface (0x01000000..0x017FFFFF), and once on the TCM interface (0x00800000..0x00FFFFFF).

    We are linking the application to use the TCM addresses.
    When using J-Link commander and JFlash.exe, we give a binary and tell to put them on the AXI addresses - works nice.

    However when using IAR EW we would have to change and use the IAR flashloader or, write our own flashloader that remaps and uses the flashloader in JLinkARM.dll.

    Is there any option in J-Link to re-route addresses for flash download?
    Images
    • fcr4_fcflash.png

      19.22 kB, 704×566, viewed 649 times
  • Can you please specify what target device you are using?
    However when using IAR EW we would have to change and use the IAR flashloader or, write our own flashloader that remaps and uses the flashloader in JLinkARM.dll.
    Wouldn't be changing the linker file an option for you? This would still allow you to use the SEGGER flash loader. Anyhow, we will check if we can add the mirror address in the J-Link DLL so that the mapping is done automatically by it. Basically this is no problem but according to the user manual, the AXI_FLASH_MEMORY_SMALL/LARGE sectors have a different offset in between as the TCM_FLASH_MEMORY_SMALL/LARGE sectors.

    - Erik
    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.
  • Hello Erik,

    SEGGER - Erik wrote:

    Can you please specify what target device you are using?

    We are using the "Atlas-L" MB9DF125 and "Titan" MB9EF226 currently.

    Wouldn't be changing the linker file an option for you? This would still allow you to use the SEGGER flash loader.

    We changed from AXI to to tighly coupled memory interface in the hope running with with zero waits, but of course we can change that
    for a debug configuration.

    Anyhow, we will check if we can add the mirror address in the J-Link DLL so that the mapping is done automatically by it.

    This would be very nice!

    Basically this is no problem but according to the user manual, the AXI_FLASH_MEMORY_SMALL/LARGE sectors have a different offset in between as the TCM_FLASH_MEMORY_SMALL/LARGE sectors.

    The offset is 8 MiB:
    0x0080_0000..0x00FF_FFFF TCM
    0x0100_0000..0x017F_FFFF AXI
    the layout of the sectors on read is exactly the same on both interfaces - we flash the TCM linked application (big sectors) and bootloader (small sectors) with J-Link to the AXI addresses.
    However it is just not possible to flash over the TCM interface.

    So for the FCR4 family it would just a base address remap.

    many thanks for investigating this.
  • Hi,

    There is already a possibility to do something like this which can be easily extended to achieve what you are looking for.
    Let me check if we can squeeze something in short term.


    Best regards
    Alex
    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.