Beginning of very long journey

[Rustynutt]

IDE is an integral part of the Falcon custom chipset, so replacing it does not make sense.

Once again I reported a post, not posted as a comment. Sorry about that.

For a couple bucks users can purchase a small iDE to SATA adapter.

[Rustynutt]

Switching DSP to 56301 will be a little setback, but hey - its a fun project and thats where the fun is. So back to the schematics.

Awesome. Just want to mention it - in this case some minor changes to the TOS are going to be needed.

If TOS needs to be changed to work with the 56301, how would compatibility with games and demos be?

When reading through the MOT docs, it states the 56301 is object code compatible

Is it the additional DSP memory and possible address difference your concern?

I have a 56301 PCI development card I was thinking of trying to use under Hatari, of course with change to access the PCI over the emulator, if possible. At a minimum, some of dml's bench test. Purchased it with the possibility of using it on the CTPCI. On a standard Falcon, if some how the DSP was replaced, think address changes in the GAL could redirect location.
Not sure if the CT60 uses the GAL's to interrupt.

[mpattonm]

Your gut feeling was right, it can not work like that. I even guessed it, Videl is indeed using VID32 to sync with the Combel (for ST-RAM access). So *that* is the reason why they put 32.08... for compatibility on the external pin when master clock was changed. You are free to modify 25.175 or external clock (they work independently from the system bus) but not VID32, must be the same as master clock.

So you can rewire it a bit - instead of switching between 32.08.../custom clock on VID32 you keep the line from the master clock on VID32 and put the exact same switch on the external clock pin.

Not sure if I understand correctly, do you mean something like.... this?

[mikro]

Not sure if I understand correctly, do you mean something like.... this?

Uhm, stop listening to me. Your v2.1 is totally fine, I don't know what I was thinking (it seems that I'd overlooked that the masterclock *is* shared with both the Videl and the Combel input).

If you like, you can add a similar switch (32.08/custom clock) to EXTCLK - similarly as on the CT2. So:

- if input to Combel == 32.08 MHz then EXTCLK would be wired from external source (video connector)
- if input to Combel == custom then EXTCLK = 32.08 MHz (for backward RGB compatibility)

[mikro]

I have remembered about one suggestion seen in another thread: viewtopic.php?f=97&t=33093#p340349

Maybe, when routing the PCB, you could somehow take this idea into account? So the next-gen expansion card wouldn't expand only CPU (and possibly TT RAM) but also ST RAM in one go. All that is needed is to somehow place the ST RAM headers close to the expansion slot headers so one PCB can be placed on all four headers at once.

[mpattonm]

Just a quick update: schematics are complete (and no, I am not going to make any more changes this time, I swear), layout is fixed and I have completed first round of routing. Memory buses, clock signals, audio out, TV out and some other subsystems were routed manually, while autorouter took care of the rest. Still on a four layer board.
Next step is a manual cleanup and optimizations, it should keep me busy for couple of days.

[arf]

Keep on hackin’!

[TheNameOfTheGame]

Thanks for the update!

[Rustynutt]

Visually check the SDMA CLKIN point. The common trace from the COMBEL to both the FPU clock and SDMA clock makes a small but severe dog leg turn around another IC's resistor. From normal view, the "jump" under the resistor is left of the SDMA clock pin, about 20mm.

Could you also consider a PGA or modified DSP pinout where the DSP can relatively easily swapped out?
Without a 56k sheet in front of me, recall the 56002 and upward compatible have a few pins swapped. They may also include increased memory management.

68030 PGA socket.

Kind of out from the scope of "the long journey", a nice additional feature would be to add separate oscillator sockets for IC's which in the past have had traces cut to insert a different clock. ie, DSP, FPU, MIDI and KB IC, VIDEL, VIDEL Genlock.
Pretty much any speeder, accelerator, CPU upgrade, basically all the reasons more Falcons didn't make it out from the System 7 wars

[calimero]

And what are final specs.?

Btw
Original Falcon board was also 4 layered?
Btw2
Will you made this opensource so anybody can make their Dream-Falcon?

[mpattonm]

Visually check the SDMA CLKIN point. The common trace from the COMBEL to both the FPU clock and SDMA clock makes a small but severe dog leg turn around another IC's resistor. From normal view, the "jump" under the resistor is left of the SDMA clock pin, about 20mm.

This is completelly new board with different layout and certainly, different routing. All clock signals were routed manually (as the only signals actually) on a GND layer. Thus the above does not apply on the new board.

Could you also consider a PGA or modified DSP pinout where the DSP can relatively easily swapped out?
Without a 56k sheet in front of me, recall the 56002 and upward compatible have a few pins swapped. They may also include increased memory management.

F030NG is designed with 56303 DSP, which, while code compatible, is significantly faster then 56001 and is coupled with 128kx24b memory. Compared to three 32kx8k modules on original Falcon030, it has four times bigger memory capacity.
At one point I was also considering a dedicated slot for DSP add-on card, but it was lef out from the design afterall. It might appear in a future tho.

68030 PGA socket.

Kind of out from the scope of "the long journey", a nice additional feature would be to add separate oscillator sockets for IC's which in the past have had traces cut to insert a different clock. ie, DSP, FPU, MIDI and KB IC, VIDEL, VIDEL Genlock.
Pretty much any speeder, accelerator, CPU upgrade, basically all the reasons more Falcons didn't make it out from the System 7 wars

Again, clock generation is way different form original Falcon. For example, instead of plain 32.089MHz crystal, F030NG features PLL programmable from 32 to 50MHz in 10 steps. There is also a switch to bypass Combell clock to CPU and FPU, allowing these two to be fed from PLL directly. Meaning you will have number of options and combinations to overclock your system, there will be no use for the basic speeders. With the exception of CT family, of course.

[mpattonm]

And what are final specs.?

Yes, I will make a wiki page eventually.

Btw
Original Falcon board was also 4 layered?

Really? I did not know that. All I have ever seen was 6 layer PCB versions. That would perhaps explain some of the weird routing artefacts that make no sence at all.

Btw2
Will you made this opensource so anybody can make their Dream-Falcon?

Eventually yes, but not from the day one.

[Galvez]

Btw
Original Falcon board was also 4 layered?

Really? I did not know that. All I have ever seen was 6 layer PCB versions. That would perhaps explain some of the weird routing artefacts that make no sence at all.

I think he was asking, see the question mark.

[Greenious]

I'm impressed by the work so far and really like where this is going!

A thought... given that most ppl interested in this new mobo probably want something faster than 030 & FPU, how about lifting them off the mobo to a daughterboard for the expansionbus instead? You can save some more space and people dont have to buy a CPU they will not use...

[calimero]

Yes, I was asking
but as I remeber from 90s that I read somewhere that Falcon MB is 4 layered... I also remeber that comparing to Amiga1200 I was thinking that Falcon motherboard and components were made in much more "modern" manner

Btw
Regarding 32.089MHz, someone, I think Mikro, mention that PAL and NTSC Falcons have different clock? In FalconNG you will put which one?

[shoggoth]

I'm impressed by the work so far and really like where this is going!

A thought... given that most ppl interested in this new mobo probably want something faster than 030 & FPU, how about lifting them off the mobo to a daughterboard for the expansionbus instead? You can save some more space and people dont have to buy a CPU they will not use...

This probably rules out the CT6x, since it needs the original 030 to be present during boot (god knows why).

[mikro]

This probably rules out the CT6x, since it needs the original 030 to be present during boot (god knows why).

I'll speculate here and say it is because R. Czuba didn't want people to manipulate the 030 in any way. AFAIK you have to ground pin 17 (BGACK-, Bus Grant Acknowledge) to signalise that another device (CT60) has become the bus master.

[MacFalcon]

Are you sure that the 030 is needed? Rodolphe wrote me one day that my Falcon could run even with dead 030 in 060 Mode (when I killed my board during some testing for flash060.prg...)

But that's offtopic

Great Work! A new Falcon Board would be awesome!

Chris

[Rustynutt]

Could you also consider a PGA or modified DSP pinout where the DSP can relatively easily swapped out?
Without a 56k sheet in front of me, recall the 56002 and upward compatible have a few pins swapped. They may also include increased memory management.

F030NG is designed with 56303 DSP, which, while code compatible, is significantly faster then 56001 and is coupled with 128kx24b memory. Compared to three 32kx8k modules on original Falcon030, it has four times bigger memory capacity.
At one point I was also considering a dedicated slot for DSP add-on card, but it was lef out from the design afterall. It might appear in a future tho.
[quote="Rustynutt"]

Have yet the chance to work with a couple of Motorola DSP developer cards picked up last year.

They may or may not be of interest.
After upgrading my Milan, will install the PCI DSP card in this machine for some simple experiments.

Installing the CTPCI on a Falcon is down the road a bit more.

The audio development board looks as if it could be interfaced directly to the CT card, honestly have not looked into that possibly, yet still has other interface designs.

The photos are located here open to public if you have a Facebook account.

https://m.facebook.com/michael.grove.39 ... 952377519/

[mpattonm]

As I am getting to the finale I can switch to a nice looking pictures again.
Still to do:
- pwr routing (should be relatively easy, as both internal layers are dedicated to VCC and GND)
- finish silkscreen
- convince myself its really the time to stop fiddling around and order the prototype PCB already
EDIT:
PCB top: https://centuriontech.eu/download/F030/F030_R01-top.png
PCB bottom: https://centuriontech.eu/download/F030/ ... bottom.png

[christos]

Just a thought. It is not really far from a falcon clone now, is it?

[dhedberg]

Cool. Do you have a final list of all major modifications?

[mpattonm]

Just a thought. It is not really far from a falcon clone now, is it?

Three to six months. This includes one qualification cycle. Lets hope its enough.
Anyway, its going to be barebone only from the start, chassis has not been worked on yet.

[alienkidmj12]

sounds like a very cool project, will keep tabs on it.

[EvilFranky]

I meant to ask before Xmas, is this missing the enhanced joypad ports?