Search Results

Update: The following steps solved the issue: - In J-Link Commander, connect to the J-Link and issue the following command ResetConf - Powercycle the J-Link - In J-Link Commander, connect to the J-Link and issue the following command Calibrate BR Fabian

Hi Philipp, Sorry for the delay in response. We agree that a crash should be avoided here. We will add a "NULL" (or similar) return message at some point in the future. Please note that we are currently fully booked with projects, so we cannot provide a timeline for when this will be available. We will close this thread now. Best regards Fabian

Hi, we are not aware of any such issue. Does the issue also occur when using the latest J-Link Software version? segger.com/downloads/jlink#J-L…twareAndDocumentationPack Do you use custom hardware or an evaluation board? In the latter case which one? If custom hardware, do you experience the same problem on an evaluation board? Could you please provide the following? - A J-Link log file of a faulty download attempt? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File - A Small sampl…

Hi, Before replacing anything, did you make sure that VCOM was not disabled for the J-Link Compact? wiki.segger.com/Using_J-Link_VCOM_functionality BR Fabian

Hi, - Only one loader is loaded to RAM at a time, and - the RAM region used by the loader is restored after each programming sequence. BR Fabian

Hi, there is no such issue known to us. Would it be possible to send us the FL_Test*.FLM files so we can check on our side? Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File BR Fabian

Hi, Thank you for your inquiry. We will answer you in the support ticket system regarding this. BR Fabian

Hi, No, it will not be reverted automatically. As a verification error indicates an issue during programming it would not really make sense to attempt another programming procedure to revert the changes, as this might very well fail again. The data on the target is not defined from the address where the verification failed onward. You can check it by reading back the programmed ranges. BR Fabian

Hi, Requests like this are handled in our Support Ticket system. Could you please create an inquiry regarding this there? Please also add a link to this forum thread, so the supporters know that these cases are related. Best regards, Fabian

Hi Sharon, Quote from sharon: “1. Where could I find the flash loader documrent to support older version? ” The older documentation is not available anymore, as it is a discontinued product. Quote from sharon: “When provide flash bankinfo in my device.xml, it seems must to provide flash loader, even I see the AlwaysPresent="0". Is it normal? ” If you specify a new flash bank via the xml, you definitively have to add a flash loader. Otherwise it would not really make sense to specify it, as no fl…

As Skvo correctly indicated, you are using a clone/cracked J-Link. Please note that the use of such a device in combination with our Software is illegal. We will close this thread now. BR Fabian

Hi, Connecting to the Apollo 3 devices should not trigger a reset by default, so connecting with the J-Link RTT Viewer should also not do so. Could you please 1) tell us what lead you to the conclusion that the device is reset on connect? 2) send us a picture of the Configuration Dialog of the J-Link RTT Viewer? 3) send us J-Link Log file of the RTT Viewer session that presumably resets the device? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File BR Fabian

Hi, Quote from Ouble: “Finally should I start a new thread if problems occur with loading and/or debugging the program onto the Due? Or should I ask in this thread? ” I think it is fine to stay in this thread regarding this. As it all concerns the sample project in the wiki that is discussed here. Quote from Ouble: “Is SWD functional in this case? ” Yes it is. The Connector is simply used to connect the signals between board and J-Link. See: segger.com/products/debug-prob…s/9-pin-cortex-m-adapte…

Hi, From the message it seems like the VTref pin is not being powered on your setup. I guess that you have to change some jumper settings to enable connection to an external debug probe or similar. We recommend to check the board manual regarding this. In general it is easier to first get things up and running with J-Link Commander (JLink.exe) to verify that the connection. Could you please follow the troubleshooting article on the page linked below wiki.segger.com/J-Link_cannot_…the_CPU#Target_…

Hi Maximilian, This is the first time we have heard about such an issue. 1) Did also turn to the MCUXpresso / NXP forum? 2) Could you please send us a J-Link log file? How to enable: wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File 3) Could you please send us a GDB log file? wiki.segger.com/J-Link_GDB_Server#-logtofile If I remember correctly, the command can be passed via Debug Configurations -> JLink Debugger -> Additional Options -> Other server Options: forum.segger.com/index.php/Att…c30886…

Hi, A couple of things: 1) Please refrain from spamming in this forum. If you want to add information to the thread before anyone answered, please use the "Edit" function. I removed the other messages and included it to the original one. 2) J-Link V7.22 is fairly outdated. Could you please check if it works with the latest version? segger.com/downloads/jlink#J-L…twareAndDocumentationPack 3) Apparently you already found the article explaining the cJTAG sequnece. Have you tried what is mentioned i…

Hi, the issue lies on SEGGER side here. Some month ago, Embedded Studio was adjusted to natively import RTT as library, when selected in the project options. The issue is that this may lead to building errors with projects that still include the old RTT files. The issue can be resolved by - removing the RTT files from the project and - changing Project > Options > Library > Library I/O from "None" to "RTT". I uploaded a new version of the project should build out of the box with the latest Embed…

Hi, Your question is not related to RTT but is concerning a general topic related to a general C and Assembler language. Please understand that this far exceeds the scope of the help we can provide in this Forum or in our support ticket system. I suggest that you take the time to check the RTT target side implementation, which you have all sources for. You could either a) follow the function calls or b) step through the code until you find where the memory is copied in the source. As a hint: As …

Hi, it seems like there might be some misunderstandings here. So I hope to clear them out with this post. 1) When is the ASM sub module used The ASM sub module contains an ASM variant of SEGGER_RTT_WriteSkipNoLock(). This function is used per default for most cores (e.g. Cortex-M4). However, you are using SEGGER_RTT_Write() not SEGGER_RTT_WriteSkipNoLock(). So in your example code the ASM routine is actually not used. You can check this by looking into the SEGGER_RTT.c and SEGGER_RTT.h files, wh…

Hi, Sorry for the delay in response. It seems like I misjudged where the problem was originating from: J-Flash does not accept aliased areas but only the actual flash areas for programming. On the KW38 devices, the flash from 0x1000_0000 - 0x1004_0000 is aliased to 0x4_0000 onward. It seems like the data file was created using the aliased flash area. Could you please try the following J-Flash + command line? %JLinkInstDir%\JFlash.exe -openprj%KW38ProjectPath% -open%PathToDataFile%\ble_shell_frdm…