TF4060 Rev2

[Higgy]

^ @terriblefire cheers I found that now about 1hr30 in. Some good stuff and that cooler from Goose!

Any chance of putting up the 'demo loop' CF card image somewhere to download?

There is another South West Amiga Group meet on 18th Feb. Not sure when the TF4060 will be out the door, but it would certainly be good to demo it there if it's available. There are a fair number of 4K owners that turn up. Quite a few TF1260 were at the last meet in Sept so it's definitely been a hit.

[terriblefire]

^ @terriblefire cheers I found that now about 1hr30 in. Some good stuff and that cooler from Goose!

Any chance of putting up the 'demo loop' CF card image somewhere to download?

There is another South West Amiga Group meet on 18th Feb. Not sure when the TF4060 will be out the door, but it would certainly be good to demo it there if it's available. There are a fair number of 4K owners that turn up. Quite a few TF1260 were at the last meet in Sept so it's definitely been a hit.

The demo CD is still WIP... but i'll do some more on it and release it at some point. I'm aware of its limitations so i can work round them... but i'll sort them out.

I've got major house rennovations underway right now but the TF4060 is the main machine on the bench. Unfortunately i keep having stupid issues like bad power supplies etc. Working on these though. Mostly working on the driver/rom/os support to make IDE rocket fast right now.

[erique]

@terriblefire you mentioned Amiga's Internal IDE is fine, how is the Boot Priority? Does the TF boot first?

At boot-up 'strap' (which is part of the Kickstart) will (among other things) go through the list of bootable device nodes (ExpansionBase->MountList). Each of these nodes corresponds to *something* that can boot, and each node has a priority.

The IDE driver adds a node for each partition it finds during the mount process (which is basically reading the RDB/PART information of the disk; typically the first blocks of the device).
The PART information contains (among other things) the PartitionBlock->pb_Environment, which for an AmigaDOS partition is a DosEnvec.
This struct contains the 'de_BootPri' which is used when adding the new node to the MountList.

TL;DR - the partition information on disk holds the boot priority information.

[quantum8]

This is amazing. I was tempted by the BFG but this will probably suit my needs more. Hopefully I can get my a4000 working by the time these are available!

[Higgy]

@terriblefire if you still need a PSU I've now finished with my ATX one which worked fine for setting up my 4000. I can send it to you if you need it.

I got this as a replacement: Be quiet! SFX POWER 3 450W 

[terriblefire]

@terriblefire if you still need a PSU I've now finished with my ATX one which worked fine for setting up my 4000. I can send it to you if you need it.

I got this as a replacement: Be quiet! SFX POWER 3 450W 

I'm planning on going to an arcade switcher setup TBH. I need time to wire it up. MAJOR houseworks underway so there is just no time to look at this.

[Higgy]

Hi @terriblefire just wondering if you have any updates to share? I think on YT you mentioned you were going to work on IDE side of things?
Is IDE already up to TF1260 levels? Because you went to the effort of adding a RPi header for easier Firmware updating, could you not start a limited card roll out?

I expect your probably knee deep in Sega Rally woodwork or electronics

[terriblefire]

Hi @terriblefire just wondering if you have any updates to share? I think on YT you mentioned you were going to work on IDE side of things?
Is IDE already up to TF1260 levels? Because you went to the effort of adding a RPi header for easier Firmware updating, could you not start a limited card roll out?

So the issue we have right now is that everything worked at Amiga 37 but when i came back to it the machine would not boot anymore. Its a frustrating step backward.

@erique is working on the IDE driver. The issue is that when we put it in ROM the driver code is effectively in a memory area 8 bits wide so code execution is very slow.

We're also facing issues with the yosys toolchain that doesnt seem to be very stable.

So in short i think we're not as close as we thought we were. But @erique and I will hook up at Revision to do some work on this.

[Higgy]

Thanks for the update and enjoy Revision.
Last year was a bit of a damp squid, so with it being face-to-face this year I am expecting some cool stuff being released by groups in person

[terriblefire]

Thanks for the update and enjoy Revision.
Last year was a bit of a damp squid, so with it being face-to-face this year I am expecting some cool stuff being released by groups in person

So a little update on this. We had 3 4060s at revision and we discovered faults with my A4000 + probably my 4060 card too. So i've been held back by actual hardware faults. I'm now looking at this with more focus.