Login or register

Username or Email Address

Are you already registered?

No, register now. Yes, my password is:

Password

Remain logged in

Lost Password

Search Results

Search results 1-3 of 3.

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

wine - Jun 21st 2018, 3:03pm - J-Link/Flasher related
Post

Thank you, Nino. I am setting Option Bytes via software inside MCU with special command. Problem solved. Regards, Andrii.
[SOLVED] BUG: STM32L100R8/A Secure chip results in damaged option bytes

wine - Jun 20th 2018, 2:00pm - J-Link/Flasher related
Post

Hello Nino, I do not set option bytes manually. I am using Secure chip functionality in the JFlash software, without any additional scripts: forum.segger.com/index.php/Att…8fb8401e885f27ca3e708ce3c For some reason, when Secure chip is used with STM32L100R8/A MCU, option bytes become corrupted. Best regards, Andrii
[SOLVED] BUG: STM32L100R8/A Secure chip results in damaged option bytes

wine - Jun 15th 2018, 3:09pm - J-Link/Flasher related
Post

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…