search

rgrr / yapicoprobe

Yet Another Picoprobe
124 stars 12 forks source link

Issues Encountered with probe-rs Connection and Performance Testing Using STM32H743VGT6 and yapicoprobe v1.20 2024-02-05 #108

Closed zh522130 closed 8 months ago

zh522130 commented 8 months ago

Hello, I am the submitter of . After seeing your test, I would like to conduct a test with yapicoprobe. My target chip is STM32H743VGT6, and the version of yapicoprobe I am using is v1.20 2024-02-05. I did not make any additional configurations to yapicoprobe. I was unable to complete the test; in Keil, only when the Max Clock was set to either 100kHz or 200kHz, could the download proceed， When I used "./probe-rs benchmark --address 0x20000000 --chip STM32H743VGTx --speed 10000", the following error message appeared:

"Error: Connecting to the chip was unsuccessful.

Caused by: 0: An ARM specific error occurred. 1: An error occurred in the communication with an access port or debug port. 2: Target device did not respond to request."

Using "./probe-rs benchmark --address 0x20000000 --chip STM32H743VGTx --speed 1000", the error message was as follows:

"Probe: Probe type CMSIS-DAP, debug interface not specified, target chip STM32H743VGTx

Test: Speed 1000, Word size 32bit, Data length 4 bytes, Number of iterations 5 Results: Read: 8587.40 bytes/s Std Dev 58.20, Write: 3034265.90 bytes/s Std Dev 1317969.03

Test: Speed 1000, Word size 32bit, Data length 32 bytes, Number of iterations 5 Readback data differs at address 20000007: expected word a1783c0b, got word 01783c0b Verification failed. thread 'main' panicked at probe-rs\src\bin\probe-rs\cmd\benchmark.rs:192:37: invalid mean note: run with RUST_BACKTRACE=1 environment variable to display a backtrace WARN probe_rs::session: Could not clear all hardware breakpoints: An ARM specific error occurred.

Caused by: 0: Error using access port 1: Failed to read register DRW at address 0x0000000c 2: An error occurred in the communication with an access port or debug port. 3: Target device did not respond to request. WARN probe_rs::session: Failed to deconfigure device during shutdown: An ARM specific error occurred.

Caused by: 0: Error using access port 1: Failed to read register DRW at address 0x0000000c 2: An error occurred in the communication with an access port or debug port. 3: Target device did not respond to request."

Using "./probe-rs benchmark --address 0x20000000 --chip STM32H743VGTx --speed 100" resulted in the following :

Probe: Probe type CMSIS-DAP, debug interface not specified, target chip STM32H743VGTx

Test: Speed 100, Word size 32bit, Data length 4 bytes, Number of iterations 5 Results: Read: 1350.73 bytes/s Std Dev 17.82, Write: 1963492.06 bytes/s Std Dev 873414.05

Test: Speed 100, Word size 32bit, Data length 32 bytes, Number of iterations 5 Results: Read: 5247.96 bytes/s Std Dev 15.18, Write: 4935.78 bytes/s Std Dev 42.91

Test: Speed 100, Word size 32bit, Data length 128 bytes, Number of iterations 5 Results: Read: 6966.85 bytes/s Std Dev 47.44, Write: 6667.35 bytes/s Std Dev 36.00

Test: Speed 100, Word size 32bit, Data length 2048 bytes, Number of iterations 5 Results: Read: 7804.27 bytes/s Std Dev 14.41, Write: 7438.97 bytes/s Std Dev 9.61

Test: Speed 100, Word size 32bit, Data length 32768 bytes, Number of iterations 5 Results: Read: 7809.12 bytes/s Std Dev 2.00, Write: 7438.02 bytes/s Std Dev 7.64

zh522130 commented 8 months ago

I'm very sorry, I was able to conduct the test normally with another pico, so it appears the issue was with the pico I was using before