You might be a child in the 70s if:

The Rocketry Forum

Help Support The Rocketry Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
I learned 6809 Machine Code ! I later learned 8088 code, it was backwards Byte wise from MOTO. Both chips where 8 bit sudo 16 bit processors. IIRC the 8086 was a full real 16 bit over the IBM PC using the 8088.
I very strongly suspect that you've misremembered that. The 8086/8088 is an Intel chip with a "philosophically" similar architecture to the 8080 (and 8085 and Z80) but not byte compatible. That architecture was completely different from the Motorola architecture of the 680x series that culminated in the 6809.

There's more to a processor's architecture than it's register set, yet that alone shows how radically different the 6809 and 8086 are.
1713454044326.png1713454274920.png
 
Well, that hardware had ASCII built into it. Such as a Chip that contained an ASCII encoder built into its "mask".

So it would take the matrix of a Key board of switches and turn it into ASCII code to feed your processors or other MPUs handling the peripherals.
I guess since you wrote your own programs you don’t have to worry about compatibility.
 
I very strongly suspect that you've misremembered that. The 8086/8088 is an Intel chip with a "philosophically" similar architecture to the 8080 (and 8085 and Z80) but not byte compatible. That architecture was completely different from the Motorola architecture of the 680x series that culminated in the 6809.

There's more to a processor's architecture than it's register set, yet that alone shows how radically different the 6809 and 8086 are.
View attachment 641209View attachment 641211

Yes, I said the 8088 was "Backwards" from the Moto designs. Also the Low Byte / High Byte vs the High Byte / Low byte stuff if I recall correctly.
 
Yes, I said the 8088 was "Backwards" from the Moto designs. Also the Low Byte / High Byte vs the High Byte / Low byte stuff if I recall correctly.
OH! My bad. Opposite endedness, of course.

I read "backwards Byte wise from MOTO" as "backwards [compatible] Byte wise [machine language] from MOTO". :facepalm:


Wow a company would NEVER provide that much documentation for there computer these days!
That's not the half of it. They actually published the entire schematic. You might be interested in part five of sheet 1. That's the keyboard matrix. The TRS-80 decoded the matrix to produce ASCII(ish) codes in software, as you suggested. An encoder chip takes that burden off of the CPU and frees up some memory address space, but adds a little bit of cost.

Anyway, as to "A company would never provide that much documentation...", well, most wouldn't.

Arduino UNO R3:
1713457150332.png

This is for one of the Raspberry Pi models. But Arduino and R-Pi are both not for profit, and are both a lot less complicated than, say, a PC motherboard.
 
Wow a company would NEVER provide that much documentation for there computer these days!

Not only did Rat Shack, but Apple II and IBM PC published the total docs. The Idea was so after market manufactures of hardware add-ons and software would support their product and make it popular; AND IT WORKED.

IBM in around '86/87 decided to make a new product that was proprietary. The IBM PSII. Nothing was disclosed unless you licensed it and/or Authorized.

Same thing Jobs did to the MAC and closed it up. IBM's was a flop and the original MACs caused Apple bankruptcy*. IBM's problems in PCs finally caused them to sell the line to Lenovo in China.

They should have stayed open docs, as Wozniak had always wanted.

*Edit: Jobs left at that time and created the NEXT PC, that went over so well that hardly anyone remembers it. Apple Hired the Pepsi CEO and he put Caffeine into the MACs to get them to sell , well they did hire the CEO...
 
Last edited:
And DEC made the same mistake with their PRO 300 line, a contemporary of the PC-XT, far superior hardware, very poor choice of OS, little third party software, and as far as I know not a shred of third party hardware. A fast and utter market flop that helped put DEC out of business (one of several factors). But of course, we're up to '83 now.
 
And DEC made the same mistake with their PRO 300 line, a contemporary of the PC-XT, far superior hardware, very poor choice of OS, little third party software, and as far as I know not a shred of third party hardware. A fast and utter market flop that helped put DEC out of business (one of several factors). But of course, we're up to '83 now.

I remember that and have seen one in person.
 
Wow a company would NEVER provide that much documentation for there computer these days!
They do provide data for the chips, and companies producing the boards will have everything well-documented.

I did a project about five years ago using a Zync chip (dual-core CPUs and FPGA on the one chip). Total amount of data sheets I had to consume for that was north of 15k pages. Plenty of good documentation :) . It wasn't just the main chip if course. There were multiple other memories, Ethernet, USB, programming, power supplies and sequencing to deal with too.
 
Last edited:
Wow a company would NEVER provide that much documentation for there computer these days!
As somebody who spent a decade doing reference designs for Intel consumer PC's, we gave away everything. Sure, you don't get the micro-code, but you could get the schematics and all the board collateral for you to do the HS paths or just copy and paste them. We would build and give away about 10k working units with full design/build collateral to "seed" the ODM's so they can do things like add a USB port and call it their own design.
 
...if you remember where you were and what you did on 7/7/77.
Our local temperature reached 100 degrees F / 38 C that day here in southern Virginia.
 
There was a blizzard in 64 in Detroit too. I was 8. In 78 Detroit must have been hit hard. I don't remember the winter of 78 being bad in Ann Arbor.

Toledo was totally buried. Our neighborhood was impassable by car for over a week. Lucky we had power.
It was down wind of many farm fields as a new development.
 
...if you remember where you were and what you did on 7/7/77.
Our local temperature reached 100 degrees F / 38 C that day here in southern Virginia.
Wow, I know where I was that day, but no one was making a big deal over the date. I just know where I was in July that year.
 
"Big-Endian" vs. "Little-Endian"
My life has been savaged by endians! 😉

I started programming in 6502 machine code without an assembler(!) in '78. The MOS Technology 6502 (used in the first Apple and Atari computers in the 70's ) is the ancient ancestor of the ARM processor. My boss at GE in the early 80's was one of the 6502 designers. I stuck with Motorola processors for many years (68HC11, 68000 series). Then came the 80x86 nightmare of porting OS code and printer drivers in mixed C and assembler into 68000 code. My face is twitching uncontrollably as I'm typing this. 🤪

I've avoided Intel ever since. I circled back to Moto/Freescale embedded processors and then ARM processors of all sizes. C/C++ mostly with some assembler.
 
Back
Top