This isn't really a problem, just wanted to bring it up in case it is helpful. I'm using the nRF Connect for VS Code Extension with nRF Connect SDK v3.0.2. I have a nRF 52 DK connected to a custom board using the 10-pin debug out port on the DK connected to the debug in on the custom board. When I try to flash the board from the ACTIONS tab in nRF Connect extension it results in an error due to nrfjprog not being installed. I think this is expected though since nrfjprog is being replaced by nrfutil device? I can successfully flash the custom board using the nRF Terminal and the nrfutil device program command. It seems like the Flash action is just outdated and needs to be updated to use nrfutil instead of nrfjprog, does that seem reasonable?
Like I said, this isn't really a problem. I can still flash the board just fine, though it would be more convenient if I could use the Flash action instead of the terminal.
