Like parents standing on the porch waiting to see their children off to their first day of school we waited for what comes next in a release to production. Among our children: The C116 ($49 Sinclair killer), the C264 ($79 office computer), and the V364 – The computer with an interactive desktop that could speak (courtesy of [John Fegans] who gave us the lion’s share of what made the C64 software great).
Something happened then, and by something I mean nothing. Nothing happened. We waited to assist in production builds and stood ready to make engineering change notices, and yet nothing happened. It was around this time that [Mr. Jack Tramiel] had left the company, I know why he left but I can’t tell due to a promise I made. Sadly, without [Tramiel’s] vision and direction the new product releases pretty much stopped.
Meanwhile in Marketing, someone came up with the idea to make the C264 more expensive so that they could then sell it for a prohibitively high price in. They changed the name, they told us to add chips, and they added software that (at best) wasn’t of interest to the users at that price. They wanted another C64, after all it had previously been the source of some success. Meanwhile the C116 and the V364 prototypes slowly melded into the random storage of a busy R&D lab. We literally didn’t notice what had happened; we were too busy arguing against abominations such as the C16 — a “creation” brought about by a shoving a TED board into a C64 case (the term inbred came to mind at the time).
My introduction to electronic manufacturing was as a production technician at Pennsylvania Scale Company in Leola PA in the early 1980’s. I learned that to work on what I wanted to work on I had to get my assigned duties done by noon or thereabouts. The most important lesson I had learned as a TV repairman, other than not to chew on the high voltage cable, was to use your eyes first. I would take a box of bad PCB’s that were essentially 6502 based computers that could count and weigh, and first go through inspecting them; usually the contents were reduced 50% right off by doing this. Then it was a race to identify and fix the remaining units and to keep my pace up I had to do my own desoldering.
It worked like this; you could set units aside with instructions and the production people would at some point go through changing components etc. for you or you could desolder yourself. I was pretty good at hand de-soldering 28 and 40 pin chips using a venerable Soldapulit manual solder sucker (as they were known). But to really cook I would wait for a moment when the production de-soldering machine was available. There was one simple rule for using the desoldering station: clean it when done! Failure to do so would result in your access to the station being suspended and then you might also incur the “wrath of production” which was not limited to your lunch bag being found frozen solid or your chair soaked in defluxing chemicals.
I suppose I can take credit for introducing the super awesome [Fran Blanche] to Hackaday’s very own crotchety old man and Commodore refugee [Bil Herd]. I therefore take complete responsibility for [Fran] and [Bil]’s Dinosaur Den, the new YouTube series they’re working on.
The highlight of this week’s episode is a very vintage Rubicon mirror galvanometer. This was one of the first ways to accurately measure voltage, and works kind of like a normal panel meter on steroids. In your bone stock panel meter, a small coil moves a needle to display whatever you’re measuring. In a mirror galvanometer, a coil twists a wire that is connected to a mirror. By shining a light on this mirror and having the reflected beam bounce around several other mirrors, the angle of the mirror controlled by the coil is greatly exaggerated, making for a very, very accurate measurement. It’s so sensitive the output of a lemon battery is off the scale, all from a time earlier than the two dinosaurs showing this tech off. Neat stuff.
One last thing. Because [Bil] and [Fran] are far too proud to sink to the level of so many YouTube channels, here’s the requisite, “like comment and subscribe” pitch you won’t hear them say. Oh, [Bil] knows the audio is screwed up in places. Be sure to comment on that.
There is a wide assortment of cheap development (dev) boards for Complex Programmable Logic Devices (CPLD), the smaller cousin of the Field Programmable Logic Array (FPLA)
Using an inexpensive board and the development software that’s free to download from the major programmable companies such as Xilinx and Altera, the only additional thing needed is a programmer module. Cheap ones are available on Ebay but I am hoping that someone takes the time to teach an ARM/Arduino to step in as a programmer.
I have a small collection of dev boards including some Ebay specials and also designs I did a few years ago to choose from. For today I am grabbing a newer board that has not been fully checked out yet; an Altera Max V device. I have stuffed the CPLD, the clock oscillator, some LED’s and part of the onboard power supply along with the JTAG header needed to program the CPLD and that’s about it.
Yeah I am still a little pissed that the competition is still around and we aren’t, and by “we” I mean Commodore Business Machines (CBM). It was Commodore that had the most popular home computer ever in the C64 (27 Million) and it was a team of MOS engineers after all, that had the idea to make a “micro” processor out of a 12 square inch PCB.
Of course they did work at Motorola at the time and “Mot” did not want anything to do with a reduction of the profit margin on the pie-plate size processor. Of course MOS got sued by Motorola but that was an average Tuesday at MOS/CBM. I absolutely credit CBM with buying the MOS Technologies chip foundry, as together we could make our own processors, graphics chips, sound chips, memory controllers, and programmable logic.
With this arsenal at our call we didn’t have to make compromises the way other companies did such as conforming to the bus spec of an industrial standard 6845 or having to add extra logic when a custom extra pin would work. We could also make sprites.
The compromise we did have to make when designing was cost, and I mean the kind of cost reduction where finding a way to save a dollar ($1USD) saved millions in the production run. I knocked $.90USD out of a transformer one day and I couldn’t focus the rest of the day due to elation.
Cost reduction is a harsh mistress however as you can’t just do it a little some of the time or only when you want to. The mental exercise of multiplying anything times a million was always there, it made it hard to buy lunch — I’d be blocking the lunch line while figuring the cost of a million tuna sandwiches FOB Tokyo Continue reading “Programmable Logic I – PLA/PAL”→
Ever since I received my PSOC 4 Pioneer kit from Cypress I have wanted to play with this little mixed-signal Programmable System-on-Chip (PSOC) developer board. I love developer boards, providing that they are priced in a way to entice me to not only open my wallet but also make time in a busy schedule. I think my kit was free after winning a swag bag from Adafruit that they themselves obtained at the Open Hardware Summit and gave away on their weekly streamcast. Ultimately it was the invitation to beta test datasheet.net which also was included in that pile of swag that led to my getting involved with Hackaday.
What is Programmable System On Chip?
So what is a PSOC 4? A quick summary is that it’s based on an ARM Cortex reduced instruction set processor (RISC) and is somewhat capable of supporting shields based on the Arduino footprint, and it also uses a bright red PCB that I have come to associate with a Sparkfun PCB. What doesn’t show is the fact that this programmable system on chip has programmable analog function blocks in addition to programmable digital logic blocks. There is also some supporting input/output circuitry such as a multicolored LED and a capacitive touch sensor directly on the PCB.
This is an intriguing amount of programmability, so much so that Newark/Element 14 highlighted a “100 projects in 100 days” event on it.
Enter the IDE
Over the years I have had to create or install many Integrated Development Environments (IDE) that linked hardware to software. Knowing that you had to, and how to, implement an IDE was part of being an engineer. Nowadays with the Arduino type environment the user has an IDE pretty much as soon as they click on the executable which I find to be one of the best aspects of the genre. It was so quick in fact that I was able to get my teenaged son into writing his first program even before he remembered to do massive eye-rolls and make sounds of utter disdain. He did give up however, just shy of learning how to have the Arduino make sounds of disdain on his behalf.
How hot are your key components getting? There’s a good chance you’ve built a project and thought: “Well I guess I better slap a heat sink in there to be safe”. But when working on a more refined build you really need to calculate heat dissipation to ensure reliability. This is actually not tough at all. The numbers are right there in the datasheet. Yes, that datasheet packed with number, figures, tables, graphs, slogans, marketing statements, order numbers… you know right where to look, don’t you?
Hackaday has you covered on this one. In under 10 minutes [Bil Herd] will not only show how easy these calculations are, he’ll tell you where to look in the datasheets to get the info you need quickly.