Search Results

Hi, We are using JLINK_PIN_Override() when perform unlocking of Secure JTAG on Cortex M7 (NXP iMX RT1050) To unlock Secure JTAG Controller (SJC), we need to set JTAG_MOD=1, then perform some actions, then set JTAG_MOD=0 But we can't keep HIGH level on pin 17, because first instruction JLINK_JTAG_WriteIR() resets pin to "RELEASE" state. Our Default.JLinkScript : C Source Code (30 lines) Our question: how we can set pin 17 to HIGH level, and not reset this pin after JLINK_JTAG_WriteIR() instructio…

Hi, We are trying to implement Challenge/Response Mechanism using Segger J-Link and VisualGDB on i.MX-RT1051 This mechanism is used to lock JTAG interface in manufacturing process to increase security of system. Authorized re-activation of JTAG interface possible in field-returned devices. Description: nxp.com/docs/en/application-note/AN4686.pdf NXP recommends Lauterbach TRACE32 debug tool. Segger J-Link is not supported yet. Mechanism is very simple, and described in 2.1.2 Debug flow when Secur…

Hi, We got same error again. Records in VisualGDB log right before failure: Source Code (24 lines) We can repeat this failure: C Source Code (24 lines)If we set breakpoint on line #9 (memcpy), and then do "Step over", we will get described failure. We reproduced this fault many times in different conditions, so we can provide more information. Our environment: - Visual Studio Community 2015 Version 14.0.25431.01 Update 3 - VisualGDB Custom Edition version 5.4 (Preview 3, build 2193) - SEGGER J-L…

Hi, We are using Segger J-Link to gebug our firmware on NXP LPC4078 microcontroller. IDE: VisualStudio 2015; VisualGDB 5.4 preview 3 build 2193 (latest at this moment). JLinkARM.dll V6.32d (DLL compiled May 25 2018 17:03:12) Sometimes gebugging process fails with error: Source Code (5 lines) This error repeates infinitely, if we try to stop debugging, read registers, set breakpoints, etc (after any command to gdb server). We can't determine cause ot this bug, but usually it occurs when we set ma…