Updated: v0256 beta soon + DAPLink Slack channels

[mathias-arm]

Updates

alpha9 + Draft PR for merging develop to main

alpha9 was built and tested, the results, were really positive. A draft PR for merging develop to main has now been created: #880.

Slack update

The #daplink-updates channel has been created to show notifications.

Deprecating boards and targets

A PR (#876) has been created for boards and target that will be removed before the 0256 release.

Preparing 0256

The tests with the different compilers have seen significantly more green (successful tests). An alpha9 has been delayed to see if #853 can be resolved (that would solve the vertical line for kl26z ). Changes have merged that should fix most armclang issues and max32625 UART. So the next series of tests could in theory the whole page turn green. Even if that turned out to happen, it would not be enough to make a release. After alpha9, the intent is to have a few beta builds to prepare for a release. At this point develop will be merged into main. The priority will be to get fixes into main. Other PRs should be targeting develop.

The manual tests cover the base functionality of a very small subset of the binaries.

• After a few fixes, the automated tests should work. One caveat is that in order for them to work they need binaries for the target. The daplink-validation repository hosts the source for those binaries refreshed to build with MbedOS 5.15. This essentially means we can only test target MCUs that are supported by MbedOS 5.15.

• As mentioned in The road to DAPLink 0256 (and beyond) #819, there is a need to start deprecating boards. We will try to figure out a process (ideas are welcome) that will make the best decisions guided by your feedback. For boards that we still think should be supported but could not be tested, we could leave v0254 as the default but offer newer versions clearly marked as untested (until we get reports either way).

Slack channel

pyOCD is a great complement to DAPLink, if you don't know it, you should try it. The project recently updated its website and it set up a Slack workspace in which it graciously invited us. Join us in the #daplink channel of that workspace and we will see if it works out.