Search results

Hello, Thank you for your inquiry. Older versions are only provided on request. You can request them at info(at)segger.com Make sure to explain your situation why you need such an old software. This thread will be closed now. Best regards, Nino

Hello Krzysztof, Try connecting the reset pin as well to J-Link. Generally it is recommended to connect the reset Pin to J-Link to have a fallback if software reset is not enough on the used target device. If it still does not work compare the eval board schematic with your custom board schematic and see if there are any other differences. Best regards, Nino

Hello, Thank you for your inquiry. Such an issue is not known to us. How is your exact setup? Is the Linux box int he same network as the Windows PC? Or are you using the RemoteServer in tunneling mode to a remote location? Does the connect generally work when using J-Link commander? Should your setup be in the same company network we suggest the usage of a J-Link PRO over Ethernet so no timing problems appear. Best regards, Nino

Hello Efthymios, we received the SAMB11 eval boards from Microchip for testing. The eval boards are named ATSAMB11-XPRO. Attached is the commander output of a testhaltgo. Everything is working as expected when selecting Cortex-M0. So it seems that this issue is not related to J-Link. We suspect your debug connection is somewhat different to the expected design or the debug cable is unreliable. Compare the schematics of the SAMB11 eval board to your custom design and find out what the differences...

Hello Mike, We received your request per e-mail as well. Please do not open several communication channels at the same time to avoid information getting lost. That way it only takes longer for us to answer. The question will be handled per e-mail further. This thread will be closed now. Best regards, Nino

Hello, Your initial JLinkScript had JLINK_CPU = CORTEX_A5;. That is incorrect, make sure to remove that line. If you want to connect to the second STM32 then the attached script should be correct except the Cortex-A5 part: JLINK_JTAG_IRPre = 25; // Sum of IRLen of all JTAG TAPs preceding the one we want to communicate with JLINK_JTAG_DRPre = 4; // Number of JTAG TAPs preceding the one we want to communicate with JLINK_JTAG_IRPost = 5; // Sum of IRLen of all JTAG TAPs following the one we want to...

Hello Dave, we received the revision 5 boards from Microchip but the issue is still not reproducible. Do you have another SAME54 eval board to test against? Could you test the setup with J-Link commander on another PC? Do you have a second J-Link for testing? Best regards, Nino

Hello, Thank you for providing the picture. It is more clear now. Currently you are supplying VTref to Pin 19 and GND to Pin 18. The interface description on our website and manual shows the pin out of the actual J-Link pin interface and not the cable out on the other end. https://www.segger.com/products/debug-pr…ce-description/ So connect your supply to the correct pin 1 and pin 4 and you should be good to go. For reference the blue line on the cable refers to the side pin 1 is at. To make sure...

Hello, Thank you for your inquiry. Quoted Alex from Segger suggests to connect an external power supply to pins 1/4, so we did. We setup the bank power supply at 3.3V (as the target board), however JLink.exe still reports VTref as 0V. Could you attach a picture of your connection setup that shows the J-Link interface to make sure the wiring was correct? Do you have any other eval board or target device to test against? Make sure you apply the voltage before checking VTref as VTref will only be d...

Hello, Thank you for providing the information. A general connect to the device works with J-Link Commander. If you are looking into only programming your devices you can keep using J-Link Commander and use command loadfile and your build output from uVision. More information can be found in the J-Link user manual. uVision itself does not know exactly which device you want to connect to and randomly selects one of the available JTAG devices which leads to the reported error. To counter this you ...

Hello Krzysztof, Thank you for providing the log. We tried to replicate your setup with a NUCLEO-F411RE board and a J-Trace PRO as debug probe and everything is working as expected. See attachment. Are you using custom hardware or an eval board? Best regards, Nino

Hello, Thank you for providing the additional pictures. Which J-Link software version are you using in Crossworks? Could you provide a J-Link log file of the session with the failed connection? https://wiki.segger.com/Enable_J-Link_log_file Please understand that we can't put much time into this issue as it does not seem to be J-Link related as a connect with Commander is generally working. The issue is either related to some hardware issue of the ST-Link hardware which is provided by ST or to t...

Hi, *Thread has been moved to J-Link/Flasher related* Thank you for your inquiry. Such an issue is not known to us. Generally J-Link will only execute tasks that the IDE tells him to do. So whatever the IDEs tell J-Link to do when you insert the semaphore will cause the hard fault. Could you provide a J-Link log file of the session when the error appears? https://wiki.segger.com/Enable_J-Link_log_file Please understand that we can only give advice for SEGGER products. Eclipse, FreeRTOS and CCS a...

Hello, Generally Embedded Studio offers the user to use any standard library they want. First disable the use of Embedded Studio standard libraries in project options under Library->Include Standard Libraries->No To add your library go to project options Linker->Additional Input Files and add your newlib directory there. Now try to rebuild your project and you should be good to go. Best regards, Nino

Hello, Thank you for your inquiry. Did you move the project around by any chance or renamed folders? To keep your project portable you can use function Project.AddPathSubstitute. How to invoke it correctly is described int he Ozone user manual. Simply open your .jdebug file and add Project.AddPathSubstitute to function OnProjectLoad(); Does that resolve the issue? Best regards, Nino

Hi, Great to hear that you are up and running again. Correct AfterTargetDownload and AfterTargetReset need to be edited this way. Sorry I thought I wrote that earlier but seems like I missed that. We will consider this case as closed now. Best regards, Nino

Hello Patryk, Thank you for providing the screen shots. I just retested the same setup you are using and everything was working as expected. But I noticed one difference on your board I believe (unfortunately it is hard to see on the pictures you provided). There is a little switch next to the display marked <-PIC-PIM->. This needs to be in PIM position for the adapter to work. In PIC position I get the same error you see. Does putting the switch in the right position resolve the issue? Best reg...