Search Results

Hi Niklas, No problems with the delayed reply, it was certainly worth waiting for, I can now connect to and debug the other cores. Thanks very much for your help and support on this! Regards, Neil

Hi Niklas, Thanks for the information. It is strange you don't support this device as I definitely read somewhere in the NXP documentation that the SEGGER j-link was the recommended j-tag device.... I have tried one of your scripts from IAR Workbench and I still can't connect to one of the other Cores. NXP documentation implies that when core 0 is in the boot ROM, all the other cores will be executing the WFI (Wait for Interrupt) instruction. Should I be able to connect in that state or do I nee…

Hi Niklas, I am struggling to find information about the IRPre and DRPrn values for the other cores....and also what state these cores are in at power-up. This is the output I see if I connect to the device and specify 'Cortex-A9' SEGGER J-Link Commander V6.10f (Compiled Oct 17 2016 17:41:50) DLL version V6.10f, compiled Oct 17 2016 17:41:18 Connecting to J-Link via USB...O.K. Firmware: J-Link Ultra V4 compiled Sep 1 2016 18:31:22 Hardware version: V4.00 S/N: 504401606 License(s): RDI, FlashBP, …

Hi Niklas, Thanks for your reply. The i.MX6 device in the SoC I am using is this one, nxp.com/products/microcontroll…x-a9-core:i.MX6Q#overview. However it is limited to a clock speed of 800MHz. It has 4 Cortex A9 cores, and as far as I can tell from the device manuals they are operating as per default. If I use J-Link.exe I see this, SEGGER J-Link Commander V6.10f (Compiled Oct 17 2016 17:41:50) DLL version V6.10f, compiled Oct 17 2016 17:41:18 Connecting to J-Link via USB...O.K. Firmware: J-Lin…

Can I assume due to the lack of response on my question that it is not possible to multicore debug using the JLinkARM.dll interface? I have also been in contact with Rowley and they do not know how to configure. Neil

Hi, I have a -link Ultra+ connected to an NXP iMX6 (on a QWKS-SCMIMX6 development board) I need to be able to connect to and debug each of the ARM A9 cores in the SOC separately. I have seen mention of using separate GDB servers one of each core in order to do this, but in my case I am not using GDB. My development environment is Rowley CrossStudio which uses the JLinkARM.dll to interface to the j-link. If I set the following in the Rowley target connect script, TargetInterface.setDebugInterface…

Just to complete this I have been working with Rowley (CrossWorks) and they have given me some new project settings which have solved my problems and I can now connect and debug. In case this is useful to anyone, I had to add the following project settings, TargetInterface.setDebugInterfaceProperty("set_adiv5_APB_ap_num", 1); TargetInterface.setDebugInterfaceProperty("component_base", 0x82150000 ); TargetInterface.stop(1000)

Hi Niklas, A further update....I have found that if I prevent the development board from booting into Linux and leave it in the NXP boot loader then if I use the MCIMX6Q4 device type you suggested I can connect and halt the processor with J-Commander. I can also connect with J-Mem and read/write memory. So it appears the j-link Ultra+ is working just fine! Unfortunately I still have problems connecting with Rowley Crossworks which now goes into a hang when I connect, I am in communication with t…

Hi Niklas, Sorry in my previous reply I assumed the CPU was halted after the connect....it is not, and when I use the 'h' command to halt the processor I see, J-Link>h ************************** WARNING: CPU could not be halted ************************** So unfortunately the issue is still present Regards, Neil

Hi Niklas, Thanks for your reply. I don't actually know how to configure Rowley to use that device name, however I have tried to connect using j-Link Commander using a device type of MCIMX6Q4 and it does appear to connect successfully and halt the processor! I will contact Rowley and see how to configure this in their software. Regards, Neil SEGGER J-Link Commander V6.10f (Compiled Oct 17 2016 17:41:50) DLL version V6.10f, compiled Oct 17 2016 17:41:18 Connecting to J-Link via USB...O.K. Firmwar…

I have just started a new 'bare metal' project using Rowley CrossWorks, a J-link Ultra+ and a NXP QWKS-SCMIMX6DQ Quickstart board. I am having trouble getting the jtag to connect and halt the processor. The Quickstart board powers up and boots Linux fine, but I need to be able to load and run my own code via the jtag. I have installed the latest version of both Rowley and Segger code, and have configured Rowley to used the latest version of the SEGGER jLinkARM.dll. I see the following in the out…