4 ms·
I can tell stories about programming things like this. It is not as easy as you might think. Here is how we used to do it: 1. Draw a flow chart on paper 2.
by znpy 10y ago
I can tell stories about programming things like this.
It is not as easy as you might think.
Here is how we used to do it:
1. Draw a flow chart on paper
2. Translate the flow-chart to assembly source.
3. Keeping the processor data-sheet in your left hand, hand-translate assembly code into opcodes, by hand. Compute relative jumps by hand. Do not use a compiler. Be the compiler.
4. Now that you have your opcodes, get your board.
4.1 Set the starting address (it was 1800_h for me)
4.2 input opcode (two hex numbers, one byte)
4.1 increment address (the '+' key is for that)
4.3 if finished goto 5
4.4 goto 4.2
5. set address back to starting point (like 1800_h)
6. Run your code! (press 'go')
Now... 60% of the times, it fails every time. But I miss doing this kind of exercise :)
- Johnythree 10y agoYou left out... Erase an eprom with ultraviolet Drive for miles to a friends place to use his eprom programmer drive back home, and plug it in then swear a lot when it still doesn't work.. ah, the memories... (that was with a hand-wired board and an MM57109 before the first microprocessors were available)
- znpy 10y agoMy unit was already programmed... I guess I was lucky! :)
- linker3000 10y ago...and I was that 'friend' with the EPROM programmer board for the Commodore 64 and a UV eraser. My office (bedroom) was very busy at weekends.
- nickpsecurity 10y agoThat's the hardcore way. Brinch Hansen used to program constrained hardware in a high-level, type-safe language with hand-coded, equivalent assembly side-by-side. It was a debated approach then but claimed some benefits of both. Recent work uses dependent types, theorem provers, and so on to do low-level stuff with tooling catching assembly-level errors and/or synthesizing it directly from specs without compilers. Also stuff like ATS lang and Ocaml subsets being used on 8-bitters. So, days of hardcore methods like yours are over and unnecessary outside an existential experience reliving history. :) Or certain subversion-resistant schemes. That's out of scope here, though.