Skip to content

stm32f4-discovery - unknown chip id! 0xe0042000 #107

Open
jpmzometa opened this Issue Sep 1, 2012 · 21 comments
@jpmzometa

Hi, i have a problem similar as #issue 64, but with a STM32F4-DISCOVERY.

st-flash write build/ch.bin 0x8000000

2012-09-01T18:33:59 INFO src/stlink-usb.c: -- exit_dfu_mode
2012-09-01T18:33:59 INFO src/stlink-common.c: Loading device parameters....
2012-09-01T18:33:59 WARN src/stlink-common.c: unknown chip id! 0xe0042000
stlink_sram_flash() == -1

Any hints?

@blueskynis

Hello,

Have a look here:
#62

"Connect under Reset" technique in STM-32 ST-LINK Utility brought back my dead mcus.

Cheers!

@Nomados
Nomados commented Mar 30, 2013

I have the same problem!

@blueskynis

To get back in touch with the chip, I have to boot into Windows and use the STM-32 ST-LINK Utility from ST to erase the flash with "Connect under Reset" enabled in Settings.

@kyab
kyab commented Jul 15, 2013

I have the same problem but now it comes back with STM-32 ST-LINK Utility on Windows. Thanks!

@perexg
perexg commented Jan 1, 2014

You can also short the BOOT0 pin with the VDD pin (using a jumper) to select the system memory (DFU bootloader) as the boot mode. Quick and simple.

@tghosgor

@perexg That does not work.

@elpaso
elpaso commented Sep 24, 2014

@tghosgor works for me...

@latsku
latsku commented Oct 29, 2014

What worked for me was:
1. Short the BOOT0 pin with VDD
2. Reset the board
3. st-flash erase

@fnack fnack referenced this issue in RIOT-OS/RIOT Jan 6, 2015
Merged

cpu/stm32f4: Add LPM implementation #2246

@joostrijneveld

Thanks @latsku, that worked perfectly.

@erwincoumans

@latsku yes, your 3 steps worked for me too. Thanks!

@ADARSHBU
ADARSHBU commented Jun 3, 2015

Hi Latsku,

Great buddy, those 3 steps works fine for me ....
Thank you..

@vdudouyt

@latsku thank you very much for your suggestion! This helped me as well.

@kont-noor

Tried all suggestions but still get WARN src/stlink-common.c: unknown chip id! 0xe0042000

@ADARSHBU
@kont-noor

@ADARSHBU it's a link to the current page

@ADARSHBU
@ogzarm
ogzarm commented Dec 23, 2015

1.open Stm32 St-link utility application
2.Target>Settings mode should be Connect Under Reset
3.Full erase chip
it is okey.

@polaroi8d

@latsku im very new in stlink and boards, so sorry for the dumb question but, what does "1. Short the BOOT0 pin with VDD" really mean?

@latsku
latsku commented Jan 27, 2016

@polaroi8d Not a dump question at all.
Connect the BOOT0 pin with the VDD pin.

And the electronics slang part. Short comes from short circuit, which is connecting the pins with a wire or similar conductor.

@polaroi8d

@latsku Okey, thanks for the answer, its woorking :)

@tcurdt
tcurdt commented Apr 9, 2016

So far I have just connected the ST-LINK V2 (with no board connected) and then ran st-util which gave the rc/stlink-common.c: unknown chip id! 0xe0042000 which let me here.

Now is this because there is no board connected?
Or is this about the ST-LINKV2 itself?
Or what is it?

I still have to try the above instructions on how to fix this - but could someone try to explain what the problem actually is? I didn't get it from the above comments yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.