Search Results

Hello everyone, I have a hardware prototype with an ATMEL ATSAMV71Q21 that has ... gone through rough times (short circuit between core and IO voltage), meaning the device may have taken physical damage. The board errors were fixed at this point, voltages, current draw and chip temperature are fine by now. I tried to connect to the Device using a JLINK and run into the following results: SWD: (Hidden Content) JTAG (Hidden Content) The JLINK seems to find something (SW-DP with 2 IDs ... are those…

Interestingly, everything seems to work fine when using GDB command line tools (at least: uploading binarys). However i cannot really execute them. Even using the example projects that come with batch files for building (just needed to install MinGW and cmake) I cannot get the CPU running properly. The program counter seems to always get out of hand and points to some reserved. By setting manual breakpoints, I can see that the Reset_Handler routine is called, but the CPU never gets to the main t…

Hello!Quote: “ Just a quick question: do you know that M4 is enabled & running before you connecting to it and trying to halt?” Well when opening the JLink conrtol panel - CPU Regs - Read all registers (after starting a debug session) the console prints: ERROR: Can not read register 20 (CFBP) while CPU is running So I guess its running.

JLink.exe has an TestHaltGo command. When connecting to the A7_0 core, 1000 halt/go cycles are done within ~3,5s and no problem occurs. On trying the same test while connected to the M4 i simply get "WARNING: CPU could not be halted". I do not know if this is a hardware/layout problem, Jlink problem, silicon problem or setup problem. (Although i can probably exclude layout problem, as i see the same behaviour on three different hardware platforms, one being the SABRE). I am absolutely stuck here…

Quote: “Please understand that we can't put much time into this as J-Link is connecting correctly to the target with GDBServer and using our other tools. The Eclipse Plugin is not maintained nor supported by us. Please contact the plug in maintainer if the linked setup guide on our website does not work. ” Ye sure, I am aware of that. So far, I am not entirely sure if this is an issue that can be resolved on the JLink side or not. Probably not, but Ill keep posting here until this is resolved f…

Alright, some more information: The debug process did not start because the Eclipse settings pointed to the JLinkRemoteServerCL.exe instead of the JLinkGDBServerCL.exe. A debug session is now created but i do not see any output. When switching to the JLink Control Panel - CPU Regs tab and click "read all registers" the following result is shown: forum.segger.com/index.php/Attachment/2295/ I guess these registers should be initialized by .. probably eclipse, through jlink? Not sure if this being …

With the script provided in the NXP Forum thread mentioned in my previous post I am able to have the JLinkGDBserver connect to the M4, waiting for the GDB connection. forum.segger.com/index.php/Attachment/2293/ So I think this part is all good now. I just dont know how to get the GDB connection up. When I started the JLinkGDBServer through the win command prompt and then start e debug sesion in eclipse, the session is started. But i do not see any debug output. Or any other hint for the system t…

I have found a ressource in the NXP Forum that describes/achieved what I want to do. After adjusting the startup and debugging options as described I no longer get the previous error when starting a debug session in Eclipse. Screenshots of the settings are attached. But I run into a different problem now: Quote: “ Error in services launch sequence Starting J-Link GDB Server timed out.” I have already adjusted the timeout setting as described here , but no success. No difference if running Eclips…

Quote: “ Try to keep information at one place.” Understood! I tried to connect to the board with and without SD card (including uboot/Linux). With SD card, i cannot connect to the M4 using JLink.exe and JLinkGDBServerCL.exe. Outputs have been attached. After removing the SD card and doing a power cycle, JLink.exe is able to identify the M4. JLinkGDBServerCL still comlpains about not being able to halt the CPU. Log file has been attached. I realized you are using version 6.30, while I am using ve…

Hello again, after kind of adding information all over the place in my last thread i decided to simply create a new one. The current state is: I seem to not be able to connect to the MX7's M4. I have attached the log files for the following four scenarios: - connect to the NXP SABRE A7_0 - connect to the NXP SABRE M4 - connect to the CUSTOM BOARD A7_0 - connect to the CUSTOM BOARD M4 On both boards, connecting to the A7 seems to work well. Connecting to the M4 ends in different error messages fo…

Alright, I have added 2 FETs so the reset signals are on 1V8 / 3V3 and get pulled down correctly. However, the error remains .. Feature(s): GDB Checking target voltage... Target voltage: 1.81 V Listening on TCP/IP port 2331 Connecting to target... J-Link found 1 JTAG device, Total IRLen = 4 JTAG ID: 0x5BA00477 (Cortex-M4) WARNING: CPU could not be halted Halting target device failed. Trying again with reset WARNING: CPU could not be halted WARNING: CPU could not be halted WARNING: CPU could not …

And some more info: The SoC has two external reset signals: TRST# and POR# (jtag reset and power on reset). On the custom board, TRST is connected to the JTAG header and the processors TRST pin. POR is connected to a PMIC (open drain), the processors POR pin and to TRST via shottky diode (to prevent overvoltage on the POR pin in case the emulator has been set up incorrectly). JTAG is running on 1V8. POR was 2V2 with the diode attached and 3V3 with the diode removed. Means i cannot have the 2 pin…

Another piece of info: On the SABRE board I can see the reset line being pulled low several times while on the custom board the reset signal is always remaining high.

Quote: “ The JLinkScript you are using, is it from the J-Link software install folder?” I used a downloaded the version from your wiki page. I checked the content of the downloaded version ... it was actually a web page and not a script so I probably screwed up the file download. Switched to the script in the install folder. Quote: “ Did you modify the JLinkScript in some way?” Nope.Quote: “ What J-Link software version are you using in Eclipse?” First console output in OP: SEGGER J-Link GDB Ser…

I have found out how to add a script file based on wiki.segger.com/Eclipse This is the output for the SABRE board: ------J-Link related settings------ J-Link Host interface: USB J-Link script: C:\Eclipse_MCU_And_Toolchains\JLink\File_NXP_iMX7D_Connect_CortexM4.JLinkScript J-Link settings file: none [...] eature(s): GDB Checking target voltage... Target voltage: 3.33 V Listening on TCP/IP port 2331 Connecting to target...ERROR: Error while compiling J-Link script file: Error while compiling. Line…

Some additional info: I enabled log file output. From the log file: 02-00000000-00-00000306-01E9: Found Cortex-M4 r0p1, Little endian. -- CPU_ReadMem(4 bytes @ 0xE000EDF0) -- CPU_ReadMem(4 bytes @ 0xE0002000) [.. many more romtbl reads ..] 02-00000000-00-00000310-00A2: T2448 000:310 JLINK_GetIdData(...) >0x0D TIF> >0x21 TIF> ScanLen=4 NumDevices=1 aId[0]=0x5BA02477 aIrRead[0]=0 aScanLen[0]=0 aScanRead[0]=0 (0001ms, 0308ms total) 02-00000000-00-00000310-0048: T2448 000:311 JLINK_GetDeviceFamily()…

Hello everyone, after being able to connect to my target hardware (i.MX7D) using JLink.exe I wanted to integrate the JLINK in ARM MCU Eclipse. I configured Eclipse based on gnu-mcu-eclipse.github.io/debug/jlink/ ON starting a debug session, Eclipse creates an error: J-Link GDB Server failed: Could not connect to target. Please check if target is powered and if ribbon cable is plugged properly. For more details, see the JLinkGDBServerCL.exe console. and my console outputs the following: SEGGER J-…

Thank you Nino for your detailed answer. Its a revision D board as well. Using SWD didn't work either. While reading your post again (especially the section about JTAG not being enabled ... "why wouldnt it be?!", I thought) I rememberd I had changed the resistor setup to put the board in boundary scan mode some weeks ago. After adjusting the resistors, everything works fine now! Many thanks! Found SW-DP with ID 0x5BA02477 CoreSight AP[0]: 0x04770001, AHB-AP CoreSight AP[1]: 0x04770002, APB-AP Co…

Hello everyone, we have just updated to a new JLink in order to program/debug an i.MX7D device. For a test, I wanted to connect to NXP demo board (MX7 Sabre). I tried connecting to the A7 using JLink.exe, but get the result listed below (see line 17). As suggested in other threads, the JTAG clock speed has been limited to <400 KHz. The target board is powered (JLINK detects 3,3V). The scripts for connecting to the cores were mentioned in the other threads as well. Based on the console output bel…