When JLink Commander is started, sometimes the communication with the target chip succeed, sometimes it fails.
In a batch of ten boards, up to eight fails. Desoldering the processors and swap them between a good and a bad board show that the problem follows the target chip and not the board itself.
The boards schematics follow the Atmel ATSAM3S-EK.
When looking at the signals on the oscilloscope I see a difference on the serial data coming from the ATSAM3S between good and bad units.
In both cases there is response, but the bit pattern look different, although the input from the J-Link look the same.
All the ATSAM3S are bought at the same time and have the same production number on the cover (week and year).
I have tried multiple J-Links, using latest and a couple of older firmware, but same result.
A good one using an old J-Link ...
SEGGER J-Link Commander V4.58 ('?' for help)
Compiled Nov 29 2012 14:18:25
DLL version V4.58, compiled Nov 29 2012 14:18:06
Firmware: J-Link compiled Jul 30 2008 11:24:37 ARM Rev.5
Hardware: V5.20
S/N: 10003175
OEM: IARKS
VTarget = 3.313V
Info: TotalIRLen = 4, IRPrint = 0x01
Info: Found Cortex-M3 r2p0, Little endian.
Info: TPIU fitted.
Info: FPUnit: 6 code (BP) slots and 2 literal slots
Found 1 JTAG device, Total IRLen = 4:
#0 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
Cortex-M3 identified.
JTAG speed: 100 kHz
J-Link>
... and a bad one using the same J-Link
SEGGER J-Link Commander V4.58 ('?' for help)
Compiled Nov 29 2012 14:18:25
DLL version V4.58, compiled Nov 29 2012 14:18:06
Firmware: J-Link compiled Jul 30 2008 11:24:37 ARM Rev.5
Hardware: V5.20
S/N: 10003175
OEM: IARKS
VTarget = 3.326V
Info: TotalIRLen = 4, IRPrint = 0x01
****** Error: Could not power up debug port: Control/Status register reads 00000F03
No devices found on JTAG chain. SWD is not supported by this emulator.
Failed to identify target. Trying again with slow (4 kHz) speed.
Info: TotalIRLen = 4, IRPrint = 0x01
****** Error: Could not power up debug port: Control/Status register reads 00000F03
No devices found on JTAG chain. SWD is not supported by this emulator.
J-Link>
The screenshots show the JTAG intial communication occuring right after JLink Commander is started.
Two recordings have been merged to show the difference between the ATSAM3S output data.
In a batch of ten boards, up to eight fails. Desoldering the processors and swap them between a good and a bad board show that the problem follows the target chip and not the board itself.
The boards schematics follow the Atmel ATSAM3S-EK.
When looking at the signals on the oscilloscope I see a difference on the serial data coming from the ATSAM3S between good and bad units.
In both cases there is response, but the bit pattern look different, although the input from the J-Link look the same.
All the ATSAM3S are bought at the same time and have the same production number on the cover (week and year).
I have tried multiple J-Links, using latest and a couple of older firmware, but same result.
A good one using an old J-Link ...
SEGGER J-Link Commander V4.58 ('?' for help)
Compiled Nov 29 2012 14:18:25
DLL version V4.58, compiled Nov 29 2012 14:18:06
Firmware: J-Link compiled Jul 30 2008 11:24:37 ARM Rev.5
Hardware: V5.20
S/N: 10003175
OEM: IARKS
VTarget = 3.313V
Info: TotalIRLen = 4, IRPrint = 0x01
Info: Found Cortex-M3 r2p0, Little endian.
Info: TPIU fitted.
Info: FPUnit: 6 code (BP) slots and 2 literal slots
Found 1 JTAG device, Total IRLen = 4:
#0 Id: 0x4BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
Cortex-M3 identified.
JTAG speed: 100 kHz
J-Link>
... and a bad one using the same J-Link
SEGGER J-Link Commander V4.58 ('?' for help)
Compiled Nov 29 2012 14:18:25
DLL version V4.58, compiled Nov 29 2012 14:18:06
Firmware: J-Link compiled Jul 30 2008 11:24:37 ARM Rev.5
Hardware: V5.20
S/N: 10003175
OEM: IARKS
VTarget = 3.326V
Info: TotalIRLen = 4, IRPrint = 0x01
****** Error: Could not power up debug port: Control/Status register reads 00000F03
No devices found on JTAG chain. SWD is not supported by this emulator.
Failed to identify target. Trying again with slow (4 kHz) speed.
Info: TotalIRLen = 4, IRPrint = 0x01
****** Error: Could not power up debug port: Control/Status register reads 00000F03
No devices found on JTAG chain. SWD is not supported by this emulator.
J-Link>
The screenshots show the JTAG intial communication occuring right after JLink Commander is started.
Two recordings have been merged to show the difference between the ATSAM3S output data.