Hi,
I used a J-Link connected via SWD to a propretary hardware to develope an application using Atmel Studio, and until now there have been no problems related to the connection with the card.
Recently I tried, before the first copies of the device were released, to enable software protection that works too much, in the sense that it prevents the target from connecting to copy the software but it no longer allows me to restore the initial status with a mass erase.
Below is a log of the operations performed with j-link:
SEGGER J-Link Commander V6.50b (Compiled Sep 6 2019 17:58:27)
DLL version V6.50b, compiled Sep 6 2019 17:57:35
Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled May 17 2019 09:50:41
Hardware version: V9.20
S/N: 59201629
License(s): GDB
VTref=3.329V
Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: ATSAMD51J20
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "ATSAMD51J20" selected.
Connecting to target via SWD
InitTarget() start
InitTarget()
Device will be unsecured now.
Mass erase done!
.
.about 240 “Mass erase done!”
.
Mass erase done!
InitTarget() end
InitTarget() start
InitTarget()
Device was not unsecured. No action performed.
User selected to not unsecure the secured device. Debugging is not possible.
InitTarget() end
InitTarget() start
InitTarget()
Device was not unsecured. No action performed.
User selected to not unsecure the secured device. Debugging is not possible.
InitTarget() end
InitTarget() start
InitTarget()
Device was not unsecured. No action performed.
User selected to not unsecure the secured device. Debugging is not possible.
InitTarget() end
Cannot connect to target.
J-Link>
Does anyone have any idea how to get out of this problem?
Thanks, Paolo.
I used a J-Link connected via SWD to a propretary hardware to develope an application using Atmel Studio, and until now there have been no problems related to the connection with the card.
Recently I tried, before the first copies of the device were released, to enable software protection that works too much, in the sense that it prevents the target from connecting to copy the software but it no longer allows me to restore the initial status with a mass erase.
Below is a log of the operations performed with j-link:
SEGGER J-Link Commander V6.50b (Compiled Sep 6 2019 17:58:27)
DLL version V6.50b, compiled Sep 6 2019 17:57:35
Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled May 17 2019 09:50:41
Hardware version: V9.20
S/N: 59201629
License(s): GDB
VTref=3.329V
Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: ATSAMD51J20
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>
Device "ATSAMD51J20" selected.
Connecting to target via SWD
InitTarget() start
InitTarget()
Device will be unsecured now.
Mass erase done!
.
.about 240 “Mass erase done!”
.
Mass erase done!
InitTarget() end
InitTarget() start
InitTarget()
Device was not unsecured. No action performed.
User selected to not unsecure the secured device. Debugging is not possible.
InitTarget() end
InitTarget() start
InitTarget()
Device was not unsecured. No action performed.
User selected to not unsecure the secured device. Debugging is not possible.
InitTarget() end
InitTarget() start
InitTarget()
Device was not unsecured. No action performed.
User selected to not unsecure the secured device. Debugging is not possible.
InitTarget() end
Cannot connect to target.
J-Link>
Does anyone have any idea how to get out of this problem?
Thanks, Paolo.