On Tue, May 29, 2012 at 9:22 PM, Xiaofan Chen <[email protected]> wrote: > On Tue, May 29, 2012 at 8:13 PM, Liviu Ionescu <[email protected]> wrote: >> >> On May 29, 2012, at 14:01 , Xiaofan Chen wrote: >> >>> For V8, there are too many versions to track. >> >> for V8, at least based on my experience, it would be useful to >> mention in the manual which was the latest version tested. > > I do agree with you here. So we can say 4.46f is the latest > release version we tested. Since Segger does not archive > the beta version, there is no point to mention the beta version > (4.47h is the current beta version). > > V8 4.46f: J-Link ARM V8 compiled May 3 2012 18:36:22 > > V8 4.22g is known to not work even with the patch. > 4.22g FW version string: J-Link ARM V8 compiled JAN 31 2011 18:34:52 > > If needed, V6/V7 can be documented as well. I am not > so sure what is the corresponding version. But the > version stings are as following. > > V6: J-Link ARM V6 compiled Feb 1 2011 14:28:14 > V7: J-Link ARM V7 compiled Feb 15 2011 11:03:33 > > V3 can be documented as well. > V3: J-Link compiled Feb 20 2006 18:20:20 -- Update -- > > Spen: could you get the latest version FW string for > your V5, and double confirm my V6 string? Thanks. > > I know you have the two working but they may not > be the latest version. > V6: J-Link ARM V6 compiled Jun 30 2009 11:04:04 - working > V5: J-Link compiled Jul 30 2008 11:24:37 ARM Rev.5 - working
If that is too detailed, we can just say please use version 4.46f to update the FW for V1-V7 since that will update them to their latest FW version up to (actually all before) 4.46f. 4.46f is not the first version to get V6/V7 to the following state but it will update the existing V6/V7 to the following version if they are not already there. V6: J-Link ARM V6 compiled Feb 1 2011 14:28:14 V7: J-Link ARM V7 compiled Feb 15 2011 11:03:33 >> the point is that after we release a version, Segger may >> release incompatible versions, and if something goes wrong, >> the user needs to know to whick of the many Segger versions >> to revert. > > Yes. This is good to have. BTW, since you have done quite extensive test on V8, did you record the version string versus Segger software version? >> I just sent my first patch to the openocd.texi file, documenting >> the already implemented J-Link commands, I can add the version >> notice there too, if agreed. > > That is a good place to put. But I think Peter wants to have it > in the codes, say to put in the version check patch, that is > good proposal as well. -- 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
