connect_test fails on DISCO_L475VG_IOT01A device
Open
Nobody has claimed this yet.
backlog
- Dominant language
- Python
- Stars
- 1.5k
- Forks
- 560
- Avg merge
- 1h 41m
- Merged PRs (30d)
- 3
Description
pyocd version : 0.18.0
Device : DISCO_L475VG_IOT01A
pyocd.yaml
probes:
0666FF555051897267232812: # Probe's unique ID.
target_override: stm32l475xg
test_binary: stm32l475vg_iot01a.bin
Test command
python connect_test.py -d
Linux
----- TESTING CONNECT/DISCONNECT -----
Flashing new binary
DEBUG:flash_builder:Analyze time: 0.509709
DEBUG:flash_builder:Chip erase count 30, Page erase est count 1
DEBUG:flash_builder:Chip erase weight 5.592700, Page erase weight 1.696700
DEBUG:flash_builder:Using double buffer page erase program
[====================] 100%
DEBUG:flash_builder:Estimated page erase count: 1
DEBUG:flash_builder:Actual page erase count: 1
INFO:pyocd.flash.loader:Programmed 60748 bytes (30 pages) at 8.35 kB/s (29 pages unchanged)
Verifying target is running
TEST FAILED
Windows
----- TESTING CONNECT/DISCONNECT -----
Flashing new binary
DEBUG:flash_builder:Analyze time: 0.568000
DEBUG:flash_builder:Chip erase count 30, Page erase est count 1
DEBUG:flash_builder:Chip erase weight 5.592700, Page erase weight 1.696700
DEBUG:flash_builder:Using double buffer page erase program
[====================] 100%
DEBUG:flash_builder:Estimated page erase count: 1
DEBUG:flash_builder:Actual page erase count: 1
INFO:pyocd.flash.loader:Programmed 60748 bytes (30 pages) at 8.12 kB/s (29 pages unchanged)
Verifying target is running
TEST FAILED
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.
Research direction
Start with pyocd.yaml and run python connect_test.py -d using the DISCO_L475VG_IOT01A device and the provided binary. Compare the Linux and Windows logs while tracing the connect/disconnect test. Done means the test verifies that the target is running instead of reporting TEST FAILED.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100