Search Results

Search results 1-20 of 1,000. There are more results available, please enhance your search parameters.

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

  • Hi Res, Little update. A guide on how to create your own Embedded Studio packages can be found in the Embedded Studio manual in chapters "Package Generator" and "Package Description file format". You can use our online manual for that: studio.segger.com/ide_package_description_file_format.htm studio.segger.com/mkpkg.htm Is that what you were looking for? Best regards, Nino

  • Hello, This is no bug. The erase value for the STM32L151 series is 0x00 (see ST Flash manual). This is why the gap is filled with 0x00 after erase. If you want some other data there make sure your hex file contains that data. Best regards, Nino

  • Hello, Thank you for your inquiry. Could you provide a screenshot of the pop-up in question? Usually they have a "do not show again" option to disable them for future sessions. Best regards, Nino

  • Hello, If you are getting constant overflows try increasing the interface speed to a higher value. Does that improve the behaviour? All information needed to get a FreeRTOS SystemView setup can be found in the SystemView manual and on our Wiki: wiki.segger.com/FreeRTOS_with_SystemView Best regards, Nino

  • Hi, Thank you for your inquiry. The PAC5532 is currently not officially supported by J-Link software which is why you see the software falling back to Cortex-M4 than staying with the actual target device which will only partially work. But you are in luck, Active/Semi( now Qorvo) provides J-Link support on their own. You can get it here: active-semi.com/products/intel…ntrol/pac5532#et_pb_tab_4 According to Qorvo you need to have a "myActive login" on their website to access it. Does it work if y…

  • Hi Ade, Quote from Adrian Parsons: “I can trigger the device erase. Sometimes this completes in 0.1sec, sometimes it takes ~5, ~10 and ~20 secs depending on device size. ” This sounds already strange. The >5s times would be expected e.g. the 64Mb chip I used took ~15s. 0.1s is definitely to short and indicates that something went wrong. I noticed that you registered with J-Links that are eligible for e-mail support. As this forum is not our official support channel could you open a support inqui…

  • Hello Steve, Thank you for your inquiry. Please not that this forum is no official support forum. To get support please fill our official support form to get in tough with our engineers directly. You can find the needed contact information in my signature. To make sure no information gets lost between channels this thread will be closed now. Best regards, Nino

  • Hello Rich, Windows 10 is fully supported by our tools and software. You can find that information on the product page of your particular J-Link model e.g.: segger.com/products/debug-probes/j-link/models/j-link-pro/ But for the old V4.66 and V4.96l etc. we will not be able to provide official support through our support channels as these software versions are out of support and maintenance for more than 10 years now. We always recommend using the latest J-Link software version as we try to stay …

  • Hello, Thank you for your inquiry. Such an issue is not known to us. We tried to reproduce the issue with a IS25LP064A which should be the same base chip just with a larger memory and everything was working as expected. Quote: “ - VTarget = 3.336V - Read SPI Flash Id = 0x9D 60 17 - Found SPI Flash: ISSI IS25LP064A - Connected successfully Executing init sequence ... - Executed successfully Reading entire flash chip ... - 128 sectors, 1 range, 0x0 - 0x7FFFFF - Target memory read successfully. (83…

  • Hello, Thank you for your inquiry. You can edit hex files in J-Flash how you like, so simply fill that empty area with 0xFF and save the hex file again. If you Flash that file now you should have the value 0xFF in memory at that location. We noticed that the J-Link you are registered with is out of support and maintenance for more than 10 years now. To get the latest features and speed benefits from J-Link we recommend upgrading to a current J-Link version. For this we offer our trade in program…

  • Hello, Good to hear that you are up and running again. Such an issue is not known to us but it sounds like Windows tempered with Embedded Studio data during the update/upgrade which should of course not happen. Unfortunately the provided information does not give enough insight to what happened to continue investigation. Should the issue be reproducible somehow we would gladly know the steps. Best regards, Nino

  • Hello, Thank you for your inquiry. Currently there are no plans to add new BSPs to Embedded Studio for RISC-V. A BSP is essentially simply a project so feel free to create your own by simply creating a new project for one of the supported RISC-V target devices. Best regards, Nino

  • Hello, Great to hear that you are up and running again. We will consider this thread as solved now. Best regards, Nino

  • Hello, Thank you for your inquiry. The function TargetInterface.message can be used for logging. Is that what you were looking for? Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Are you using custom hardware or an eval board? If the latter which one? Could you provide a sample project for reproduction that shows the described behaviour? Best regards, Nino

  • Hello, We will see if this feature can be shown more prominently and improved in future but no promises here. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. Could you try and verify general connection via J-Link Commander? wiki.segger.com/J-Link_cannot_…ty_using_J-Link_Commander Could you post a screenshot of the connect sequence? Should no connection to J-Link work at all check the wiring to your PC and see if all drivers are correctly installed. Best regards, Nino

  • Hello Torsten, Generally when starting the Reflash utility you also get an option to restore the ST-Link. So we suggest to try that and then refnash it again to J-Link. It is possible that you might need a ST-Link image for restoring the device. In that case we suggest requesting such image directly at ST. Best regards, Nino

  • Hello Simon, Thank you for providing additional items. Could you create a support ticket for this inquiry? In my signature you can find out how. Please also attach the xml and elf file when creating a ticket so we can try to reproduce the reported behaviour. To make sure no information gets lost between mutliple channels this thread will be closed now. Best regards, Nino

  • Hi Thomas, Good to hear that you are up and running again. This is indeed an error in the handler for NRF_LOG in the Nordic SDK. We will check if ES and Ozone can be streamlined in their behavior regarding the output of \r\r\n As the initial topic has been answered this thread will be closed now. Best regards, Nino