Search Results

There are multiple possible error sources: - Bad connector on board (even though the cable itself is fine) - CPU in some low power mode that disables all debug clocks and make the device to become unresponsive over JTAG - Device secured and debug interface has been disabled (not sure if there is a way to lift security on i.MX6 devices) - ...

Hi, It looks a bit like you are using some kind of weird combination of J-Link Commander V6.88b from 2020 with a DLL V7.82d from 2022. You should always use Commander + DLL from the same shipment with the same version. + I recommend to use the current version as there is neither support given nor problems being investigated for old versions. BR Alex

Pretty much sounds like your flash loader project is configured incorrectly. You may get a copy of the DSK which comes with correctly configured templates for Embedded Studio in which you would fill the Erase() Program() ... functions (you should already have the contents to be filled into these functions) and should be up and running. You may post your IAR project and somebody may or may not be able to help here but this is definitely outside of SEGGER support.

From the SEGGER side, there is no support given for Calliope mini directly. Support is given through Calliope. When the mini rev 2.1 was designed, Windows 7 was not considered as to be supported, so it may or may not work, no guarantees given.

Sorry but your description is confusing. Can you please post screenshots of what messages you are seeing and what you are doing?

If you are using it in a commercial context, it is not free. - The SDK gives you additional rights (writing your custom applications that make use of the J-Link API) - very likely creates support for us If it is used in a purely academic / non-profit context, there is always the option for discounts, exceptions, free in limited scope, ... but there is no generic recipe for this. This is case-by-case. However, this thread is closed at this point now, as the initial question has been answered. BR …

Hi Vadim, The ADAU1860 seems to incorporate an HiFi 3z core from Cadence. While this core is supported, the ADAU1860 has not been tested. HiFi core support is currently limited to Xtensa Xplorer IDE via GDBServer. There is no HiFi core support outside these tools (apart from basic operations via J-Link Commander). So you may or may not be able to debug the ADAU1860 via Xtensa Xplorer + J-Link. Has not been tested so no guarantees are given. Trace is definitely not supported. (There is not even a…

OK, so the answer is still "no" as you are planning to use it in a commercial context, so you need to purchase it as a commercial product.

Hi Sharon, The answer if it is "normal" is basically yes. As SectorInfo[0].SectorSize == 0x1000 (4 KB) and PageSize = 0x100 (256 bytes) and SectorSize = 16 * PageSize, a multiple of PageSize is passed to SEGGER_FL_Program() so what the J-Link software does is allowed and within the spec. BR Alex

No, the SDK is not a free solution. What do you plan to use it for?

shop.segger.com/debug-trace-pr…ftware-add-ons/j-link-sdk

Hi, I updated our wiki page accordingly: wiki.segger.com/OpenOCD#Restoring_the_USB_driver BR Alex

Hello Sharon, Not sure if I understand you correctly. For SEGGER_FL_Program(), <NumBytes> is guaranteed to be a multiple of FlashDevice.PageSize For SEGGER_FL_Verify(), there are no guarantees what <NumBytes> will be. The J-Link software is allowed to verify in chunks whatever it likes to. BR Alex

Hi, The PID used depends on what features are reported on the USB level. PID 0x0105 is the default for that kit which means J-Link + VCOM + drag & drop. The 0x0101 you are seeing is most probably the bootloader of the OB because the bootloader does not support VCOM + drag & drop. We must use a different PID when reporting different features for the same S/N because otherwise the host OS may get confused. Same S/N but different feature set must be handled as a different "product" (PID) on the hos…

Hi, Sorry for the delay in response on this. What you are running into is what is described as "case 9" here: wiki.segger.com/J-Link_RISC-V#JTAG_chain_auto-detection Why is that the case? Because J-Link does not know your RISC-V TAP Id, so it does not consider it as a potential RISC-V TAP. This is why the auto-selection of the TAP does not work, even though TAP_0 would be the correct one. Solution: 1) Use a J-Link script file as mentioned in the other thread 2) We add your TAP Id to the list of …

Hi, As you correctly pointed out, VCOM uses the USB CDC-ACM class which is USB specific and therefore not available over Ethernet. There are J-Link API functions that may be used to access the VCOM channel (of course not concurrently with a terminal application on the host. They are mutually exclusive) The J-Link API description is part of the SDK: shop.segger.com/debug-trace-pr…ftware-add-ons/j-link-sdk

Quote from JavierSVE: “and e2studio is just another eclipse. ” Well, I would not take that for sure. Under the hood, Renesas did a lot of stuff and initially broke things that were working in a vanilla Eclipse. So it is not necessarily just "another" Eclipse. Quote from JavierSVE: “Sorry, but the tool is a J-Link OB from SEGGER ” Correct, but neither there is support provided directly by SEGGER, for J-Link OBs, nor e2studio and its features / configuration is SEGGER-related. Quote from JavierSVE…

Wrong forum to ask. This is regarding configuration of Renesas e2studio. I am not even sure if what you are trying to do is possible. I recommend to check with Renesas. By the way: If you only want to flash the micro, why firing up a whole Eclipse environment when there are many much more performant ways? segger.com/products/debug-prob…-for-development-purposes

If you check the release notes, you will notice a fix for installing the DEB package under WSL2. segger.com/downloads/jlink/ReleaseNotes_JLink.html This probably has some kind of bad side effect onto installation to docker images. Do not know yet. We will have a look but I cannot exactly say when, as schedules are quite full. I am confident that there is a solution to make both work, WSL2 installations and installations inside docker containers.

Hi, For my understanding: Are you trying to build a docker image or run an existing docker image? So far, the thread you referenced in [2] more or less clearly says it: "A Docker container doesn't have access to host devices and isn't running system daemons,[...]" The J-Link DEB installer uses udevadm to reload the rules files because a rules file was just copied as part of the installer. This is needed to make sure that J-Links are accessible with normal user rights later on. You might want to …