Hi Martin. I absolutely agree with you on OpenOCD (Open-On-Chip-Debugger) is for more than killing bugs. My main reason for suggesting the 'bug' is that the 'D' in OpenOCD is an abbreviation for "Debugger". -But it's not just a flash-tool either. OpenOCD differs from other flash-tools by being a debugger, which makes it stand out a lot (in addition to being universal for many targets and many platforms).
A more "describing" name would probably be "OpenOCT", Open-On-Chip-Tool, since it has multiple purposes. That said, I do not think OpenOCD should be renamed; it's had its name for a long time and everyone using it knows it by that name. Maybe it would be better to 'zap' the bug by a "flash" of lightning ? ;) -That would include both debugging and flashing - but icons / logos should also be easy to understand. I do like that Kristof is focusing on shape without color; color can easily be added and it can easily make a shape more clear. Personally, I'm using it for flashing Cortex-M based microcontrollers most of the time, but at times, I do find myself using it as a debugger and for investigating data inside a MCU's RAM or registers (also a kind of debugging; eg. verifying that my data are correct - or trying to figure out what went wrong). I'm only using it for "unlocking" when a MCU is locked from a board manufacturer; this is only necessary on flashing the first time, so I consider that to be a part of 'flashing', though technically it isn't. One word that is seen often in relation to OpenOCD, is 'hacking' (meaning "making modifications to something, in order to get it to function properly"). Basically that would more or less cover both flashing and debugging, though it might remove the focus from flashing and debugging. Love Jens On Fri, 9 Oct 2020 15:49:45 -0300, Martin Meier wrote: > Hi guys, > I haven't developed anything for the OpenOCD, so I don't think my > vote should count as a developer. Bus as a "customer", I'd like to > say that I like the logo idea from opensource/openhardware > communities, because of the relation with the "OPEN" word: > > https://reelyactive.github.io/images/osi-oshw.png > > Maybe something like this (but not made in m$paint): > > or this (unlock your mcu full potential!): > > > Regarding the existing options, I like the options 4 (more dynamic) > and 5 (more emphasis on the "OPEN" side). > Regarding Jens options (bug image), I liked it at first, but after > thinking a while... Although openOCD is a "debugger", it can also be > used in production (the reason I found it) and embedded development > is not only about killing bugs... > But that's just my 2 cents... > > Thanks for the amazing work! > > Martin > > > Em qui., 8 de out. de 2020 às 13:19, Spencer Oliver > <s...@spen-soft.co.uk> escreveu: >> On Thu, 8 Oct 2020 at 10:35, <kristof.mul...@telenet.be> wrote: >>> Dear OpenOCD developers, >>> >>> Let's have a look again at choosing a logo for OpenOCD? >>> As you might remember, I've drawn a couple of samples, >>> which you can find here: >>> >>> https://new.embeetle.com/figures/logo_matrix.png >>> >>> Some of you already voted for a logo: >>> >>> - Tomas Vanek >>> - Anton Krug >>> - Antonio Borneo >>> - Andreas Bolsch >>> - Tommy Murphy >>> - Vladimir Zapolskiy >>> - Oleksij Rempel >>> - Jan Matyas >>> - Paul Fertser >>> - Tarek Bouchkati >>> >>> The votes are also listed on the figure (see link at >>> the top). Please feel free to: >>> >>> - Change your mind (just send me a mail to >>> change your vote). >>> >>> - Make suggestions for a new logo. I'm happy >>> to make new drawings. >>> >> >> thanks they look great - my vote is A6. >> >> Spen >> _______________________________________________ >> OpenOCD-devel mailing list >> OpenOCD-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/openocd-devel > > _______________________________________________ > OpenOCD-devel mailing list > OpenOCD-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openocd-devel _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
