Skip to main content
R
Rajesh Tripathi
Graduate II
April 16, 2017
Question

Can not read memory! Disable Read Out Protection and retry

  • April 16, 2017
  • 7 replies
  • 8710 views
Posted on April 16, 2017 at 04:55

Hello, I have problem with a custom stm32f437 based board. It was working for few days then suddenly stopped working and can't program it anymore From keil/St-Link setup.

Installed the ST-Link utility (V4.0) and updated firmware on ST-Link. When I try to connect it says

'Can not read memory!

Disable Read Out Protection and retry.'

Not sure how it got into 'Read Out Protection Level 1'  as I had never even used ST-Link Utility.

When I try to switch to ROP level 0 and deselect all sector and apply, it complains

'Could not set Option bytes!

Please reset the target and retry.'

Already reset/retry many time with no improvement!

The board is unusable now. Please help.

#stm32-stlink #stm32f4-read-out-protection #stm32f437
    This topic has been closed for replies.

    7 replies

    T
    Tesla DeLorean
    Graduate II
    April 17, 2017
    Posted on April 17, 2017 at 13:44

    Try reprogramming with BOOT0 pulled high.

    T
    Tesla DeLorean
    Graduate II
    April 17, 2017
    Posted on April 17, 2017 at 15:06

    >>

    I have problem with a custom stm32f437 based board.

    Assume no one here is at all familiar with the design of the board, or the software changes that resulted in the failure here.

    Review the code for interference with the JTAG/SWD pins.

    Review the design for debug connectivity, and ability to use System Loader to access USART1/USART3 or USB

    R
    Rajesh TripathiAuthor
    Graduate II
    June 3, 2017
    Posted on June 03, 2017 at 23:39

    Programming with BOOT0 pulled high didn't help.

    The JTAG/SWD pins are not reused as GPIO so there is no code related to that. There is only 10 lines of extra code to what was generated by STM32CubeMX. Just to poll one GPIO line and toggle 3 other GPIO lines. There is no other code and that's why it's puzzling as to why the board goes into this read only mode.

    Can't connect with the System Loader either, always times out. The same system loader setup work fine with STM32F429 discovery board.

    Is there a way to recover the board using any other JTAG?SWD tool?

    So far 3 boards have gone into this Read only mode own it's own.

    T
    Tesla DeLorean
    Graduate II
    June 4, 2017
    Posted on June 04, 2017 at 00:03

    Segger has STM32 specific tools for their J-Link, there are J-Link loads for the ST-LINK.

    There sounds to be some design issue with your board and firmware, unfortunately I lack psychic skills to debug this remotely.

    R
    Rajesh TripathiAuthor
    Graduate II
    June 4, 2017
    Posted on June 04, 2017 at 23:38

    Hi Clive one. Thanks a lot for your always prompt response.

    I'll try with Segger's JLinkSTM32.exe tool.

    What hardware design issue could cause the boards gong to Protection level 1? I'm rather new to STM32 but this seems to be very simple chip with single power supply rail at 3.3V and only few control line like BOOT0/1, NRST etc in comparison to QorIQ P2040/iMX6Q etc I've worked on earlier.

    The firmware right now is just few GPIO lines code as this is a co-processor to manage main power on/off with push button.. No other peripherals like USART/I2C/SPI are being used or interrupts enabled. No RTOS either. Just STM32CubeMX generated code for GPIOs compiled with Keil tools.

    The Flash loader also doesn't work. I've checked with Scope that BOOT0 is high , BOOT1 is low. And USART3_RX pin is receiving serial pulses but nothing comes out at USART3_TX pin. Atmel's ATSAMA5D35 Micro I worked on earlier has similar serial loader and that always worked.

    I'm just trying to understand as what can cause this strange behavior. Generally ST-Link/Serial loader tool is needed to put STM32 in protection level 1. Has anyone else seen the same problems with STM32s and what was cause?

    D
    Denise Andreozzi
    Visitor II
    June 6, 2017
    Posted on June 06, 2017 at 18:34

    My team is having a very similar problem with the STM32F407 chip.  Electrically, the circuit is sound.  Have you discovered the root cause of the issue?  If so, please post your results.  We are continuing to debug, but I will post with any new information.

    R
    Rajesh TripathiAuthor
    Graduate II
    June 8, 2017
    Posted on June 08, 2017 at 06:36

    No one knows the root cause. No help from ST. Clive one has been kind enough to give some ideas but that didn't help.

    I suspect there may be some silicon bug with STM32F4 series chip. I was wondering why Segger has STM32 specfic unlock utility?! Is this very common problem with STM32?

    R
    Rajesh TripathiAuthor
    Graduate II
    June 8, 2017
    Posted on June 08, 2017 at 06:44

    Looks like the problem may be related to power supply.

    http://www.onarm.com/forum/20658/

     
    D
    Denise Andreozzi
    Visitor II
    July 3, 2017
    Posted on July 03, 2017 at 14:46

    My company has received the Failure Analysis Report from STMicro.  We sent them two disabled units.  Based on their findings, both units have their VCAP1 and VCAP2 lines internally short circuited to VSS (ground).  They were unable to determine the root cause, and they do not have any other reports of this problem.  My team is now reviewing the results and looking into a failure of the internal voltage regulator.  I will keep this thread going as we progress.

    T
    Tesla DeLorean
    Graduate II
    July 3, 2017
    Posted on July 03, 2017 at 18:08

    So probably wouldn't be able to measure 1.25V on the VCAP pins in-circuit.

    Would look at components as placed. Board shorts, and device orientation.

    D
    Denise Andreozzi
    Visitor II
    July 6, 2017
    Posted on July 06, 2017 at 20:51

    Actually, I am able to measure 1.25V on the external caps.  We had 3 non-functional units and all three exhibited the same symptoms. We sent 2 of those units over to ST for the failure analysis.  Both had the same results, shorted VCAP pins.  I suppose it is possible that this third unit failed for an entirely different reason, but it seems less likely.  

    We have e-mailed our technical contact at ST for any potential explanation.  In the meantime, I am working through the 'nitty-gritty' looking for an error.

    M
    martin su
    Visitor II
    August 23, 2017
    Posted on August 23, 2017 at 17:30

    Hi Denise,

    Have you found the root cause of this issue? I encountered one similart issue with STM32L072 chip,could you share some update  about this issue? thanks.

    R
    Reema O
    Visitor II
    October 30, 2017
    Posted on October 30, 2017 at 19:13

    I am also facing the similar issue with STM32F405. Any updates? Do we need to update ST-Utility software?

    T
    Tesla DeLorean
    Graduate II
    October 30, 2017
    Posted on October 30, 2017 at 20:54

    In my experience software updates will not fix board level shorts or incorrect components or design. 

    What voltage do you measure on the VCAP pins?

    Has the designed be reviewed by an ST FAE?

    R
    Reema O
    Visitor II
    October 30, 2017
    Posted on October 30, 2017 at 21:26

    VAP_1 1.85 and Vcap2 is 1.18 

    How can I contact ST FAE

    Terms & ConditionsAccessibility statement