“Source code or hex files for the PIC firmware”, to be precise.
They are very “open source” about the PC side drivers and libraries where it applies. Thank you Velleman for that!
And it makes perfectly sense to me. One can get the components, needed to build one of their kits, for pennies these days. Many of these kits could be built on a breadboard style setup, so you don’t even need that custom PCB. But without the PIC code you don’t have a working kit. People who can turn the kit specs into working PIC code are few and far apart (just look how long and hard I’m trying to gather some people behind the Open8055 project … with small but at least some success, if I may say so myself).
IMHO not providing the PIC source code has little to do with copyrights. I think all the Microchip Application Libraries code, used in those firmwares, is perfectly suitable for open source. Microchip Inc’s “license” basically requires the code to be used on Microchip micro controllers. I think that’s exactly what we all are doing, don’t we?
The real issue is that with that PIC code, one can easily build knock-off’s without actually going through the labor of developing the PIC code. Let me give you an example:
You can buy a PIC-KIT 3 “knock-off” programmer from Olimex, that costs less than the original one done by Microchip. Why is that? Because Olimex didn’t have to develop either the PIC firmware or the actual design of the hardware. They just copied everything and didn’t have to pay someone like me to write code for them. The thing connects to the Microchip IDE just like the original … no surprise … it runs the “original” firmware inside. Why does Microchip not care? Because their core business is selling micro controllers, not programmers. If the availability of cheap programmers, that come without a single piece of paper or any install CD, can boost their micro controller sales, they win. That is why they put their programmer design and PIC firmware out there in the open. A guy like me doesn’t need an install CD or printed setup instructions. For those saved $20 I go and buy another 5 “test subjects”, so Microchip still gets some money after all. Oh, and that Olimex programmer has a Microchip controller inside it too … they made a buck on that, didn’t they?
The case of Velleman is different. If you had that PIC code, you could build one of their kits for a fraction of what it costs. Microchip would still earn some of that money, but Velleman would earn none of it.
The case of the Open8055 firmware is again a little different. The K8055/K8055N PCB is way beyond something, that could easily be recreated on a breadboard. So even if you have that Open8055 firmware, you’re not getting anywhere without actually buying a K8055/K8055N kit.
This is how it all makes sense to me. Maybe I forgot to tell you that my original profession had nothing to do with software or electronics. I was a bank clerk back in the 80’s in the old country (Germany). Does that explain why I reverse engineer policies from a “money flow” point of view?
Just my $.02
Jan