Setting SWO speed above 50 MHz on J-Trace
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- devtools, embedded-iot
Research direction
Start by tracing the jlink.swo_start(100_000_000) entry point and the handling of SWO speed limits for J-Trace PRO devices. Verify the behavior against the documented 100 MHz capability and determine whether 100 MHz can be accepted; done means the supported behavior is implemented or the limitation is clearly documented.
Written by the indexing model from the issue text.
Description
According to Segger, the J-Trace PRO models are capable of SWO speeds up to 100 MHz.
However, when I call jlink.swo_start(100_000_000), the following dialog pops up:
Is there a way to enable speeds above 50 MHz?
- Dominant language
- Python
- Stars
- 430
- Forks
- 151
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from square/pylink
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
beginner good first issue
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100