1. at last, rvds4.0 can completely replace rvds2.2. Previously, because rvds4.0 could not display C code synchronously during debugging, debugging was not very convenient. I used axd for debugging and checked it online last night, I found that the-G parameter needs to be added in GCC to add synchronization debugging information. I tried to interview rvds4.0. If that is the case, I 'd like to share it with you now, finally, we can completely discard the old rvds2.2.
2. We recommend that you disable or tune the optimization to the lowest level when using rvds4.0. Otherwise, there may be issues of inintention.
3. in fact, axd blocking is not a problem of axd or rvds2.2. This is actually a problem of jlink. Specifically, it is a problem of jlinkgdbserver. It will also be stuck in eclipse and rvds4.0, end the jlinkgdbserver.
4. I hope you can try rvds4.0 in various aspects. After all, rvds4.0 is eclipse + GCC, which is similar to eclipse and GCC, in addition, I think writing a Linux driver is faster to implement functions in bare metal mode. I don't know if it is correct because I 've been exploring it all the time.