TF536 on A2000

[terriblefire]

Can you both confirm you have edited CD0 and changed

BufMemType = 0

to

BufMemType = 3

?

[matt020]

Can confirm I have tried BUFMEMTYPE=3 ..... and 2.

A2000 boots from TF536. CD0 is mounted. But when a disc is inserted and it goes to read from the disc, it crashes. I have onboard fastmem disabled via jumper on the A2091.

[terriblefire]

Can confirm I have tried BUFMEMTYPE=3 ..... and 2.

A2000 boots from TF536. CD0 is mounted. But when a disc is inserted and it goes to read from the disc, it crashes. I have onboard fastmem disabled via jumper on the A2091.

OK i guess i need to get one of these cards.

[matt020]

Anyone having some minor behaviour issues at first power on with the TF536 in the A2000?

With KS3.1, I would get WB loading, then a crash or a yellow screen.... then after a reboot, she's fine!
With KS3.1.4 softloading via loadmodule, it'll crash on loadmodule giving option to suspend or reboot... after a reboot, she's fine!

It's always just the first 10-20 seconds after power on, its unhappy, then, after 20 seconds or so she'll run fine for HOURS.

I have a DKB megachip clone with 2mb chip, A2091 but with fastmem jumper set to 0 and bootrom disabled (so it's effectly deadwood).
TF536 with 2gb CF card, Fastfilesystem, 4096 block size.

Edit: previously had a TF534 in this set up,nil issues at all, even with megachip and A2091, so Im happy its not the A2000

[alenppc]

Anyone having some minor behaviour issues at first power on with the TF536 in the A2000?

With KS3.1, I would get WB loading, then a crash or a yellow screen.... then after a reboot, she's fine!
With KS3.1.4 softloading via loadmodule, it'll crash on loadmodule giving option to suspend or reboot... after a reboot, she's fine!

It's always just the first 10-20 seconds after power on, its unhappy, then, after 20 seconds or so she'll run fine for HOURS.

I have a DKB megachip clone with 2mb chip, A2091 but with fastmem jumper set to 0 and bootrom disabled (so it's effectly deadwood).
TF536 with 2gb CF card, Fastfilesystem, 4096 block size.

Edit: previously had a TF534 in this set up,nil issues at all, even with megachip and A2091, so Im happy its not the A2000

I haven't observed this on my A500. I wonder if your power supply takes a bit to stabilize voltages when first powered on.

I am using 10uF caps next to the voltage regulator, I wonder if I should change these to 1uF.

[matt020]

I did think this... that its just taking something just some time to settle down... because after the initial problem, it runs beautifully!!

[richx]

I did think this... that its just taking something just some time to settle down... because after the initial problem, it runs beautifully!!

Can you monitor the voltage on the nice 5V header, preferably with a scope to see any ripples? Could be old/dry capacitor somewhere that needs time to warm up.

I did not see this any warm up issues on my A2000s either. I did see however that previous battery acid leak must have weakened some traces and the added stress of removing 68000 and plugging in TF536 did result in black screen, needed to add patch wire.

Also, been seeing weird IDE issues on both Rev4.5 and Rev6, "cpu fastrom" on older smaller CFs results in horrible transfer speeds, meaning SysInfo never finishes within reasonable amount of time, but the fastrom slowness seems to affect the RAM: drive as well! On newer 8GB CFs, I get a nice ~4MB/sec with "cpu fastrom" but some larger files experience consistent corrupt transfers in what appears to be the very same blocks when copying from WB, but not from Shell! Still troubleshooting this one, will post more info probably in new thread.

[alenppc]

some larger files experience consistent corrupt transfers in what appears to be the very same blocks when copying from WB, but not from Shell!

WB and Shell employ different methods to copy files. The shell copies the entire file into the RAM first and then writes it on the disk as a long data stream. WB reads a small chunk, writes it, then reads the following one and appends it. In most cases this causes the WB copy to be more reliable (for example in case of MaxTransfer issues) but slower.

In your case you have the opposite problem...

[jcarvalho]

Hello! First of all I would like to thank to TerribleFire for is awesome work and dedication to the Amiga/Atari enthusiasts.

I have one TF536, bought the PCB in exxos store and assembled at home. At this moment is installed on A2000 rev 6.2. I would like to know if I can connect an AT BUS 2008 clone and use it instead the IDE of TF536... it would be easy for me to connect an CF to the AT BUS 2008 Clone.

Many thanks!

[8 Bit Dreams]

Have built AT BUS Clones in 2018,
these was not working with TF530 because of autoconfig and boot rom (oktagon.device).. i assume it will not work with TF536 due same reason...