Search Results

Hello, please note that V5.10 and V6.11 are outdated versions of J-Scope. J-Scope has been reworked and is now a part of the "J-Link Software and Documentation Pack": segger.com/downloads/jlink/#J-…twareAndDocumentationPack Could you give the reworked version of J-Scope a try (V7.52a)? Best regards, Daniel

Quote from minchingho: “I'm using a Jlink Pro. HW ver 4.5. S/N 174505067 My device baud rate is running at 230400. ” Please note that the maximum baud rate supported by the J-Link PRO V4.5 is 115200 baud. Prior to version V7.00a there was no internal limit in regard to the baud-rate, however setting baud-rates above 115200 did cause several instabilities (e.g. lockup of the J-Link firmware). Therefore we added a maximum baud-rate for the J-Link PRO V4.5 in version V7.00a. Baud-rates above 115200…

Hello Norbert, thank you for providing additional information on this. Update: I just gave this a try on one of our evaluation boards (p-nucleo-wb55 USB dongle), however on our side a wireless stack upgrade or FUS upgrade works as expected (see attached screenshot) with the latest J-Link Software installed (V6.86f). Do you experience the same problem on an evaluation board? Does this issue persist when programming the 1MB variant of the STM32WB55 series (STM32WB5xxG) instead? Best regards, Danie…

Hello Norbert, thank you for your inquiry. Such an issue is not known to us. Do you use custom hardware or an evaluation board? In the latter case which one? Could you also please send us a J-Link log file of the failing session? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File Best regards, Daniel

Hello, thank you for your inquiry. Do you use custom hardware or an evaluation board? In the latter case which one? If custom hardware, do you experience the same problem on an evaluation board? Furthermore: We recently resolved an issue concerning ST STM32WB55 flash-programming support. Could you therefore give the latest version a try (segger.com/downloads/jlink/#J-…twareAndDocumentationPack)? Does the behavior improve? Best regards, Daniel

Hello, we were able to resolve the issue: The return value of the SEGGER_OPEN_Erase function is now correctly evaluated. The fix will be a part of the next release (~ one to two weeks). Best regards, Daniel

Hello, We were able to reproduce the issue. Right now the return value of SEGGER_OPEN_Erase is not correctly evaluated on our side. We are working on a fix for this and I will update this thread accordingly. Please excuse any inconveniences caused. Best regards, Daniel

Hi Wim, Update: Unfortunately we do not have a STM32L151VC to test right now, but it should be the same procedure on every STM32L151xx, so I tested to set the option bytes that you provided on a STM32L151VD and STM32L151CB device and it works flawlessly. The only issue with a block-verification error occurred when I tried to set the read protection (RDP) back to 0xAA (Level 0) through J-Flash. Setting the RDP back to 0xAA through a program-operation in J-Flash is not possible because writing 0xA…

Hi Wim, Thank you for your inquiry. Such an issue is not known to us. We will try to reproduce your issue and update this thread accordingly. Best regards, Daniel