Expansion board for the CD32

[RiotRetroGaming]

Originally Posted by Stedy

Hi,

With regard to IDE LEDs, if a rev 2 TF328 is made, connect pin 39 of the IDE connector to pin 126 of the edge connector, then the CD activity light will also double as the IDE activity light.

For a mod, you can wire to pin 39 of the IDE connector (on the underside as it's easier) and connect to R634, find it here: http://beta.amigapcb.org/

The DCE SX32 uses the same method.

Ian

Awesome!!!

Can you also jumper the rear of the riser to do the same thing at all?

[RiotRetroGaming]

Originally Posted by ooBumbleBeeoo

Awesome!!!

Can you also jumper the rear of the riser to do the same thing at all?

EDIT: I'm guessing you have to have an ide line to the zorro like the A600/A1200 to do that. Bugger

[solidcore]

Originally Posted by amigadude

Flashed solidcore's 0ws firmware to my TF328 with Samsung RAM got 2814 dhrystones whatever they are... but the bit I noticed most was the fact the drive speed went from 1.5MB/s to 2MB/s

Looking at doing the LED mod on the CF reader cos the grey screen is still a little long with no sign of activity... probably look thru my extensive pile of dead laptops and addons for a suitable part donor cos reuse/recycle not just cos I'm a tightwad yorkshireman...

Get about 2.92 on a ide to cf card 4gb. With the same firmware as your running so I believe the bottleneck is your ide for some reason ? . Grey screen doesn't feel too long but then again I enjoy watching the led light up.. easily entertained

[FOL]

Originally Posted by kolla

Majority of PC keyboards today do not have the "right-windows" key, and instead only have "menu" key there, so I tend to map the "menu" key to "right-amiga".

Or, much rather, not use PC keyboard at all.

Alot use key combinations. Mine uses menu + Scr Lk to do right Windows key.

@SuperDuper.
How long did it take for your programmer to arrive. As mine landed in UK on 12th and tracking has never been updated since.

[alenppc]

Any experiences programming the pic on kipper's adapter? After lots of experimenting, I figured out that the pic configuration check marks are all to be left blank except for FOSCO1 bit, but it still seems to be a hit and miss... not every pic works after

[solidcore]

Alenppc, it may be unrelated to your experience with your programmer but it reminds me of exactly the same situation I had with my k150. My cheap k150 Chinese clone would pretend to successfully burn a pic with a hex only to discover that reading it back certain values were wrong . After a few days time trying different software etc I found out the driver itself was the culprit . Unfortunately regarding Chinese clones the USB to serial module isn't the one used with the legit device and the protocol is slightly different .

Generally for these sort of devices Windows xp is recommended with such drivers due to zero support in windows 8-10 however I did find a windows 10 driver or 5 candidates and having to try each one unfortunately ended up irreversibly destroying a few pics . The problem is with the wrong driver it only worked 1/100 of the time. However light at the end of a seamlessly long dark tunnel, a single driver was showing successful burns 100 percent of the time and not only that it was 64 bit windows 10 compatible. With 'clones', unfortunately a change of protocol may of happened in other drivers leading to the problems exactly as you describe and I believe the solution to your pic programmer is test all drivers you can find for it .

Chris

[Amiga1992]

About the Xilinx programmer... is there no way to use the Raspberry Pi method for the first flashing?

[Stedy]

Originally Posted by alenppc

Any experiences programming the pic on kipper's adapter? After lots of experimenting, I figured out that the pic configuration check marks are all to be left blank except for FOSCO1 bit, but it still seems to be a hit and miss... not every pic works after

What PIC device is it?

Some of the 10F and 12F devices have oscillator calibration values, which overwritten, make the part appear dead. They can be recovered. If you can point me to the hex file, I'll decode the config words.

[plasmab]

Originally Posted by Akira

About the Xilinx programmer... is there no way to use the Raspberry Pi method for the first flashing?

Yup it will work just the same.

[Amiga1992]

Oh since the Wiki says it is for RE programming, I thought it wouldn't work! That's great news!

[plasmab]

Originally Posted by Akira

Oh since the Wiki says it is for RE programming, I thought it wouldn't work! That's great news!

[Amiga1992]

Can I edit the wiki and remove the (Re)? makes it seem like it will not work when the CPLDs are "stock".

By the way, BumbleBee, took a while (had to do it again), but yesterday I managed to do some recording of the TF328 running some stuff. The quality is shit (filming at my TV :S) and I forgot to turn sound on, but you can get an idea of speed and stuff.
Here it is, an hour of me fucking around with the CD32 running some demos and games (starts with Captured Dreams for your comparison)
You can see how my XBench setup is working. Thanks to spudje for getting me into XBench:

[ Show youtube player ]

[solidcore]

@Akira I absolutely enjoyed your video mate. Your MK gameplay really got me reminiscing those good old times.

@Everyone, and specifically Plasmab
The tf328 project has certainly given us a lot of joy and pleasure and I know everyone here appreciates the hard work Steve has put into it.

Steve has been a huge influence so thank you mate. I'm reading more books as a consequence, and a lot of flux up my nose. Yuck :P

All the best with the other TF projects and I hope we can all sit down one day and bring our amiga's to a huge hall and let's hope there's no terriblefire-TM there

Chris

[alenppc]

Originally Posted by Stedy

What PIC device is it?

Some of the 10F and 12F devices have oscillator calibration values, which overwritten, make the part appear dead. They can be recovered. If you can point me to the hex file, I'll decode the config words.

That would be very helpful, thank you. This is the firmware http://www.kipper2k.com/tfpics/mmkeyboard.zip

And the pic is a PIC16F628A-I/P

[kipper2k]

Just got back, i tried 0wait core in the A1200 and managed 2821 Dhrystones


naptime

[solidcore]

Originally Posted by kipper2k

Just got back, i tried 0wait core in the A1200 and managed 2821 Dhrystones


naptime

Brilliant news for the a1200 then Thanks for letting us all know kip.

Edit: @alenpcc regarding the advice below this one, if that doesn't work it's probably drivers like I said in my previous post as they f'ked 6 PIC's until I found 1 driver... but if you're using a legit non-Chinese then disregard as probably not drivers

[kipper2k]

Originally Posted by alenppc

Any experiences programming the pic on kipper's adapter? After lots of experimenting, I figured out that the pic configuration check marks are all to be left blank except for FOSCO1 bit, but it still seems to be a hit and miss... not every pic works after

I provided a picture with the configuration settings, that should be all you need

[RiotRetroGaming]

Originally Posted by Akira

Can I edit the wiki and remove the (Re)? makes it seem like it will not work when the CPLDs are "stock".

By the way, BumbleBee, took a while (had to do it again), but yesterday I managed to do some recording of the TF328 running some stuff. The quality is shit (filming at my TV :S) and I forgot to turn sound on, but you can get an idea of speed and stuff.
Here it is, an hour of me fucking around with the CD32 running some demos and games (starts with Captured Dreams for your comparison)
You can see how my XBench setup is working. Thanks to spudje for getting me into XBench:

[ Show youtube player ]

Awesome!
So that means the 030+ is actually a higher cpu clock and the TF328 has no bearing on that.
I get it now. Cheers for that bud

[Stedy]

Originally Posted by alenppc

That would be very helpful, thank you. This is the firmware http://www.kipper2k.com/tfpics/mmkeyboard.zip

And the pic is a PIC16F628A-I/P

I loaded the files into MPLAB.

At address 2007 of the Flash (config word) you should have a value of 0x3F10.

Try connecting pin RB4/pin 10 to ground to ensure you disable Low Voltage Programming (LVP) and maybe add a 100nF capacitor across the PIC power pins when programming.

Does your programmer have an option to control the speed?

Sometimes slowing it down can help.

A capture of the settings is attached.

[alenppc]

Originally Posted by kipper2k

I provided a picture with the configuration settings, that should be all you need

Except the settings don't match what's on my programmer software... there is no desctiption what IntRC is and anyway it doesn't match the data sheet