Figuring out the causes of slow disk access on the TF536
Moderators: terriblefire, Terriblefire Moderator
Re: Figuring out the causes of slow disk access on the TF536
I don't notice any difference but I never had any speed issues here...
- arkadiusz.makarenko
- Moderator Team
- Posts: 1208
- Joined: Wed Jun 19, 2019 7:36 am
- Location: Edinburgh
Re: Figuring out the causes of slow disk access on the TF536
With new firmware plus combination of all tricks I could find. I managed to get to 12 seconds boot time. Classic WB 68k on 8 GB CF card.
It is without MMULibs, but with cpu fastrom very high in startup-sequence.
I have noticed that initial startup is much faster with CF card than SD2IDE (more than 12 seconds just to start loading anything).
It is without MMULibs, but with cpu fastrom very high in startup-sequence.
I have noticed that initial startup is much faster with CF card than SD2IDE (more than 12 seconds just to start loading anything).
Do not trust people. They are capable of greatness.
~ Stanislaw Lem
~ Stanislaw Lem
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Figuring out the causes of slow disk access on the TF536
Have absolutely no clue if this will work (may wipe your drive) but this firmware accesses IDE at 25Mhz instead of 7mhz.arkadiusz.makarenko wrote: ↑Mon Jul 20, 2020 8:08 pm With new firmware plus combination of all tricks I could find. I managed to get to 12 seconds boot time. Classic WB 68k on 8 GB CF card.
It is without MMULibs, but with cpu fastrom very high in startup-sequence.
I have noticed that initial startup is much faster with CF card than SD2IDE (more than 12 seconds just to start loading anything).
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
- arkadiusz.makarenko
- Moderator Team
- Posts: 1208
- Joined: Wed Jun 19, 2019 7:36 am
- Location: Edinburgh
Re: Figuring out the causes of slow disk access on the TF536
It didn't wipe my cards, but I didn't do any writes. It didn't have impact on speed of loading workbench or fake news sysinfo numbers. I didn't perform any more tests.
If there is even slight more chance of corrupted card on this firmware personally I wouldn't risk it.
PS
With 4096 block size on my SD cards system starts to load much quicker as well. It was about 10-14s after power on, now it is about 7s (almost like cf card) after power on, which makes 13s to load workbench vs CF 10s on CF card.
Conclusion: If your system loads very long on TF536, test firmware says everything is OK then this means you are doing something wrong!
PS2.
Do you think it is worth to write like tutorial how to set CF up?
If there is even slight more chance of corrupted card on this firmware personally I wouldn't risk it.
PS
With 4096 block size on my SD cards system starts to load much quicker as well. It was about 10-14s after power on, now it is about 7s (almost like cf card) after power on, which makes 13s to load workbench vs CF 10s on CF card.
Conclusion: If your system loads very long on TF536, test firmware says everything is OK then this means you are doing something wrong!
PS2.
Do you think it is worth to write like tutorial how to set CF up?
Do not trust people. They are capable of greatness.
~ Stanislaw Lem
~ Stanislaw Lem
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Figuring out the causes of slow disk access on the TF536
If that firmware works at all write will be fine.arkadiusz.makarenko wrote: ↑Tue Jul 21, 2020 7:46 pm It didn't wipe my cards, but I didn't do any writes. It didn't have impact on speed of loading workbench or fake news sysinfo numbers. I didn't perform any more tests.
If there is even slight more chance of corrupted card on this firmware personally I wouldn't risk it.
PS
With 4096 block size on my SD cards system starts to load much quicker as well. It was about 10-14s after power on, now it is about 7s (almost like cf card) after power on, which makes 13s to load workbench vs CF 10s on CF card.
Conclusion: If your system loads very long on TF536, test firmware says everything is OK then this means you are doing something wrong!
PS2.
Do you think it is worth to write like tutorial how to set CF up?
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: Figuring out the causes of slow disk access on the TF536
I haven't had any problems with the boot time on my TF536 rev 2b but I've been following this thread out of interest.
I've run a few tests on WB2.1, 3.0, 3.1, and 3.9 base installs with the TF536 (no IDE buffers installed) using the TF330 as reference.
* Start time is measured from switch on to the Workbench drive icon appearing on the screen.
I've run a few tests on WB2.1, 3.0, 3.1, and 3.9 base installs with the TF536 (no IDE buffers installed) using the TF330 as reference.
- 3.1 ROM in all tests
- MC68030RC50 in both cards
- In all cases the 2.1/3.0/3.1 Workbench base installs are approximately the same so I've just included 3.1 and 3.9.
- I tried the original 2b firmware and the test firmware from TF (534 timings), it didn't appear to make any difference to boot time or IDE speed.
- SD2IDE adapter with Verbatim Premium 16GB SD card (the 330 is on a 15cm cable, the 536 is on a 5cm cable)
- PFS3AIO PDS/03 formatted single 100MB partition image with 100 buffers and a 512B block size in all tests.
System | OS | Start time* | Sys info 4.3 disk speed |
TF536 | 3.1 | 19 seconds | 702KB/s |
TF330 | 3.1 | 10 seconds | 2.1MB/s |
TF536 | 3.1 with MMU Libs and MUFastRom | 19 seconds | 1.97MB/s |
TF330 | 3.1 with MMU Libs and MUFastRom | 10 seconds | 3.9MB/s |
TF536 | 3.9 | 44 seconds | 1.8MB/s |
TF330 | 3.9 | 30 seconds | 3.9MB/s |
TF536 | 3.9 with MMU Libs and MUFastRom | 43 seconds | 2.8MB/s |
TF330 | 3.9 with MMU Libs and MUFastRom | 30 seconds | 3.4MB/s |
* Start time is measured from switch on to the Workbench drive icon appearing on the screen.
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Figuring out the causes of slow disk access on the TF536
Thanks for that. I'd say that this entirely acceptable for the way we've avoided people needing to solder down an INT2 wire.
Remember the CD32 has an INT2 signal out on the edge connector. The TF536 emulates that .. so its slower. Its also 7Mhz vs 14Mhz.
Remember the CD32 has an INT2 signal out on the edge connector. The TF536 emulates that .. so its slower. Its also 7Mhz vs 14Mhz.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
-
- Posts: 290
- Joined: Thu Feb 28, 2019 5:02 pm
Re: Figuring out the causes of slow disk access on the TF536
Would it be possible and acceptable to make a firmware with and without INT2 emulation?
- 8 Bit Dreams
- Moderator Team
- Posts: 785
- Joined: Fri Nov 09, 2018 7:12 am
- Location: Germany
Re: Figuring out the causes of slow disk access on the TF536
Unlike TF534 there is no INT2 Pin on TF536
Retro computer hardware & repair in Germany
-
- Moderator Team
- Posts: 5389
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Figuring out the causes of slow disk access on the TF536
It’s literally the entire design goal of this card. I really invite people to read up before buying.Maximilian wrote: ↑Wed Jul 22, 2020 7:52 pm Would it be possible and acceptable to make a firmware with and without INT2 emulation?
Can people who want fast IDE not buy a TF536
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."