Hi Aditi, > On Nov 5, 2015, at 1:11 PM, aditi hilbert <[email protected]> wrote: > > I tested the download/debug function on Olimex board and it works good! > > As for the example of using the identity as an argument > (e.g. newt target download boot bootloader), the image “boot.elf.bin” > will be written in some specific area of flash but that is yet to be defined, > right? > (Currently I see only one flash offset in the script.)
Thanks for testing. So the newt download actually picks up the identities that the target project has specified, and passes those on. It does not inspect additional command line arguments when invoked. Like project/boot/boot.yml has set “identities” to be bootloader, and this is something that the download script checks for, and adjusts the download offset accordingly. The flash offset in the download script has to match what’s specified in linker script. It’s really dependent on the BSP what the available option for offsets are, and I imagine that is where we'd keep the info about what goes where in the flash. project identities can be used in specifying where different types of build targets should go. I.e. for Olimex the bootloader goes to beginning of internal flash, and the other project targets we have are placed after that. Sorry for the verbosity, M
