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 J-link OB S/N.

    Post
    Hi, A S/N is not designed to be changed by the user. Can you please send a screenshot of J-Link Commander when using the OB on your board? There are several different OBs out there, so this screenshot would give us an idea what OB you have and if there…
  • Customer already contacted us via ticket system & J-Link PLUS. Thread closed.
  • SEGGER - Alex -

    Replied to the thread Indiemicro IND83209.

    Post
    Hi, There is no official support from SEGGER at this point but you can add support on your own: wiki.segger.com/Open_Flashloader There may also be an open flash loader implementation from Indiemicro at this point, we simply do not know, as they could…
  • SEGGER - Alex -

    Replied to the thread RT1061 debugging issue (JLink).

    Post
    Hi, If you are entitled for support, we recommend to go through the regular support channel, as there is no guarantee to receive any answer from SEGGER employees here in the forum. We only guarantee that our flash loaders are able to program the flash…
  • SEGGER - Alex -

    Replied to the thread [SOLVED] Could not access to the my own RISC-V core via cJtag protocal.

    Post
    Just to be precise / correct on Fabian‘s latest statement: Most RISC-V cores implement the short connect sequence. The short sequence is NOT standard compliant. The long sequence is standard compliant. Therefore, the long one is used by default, if…
  • SEGGER - Alex -

    Replied to the thread [SOLVED] Send custom JTAG commands to unsupported micro.

    Post
    The Commander is more a getting started / verification utility for supported cores. What you are probably looking for is JTAGLoad: wiki.segger.com/JTAGLoad It‘s part of the J-Link software package.
  • SEGGER - Alex -

    Replied to the thread J-Link Pro RamCode.

    Post
    Hi, You are most probably using a different SW version with your BASE V11 than you are using with your PRO V5. V7.66a had bug which made flash programming to fail on various Cortex-M33 / M23 based MCUs. Has been fixed in V7.66b.
  • SEGGER - Alex -

    Replied to the thread question about semihosting for aarch64 A53.

    Post
    Hi, the "Remote 'g' packet reply is too long..." error message indicates that GDB received an answer on the 'g' packet (read registers) that is longer than expected. The response to the 'g' packet is fixed for a specific GDB client and selected…
  • SEGGER - Alex -

    Replied to the thread gdbserver + gdb + generic semihosting.

    Post
    Hi, When using GDB, you first need to decide which way to go: #1 Have GDB handling the semihosting requests #2 Have J-Link GDB Server handling the semihosting requests Then you need to determine what approach your target application is following: #a…
  • SEGGER - Alex -

    Replied to the thread [SOLVED] J-Flash Target Device Setting.

    Post
    Hi, This is a MCU from the Infineon / Cypress PSoC-6 series. Support for these chips was added by Cypress, we are just shipping the connect scripts and flash loaders they provided. For support, you need to get in touch with Infineon.
  • SEGGER - Alex -

    Replied to the thread Slowly stepping over cache maintenance.

    Post
    We need more info. What is your debug environment / debugger on the PC side? Usually, the debugger would resolve the step-over to setting a BP on the next line and issue a Go(). However, sometimes the debugger comes to the conclusion that it needs to…
  • SEGGER - Alex -

    Replied to the thread Write or read external flash registers.

    Post
    Not 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.

    Post
    Hi, 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.

    Post
    Semihosting 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.

    Post
    Semihosting 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…
  • St‘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