Can anyone help me understand how to begin the task of looking through the MS code (just out of curiosity, to see if I can understand any of it)?

I'm 20+ years out of date, and even then I was working in Fortran or 8-bit assembler, but I thought "how hard can this be?". So I tried following the clues on another couple of threads here.

Downloaded Cygwin, which gives me a nice window with a command line prompt. Stared helplessly at that for a while. Quit.

Next I downloaded the windows zip file of tools. And on second thoughts the Linux version too. Now I'm going round in circles trying to copy what others did in the couple of threads I found. Getting nowhere and not at all aware of what I'm doing...

Grateful for any nudges in the right direction. Please be gentle. Even if I understand in principle what you are saying, syntax will probably fly harmlessly over my head. I have zero knowledge of Unix.

If you just want to look at the code (not change and recompile it) then you don't need Cygwin or the tools.

The whole source for MS2/Extra is included within the MS2/Extra firmware zips in the "ms2extra" subdirectory.The C files are *.cThe C headers are *.hThe assembler files are *.sThe assembler includes are *.inc

gslender wrote:...Exract that zip and follow README.txt and untar the gzip'd archive....

OK. Here I'm stuck. I read this:

cd /tar xfz <path>/tools.tar.gz

... and I don't know what it means.

"cd" looks like "change directory" I vaguely recall from DOS, but the "/" is a mystery.

As for "tar", well having typed "info tar" into Cygwin it looks like i have a day's reading to do.

Anyway, I try to follow the instruction but having entered the tar command with the path to get to the tools.tar.gz file, nothing appears to happen. I don't know if anything ought to happen, but nothing does.

Fortran to C is a pretty big leap (Fortran IV and 77 had no pointers, no data structures and pretty feeble control structures and these are fundamental in C) and 20+ years of accumulated cobwebs won't have helped, so you should probably read up on C programming. Depending on which processor you were using, the assembly language might be surprisingly familiar. In the early '80s the Motorola 6809 was an elegant 8-bit processor that I enjoyed programming. It was quite a nostalgia kick 25 years on to see the Megasquirt processor's assembly language so similar. But if you were working with Z80/808x or 68k, your earlier assembly language experience won't be so applicable.

Plenty to delve into. At some stage, you may find my tutorial helps you get started understanding some of the oddities of this all-in-one processor. (see further down the subject headings)

Martin Young wrote:Anyway, I try to follow the instruction but having entered the tar command with the path to get to the tools.tar.gz file, nothing appears to happen. I don't know if anything ought to happen, but nothing does.

If it didn't give an error message then it worked.If you prefer to see tons of output, use:

robs wrote:... Depending on which processor you were using, the assembly language might be surprisingly familiar. In the early '80s the Motorola 6809 was an elegant 8-bit processor that I enjoyed programming. It was quite a nostalgia kick 25 years on to see the Megasquirt processor's assembly language so similar. But if you were working with Z80/808x or 68k, your earlier assembly language experience won't be so applicable...

Last time I looked at assembler was a couple of years ago when I spent ages on a more or less futile attempt to decode my '94 MX-5's ECU. I was seeing 6811 code in my sleep. Pity if it's irrelevant.

TBI_Master wrote:So when 'make" returns a 'make: command not found'... Is because that package was not selected when installing cygwin?I'm already in the ms2extra directory, Am I missing an argument or something?

I do embedded C,testing, calibrations etc for a paid living. Mostly Texas Instruments MSP430F and TMS320F MCU's. We have always just used a fully featured IDE that is basically download a 4gb package and install it, next next next, done click the right cpu and it 'just works'. I have used Hightide C for PIC18F, mplab for PIC16F asm. We also used minide with a HC12 at university. Any other time I have done work in this field I have always been spoon fed to get started. Install this install that, someone on hand to help out.

So right now I'm looking at my 2.1.0E zip with the source code in it. I have bloody no idea how to get it to work even with following the instructions.

#1 I have downloaded s12buildtools-win32.zip (filesize: (57,611,176 bytes))#2 I have downloaded setup.exe from the www.cygwin.com

Which packages exactly do I need to get cygwin doing what it needs to? Are we just using cygwin because it includes the gcc compiler and someone has developed the s12 tools so that gcc works as required?