On Tue, May 29, 2012 at 4:32 PM, Xiaofan Chen <[email protected]> wrote:
> On Tue, May 29, 2012 at 2:02 PM, Liviu Ionescu <[email protected]> wrote:
>>
>> On May 29, 2012, at 08:41 , Xiaofan Chen wrote:
>>
>>> And it seems to me that V7/V6 work with or without the patch
>>
>> did you keep track of the FW version for each test?
> Yes since I use the latest FW for the V6 and V7.
>
>> I think that a statement like the above is too general, and you
>> should always mention the FW version.
>
> For V6/V7 and below, it seems to me Segger has not provided
> FW change for more than a year. It is not that unreasonable
> to ask V6/V7 J-Link users to update to the latest FW if some
> old version does not work with OpenOCD but the recent FW
> works with OpenOCD.
>
> V8 is a bit different since it is a moving target and Segger
> keeps updating the FW with some versions not working with
> OpenOCD and some versions working with OpenOCD.
> So we do need to track V8 J-Link.
>
>> I don't know how Segger organised their development, but I guess
>> that the FW version might be more relevant than the HW version,
>> i.e. if a FW version runs on both V8 and V7, then the features
>> (and bugs) would be similar.
>
> As stated in the above, FW of V6/V7 has not been updated
> for more than a year. FW of V8 keeps been updated.
Also HW revision is quite important.
This is the output for V7 with the Segger utility using their
beta Mac OS X version. You can see that V7 lacks
certain functionality that Segger issues a warning to the user.
+++++++++++++++++
mymacmini:mac xiaofanc$ ./start
SEGGER J-Link Commander V4.43c ('?' for help)
Compiled Feb 22 2012 20:13:08
DLL version V4.43c, compiled Feb 22 2012 20:13:03
Firmware: J-Link ARM V7 compiled Feb 15 2011 11:03:33
Hardware: V7.00
S/N: xxxxxxxx
OEM: MIDAS
Feature(s): RDI
VTarget = 3.274V
Info: TotalIRLen = 9, IRPrint = 0x0011
Info: Found Cortex-M3 r1p1, Little endian.
Info: TPIU fitted.
Info: FPUnit: 6 code (BP) slots and 2 literal slots
*** J-Link V4.43c J-Link V4.43c Warning ***
You are using a J-Link which does not have intelligence
for the selected CPU core (Cortex-M3) in the firmware.
Intelligence in the firmware enables J-Link
to generate sequences for the CPU core.
Without this feature, all sequences are generated by the PC.
Intelligence in the firmware allows higher target interface speeds
and significantly enhances both speed and stability of the
communication with the target CPU.
You can use this J-Link with your target CPU, but we recommend
using a newer model of J-Link / J-Trace.
*** J-Link V4.43c J-Link V4.43c Warning ***
Found 2 JTAG devices, Total IRLen = 9:
#0 Id: 0x3BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
#1 Id: 0x16410041, IRLen: 05, IRPrint: 0x1, STM32 Boundary Scan
Cortex-M3 identified.
JTAG speed: 100 kHz
++++++++++++++++++++++++
Same for V6.
+++++++++++++++++++++++++
mymacmini:mac xiaofanc$ ./start
SEGGER J-Link Commander V4.43c ('?' for help)
Compiled Feb 22 2012 20:13:08
DLL version V4.43c, compiled Feb 22 2012 20:13:03
Firmware: J-Link ARM V6 compiled Feb 1 2011 14:28:14
Hardware: V6.00
S/N: xxxxxxxx
OEM: SAM-ICE
Feature(s): RDI
VTarget = 3.287V
Info: TotalIRLen = 9, IRPrint = 0x0011
Info: Found Cortex-M3 r1p1, Little endian.
Info: TPIU fitted.
Info: FPUnit: 6 code (BP) slots and 2 literal slots
*** J-Link V4.43c J-Link V4.43c Warning ***
You are using a J-Link which does not have intelligence
for the selected CPU core (Cortex-M3) in the firmware.
Intelligence in the firmware enables J-Link
to generate sequences for the CPU core.
Without this feature, all sequences are generated by the PC.
Intelligence in the firmware allows higher target interface speeds
and significantly enhances both speed and stability of the
communication with the target CPU.
You can use this J-Link with your target CPU, but we recommend
using a newer model of J-Link / J-Trace.
*** J-Link V4.43c J-Link V4.43c Warning ***
Found 2 JTAG devices, Total IRLen = 9:
#0 Id: 0x3BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
#1 Id: 0x16410041, IRLen: 05, IRPrint: 0x1, STM32 Boundary Scan
Cortex-M3 identified.
JTAG speed: 100 kHz
++++++++++++++++++++++++++
For V3, warning is even more severe.
++++++++++++++++++++++++++
mymacmini:mac xiaofanc$ ./start
SEGGER J-Link Commander V4.43c ('?' for help)
Compiled Feb 22 2012 20:13:08
*** J-Link V4.43c Warning ***
You are using an older version of the J-Link hardware.
The J-Link you are using is significantly slower than current models
and can not take advantage of some new software features.
You can however still use this older J-Link with this version of the software.
If speed is important, we recommend using a newer model of J-Link / J-Trace.
*** J-Link V4.43c Warning ***
DLL version V4.43c, compiled Feb 22 2012 20:13:03
Firmware: J-Link compiled Feb 20 2006 18:20:20 -- Update --
Hardware: V3.00
S/N: xxxx
OEM: IAR
Feature(s):
VTarget = 3.277V
Info: TotalIRLen = 9, IRPrint = 0x0011
Info: Found Cortex-M3 r1p1, Little endian.
Info: TPIU fitted.
Info: FPUnit: 6 code (BP) slots and 2 literal slots
*** J-Link V4.43c J-Link V4.43c Warning ***
You are using a J-Link which does not have intelligence
for the selected CPU core (Cortex-M3) in the firmware.
Intelligence in the firmware enables J-Link
to generate sequences for the CPU core.
Without this feature, all sequences are generated by the PC.
Intelligence in the firmware allows higher target interface speeds
and significantly enhances both speed and stability of the
communication with the target CPU.
You can use this J-Link with your target CPU, but we recommend
using a newer model of J-Link / J-Trace.
*** J-Link V4.43c J-Link V4.43c Warning ***
Found 2 JTAG devices, Total IRLen = 9:
#0 Id: 0x3BA00477, IRLen: 04, IRPrint: 0x1, CoreSight JTAG-DP (ARM)
#1 Id: 0x16410041, IRLen: 05, IRPrint: 0x1, STM32 Boundary Scan
Cortex-M3 identified.
JTAG speed: 100 kHz
+++++++++++++++++++++++++++++++++++++
>>> Firmware: J-Link ARM V6 compiled Feb 1 2011 14:28:14
>>> It seems to me this is already the latest for V6
>>
>> do you know if V7 is still able to run the latest FW?
> I check my V7 and the latest FW of the same date as V6.
> J-Link ARM V7 compiled Feb 15 2011 11:03:33
>
>> if so, it would be useful to test it with this latest version.
>>
>> perhaps we could put all these findings in a table, with some
>> recommendations for the user which is the latest tested version.
>>
>
> V8 FW is still being updated so we do need to keep track of it.
> For V6/V7 or earlier versions, I do not think it is worth the
> efforts unless Segger updates the FW for then again.
>
--
Xiaofan
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
