Xiaofan Chen wrote: > > Please create two matrixes of recommended firmware versions for each > > hardware somewhere in the code: .. > > Please don't build these matrixes using the mailing list. > > I do not think this is strictly necessary for V7/V6 and below, > just ask the user to update to the latest Segger FW which > is included in the Segger software package. > > For V8, there are too many versions to track. > http://www.segger.com/j-link-older-versions.html > > Anything below 4.10 is not worth tracking, for example. > I would even argue that we do not need to track any > old version once the patch is integrated. Just track > from V4.46f onwards for V8 (current release version). > > Right now we only know 4.22g does not work with > the patched version.
I lost track of your intensive testing, I'm happy that you have the overview! :) The point is to please move the results into the code instead of sending them to the mailing list. You mention two versions so far: 4.46f and 4.22g. So someone please add at least these into the code with appropriate warnings. The talk about arrays/matrixes is because these checks must be added in a way that makes it trivial for anyone who has done testing to change the actual source code and push a commit with the updated information, without having to create a horrible long list of if() else if() statements. This is critical in order to keep the information accurate. //Peter ------------------------------------------------------------------------------ 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 OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
