Not able to Drag-and-Drop with BIN Files

Hello,

I'm using the LPC55S69 (MCU-Link Hardware) as HIC which I've attempted to port to the MIMXRT1010-EVB as Target.

With the hardware and software and I can debug the target in IDE (MCUXpresso) and the drag-and-drop functionality works with HEX files.

When I try and program using BIN files I receive "FAIL.TXT : Transfer timeout".

My first thought is that it doesn't recognise the BIN files.

I'm not sure what I need to change in the code to resolve the issue.

Thought / Issues
1. When I generate c_blob.c for flash_blob.c from "MIMXRT1011_QuadSPI_4KB_SEC.FLM" it generates the data below for "Verify":

When compiling, "0x120000003, // Verify" isn't a valid value. Should this be deleted or set to "0x00000000, // Verify"?

2. When I generate c_blob.c for flash_blob.c from "MIMXRT1011_QuadSPI_4KB_SEC.FLM" it generates the data below for "sectors_info":

When compiling there are errors as "sector_info_t sectors_info" is expected. Should it be changed to as below:

3. When populating "Target.c" I can find the information supplied with MIMXRT1011_QuadSPI_4KB_SEC.FLM as below:

Have I populated "Target.c" correctly or is this issue here:

(I ask as there's 3x RAM-Start addresses.)

Thanks for any help, I really appreciate it.
[Data.zip](https://github.com/ARMmbed/DAPLink/files/8995210/Data.zip)

Start with the attached Data.zip and compare the generated c_blob.c, flash_blob.c, and Target.c against the MIMXRT1011_QuadSPI_4KB_SEC.FLM details shown in the report. Reproduce the BIN drag-and-drop transfer timeout while confirming that HEX programming still works, then identify whether the generated Verify, sectors_info, or RAM-start values cause the failure. Done means BIN programming completes without producing “Transfer timeout” in FAIL.TXT.

Written by the indexing model from the issue text.