anyone have an ancient SDS tool suite?

As I recall, SDS was node locked, with the license key based on your hard disk's serial number. I don't know if you'd be able to get a new key easily.

Then I guess that means I would have to buy the hard disk, too.

Andrew

You probably need just the old disks serial number. There is a place to install this in the first boot sector. I don't remember where, but there are/were utilities about to do so.

If I had not just answered the previous message this would make absolutely no sense to me. It is essential to include adequate context in your replies. Google is NOT usenet, and their foully broken and incompetent interface presents a distorted view. There is absolutely no reason to assume that readers have received, or will ever receive, previous messages in the thread. Even if they have received them, accessing them may well be awkward or impossible, as most usenetters destroy or otherwise make invisible anything they have read. Read my sig, and especially read the references therein.

I do not know why some people hates google so much. Say the least of it, google is a good tool to search previous thread and prevent posting duplicated discussion.

You can present the shotcuts of google here. Just discuss, Do not use words lik "foully".

Even this is threatened by the foul incompetent google interface.

So why did you ignore the advice of how to use it intelligently? That is why their interface is foul and incompetent. By default it should do the right things. Google is causing heavy damage to the usenet system, and is generally being extremely evil.

All they have to do is fix their interface (which has been requested time after time for at least a year now) and we can stop pillorying them.

Many users simply plonk all articles originating on google, which means they never see them. Some organizations maintain their own private news servers and allow google to echo them, but not to accept articles for them (mozilla). Many users are annoyed by google and so mark their articles as to prevent them appearing on the google archives. All of this is non-productive, and directly caused by the FOUL and INCOMPETENT google interface.

Why don't you start with the Gnu Compiler Suite? You'll get up-to-date software for free, and for most of the important archtectures like 68k, Coldfire (a somewhat RISCized 68k), ARM, PPC, etc etc.

The BDM debugger interface for 68k and Coldfire is rather easy, and there are several schematics for parallel port interfaces on the net, e.g.:

As you are an engineer you should have no problems building your own for very little money.

Mit freundlichen Grüßen

Frank-Christian Krügel

We ported all our 68K code written for the SDS compiler suite to gcc. This was quite painless if you get the patched version that supports the interrupt attribute. The gcc code is MUCH faster than the code generated by the SDS compiler.

Regards Anton Erasmus

WE? WHAT WE? Maybe WE should all chip in and buy you a share of Google stock so you can vent at their next stockholders meeting. If you think this tiresome, repetitive ranting about Google Groups is changing anyone's behavior, you're wrong.

Maybe you should take this under advisement; it would probably lower your blood pressure, and the SNR of the post you DO see would go up.

--Gene

... snip ...

Experience has shown that failure to correct newbies and general misuse leads to the destruction of newsgroups. Moderated groups can take other steps, but have other problems.

Believe me, I am really thinking hard about doing this. My only reluctance regarding this is whether there is a free version of the CGS that will actually do breakpoint debugging via the JTAG interface. Too many companies charge $$$ just for a GNU tool chain modified to user thier particular wiggler.

Your thoughts?

The Eternal Squire

And this version resides where?

The Eternal Squire

The "interrupt" patch has been merged with the main gcc tree for some time now, although it changed name from the original "__attribute__((interrupt))" to "__attribute__((interrupt_handler))". I've no idea why. A current 3.4.5 gcc should build cleanly for the m68k family on cygwin or *nix - see

You can also get pre-built binaries from a few places. ucLinux and RTEMS are obvious candidates.

The 68332 does not have a JTAG interface, it has a BDM interface (both are synchronous serial "back door" interfaces, but the BDM is designed specifically for debugging). The bdm_driver software fully supports debugging using the P&E Micro or standard Motorola ICD compatible parallel port JTAG interfaces. There are even schematics available to build your own if you prefer.

If you read the link I included in my posting you'll find links where to look. The key is including a suitable BDM driver in the Gnu Debugger gdb. The rest of the compiler suite is unaffected.

And as far as I remember the 68332 doesn't use JTAG for debugging, but the Motorola BDM interface, which is a bit simpler. So just google for "m68k bdm gdb", and you'll find enough links to start within the first two search result pages.

If you use Windows, start reading here:

Mit freundlichen Grüßen

Frank-Christian Krügel

Sorry, I'm still using it. The SDS key is locked to the network card MAC, so I'm the only person in the office still using 10Mbps ethernet.

Peter

It evens itself out just fine without the paesty netiqutte reminders. You are never going to get everyone to voluntarily do what you want them to do.

CBFalconer wrote: > Many users are annoyed by

I would appreciate references to any independent Usenet archives (available on the Web or not) that attempt to preserve traffic in the traditional technical hierarchies. The Internet is too evanescent to rely on only one preserve. I realize that often websites mirror and doll-up newsgroup traffic that specifically relates to their target audience but I am seeking scholarly archival efforts independent of Google.

Michael Grigoni Cybertheque Museum