-
Notifications
You must be signed in to change notification settings - Fork 483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failures when testing programmers with pyocd and the puya py32 #1523
Comments
STM32
PY32
|
STM32
PY32
|
STM32
PY32
|
STM32
PY32
|
STM32
PY32
|
STM32
PY32
|
STM32
PY32
|
STM32
PY32
|
STM32
PY32
|
STM32
PY32
(See the attached .odt doc for the full text - there's like a hundred pages for this one) |
Something I just discovered: programming works better at 3V3 Vcc. At least some of the probes that weren't working for me actually DO work, but only when running the PY32 at 3.3V. And all probes seem to work with more stability and reliability at 3.3V |
@prosper00 I'm having the exact same problem. which programmers did you use to connect? I have a st-linkvs but I can't connect to it using neither stlink nor dap link. |
any of the jlinks generally work, but only when the target is on 3.3V |
@prosper00 would a clone Jlink OB work as well? like this one |
probably, yeah |
I have used this board with success: Air32F103CBT6 With the air32_daplink_v1.hex , from the below I couldn't get the "new" v2 firmware to work. I programmed the Air32 w. a jlink , specifying taget as : STM32F103CB |
I was attempted to flash a Puya PY32F003 on the official development board (PY32F003F18P EVB) with a DAPLink (no brand on it), and got |
Summary
I recently bought a stack of puya py32 mcu’s after reading this article
I’ve been testing them out using the SDK here
I noticed that many of my daplinks and other probes fail to connect
to this mcu with pyocd [and openocd, though I didn’t test it as
thoroughly] when using the pack file provided by the vendor here
I have a stack of different probes and mcu’s running daplink
firmwares, and only one of them works OK. Most of the
daplinks fail with:
Method
To ensure the probes are working OK, I tested each on an STM32F103C8
mcu, as well as with a Puya PY32F002AL15. I figured the STM should be a
good control test, as it’s a very well supported and commonplace mature
product.
I’m running pycod 0.34.3.dev36 – though I did also test .34.3 release as
well with identical results.
My OS is Ubuntu lunar (dev), on linux 5.18.13
I prepared a firmware for each mcu, and programmed it with the following
commands:
STM32:
$ pyocd erase --chip -t stm32f103c8; pyocd load -t stm32f103c8 ./miniblink.bin
PY32:
$ pyocd load ./Build/example-blink.hex -t py32f002x5 --config ./Misc/pyocd.yaml
(the config file simply loads the pack file from the vendor)
Results table
Details: Programmers.odt
Details from each probe are in the comments below
The text was updated successfully, but these errors were encountered: