[SOLVED] BUG: STM32L100R8/A Secure chip results in damaged option bytes

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] BUG: STM32L100R8/A Secure chip results in damaged option bytes

    Hello. I am observing strange Jflash behavior when using Secure Chip option.

    How to reproduce:

    1. Connect to the target.
    2. Perform Production Programming(erase, program, verify).
    3. Check option bytes. I am using special software here. It reads option bytes and sends them via UART. Option Bytes values: 0xAA005500;
    4. Perform "Secure Chip" operation.
    5. Check option bytes. Option Bytes values: 0x0000FFFF; Option bytes are in Electrical Erase state? Chip is not secured, option bytes are't correct.

    Tested with V612a and V632f, MCU STM32L100R8/-A.


    Jflash project file is attached to the message.

    Best Regards,
    Andrii

  • Hello Andrii,

    A similar inquiry has been made here: [SOLVED] Options Bytes für STM32 programmieren
    How are you setting the option bytes? Are they part of your image or do you want to set them manually after programming?
    Does securing the chip using the exit steps explained in our Wiki work for your case?

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hello Nino,
    I do not set option bytes manually. I am using Secure chip functionality in the JFlash software, without any additional scripts:

    For some reason, when Secure chip is used with STM32L100R8/A MCU, option bytes become corrupted.

    Best regards,
    Andrii

  • Hello Andrii,

    The Secure Chip option only works on specific devices (see J-Flash user guide UM08003). This is not the case for the STM32L1 series. We will see if we can improve documentation in that regard so it becomes more clear which devices are supported.
    For the STM32L1 you need to do this either via exit steps or have them as part of your image.
    The correct sequences can be found here: wiki.segger.com/STM32#Enabling_readout_protection

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.

  • Hi Andrii,

    Great to hear that you are up and running again.
    We will consider this thread as solved now.

    Best regards,
    Nino
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.