-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Unknown Chip ID 0xe0042000 #451
Comments
OK, looks like this is some kind of standard error that I have to fix by finding someone with a Windows system, and reprogramming the adapter in some way? It would be great if there were a clear statement somewhere about what needs to be done. Unfortunately I don't know anyone using Windows who is geeky enough to be able to help (or who I could borrow their computer) so it would be amazing if there were some instructions about how to fix this from Linux... Or OSX - I guess I can find geeks using OSX as well, or borrow a laptop from one. |
Hunting through the issues a little more, I see the patch in issue #428 and given the way this board is designed to work, I guess that's the problem. After applying that patch I can now:
So perhaps the issue is that when a chipid of 0xe0042000 is detected the error message should suggest trying again with a --reset option (especially after this patch is added). Thanks, |
Fixed by merge of #430. |
I have this same problem. After installing on linux libusb-1.0.0 for :i386 on machine 64bit, I get message |
How can I help to fix "stlink/src/common.c: unknown chip id! 0xe0042000" ?
ST-LINK / V2
B 2015 30
This looks like a normal standard Stlink/v2, as far as I can see from the various pictures on the internet.
Unknown. Perhaps the lsusb output is useful?
Linux, Debian Sid, x86-64
git ee2681e
st-info
,st-flash
,st-util
st-flash (& others)
The top of the chip is printed in full with:
STM32F405
RGT6
7B357 VQ
PHL 7B 527
A as-detailed description possible of the problem with debug output when available.
Output:
Expected/description:
I'd hoped the chip ID would be supported :-)
Thank you,
Andrew McMillan
The text was updated successfully, but these errors were encountered: