Previous Thread
Next Thread
Print Thread
Page 13 of 14 1 2 11 12 13 14
#108478 - 01/18/17 03:44 PM Re: VME boards [Re: Edstrom]  
Joined: Aug 2015
Posts: 339
Edstrom Offline
Senior Member
Edstrom  Offline
Senior Member

Joined: Aug 2015
Posts: 339
I finally got the first printouts on the Force CPU-20 PDOS bootstrap working with the new MPCC 68561 device:


#108508 - 01/20/17 10:00 AM Re: VME boards [Re: Edstrom]  
Joined: Aug 2015
Posts: 339
Edstrom Offline
Senior Member
Edstrom  Offline
Senior Member

Joined: Aug 2015
Posts: 339
And now the keyboard works as well as some jumpers emulated so we fall into FORCEbug rather than trying to auto boot some so far non existing floppy disk.
This is rather cool as it is FOREbug and not VMEprom, PDOS is not integrated but separated. later on the VMEprom replaces FORCEbug and all it s functionality and also integrating a PDOS kernel.




Next thing will be to load the fccpu20 in the miniforce chassi previously skeltonized and now I want to explore how the VME bus calls can be dispatched between the boards.
Yet then we need to write the WFC1 mass storage controller board to get to the floppy controller.

Last edited by Edstrom; 01/20/17 10:01 AM.
#108512 - 01/20/17 08:32 PM Re: VME boards [Re: Edstrom]  
Joined: May 2012
Posts: 420
shattered Offline
Senior Member
shattered  Offline
Senior Member

Joined: May 2012
Posts: 420
besta.cpp (CP31 board, essentially Force CPU-25M + RTC chip):



diff: https://gist.github.com/shattered/4ec094bc1fcee96c6980a9fc5762069b

#108513 - 01/20/17 08:54 PM Re: VME boards [Re: Edstrom]  
Joined: Aug 2015
Posts: 339
Edstrom Offline
Senior Member
Edstrom  Offline
Senior Member

Joined: Aug 2015
Posts: 339
if you enable LOGSETUP by

#define VERBOSE (LOG_PRINTF | LOG_SETUP)

you'll get output about what it tries to do and what is not implemented

#108519 - 01/21/17 02:37 PM Re: VME boards [Re: Edstrom]  
Joined: May 2012
Posts: 420
shattered Offline
Senior Member
shattered  Offline
Senior Member

Joined: May 2012
Posts: 420
'cp31dssp' BIOS apparently doesn't like something here:

Code:
[:mpcc]  * : Reg 19 -> 1e  
[:mpcc]  * : Reg 1c -> 8c  
[:mpcc]  * : Reg 1d -> 00  
[:mpcc]  * : Reg 1e -> 1c  
[:mpcc]  * : Reg 1f -> 00  
[:mpcc]  * : Reg 0d -> 00  
[:mpcc]  * : Reg 15 -> 00  
[:mpcc]  * : Reg 05 -> 80  
[:mpcc]  * : Reg 11 -> 40  
[:mpcc]  * : Reg 08 -> 80  


It prints 'MPCC ERROR' right after.

#108523 - 01/21/17 08:34 PM Re: VME boards [Re: Edstrom]  
Joined: Aug 2015
Posts: 339
Edstrom Offline
Senior Member
Edstrom  Offline
Senior Member

Joined: Aug 2015
Posts: 339
Can't determine without knowing how the initialization was done, I will come back to the MPCC when I have PDoS booting to add interrupts and a few other things but it may take a while, feel free to contribute to the MPCC meanwhile. Here is the data sheet, it is quite good actually:

https://drive.google.com/open?id=0B685nj_1DkduUndEUkx0UWJTY00

#110938 - 10/01/17 05:13 PM Re: VME boards [Re: shattered]  
Joined: May 2012
Posts: 420
shattered Offline
Senior Member
shattered  Offline
Senior Member

Joined: May 2012
Posts: 420
Originally Posted by shattered
far as I can see from the docs, the non-Force boards are
Code
<...>
hcpu30	=
	68030, 68882 @ 33 MHz
	68020 -- I/O cpu
	:
	DRAM -- 4 or 16 MB
	PROM -- up to 64 KB
	SRAM -- 8 KB non-volatile or 32 KB volatile
	:
	2xRS232/RS422	$FFFF8120, $FFFF8140
	SCSI		$FFFF8160
	Floppy		$FFFF8260
	Centronics	$FFFF8280
	RTC		$FFFF8100
	Ethernet	$FFFF82A0


Linux port supports CP20, CP30, CP31 and HCPU. Don't know what SysV supports -- there are boot floppies for that, too.


Got a dump from HCPU30 board; what little docs I have leads to this:

[Linked Image]

Going to submit a skeleton of that soon.

#110965 - 10/03/17 07:00 PM Re: VME boards [Re: Edstrom]  
Joined: Aug 2015
Posts: 339
Edstrom Offline
Senior Member
Edstrom  Offline
Senior Member

Joined: Aug 2015
Posts: 339
Cool, nice to see additional VME boards being added! smile I am not sure when I will get back to VME again, I need to get some of my other skeletons up to working first and then I have a pile of stuff in the garage that needs to be added to existing drivers or new ones. But sooner or later I will and by then we might have a chance to make an improved VME bus, contributions are welcome!

#110966 - 10/03/17 07:36 PM Re: VME boards [Re: Edstrom]  
Joined: May 2012
Posts: 420
shattered Offline
Senior Member
shattered  Offline
Senior Member

Joined: May 2012
Posts: 420
I think this board has the best chance of running an OS (everything is integrated - SCSI, floppy and Ethernet), but some reverse-engineering will need to happen first (there's a schematic somewhere but I don't have a copy). Right now it's stuck waiting for IRQ from DUSCC -- I was hoping you'd take a look at DUSCC code smile

#110968 - 10/03/17 10:28 PM Re: VME boards [Re: Edstrom]  
Joined: Aug 2015
Posts: 339
Edstrom Offline
Senior Member
Edstrom  Offline
Senior Member

Joined: Aug 2015
Posts: 339
Sure, that is maintenance, I can have a look at it soonish, just need the driver to be merged and the roms of course. It would be nice to know how the IRQ is actually hooked up to the CPU, usually there is an interrupt controller in between that also arbitrates the VME interrupts so it can get tricky if that is an unknown. At least we need to know the vector and the level used.

Page 13 of 14 1 2 11 12 13 14

Who's Online Now
2 registered members (Heihachi_73, Tauwasser), 14 guests, and 2 spiders.
Key: Admin, Global Mod, Mod
Shout Box
Forum Statistics
Forums9
Topics8,454
Posts109,718
Members4,767
Most Online225
May 26th, 2014
Powered by UBB.threads™ PHP Forum Software 7.6.0
Page Time: 0.031s Queries: 14 (0.011s) Memory: 5.0276 MB (Peak: 5.2545 MB) Zlib enabled. Server Time: 2017-12-14 02:29:12 UTC