I am as keen as mustard, like the rest to build one of these terrific boards, but I am also on the same page as TF on a large sample of a untested altered design.
Happy either way, to test the new design or wait for the next batch
Limited TF536 Run - Sort of Sales (All gone)
Moderators: terriblefire, Terriblefire Moderator
Re: Limited TF536 Run - Sort of Sales (All gone)
Life is really simple, but we insist on making it complicated - Confucius
Re: Limited TF536 Run - Sort of Sales (All gone)
So I thought why the hell not and added these using a SIL-10 resistor pack bodged on to those address lines on the CPU socket pulled up to Vcc.terriblefire wrote: ↑Sun Feb 23, 2020 5:52 pm 1) 4K7 pull ups are needed on A31-A24 + A0 (as they can float).
Maybe it's placebo but my CPLD seems a bit cooler too - still the warmest thing on the board but I don't think as bad as before. Shame I don't have any way of measuring the temperature properly other than the frontier intro + pinky touch test.
Re: Limited TF536 Run - Sort of Sales (All gone)
I think shipping around the world is about to ground to a halt...?
Re: Limited TF536 Run - Sort of Sales (All gone)
Transport of people, yes.
Transport of goods, no.
For now...
Transport of goods, no.
For now...
Re: Limited TF536 Run - Sort of Sales (All gone)
It's all at https://github.com/agranlund/tf534terriblefire wrote: ↑Sat Feb 15, 2020 4:23 pm If i had a set of @agranlund's patches i could incoroprate those into the 536 build process and always produce an ST version.
I am not terribly well versed with Github but if there's anything I can do to help produce the necessary diff/patches from that fork let me know
Cheers,
--Anders
-
- Moderator Team
- Posts: 5368
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: Limited TF536 Run - Sort of Sales (All gone)
How did you handle the fastram in there then? I'm curious how to make 64Mb fastram available on an ST.agranlund wrote: ↑Mon Apr 13, 2020 7:22 pmIt's all at https://github.com/agranlund/tf534terriblefire wrote: ↑Sat Feb 15, 2020 4:23 pm If i had a set of @agranlund's patches i could incoroprate those into the 536 build process and always produce an ST version.
I am not terribly well versed with Github but if there's anything I can do to help produce the necessary diff/patches from that fork let me know
Cheers,
--Anders
———
"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: Limited TF536 Run - Sort of Sales (All gone)
I'm planning to get my next 536 set up on an ST, so can test out the firmware etc if you guys need it.
If it ain't broke, test it to Destruction.
Re: Limited TF536 Run - Sort of Sales (All gone)
Atari 32bit FastRAM is at 0x01000000 onward (called TT-RAM in Atari lingo).terriblefire wrote: ↑Mon Apr 13, 2020 8:30 pm How did you handle the fastram in there then? I'm curious how to make 64Mb fastram available on an ST.
Just make sure it cannot read/write past your 64MB since the operating system(s) rely on getting a bus error at the end when probing how much FastRAM is installed.
EmuTos will pick up and use this RAM automatically.
Atari TOS does not unless the machine is an Atari TT - the only machine which officially had FastRAM, hence the need for additional "driver" (MAPROM takes care of this if needed)
This is what I did in autoconfig.v for the TF534:
assign DECODE[RAM_CARD] = ({A[31:22]} != {8'h01, 2'b00}) | shutup[RAM_CARD]; // 4MB TT-RAM
and likewise for the TF530:
assign DECODE[RAM_CARD] = ({A[31:21]} != {8'h01, 3'b000}) | shutup[RAM_CARD]; // 2MB TT-RAM