Hi, I’ve wanted to have this since beginning, so…
I added BSP specific download/debug functions. The way this works now is that in the BSP egg you can specify a command to invoke for download and/or debug. The way I was going to use this is that the thing that gets invoked is most likely a shell script. As arguments that one will get a) the path to binary basename and b) any project identities that were specified. So if I’m downloading, say blinky for olimex I say newt target download blink_olimex This makes newt invoke the shell script responsible for download with arguments ‘download.sh patch_to_binary’. And script then invokes openocd to do the download. And the reason I pass project.identities as arg is so that this download script can decide where in the flash to download to. Boot loader project sets identity “bootloader”. ‘newt target debug blink_olimex’ works similarly, except it starts openocd/gdb combo and gdb takes over the terminal. I did not add NRF BSP support, as I don’t have that board with me. Try this out, check out how download/debug scripts look like and give feedback. Thanks, M
