Skip to content

Error uploading to STM32 Ladybug L432KC board #1084

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

Open
eloquentarduino opened this issue Nov 24, 2020 · 1 comment
Open

Error uploading to STM32 Ladybug L432KC board #1084

eloquentarduino opened this issue Nov 24, 2020 · 1 comment
Labels
status: waiting for information More information must be provided before work can proceed type: imperfection Perceived defect in any part of project

Comments

@eloquentarduino
Copy link

eloquentarduino commented Nov 24, 2020

Bug Report

When uploading to the Ladybug L432KC board with the arduino-cli, I sometimes get an error.

Current behavior

This is the output from the cli:

arduino-cli upload -b grumpyoldpizza:stm32l4:Ladybug-L432KC -p /dev/tty.usbmodem1411 --verify
Open On-Chip Debugger 0.10.0-dev-00272-gf17dc4a (2016-10-10-09:57)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
debug_level: 0
adapter speed: 500 kHz
adapter_nsrst_delay: 100
none separate
none separate
Error: open failed
in procedure 'program'
in procedure 'init' called at file "embedded:startup.tcl", line 473
in procedure 'ocd_bouncer'
** OpenOCD init failed **
shutdown command invoked

Expected behavior

I expect the upload to succeed.

Environment

Additional context

This happens most often after I read the serial output from the board via Python's pySerial library.

@ubidefeo
Copy link

@eloquentarduino
this might very well be an issue with a serial port not being released properly.
I run Mac OS myself and have learned over the years that Darwin gets very possessive of UARTs to the point that sometimes I had BSOD when unplugging a board.

Make sure you dispose of your Serial connections properly.
Sometimes resetting a board might do the trick for you, forcing PySerial to throw an exception if it's still hung on the port.

I doubt this is a bug on arduino-cli, but keep us posted with your findings.
u.

@per1234 per1234 reopened this Mar 30, 2021
@fstasi fstasi removed the type: bug label Sep 16, 2021
@rsora rsora added the type: imperfection Perceived defect in any part of project label Sep 22, 2021
@umbynos umbynos added the status: waiting for information More information must be provided before work can proceed label Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting for information More information must be provided before work can proceed type: imperfection Perceived defect in any part of project
Projects
None yet
Development

No branches or pull requests

6 participants