- #OS9 68K EMULATOR MAC MACOS ZIP FILE#
- #OS9 68K EMULATOR MAC MACOS FULL#
- #OS9 68K EMULATOR MAC MACOS SOFTWARE#
- #OS9 68K EMULATOR MAC MACOS CODE#
I used a Dragon 32 from 1982 to 1988, and knew the machine and OS inside out.
The problem with Sir Clive is that you could give him any amount of cash and he'd find a way to spend it inventing something. Even if sales hadn't fallen, Sinclair would have failed. Sinclair failed because the Spectrum was bankrolling all of their ill thought out projects. We also mustn't confuse the fall of Sinclair with these changes in the market. People who had wanted computers already had them, and the market was crowded. It wasn't CD players, it was market forces. In short it was a complex situation that was over simplified in Micro Men. Even Acorn had retreated to the safety of the education market where they had a considerable niche. Your Dragons, Orics, etc had all vanished. Walk into a branch of Dixons by 1986 and your choice would have simply been Amstrad, Spectrum, Commodore.
#OS9 68K EMULATOR MAC MACOS SOFTWARE#
All the smaller players were squeezed out as evidenced if you look at hardware and software sales across the period. Sinclair were already dominant, the C64 was having its first proper Christmas and Amstrad had muscled their way in with a very aggressive strategy. The real problem was the market was flooded with different models from different companies.īy Christmas '84. You wouldn't see much change from £500, which was way above the cost of these home micros. Indeed they were still excruciatingly expensive. I guess they were eventually outcompeted by those more specialist stores and decided to focus on their core business.Ĭhristmas '84 was tough for computer companies, but I'm not sure it was CD Players that did it. This was all before we had a local Jessops, Virgin Megastore and HMV though, and (e.g.) Boots music range slowly degenerated to a single pitiful rack of CDs before disappearing. In fact, looking back, they were almost like a mini department store back then.
They even sold homeware and electronics like TVs and hifis. They even had their own-brand equipment(!). beer not software!) and equipment there too- I'm sure they were still selling that well into the nineties. My Dad even used to buy his home brew kits (i.e. gimmicky camera filters I thought looked cool but couldn't afford nor use with my Instamatic(!)) My local branch (e.g.) also had a good range of both blank and pre-recorded cassettes in the early 80s, alongside more photo stuff (e.g.
#OS9 68K EMULATOR MAC MACOS ZIP FILE#
I've included a quick and dirty C program in the ZIP file below to patch up the binary after linking."I was starting to wonder if my memories of the 'lotions and potions' retailer selling computers was made up, its so different from what they normally sell."īoots used to sell a lot wider range of products in general back then. Otherwise the USB programmer won't accept the firmware.bin file.
#OS9 68K EMULATOR MAC MACOS CODE#
I'm still reading up on all the differences but it makes bootstrap code for 'standard' ARM totally inapplicable.Īs for NXP-specific differences: not mentioned explicitly on ezSBC's website, but buried in the lpc1347 user manual, is the fact that one must put a 32-bit checksum in the first reserved vector 0x1C to validate the code. They also don't have nearly as many contexts as traditional ARM (IRQ, FIQ, etc.).
One thing that isn't spelled out anywhere is that the Cortex-M chips are very different from traditional ARM chips in a lot of ways for instance, the vector table isn't composed of branch instructions - it's just a list of absolute addresses, like the old 68000 (and at vector 0x0, just like the 68000, is the initial system stack pointer value). I had to modify the startup.S, main.S and linker script to fit the LPC1347 memory map and peripheral registers. The best I could find was some for the related LPC1766, which was close enough for me to eventually figure it out.
#OS9 68K EMULATOR MAC MACOS FULL#
However, it took me two full nights' worth of searching online to find any kind of 'Hello World' reset startup code for the LPC134x chips. This chip has a neat built-in ROM that makes the chip virtually unbrickable - pull a certain pin on power-up and the chip appears as a USB flash drive, and you just paste in a new 'firmware.bin' file with your code, reset and it's reprogrammed. I like using a simple text editor and command-line toolchain but since most ARM vendors have wrapped up all the details of their chip startup in wizards within their huge IDEs, it's a pain to figure out just what's happening and what is required to bootstrap a given chip.įor my experiment, I chose the LPC1347 microcontroller from NXP, on a simple board called the ezSBC2. I've been meaning to learn some embedded ARM-fu for years, and just never got around to it since AVRs are just so darn easy (or familiar, in my case). Doing things the hard way sometimes is the best way to learn.