-
Maybe just use adafruit-nrfutil from the Makefile, and leave how to install it up to the person building?
Well, the point of
scripts/provision.sh BOARDNAMEis to get everything prepared, so next step ismakethat works. It installs nrfutil for other SDKs too. So in that sense it would do only half of the job for SDK11 and won't allow e.g. automated building from github pipelines. So adding symmetrical pip install adafruit-nrfutil would make better sense, otherwise adding automated SDK11 download is not that much useful.Well, except that it would break your existin nrfutil install when you are building locally. So my thinking/question was if both versions of the nrfutil could be installed in a better way.
Maybe by using venv https://docs.python.org/3/library/venv.html into some espruino folder? like arm gcc compiler or esp32 sdk or other parts downloaded by provision script.
You are reading a single comment by @fanoush and its replies.
Click here to read the full conversation.
fanoush
That would be great! Ideally we'd do it like we do for SDK15 with Nordic SDK files and a patchset, but SDK11 is niche enough I don't think that really matters.
Maybe just use
adafruit-nrfutilfrom the Makefile, and leave how to install it up to the person building?Probably having only DFU zips for most people isn't a big deal since that's why you'd use SDK11 surely? If you could write via SWD you'd just use a newer SDK?