I am trying to program an F4 with an external flash chip in mapped memory mode using the STM32_Programmer_CLI. I use the cli command
STM32_Programmer_CLI.exe --connect port=SWD mode=UR reset=hwRst -halt --erase all --download <path_to_hex> -el <path>/N25Q128A_STM32469I-DISCO.stldr
Which completes erase on internal flash and external flash, but then sits at parsing file. The file I am trying to write is 12.9MB with some flash existing in internal flash space and some flash existing in the hex position that correlates to the mapped memory modes position.
If I try to write all of just the external hex (11.8MB), I still experience the same issue. If I crop the hex file into smaller parts, it will program the correct locations in external flash.
I can successfully use the ST-LINK Utility with the same external loader to program the same hex file. I require the CLI however, because I require programming this through a script.
Is there a known limitation to the hex size the CLI can accept? How do I solve this issue?
EDIT:
I used the ST-LINK_CLI.exe with the same hex, the same external loader, and similar command line arguments and the programming worked as expected.
