Hardware > Debug probe: clarity, style, and consistency issues fixed#356
Hardware > Debug probe: clarity, style, and consistency issues fixed#356galleon8 wants to merge 5 commits into
Conversation
|
Hi @galleon8! Thank you for your contribution. We'll review it soon. |
NickVolynkin
left a comment
NickVolynkin
left a comment
There was a problem hiding this comment.
Hi @galleon8, thanks for your contribution. I've made a few suggestions. Feel free to discuss them.
There was a problem hiding this comment.
Why did you resize the images? The first one, showing a large portion of the screen, is now smaller (width of 1475), and the second, showing a smaller portion, is larger (width of 1984).
There was a problem hiding this comment.
I reduced the number of steps in the procedure, so I had to mirror this in the screen as it showed different numbers in it. Resizing is unintentional — please do whatever fits best, just make sure the number of steps in the procedure and its reference in the screen is the same.
| * **USB-serial #4** for access to the Debug Probe CLI (Command Line Interface). | ||
| * **USB-GPIO bridge** providing access to several GPIO pins of the Flipper One CPU and MCU. These pins can be read and write through the Debug Probe CLI. | ||
| * **MCU debugging via SWD (Serial Wire Debug)**: the probe supports CMSIS-DAP, allowing you to control CPU execution, access memory and peripherals, and program the Flipper One MCU (RP2350) flash. The MCU Firmware VS Code project is preconfigured for CMSIS-DAP debugging, so you can start a debug session right away. | ||
| * **USB-serial 1**: Flipper One Linux terminal. |
There was a problem hiding this comment.
Why not use #1-style?
There was a problem hiding this comment.
Just reducing the amount of items that don't have any specific meaning but add up space.
Co-authored-by: Nick Volynkin <nick.volynkin@gmail.com>
Co-authored-by: Nick Volynkin <nick.volynkin@gmail.com>
Co-authored-by: Nick Volynkin <nick.volynkin@gmail.com>
|
@galleon8 I see the update, thank you. Will review it early next week. |
2 participants
No description provided.