Replies: 14 comments 7 replies
-
|
\inav\docs\development\Hardware Debugging.md |
Beta Was this translation helpful? Give feedback.
-
|
is it this document? |
Beta Was this translation helpful? Give feedback.
-
|
the debugger must use st-link? can i use j-link as the debugger to debug the FC hardware? |
Beta Was this translation helpful? Give feedback.
-
|
You can also use simple printf debugging with the USB cable. https://github.com/iNavFlight/inav/blob/master/docs/development/serial_printf_debugging.md |
Beta Was this translation helpful? Give feedback.
-
|
the method is too inefficient！！！ |
Beta Was this translation helpful? Give feedback.
-
You are welcome to use whatever methods you prefer for any particular task. printk() and pr_debug() are popular with kernel developers for a number of reasons. Stepping the processor can create new issues in hardware interfaces and real-time systems because the baro, the accelerometer, the gyro, and everything else aren't paused waiting for you. It will also HIDE timing issues. You can spend all day trying to find a bug with ST-Link that could have found quickly using the logging so the timing doesn't get messed up as much. You can also send a hex with debug logging to someone else, who may have different hardware or be having a problem you can't reliably reproduce. Or someone who may be able to give a different perspective on the problem. Someone like Jetrell. Again, you're welcome to do it the way prefer, though! Linus said it well:
|
Beta Was this translation helpful? Give feedback.
-
|
Whether to use it or not is not the key, but the most important thing is to master this debugging method. Being able to step debug in the early stages is very useful for familiarizing oneself with the code. |
Beta Was this translation helpful? Give feedback.
-
|
the vscode software should install where? at windows? or at wsl in windows? |
Beta Was this translation helpful? Give feedback.
-
|
It's only been that last few months that WSL2 has supported GUI applications (officially). So the documented process is running VSCode on the Windows, with a remote plugin to connect to Linux. It's entirely possible that it would be easier to just run it on the Linux side, now that it is possible to do so. |
Beta Was this translation helpful? Give feedback.
-
|
can i use jlink to replace stlink to use WSL debug inav source code? |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
It looks like maybe the image didn't finish uploading before you posted. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
can i use jlink to replace stlink to use WSL debug inav source code? |
Beta Was this translation helpful? Give feedback.
-
|
If you HAVE the jlink device, you probably know more about it than the active INAV developers, who use the ST Link for hardware debugging. Obviously for software debugging, you can debug the SITL just as you would any other Windows or Linux program. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
it is ok now!!! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
how to debug the inav source code at windows system? which software tool to use? how to realize it?
Beta Was this translation helpful? Give feedback.
All reactions