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, If your application reconfigures the debug pins as GPIOs, this effectively inhibits debugging. As the PSoC6 support has been implemented by Cypress / Infineon, no direct support is given by SEGGER. If there is a workaround / fallback method for this case, Cypress / Infineon would have to implement it, as they maintain the support, flash loaders, ... BR Alex

  • Hi Bernd, There is no example project for (Q)SPI flash. However, it is not really different from internal flash, as the functions to fill are the same. BR Alex

  • Hi, Some hint for the beginning: You may throw away the J-Link script file. By selecting "Cyclone V" as the MCU to be debugged, J-Link already knows that it is Cortex-A9 based. So the script you are passing, does not provide any additional information. To the problem itself: I am not sure if J-Link GDB Server is to blame here. Even though the log you provided does not show the session from the beginning, it looks like GDB itself ends up in some endless loop. - "n" tells GDB to go to the next C-c…

  • As you have also contacted us via the support ticket system, we will close this thread, to keep it to 1 channel.

  • Hi, If the datasheet says 10 MHz, it is likely that even 20 MHz will still work, as every vendor has certain tolerances in their "max." specification values. However, using higher speeds than 10 MHz on the JTAG interface is simply out of spec. It is like configuring the PLL in the MCU for 200 MHz if only 168 MHz are specified: You won't get any error and it is likely that the 200 MHz will still work but you do not know how stable they are and if they work if the temperature goes up etc. Right no…

  • Hello, The J-Link EDU Mini is 3.3V only. Any level shifter adding etc. is made at your own risk and out of warranty and support. We cannot guarantee that it works. Especially if you are using SWD debug protocol for which 1 pin is bidirectional, which is tricky for level shifters that auto-detect the direction of a signal. Using a J-Link EDU with 20-pin connector: Assuming that X6 on the Infineon board is the debug connector and follows the standard pinout from ARM, this should be the adapter you…

  • Hi, Are you 100% confident that the „CoreBaseAddr“ and „AP“ you manually configured, are correct? J-Link auto-detects the presence of SB by checking some SB related registers. If any of the manually configured settings is incorrect, nothing will work and you will probably see incorrect output. From the log I would say that at least your AP specification is incorrect. Can you send us your script and an excerpt from your CoreSight layout, to see how the core is connected to the DAP? We are 100% co…

  • The V9 hardware you are using, only supports up to 12 MHz. The 15 MHz refers to the current hardware version (V11). Also, the speed may be further scaled down if there is a device specific for your MCU (e.g. for most MCUs from NordicSemi max. SWD speed that can be used is 6000 kHz, so selecting more will be scaled down to 6000 kHz). Also, J-Link may decide to reduce the speed further if the connection occurs to be unstable at the selected speed.

  • If SB is available on the core, J-Link will use it. Nothing needs to be setup. BR Alex

  • You can do it like this: JLink.exe -device AMA3B1KK-KBR -if SWD -speed 100 -autoconnect 1 -CommanderScript JLinkCommandFile.jlink > MyOutFile.txt Note that the output format of J-Link Commander may change in a new version without prior notice or release note entry. It is a test utility and not designed for customized automation. We recommend the J-Link SDK for such setups. BR Alex

  • It has nothing to do with the EDU… It‘s just your setup that is broken. GDB listens on port 2331 by default (common GDB Server listening port). See log output of GDB. IDAPro is configured to connect on port 23946. Of course this cannot work. You need to specify the same port on both sides…

  • Hello Haly, As you have already contacted us via the support system, this thread will be closed. Could you please avoid contacting us on multiple channels, as this doubles the work on our side and makes things slower for both sides? BR Alex

  • No worries. Mistakes happen. Glad to hear that you were able to resolve this.

  • The IAR J-Links have been discontinued years(!) before the nRF91 was released. You also do not expect your Windows 2000 to run the latest software from 2015-2020, right? It is similar for this J-Link and MCU support… We recommend to get a new J-Link: segger.com/purchase/trade-in-program/ BR Alex

  • What exactly is the question? When starting a debug session, J-Link takes care of the potentially required flash programming automatically. If you are looking for a stand-alone flash programming solution, I doubt that VSCode is the way to go.

  • You are mixing things here…. First, you asked for debug support, now, in your latest post, you are referring to production programming. These are 2 totally different things. Production programming: The easier part. You do not have to mess around with various specifics of the device. No caches, less silicon bugs, … that can come into play. As you might have noticed, we already support a lot of ATMega, PIC16, PIC18, … devices with our Flasher PRO production programmer. Debug support: Much more wor…

  • Yes it is but you would need to create a flash loader on your own: wiki.segger.com/Open_Flashloader Sorry to say that we do not have any samples for eMMC.

  • Hello, The V10 is in the maintenance period. So bugfixes will be added but no new features. Quote from Noy: “ Are there plans to support other PIC (18, dspic) beside PIC32? V10/V11 should support ICSP but why not PIC18? Would be great if i don't need my PICkit 3 anymore.. Only a JLink for all... ” No plans for PIC16 / 18 /33 / ... debug support right now. ICSP for PIC32 is different from ICSP from PIC18 / 33 / ... (Microchip just calls it ICSP on all platforms but they are actually different pro…

  • Hi, I see. This makes sense for sure. We will add this option. BR Alex

  • Hi Phil, USB: J-Link might be connected via USB but GDB and GDBServer communicate via TCP/IP with each other. Again: It is a problem in GDB. GDB is used by KDS to load the ELF file (your target application) and to interpret the debug information. During that interpretation, something goes wrong on the GDB side that causes it to half-way crash and being left in an unusable state. So if you are looking for a solution: It is still no SEGGER problem. You still need to get in touch with NXP regarding…