SEGGER - Alex Administrator
- Member since Dec 18th 2007
- Last Activity
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
SEGGER - Alex -
Replied to the thread Write or read external flash registers.
PostNot exactly sure what the question is here... What you can always do is using J-Link to access the registers of the i.MXRT1062 QSPI controller and send custom sequences to the QSPI flash to make happen whatever you would like to happen. Unfortunately, I… -
SEGGER - Alex -
Replied to the thread S32K144 RAMCode Failed Question.
PostHi, Such errors often point to connection / setup issues. It looks like J-Link either cannot write the RAM @ 0x1FFF8000 *or* the RAM is written correctly but reading brings garbage data. Some things to check: - Does it get better with slower interface… -
SEGGER - Alex -
Replied to the thread question about semihosting for aarch64 A53.
PostSemihosting support for ARMv8-A AArch32 has been added in V7.64d: segger.com/downloads/jlink/#J-…twareAndDocumentationPack This does not include semihosting support for AArch64. As I wrote, there are no immediate plans to add semihosting support for… -
SEGGER - Alex -
Replied to the thread question about semihosting for aarch64 A53.
PostSemihosting in general is possible on ARMv8-A targets (Cortex-A53 etc.). However, J-Link does not support it yet. We are working on AArch32 semihosting support for GDB Server which should be available in 1-2 weeks. There are no immediate plans for… -
SEGGER - Alex -
Replied to the thread [SOLVED] ETM trace with JTrace on STM32F4xx bootROM - is it possible to enable?.
PostSt‘s forum is a better place to ask, as it is their chip and their boot ROM. Most chip vendors suppress (certain) debug operations in boot ROM on purpose. BR Alex -
SEGGER - Alex -
Replied to the thread [SOLVED] Forcing chip erase in MK22FN1M0 parts.
PostHi, Currently, chip erase is not explicitly available for this device. There are no immediate plans to add support for it. You may write your own flash loader, doing exactly what you want: wiki.segger.com/Open_Flashload…ending_an_Existing_Device You… -
SEGGER - Alex -
Replied to the thread Segger SystemView logging not working with NUM_UP_BUFFERS size greater than 64.
PostThe FINE protocol supports 2 MHz max. and everything selected > 2 MHz will be scaled down to 2 MHz. 64 buffers sounds weird… SystemView is not designed to have information disteibuted over multiple buffers if they belong to the same instance. If you… -
SEGGER - Alex -
Replied to the thread [SOLVED] unknown entry point in jlink command file.
PostYou could also get your hands on the J-Link SDK and write your own applications, adapt J-Link Commamder to your needs, … BR Alex -
SEGGER - Alex -
Replied to the thread micro:bit V2 J-Link OB firmware problem on BL 0256.
PostHi, That's unfortunate news. Right now, there are no immediate plans to have a J-Link OB firmware image for the micro:bit V2.20. I will update this thread in case plans change. BR Alex -
SEGGER - Alex -
Replied to the thread Microchip Studio (latest) J-link integration.
PostDoes J-Link Commander from our software package detect this J-Link? If yes, we are back to the point where you need to contact Microchip, as a working J-Link Commander proves that the USB connection is fine and it is more probably an IDE issue. We are… -
SEGGER - Alex -
Replied to the thread Microchip Studio (latest) J-link integration.
PostHi, Microchip Studio is not listed on the “supported IDEs” page and untested. Therefore, we cannot guarantee that it works. No matter if it worked under Win 10 or not. We recommend to contact Microchip regarding this. This is actually the wrong… -
SEGGER - Alex -
Replied to the thread [SOLVED] J-Trace PRO not accessible Win11.
PostHi, Microchip Studio is not listed on the “supported IDEs” page and untested. Therefore, we cannot guarantee that it works. As J-Link Commander is able to detect the J-Link, the USB connection is fine. We recommend to contact Microchip regarding… -
SEGGER - Alex -
Replied to the thread [SOLVED] gdb command error for A53 program debug.
PostThanks for trying. Then it is a bug in GDB Server. Will be fixed in one of the upcoming versions. I recommend to sign up for the notifications. segger.com/notification/subscribe.php?prodid=7 -
SEGGER - Alex -
Replied to the thread [SOLVED] gdb command error for A53 program debug.
PostIt’s probably a bug. If you do not use the monitor command but use the GDB commands “info registers” “info all-registers” instead, does it work then?