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.

  • Hello, Thank you for your inquiry. Could you name the exact device description of the target device you are trying to debug? Unfortunately Keil documentation is not clear if MTB is supported with third party probes. For verification could you use Ozone instead? segger.com/products/debug-probes/j-link/ Simply load up your Keil output file in Ozone using the project wizard and go to Tools->Trace Settings->Trace Source->Trace Buffer. If you now open the instruction trace window you should see trace…

  • Hello, Thank you for your inquiry. Each command line option will return 0 if successful and a negative value if not. This can be used e.g. in a batch script with error handling. An example can be found in the J-Flash documentation UM08003 in section "Batch processing". Best regards, Nino

  • Hello, ST-Link is a J-Link OB and does not need to use VTref as OBs are only used with 3.3 V targets. External J-Links however work from 1.2 V to 5 V. That is why VTref/Pin 1 needs to be connected to the target supply voltage. Alternatively you can also use J-Link Commander with comand VTREF. The syntax is Source Code (1 line)More information can be found in the J-Link user guide UM08001. Best regards, Nino

  • Hello, Thank you for your inquiry. Could you clarify what the problem is? J-Link currently only supports internal Flashes for programming MKE06Z128. For more information see here: segger.com/downloads/supported-devices.php How to add support for external Flash is explained here: wiki.segger.com/Adding_Support_for_New_Devices If it is a CFI compliant Flash more information can be found in the J-Link user guide UM08001. Best regards, Nino

  • Hello, Thank you for your inquiry. J-Link requires VTref to function, otherwise supported voltage levels of the target are unknown: segger.com/products/debug-prob…gy/interface-description/ So you need to connect the target supply voltage to Pin 1 of the debug interface. Best regards, Nino

  • Hello, Thank you for your inquiry. Currently we do not have any S6J335 hardware in house to implement support. We do support the S6J334 series however. If this core is compatible to the 35 series you can use this instead. In the meantime we will get in touch with Cypress and see if we can get hardware samples for support. The Cypress Traveo cores that we support currently all needed more complex init setups running to be able to access the target. So this is most likely needed for the 35 series …

  • Hello, Thank you for your inquiry. We were able to locate the probable cause of this issue and it should be fixed with the next Ozone release version. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. How exactly are you setting up your project? Is FPU enabled? Could you provide an example project for reproduction purposes? Best regards, Nino

  • Hello, Thank you for your inquiry. Generally such a setup is possible. However due to the limited functionality of ARM based Linux targets like the Raspberry-PI platforms the ARM software package from us comes without further support (see attached picture from our download page). The software package can be downloaded here: segger.com/downloads/jlink/JLink_Linux_arm.tgz Setup instructions should be comparable to a native Linux system which is explained in the J-Link user guide UM08001. Best rega…

  • Hello, Thank you for your inquiry. Ozone does not implement fopen for semihosting as Ozone is a host PC application and does not execute code on the target device. You can use fopen in your C source code however that runs on the target device which then will open the file on your host PC as expected. More information can be found in the J-Link user manual UM08001 and in this thread: [SOLVED] Semihosting and JLink 6.32a Best regards, Nino

  • Hello, quick update on the remaining points. 5: Can be enabled or disabled. In the "Project Explorer" window in the top right corner click on the arrow and deselect "Statistics Column" 6: Currently only Navigate -> Find References -> Replace All 7: We can only know dependencies when the project has been indexed, which it needs to compile for. When Headers are included in the project, they are searched. 8: That is standard behavior of a compiler. It cannot continue on most errors. Best regards, N…

  • Hello Mario, Thank you for your inquiry. Such an issue is not known to us. Which ES version are you using? What is the target device being debugged? How are your target connection settings? Which speed are you using? Could you provide an example project for reproduction? Best regards, Nino

  • Hello, Thank you for your inquiry. The issue was reproducible with the example project. We will investigate further and notify you once we have more information. Best regards, Nino

  • Hello, Thank you for your inquiry. For binary file manipulation we suggest using the J-Flash tool. The Flash loader then just needs to Flash the whole image. Best regards, Nino

  • Hello Ben, Thank you for your inquiry. Quote from Benjamin: “Do you have any solution for that? ” Yes, more information can be found here: wiki.segger.com/Programming_External_SPI_Flashes For direct mode you can specify the Flash commands in the J-Flash SPI tool. For indirect mode over a MCU you can use our open flash loader interface: wiki.segger.com/Adding_Support_for_New_Devices Best regards, Nino

  • Trace with ozone

    SEGGER - Nino - - J-Link/Flasher related

    Post

    Hello, Thank you for the additional information. The PCB layout looks fine on first glance. Quote from Brice_38_FR: “About the upgrade, I would love to get the last model but my boss won't understand and allow to buy a new one ... ” That is very unfortunate. The old J-Trace CM lacks any options to counter trace timing issues. You could try reducing 4-bit trace to 1 or 2 bit to see if signal integrity improves. Does that make a difference? Could you try setting a BP right after the PLL init and r…

  • Hello, Quote from 40490FDB: “The connector I use is an Atmel part. ” Please understand that we can't guarantee functionality with third party adapters. Make sure to either use the one shipped with J-Link or one from our shop. Best regards, Nino

  • Hello, sorry for delay in response. In the meantime we have setup a support ticket system. Could you open a ticket at segger.com/ticket for further discussion? Best regards, Nino

  • Hi Phil, Great to hear that you found a workaround for your setup. We will consider this thread as closed now. Best regards, Nino

  • Hello, Thank you for your inquiry. Such an issue is not known to us. For easier communication could you create a support ticket at segger.com/ticket ? This thread will be locked now. Best regards, Nino