heh piling up those commits 😆

heh piling up those commits 😆

that's (really) just so we can identify and revert if a certain board or tool fails 😬

Would be good to verify all the values are still the same with info-debug-variable-RESET and info-debug-variable-RESET_FLAGS for the different configurations and boards.

If you want to prevent the pattern to be re-appearing in the future, you can add a detection for it in https://github.com/cladmi/RIOT/blob/master/dist/tools/buildsystem_sanity_check/check.sh

I checked the output right now.

#! /bin/sh
BOARDS=$(find boards/* -maxdepth 0 -type d \! -name "common" -exec basename {} \;)

list_all_variables() {
    for BOARD in ${BOARDS}
    do
        export BOARD
        echo ${BOARD}
        make --no-print-directory -C examples/hello-world/ info-debug-variable-RESET info-debug-variable-RESET_FLAGS
    done
}

list_all_variables | tee $1_output_simple
PROGRAMMER=jlink list_all_variables | tee $1_output_jlink

And the output of RESET and RESET_FLAGS is the same also with PROGRAMMER=jlink.

The uniflash 3 looks good even if not re-tested locally.

It is also a task I would like to have with FLASHER and FFLAGS in general, but the review will be a bit trickier I think.

thanks @cladmi for review and merge!!