> Before posting a lot here, I suggest trying to work out how to send me a private message on this system ..
> You should subscribe to the "comp.sys.m68k" Google Group, then post some questions there too:....
I'll try to do so, since I too think that this discussion can get long-winded and very technical pertaining just my particular efforts with a particular (and obsolete at that) product.
I look much forward to exchange some details and further info, thanks for the offer.
> I applaud that, but sometimes to "make something live forever" you had to be there at its birth, and not working with a shovel in the cemetery at midnight.
I LOL at that analogy and yes, it more or less describes how I feel sometimes with this :smileyhappy:
> Also, if your first instinct when confronted with that RJ11-based serial port isn't to grab a multimeter and start probing, then that's a skill-set or mind-set that's worth developing for this project. Do you have an oscilloscope? If not, get one.
It is, of course I figured that I needed to do that eventually but was too busy with getting a basic hardware info/ schematics first. Besides, as you later suggest, there might be a couple different ways to the pinout.
I own a multimeter and a function generator, an oscilloscope is out of the question (a good one I mean) for the moment and in fact I'm trying to get my head around a project which uses Spartan 3 board to give you one basic oscilloscope with Java interface and all that (I own several of these boards, quite cool hardware and easy to program with Xilinx ISE).
I think the multimeter will do (aided by my microscope since most of the signal to the busses etc are SMT). As I said I can guess it's not going to be the bottleneck here... when I have some definite info I'll let you know.
> If you don't like the IDEs that automatically connect to the pod and your device, and support compile-program-run-debug with one click, then you should try and get a set of Windows command-line tools to do that. You'll need a gcc-m68k...
I already did my homework here, at least following the excellent tutorial/ info on:
ColdFire Development Resources - GNU C
which applies to ColdFire, I was able to successfully build my own cross-compiler able for 5307 using that info.
BTW, there's similar approach tailored to the MPC8xx (I guess you already knew about this):
http://www.connotech.com/gcc_mpc8xx/powerpc_eabi_mpc850.htm
Regarding this see my next response too.
> Keep looking for bits, like this one. It might come with some documentation..
WIND RIVER SYSTEMS EST XPC860 Dev Board PC104 - $59.00 | PicClick
Alas, man, that's incredible as I got one of those precisely, too, along with the MDPBAA+ICM307 (Integrated CPU Module), in fact it was the same US-based guy who sold me those.
I've always wondered btw, how on earth do these guys get so many boards and development systems? Most of them admit, it's from dismantled Univ. labs and the like. Hey, I got myself a MPLAB ICE 4000 complete IN THE BOX never used, just a couple weeks ago!!! (now I just have to buy some headers and adapters for using this, LOL, but the prospect of this platform is excellent I really love and dig this platform!).
But I digress. BOTH my SBC5307 (=MDPBAA+ICM307) and my MPC860 (MDPBAA+daughterboard with MPC860 on it) came without any information, documentation or stuff. Cmon, if you get this as obsolete/ expurged material from an Univ. Lab, then how come they don't get the full boxes????
(Btw, I tried the old trick of using Wayback machine to restore/browse older versions of some EE courses deasling with Motorolas/FReescales ColdFires, see if they have even some Lab doc sheets or soemthing for any Lab that used the SBC5307, to no avail up to now..... :smileysad:) very sad indeed....
Since those two (SBC5307 and the 860-based board) share same base board, documentation of one would apply to the other. I see you insist that I try and get some inspection/ further info on the base board first. I second that, of course, just I don't have as many spare time as I'd like, so with these (multiple) platforms I advance slowly (but regularly).
If you use a MPC860 MDP by the Wind River (more on their support policy for obsolete products when we chat privately you can be sure), and can offer additional info or insight. We can work together and benefit from the bits each other finds out.
To sum up, too, a brief enumeration of current "obsolete parafernalia" I'd love to get up and running:
- SBC5307 (the Wind River PC104 MDPBAA+ICM307, not the Arnswesh brand)
- The BDM for this (Noral Flex Tool BDM) Alas, came too without any support, software or anything. Go figure, the guy who sold me said "I don't know what it is" in the official description hehehehe. But I could not pass on this...
- Software for above I got from another seller. Turned out it was HCS12 version. I'm "trying" to adapt it since Wind River doesn't care s*** about supporting this, and I understand.
- MPLAB ICE 4000 -that's to take on another free evening. Let's figure out first the 5307 bits.
- The board same as you mentioned, with 860 on it (Wind River with same base board)
- An old visionICE II unit, but the socket is for MIPS processor. It's easy to get the ColdFire socket individually later on. Not a priority right now, I'd prefer to get the FLEX BDM tools or the P&E environment and/or C toolset working first.
> I have no idea why an MPC860 is a "Clothing Accessory" or why it is a "Temperate Wind River Systems Est Xpc860 Dev Board Pc104 To Have A Unique National Style". Or why there are 800 of every unit listed there (makes me very suspicious about that site)... Make sure you look at the next item in that listing (52 of 53). It is a "Schreiber Hygrothermograph" for $19.
Now this is really funny, it's nearly a miracle that we can end up with the tidbits we need to sniff for to eventually get this running. Besides, as I said before, sellers are not that interested. If someone you know at an University offers you to go there unload a full drawer of development boards equipment for a Lab, just because they updated the Syllabus to the newest flashy (pun intended) platform, for free, then you have a huge money gain just by dropping some eBay adds with "I don't know what to do" or "What you see" descriptions.
If it were not for poor us crazy freaks, they wouldn't get their bucks. It would not compensate their truck loading much less any profit.
> The Altera Max is probably converting the MCF5307 bus (and the MPC860 bus on that dev board) to the PC104 standard the baseboard uses.
Yes I know that most Altera FPGAs/CPLDs I see around there in develipment boards are for glue logic. I've also seen a lot of professional audio products embed these for same purpose. But, is it viable that
If the only task it does is MUXing busses and the like, it's not worth the effort. I mean, I don't really need to know how the, say, memory busses are set up, I just wish to declare/ use them for my firmware, know their addresses, their CS spaces, how to configure and access them, all that rigmarole.
I'll try to contact you privately and to suscribe to the aforementioned Google Group.
As always, thanks so much for your help and your share.