See related Octoprobe issue: octoprobe/testbed_micropython#31

@hmaerki FYI

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.57%. Comparing base (4bd9926) to head (ca49faa).

@@           Coverage Diff           @@
##           master   #17558   +/-   ##
=======================================
  Coverage   98.57%   98.57%           
=======================================
  Files         169      169           
  Lines       21968    21968           
=======================================
  Hits        21654    21654           
  Misses        314      314           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Code size report:

   bare-arm:    +0 +0.000% 
minimal x86:    +0 +0.000% 
   unix x64:    +0 +0.000% standard
      stm32:   +36 +0.009% PYBV10
     mimxrt:    +0 +0.000% TEENSY40
        rp2:    +0 +0.000% RPI_PICO_W
       samd:    +0 +0.000% ADAFRUIT_ITSYBITSY_M4_EXPRESS
  qemu rv32:    +0 +0.000% VIRT_RV32

Octoprobe run results are here: https://reports.octoprobe.org/github_selfhosted_testrun_127/octoprobe_summary_report.html

That looks a lot better, although still a few tests are failing.

• I added PYBV11. Testrun https://reports.octoprobe.org/github_selfhosted_testrun_128/octoprobe_summary_report.html (does not include your latest commit).
• My 2f2c-NUCLEO_WB55 is slow, even when I connect it to my notebook! So I assume it has to to with the board or the firmware update we did together yesterday flash nucleo-wb55 bluetooth-stack

  RUN-PERFBENCH
  * 497s: 2f2c-NUCLEO_WB55 on tantacle: https://reports.octoprobe.org/github_selfhosted_testrun_126/RUN-PERFBENCH@2f2c-NUCLEO_WB55/testresults.txt
  * 495s: 2f2c-NUCLEO_WB55 on tentacle: Hans Lenovo T14S running 'mptest test --only-test=RUN-PERFBENCH'
  * 495s: 2f2c-NUCLEO_WB55 USB connected directly: Hans Lenovo T14S running 'time ./run-perfbench.py -p -d /dev/ttyACM0 100 100'
  

• These are the jumper settings (according to tentacle_specs.py): https://www.maerki.com/hans/download/damien/tentacle_2f2c-NUCLEO_WB55_2025-06-25a.jpg

@dpgeorge: Which usb connection do you use? I use the one behind 'RESET'.

    USB_STLINK CN15: located on the back side of 'LED4'
    USB_MCU    CN1 : located on the back side of 'RESET'

What I am doing next:

• Test the crystal: make a LED blinking 1 Hz. If the blinking is too slow, the crystal may be broken.

My 2f2c-NUCLEO_WB55 is slow, even when I connect it to my notebook! So I assume it has to to with the board or the firmware update we did together yesterday

It could be due to left over files on the filesystem, from the BT firmware update. Can you try to reset the filesystem with:

import vfs, pyb
vfs.VfsFat.mkfs(pyb.Flash(start=0))

These are the jumper settings (according to tentacle_specs.py)

Those jumper settings are correct.

Which usb connection do you use? I use the one behind 'RESET'.

The one behind RESET is the correct USB port to use.

I have updated the tests here so that they should all now work on NUCLEO_WB55.

If you bridge PA2/PA3 on the NUCLEO_WB55 (Arduino D0/D1 on CN9, or 35/37 on CN10) then that will allow the UART tests to pass.

If you bridge PA2/PA3 on the NUCLEO_WB55 (Arduino D0/D1 on CN9, or 35/37 on CN10) then that will allow the UART tests to pass.

Stupid me. Thanks for your help! I didn't read the table in datasheet correctly. I will correct it tomorrow morning and run another test.