Yo Yo Yo Retro Users.
Here is another one of my crazy builds a CD32 with a TF360 Rev 3.0 with a Rev 1 060 fitted & ELSAT ProModule
little back story about the ProModule a few years back a friend of mine gave me the promodule due to it not working and its sat under my CD32 waiting for me to get around to it. I read on facebook that someone managed to get the ProModule to work with a TF330 which I thought would be great and give the system an FPU and all the ports an Amiga 1200 has. This prompted me to look in to why the ProModule I had was not working.
On prior inspection I noticed the Riser had track damage to the FMV expansion slot but this wasn't the reason the Promodule wasn't working but I had to repair it if the TF330 was to work with it. The Initial test of the ProModule just made the CD32 go into a boot loop i.e., green light then green flashing light over and over again. It did this with everything disconnected even the memory and FPU. So I decided take it apart and look under the board. It looks perfect under there but I did notice it had 2 CIA chips, I had one spare so I thought I would try and change one and lo and behold the ProModule sprung into life. Now came the search to find a floppy drive which would work but every amiga disk drive I had would not be seen, but I could get it to read from an external disk drive.
Now it was up and running I thought lets try the TF330 however I just found the ProModule and TF330 would just boot loop again, now I'm not sure if this is due to the revision of my ProModule which is a v1.1 or if I'm just doing something wrong so I gave up.
After @fitzsteve making me jealous of his TF360, My TF360 arrived and I thought to myself I wonder if it will work with the ProModule, hey presto the machine powered up and booted into workbench and the external floppy was seen and video out and AT Keyboard Ports all working however I was experiencing crashes and this was due to the FPU in the ProModule, so I removed the FPU IC and set JP1 to Sync so the oscillator was taken out of the picture. this sorted my crashing issue
Then I thought I wonder if it can add an extra 8mb of fast ram to the 128mb already given by the TF360. Now I forgot to mention that with the TF360 Installed and the memory jumper on the promodule is removed = onboard Memory off, the ProModule is not seen in the Amiga CD32's Expansion section of the Boot menu also if I set the memory Jumper to on, then the TF360 is not seen in the Expansion section of the boot menu but the promodule is, the TF360 seems to function as normal and the extra 8mbs of fast ram is seen however I did find that it had to be a certain type of simm or again I would see crashes.
Now back to finding the main floppy disc drive: Reading through EAB's forums I tried to find as much information as possible on the ProModule, to see what disk drive would work with it. I read that it was possibly a PC disk drive but no firm confirmation of this. Finding a manual was a nightmare, luckily @a.mi.goun had a manual but it was in polish, so slow time using google translate, I translated the floppy drive section of the manual which stated that it was indeed a PC floppy drive and would work like a normal DD amiga disk drive. So I bought a black Alf floppy disk drive which seems to work perfectly. sadly everywhere I read stated that the ProModule would not work with a Gotek.
Today sitting in my man cave I wondered to myself, wait a minute can I set the Gotek up to be an IBM PC Drive with flash floppy installed, scouring the FlashFloppy site I found this wonderful bit of information.
I'm having one issue with the ProModule (this happens without the TF360 installed too) is that switching the jumpers so that DF1 is seen as DF0 doesn't work correctly if a drive is attached to the internal floppy drive header of the ProModule I don't know if this is normal or if there is still an issue with it. the manual does state that the internal drive will not be seen if this is selected but it doesn't state it need to be disconnected which is the case with mine would like to know if other who have the pro module have this issue too.
Spec of CD32
TF360 with 128mb
060 rev 1 @ 50mhz (not tried speed boosting yet)
Elsat Promodule with 8mb (FPU Removed) battery backup clock functioning
Gotek with rotary selector and OLED
read on @alenppc TF360 page that they manage to get a subway USB to work with the TF's Notport so this is something I May add to it.
Pictures to follow as I went through the stages of discovery Hope you enjoyed it.
Other projects of mine you maybe interested in:
A500+:
Here is another one of my crazy builds a CD32 with a TF360 Rev 3.0 with a Rev 1 060 fitted & ELSAT ProModule
little back story about the ProModule a few years back a friend of mine gave me the promodule due to it not working and its sat under my CD32 waiting for me to get around to it. I read on facebook that someone managed to get the ProModule to work with a TF330 which I thought would be great and give the system an FPU and all the ports an Amiga 1200 has. This prompted me to look in to why the ProModule I had was not working.
On prior inspection I noticed the Riser had track damage to the FMV expansion slot but this wasn't the reason the Promodule wasn't working but I had to repair it if the TF330 was to work with it. The Initial test of the ProModule just made the CD32 go into a boot loop i.e., green light then green flashing light over and over again. It did this with everything disconnected even the memory and FPU. So I decided take it apart and look under the board. It looks perfect under there but I did notice it had 2 CIA chips, I had one spare so I thought I would try and change one and lo and behold the ProModule sprung into life. Now came the search to find a floppy drive which would work but every amiga disk drive I had would not be seen, but I could get it to read from an external disk drive.
Now it was up and running I thought lets try the TF330 however I just found the ProModule and TF330 would just boot loop again, now I'm not sure if this is due to the revision of my ProModule which is a v1.1 or if I'm just doing something wrong so I gave up.
After @fitzsteve making me jealous of his TF360, My TF360 arrived and I thought to myself I wonder if it will work with the ProModule, hey presto the machine powered up and booted into workbench and the external floppy was seen and video out and AT Keyboard Ports all working however I was experiencing crashes and this was due to the FPU in the ProModule, so I removed the FPU IC and set JP1 to Sync so the oscillator was taken out of the picture. this sorted my crashing issue
Then I thought I wonder if it can add an extra 8mb of fast ram to the 128mb already given by the TF360. Now I forgot to mention that with the TF360 Installed and the memory jumper on the promodule is removed = onboard Memory off, the ProModule is not seen in the Amiga CD32's Expansion section of the Boot menu also if I set the memory Jumper to on, then the TF360 is not seen in the Expansion section of the boot menu but the promodule is, the TF360 seems to function as normal and the extra 8mbs of fast ram is seen however I did find that it had to be a certain type of simm or again I would see crashes.
Now back to finding the main floppy disc drive: Reading through EAB's forums I tried to find as much information as possible on the ProModule, to see what disk drive would work with it. I read that it was possibly a PC disk drive but no firm confirmation of this. Finding a manual was a nightmare, luckily @a.mi.goun had a manual but it was in polish, so slow time using google translate, I translated the floppy drive section of the manual which stated that it was indeed a PC floppy drive and would work like a normal DD amiga disk drive. So I bought a black Alf floppy disk drive which seems to work perfectly. sadly everywhere I read stated that the ProModule would not work with a Gotek.
Today sitting in my man cave I wondered to myself, wait a minute can I set the Gotek up to be an IBM PC Drive with flash floppy installed, scouring the FlashFloppy site I found this wonderful bit of information.
IBM PC
IBM PC compatibles have a non-Shugart interface which must be explicitly configured in FlashFloppy:- IBM-PC interface mode must be configured
- Strap jumper JC at the rear of the Gotek; or
- Specify via FF.CFG: interface = ibmpc
- Strap select-line jumper S1 at the rear of the Gotek
- S0, S2, MO should all be left open
I'm having one issue with the ProModule (this happens without the TF360 installed too) is that switching the jumpers so that DF1 is seen as DF0 doesn't work correctly if a drive is attached to the internal floppy drive header of the ProModule I don't know if this is normal or if there is still an issue with it. the manual does state that the internal drive will not be seen if this is selected but it doesn't state it need to be disconnected which is the case with mine would like to know if other who have the pro module have this issue too.
Spec of CD32
TF360 with 128mb
060 rev 1 @ 50mhz (not tried speed boosting yet)
Elsat Promodule with 8mb (FPU Removed) battery backup clock functioning
Gotek with rotary selector and OLED
read on @alenppc TF360 page that they manage to get a subway USB to work with the TF's Notport so this is something I May add to it.
Pictures to follow as I went through the stages of discovery Hope you enjoyed it.
Other projects of mine you maybe interested in:
A500+:
Timtheloon's A500+ with A570 CD-ROM and TF536 Build
A600:Timtheloon's A600HD PiStorm Build
A2000:Timtheloon's A2000 Triple Processor Project
A1200:Timtheloon's Checkmate A1500 Plus (A1200 Build)
CD32:Timtheloon's CD32 SX32 Pro Setup with Cosmos Kickstart Mod
Timtheloon's CD32 TF360 Plus ProModule Build
A4KD & A4KTTimtheloon’s A4000cr Alice project
Timtheloon's A4000T Project
Acorn RiscPC:Timtheloon's RiscPC 600 build
RetroPCTimtheloon's Retro High-End AGP (HD3850) PC (Dual Boot WinXP & Win7)
Attachments
Last edited:

I got this from the seller, it's actually well packed away just now as I am still finishing off the Man Cave, will be happy to get all my retro stuff back out when I get the units and storage all set up with the sockets and network as well.