Tuesday, June 27th 2017, 2:14pm UTC+2

You are not logged in.

  • Login
  • Register

Search results

Search results 1-20 of 1,000. There are even more results, please redefine your search.

Yesterday, 9:00am

Author: SEGGER - Niklas

Is this a bug of OZone? [bit field handling ]

Hi Masa, thanks for testing the new version and for reporting theses issues. I forwarded your inquiry to the Ozone maintainer. Best regards, Niklas

Friday, June 23rd 2017, 7:23pm

Author: SEGGER - Niklas

[SOLVED] J-Link Plus Ver9.2 fails to debug ATSAM4LS4B with 6.14H

Hi, thanks for the update and good to hear that you are up and running again! Best regards, Niklas

Friday, June 23rd 2017, 7:16pm

Author: SEGGER - Niklas

J-Link not found by SWO-Viewer

Hi Forum, this issue has been fixed in version 6.16c of the J-Link software & documentation pack. Best regards, Niklas

Friday, June 23rd 2017, 7:15pm

Author: SEGGER - Niklas

J-Link Commander V6.14h on Ubuntu 16.04.2 LTS, cannot connect to nRF52832.

Hi Forum, this issue has been fixed in version 6.16c of the J-Link software & documentation pack. Best regards, Niklas

Friday, June 23rd 2017, 7:13pm

Author: SEGGER - Niklas

Invalid syntax in /etc/udev/rules.d/99-jlink.rules from JLink_Linux_V614f_x86_64.deb

Hi Forum, this issue has been fixed in version 6.16c of the J-Link software & documentation pack. Best regards, Niklas

Friday, June 23rd 2017, 6:58pm

Author: SEGGER - Niklas

J link gdb server problem

Hi, as mentioned before, could you please give the most recent J-Link software & documentation pack a try and provide us with a screenshot of J-Link Commander and log files if anything fails? Log output can be enabled like as follows: Open a connection to J-Link, e.g start J-Link CommanderIn J-Link Control Panel: (Click the J-Link symbol located in the notification / tray area in order to open J-Link Control panel)Open the tab "Settings"Next to the field "Log file" check "Override" and click ".....

Friday, June 23rd 2017, 6:54pm

Author: SEGGER - Niklas

Issue with J-Link debugger while working with bootloader on STM32F765

Hi, I just gave it a try and could not reproduce it using a STM32F769NI eval board. Could you please give resetting the option bytes to factory defaults a try? The J-Link software & documentation pack ships with a utility for STM32 MCUs called JLinkSTM32.exe. If the issue persists, would it be possible for you to provide us with an example data file and step-by-step instructions in order to reproduce the issue? Best regards, Niklas

Friday, June 23rd 2017, 6:25pm

Author: SEGGER - Niklas

Double Invocation of JLink GDB Server

Hi, Do I understand you correctly, that this happens on each debug session start, even after a PC reboot? I can only think of 2 possible causes of this message: 1) emIDE does not close the first connection correctly, therefore a connection to J-Link is still established at the start of the next debug session 2) emIDE has a bug where it does open 2 connections at once. Best regards, Niklas

Wednesday, June 21st 2017, 7:00pm

Author: SEGGER - Niklas

[SOVED] Unable to program in stand-alone mode

Hi Forum, Update: This issue if fixed in current version of the J-Link software & documentation pack. Best regards, Niklas

Wednesday, June 21st 2017, 6:58pm

Author: SEGGER - Niklas

[SOLVED] jflash spi eval license

Hi, thanks for the update. I hope everything worked well! Best regards, Niklas

Wednesday, June 21st 2017, 6:56pm

Author: SEGGER - Niklas

[SOLVED] j-link support for STM32L496 and STM32L4A6

Hi Marian and Forum, support for STM32L49x and STM32L4Ax devices is now available in the release version of the J-Link software & documentation pack. Best regards, Niklas

Wednesday, June 21st 2017, 6:49pm

Author: SEGGER - Niklas

[SOLVED] J-Flash V6.14f fails to "Save Flasher data file"

Hi Forum, sorry for the delay in response. This issue has been fixed a while ago in the J-Link software & documentation pack. Best regards, Niklas

Wednesday, June 21st 2017, 6:41pm

Author: SEGGER - Niklas

[SOLVED] Re: BMI Issue in XMC1300 J-Link Lite CPU-13A-V1

Hi Forum, this issue has been resolved via mail. Best regards, Niklas

Wednesday, June 21st 2017, 5:59pm

Author: SEGGER - Niklas

How to program mac address for tm4c129encpdt

Hi, please refer to the Ti reference manual of the tm4c129encpdt regarding this information. If the address is not located in the flash, it probably needs to be written by writing to SFRs. This can be done using either J-Link Commander for development purposes or the J-Flash init / exit steps for production purposes. Best regards, Niklas

Wednesday, June 21st 2017, 5:56pm

Author: SEGGER - Niklas

[SOLVED] J-Link: Write Program flash 0 IFR in MK64FN1M0VLL12

Hi, thanks for the feedback and good to hear that everything is working for you now! Best regards, Niklas

Wednesday, June 21st 2017, 5:36pm

Author: SEGGER - Niklas

DAP error while reading AHB-AP IDR

Hi, I just gave it a try in J-Link Commander and unfortunately could not reproduce any issue. Could you please give J-Link Commander a try? J-Link commander is part of the J-Link software package, which is available free of charge here . Start J-Link Commander (jlink.exe)Type "connect" in order to start a debug sessionType in the target device name if asked (Or type "?" for a target selection Dialog)Choose the correct target interface (JTAG/SWD/etc..)Use a valid speed (Default: 4000kHz, try 100-...

Wednesday, June 21st 2017, 12:40pm

Author: SEGGER - Niklas

Add a new flash device to the JLInkDevices database

Hi Alexey, if I understand you correctly, the boot header / QSPI config block is always read as LE64. Therefore, the issue can be resolved by swapping the bytes in the data file accordingly before passing it to the J-Link flash loader. Most QSPI flashes have different available configurations / modes regarding the data format (LE32/LE64/BExx/"striping" modes with another flash, etc [..]). Therefore, the J-Link flash loader always programs the flash in the same predictable way. For example: You h...