Skip to content

fix: resolve #706 — "No communication port specified" when using ST LINK V2 debugger#807

Open
andoan16 wants to merge 2 commits into
Autonomy-Logic:developmentfrom
andoan16:contribai/improve/quality/add-st-link-v2-port-detection-support
Open

fix: resolve #706 — "No communication port specified" when using ST LINK V2 debugger#807
andoan16 wants to merge 2 commits into
Autonomy-Logic:developmentfrom
andoan16:contribai/improve/quality/add-st-link-v2-port-detection-support

Conversation

@andoan16

Copy link
Copy Markdown

Summary

fix: resolve #706 — "No communication port specified" when using ST LINK V2 debugger

Problem

Severity: High | File: docs/ports/debugger-port.ts

The current debugger port detection logic doesn't properly identify ST LINK V2 debuggers which use SWD interface rather than standard COM ports. This file likely contains the port detection and enumeration logic that needs to be enhanced to detect ST LINK V2 devices.

Solution

Add logic to detect ST LINK V2 devices using their USB vendor/product IDs (STMicroelectronics VID: 0x0483) and handle them appropriately in the port enumeration. Implement special handling for SWD interface devices that don't appear as standard COM ports.

Changes

  • docs/ports/debugger-port.ts (modified)
  • docs/ports/device-port.ts (modified)

Testing

  • Existing tests pass
  • Manual review completed
  • No new warnings/errors introduced

andoan16 added 2 commits May 31, 2026 09:28
…hen using ST LINK V2 debugger

Fixes Autonomy-Logic#706

Signed-off-by: Ân Đoàn <33853760+andoan16@users.noreply.github.com>
…hen using ST LINK V2 debugger

Fixes Autonomy-Logic#706

Signed-off-by: Ân Đoàn <33853760+andoan16@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented May 31, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@andoan16, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 25 minutes and 20 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: a0610095-795f-4167-ac9a-ee1c700ce56d

📥 Commits

Reviewing files that changed from the base of the PR and between 456c08a and 9add79f.

📒 Files selected for processing (2)
  • docs/ports/debugger-port.ts
  • docs/ports/device-port.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"No communication port specified" when using ST LINK V2 debugger

1 participant