Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fixed "unkown chip id", piped output and st-util -v #763

Merged
merged 3 commits into from Jan 24, 2019
Merged

Fixed "unkown chip id", piped output and st-util -v #763

merged 3 commits into from Jan 24, 2019

Conversation

jicksaw
Copy link
Contributor

@jicksaw jicksaw commented Jan 21, 2019

A few small tweaks.

  • I had the problem described in STM32F4 Discovery - unknown chip id! 0xe0042000 #107, and noticed the official ST-Link Utility's "Hot Plug" mode would work when the SWD freq. was lowered from 4.0 MHz to 1.8 MHz. The utility changes frequency before resetting when using "Connect Under Reset", so I moved it before the reset here as well.
  • On Win32 redirecting streams makes them buffered, so without
    flushing there would be no output before exit, resulting in [st-util] Can not get piped output on Windows #665. BTW using setvbuf to force the streams into line buffered mode doesn't work on Win32.
  • Currently st-util's --verbose does nothing, which is quite counterintuitive. The output isn't pretty, but at least it's something.

@jicksaw
Set SWD clock before using SWD (#107, #568 ?)
b167d27
@jicksaw
Make st-util -v print more than default
48e2fcf
@jicksaw
Flush output streams explicitly. Fix #665
08af942 
On Win32 redirecting streams makes them buffered, therefore without
flushing there would be no output before exit. Stdout and stderr are
also often buffered differently, making them disordered.
@xor-gate xor-gate added this to the Next milestone Jan 24, 2019
@xor-gate
Copy link
Member

Thanks!

@xor-gate xor-gate merged commit 30de1b3 into stlink-org:master Jan 24, 2019
@Nightwalker-87 Nightwalker-87 removed this from the General milestone Feb 21, 2020
@Nightwalker-87 Nightwalker-87 self-assigned this Feb 21, 2020
@Nightwalker-87 Nightwalker-87 added this to the v1.6.0 milestone Feb 21, 2020
This was linked to issues Mar 18, 2020
STM32F103C8Tx: Sudden unknown chip id #568
Closed
STM32F4 Discovery - unknown chip id! 0xe0042000 #107
Closed
[st-util] Can not get piped output on Windows #665
Closed
@Nightwalker-87 Nightwalker-87 removed a link to an issue Mar 20, 2020
STM32F103C8Tx: Sudden unknown chip id #568
Closed
6 tasks
@stlink-org stlink-org locked as resolved and limited conversation to collaborators Apr 23, 2020
@Nightwalker-87 Nightwalker-87 changed the title Fix "unkown chip id", piped output and st-util -v Fixed "unkown chip id", piped output and st-util -v Mar 24, 2021
@Nightwalker-87 Nightwalker-87 removed a link to an issue Mar 24, 2021
STM32F4 Discovery - unknown chip id! 0xe0042000 #107
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers
No reviews
Assignees

@jicksaw jicksaw

Labels
bug/fixed component/st-flash component/st-util error/unknown-chipid status/resolved
Projects
None yet
Milestone
v1.6.0
Development

Successfully merging this pull request may close these issues.

[st-util] Can not get piped output on Windows
3 participants
@jicksaw @xor-gate @Nightwalker-87