Search Results

Hi, In testing the option bytes to set protection level for STM32L151 chip, I checked the pop-up message box 'Do not show this again'. This caused the chip to be unsecured automatically every time I perform a memory read. How do I undo this action? I am running J-Flash v5.10k. Thanks, Henry

Hi Niklas, I tried option byte programming. When execute 'auto', J-Flash goes through erase, program and verify before running the exit script. In this case, how do I avoid it overwriting the data already in the flash? In a way, how do I set the project that the exit script is executed, but my programmed data not being changed? This 'option byte programming' would be the last step in my program where data file downloaded, some tests executed, then read protect the chip. Thanks, Henry

Hi, I need to run secure chip on the STM32L486 MCU, but the command is not available in current release of J-Flash v5.10h. Is there a plan to update J-Flash to allow option bytes for Cortex-M4 devices? When would that be approximately? Thanks, Henry

Hi, We are trying to program the TI CC2640F128 BLE chip using the SEGGER JLink Plus. I'd like to know if JLink Plus supports 2-pin cJTAG. If so, how do I set it up to use the feature? Thanks, Henry

Hi, Can you tell me which version of Jlink provides support for flashing the ST chips STM32L486QG16? I installed v502k but didn't find the supporting chip on the device list. Thanks, Henry

forum.segger.com/index.php/Attachment/331/forum.segger.com/index.php/Attachment/332/Hi Erik, Thanks for following up with my request. I used the same set up and project as yours. I still couldn't secure the chip by running the command once. I am using the AT91SAM7SE-EK eval board and J-Flash v4.68a. The steps: connect to target read back chip - successful secure chip - successful Disconnect Remove power, wait 1 minute Reconnect power connect to target read back chip - successful. So the target i…

Hi Alex, I tried a few more chips and they all had to be run several times, different numbers of runs, to secure the chip. My process: power on , download to the chip, power off, power on, secure chip, power off. Then I verify by downloading to the chip again and it was able to download. Any suggestions? What should I do differently, proecss wise? Thanks, Henry

I used Securechip command in J-Link to lock the Jtag port of AT91SAM7SE512; however, it didn't work consistently for me. I had run to the program two or more times to get it secured. Did anyone have this problem before? Is there something I missed such as some set-up in order to run this command? Thanks for any help, Henry