Page 6 of 15
Re: kludge’s TF534 build
Posted: 27 Mar 2019 20:50
by terriblefire
I can try a ZII firmware for you guys but TBH the machine will not boot if i do that. You have a ram problem.
You need to add the address range 0x40000000 to 0x40400000 to the system pool somehow. I usually use AddMem but it doesnt work on Kick 1.3
I could give you a firmware where the ram doesnt autoconfig but appears in the above location. Then it would at least let you use addmem etc.
Re: kludge’s TF534 build
Posted: 27 Mar 2019 21:07
by 8 Bit Dreams
i can provide You 1.3 KS with scsi.device installed if that help, but this will not solve ZorroIII RAM Problem though..
You need to figure out why Your Amiga boots with KS 1.3 (256kb rom) and rejects to with KS3.1 (512KB),
onboard RAM failure can be a reasion fot that.. In other words - You need to remove all expansions and make Your Miga work (with all Kickstart versions) Then move 1 step forward..
Re: kludge’s TF534 build
Posted: 27 Mar 2019 21:17
by kludge
Ok... DiagROM fails the chipmem test on the A500 with the 68000 installed, but Workbench 3.1.4 boots from floppy without issues.
On the A500+ Diagrom shows a red screen briefly (checksum error?), but memory tests are good as far as I can tell. But with the TF534 installed it's the exact same problem as with the A500 on KS 3.1.4.
BTW. I'm using this:
https://github.com/terriblefire/terribl ... _alpha.zip
Maybe I should have started out by mentioning that? :)
Re: kludge’s TF534 build
Posted: 27 Mar 2019 21:35
by 8 Bit Dreams
kludge wrote: 27 Mar 2019 21:17
Ok... DiagROM fails the chipmem test on the A500 with the 68000 installed, but Workbench 3.1.4 boots from floppy without issues.
Workbench may boot in area that is not affected, THIS DOESN'T MEAN ANYTHING
kludge wrote: 27 Mar 2019 21:17
On the A500+ Diagrom shows a red screen briefly (checksum error?), but memory tests are good as far as I can tell. But with the TF534 installed it's the exact same problem as with the A500 on KS 3.1.4.
does this mean, You have two Amigas: A500 & A500+, while A500+ doesn't even boot with DiagRom?
this is Firmware pack? seems ok to me, using same binaries
Re: kludge’s TF534 build
Posted: 27 Mar 2019 21:50
by kludge
8 Bit Dreams wrote: 27 Mar 2019 21:35
does this mean, You have two Amigas: A500 & A500+, while A500+ doesn't even boot with DiagRom?
Yes, A500 and A500+. A500 and A500+ boots with the 68000, but DiagROM shows a red screen briefly at the beginning with A500+, but then starts as normal.
The 500 and the 500+ behave the exact same way with the TF534 trying to boot 3.1.4. Blinking power LED and resets every 7-8 seconds.
8 Bit Dreams wrote: 27 Mar 2019 21:35
Workbench may boot in area that is not affected, THIS DOESN'T MEAN ANYTHING
True, but KS 3.1.4 fails to do anything with the TF534 (on both machines, as well as on the A600, but that's for another day), but boots Workbench with the 68000. If the Amiga(s) was the main problem, shouldn't I get the same issue without the TF534?
I'm not trying to argue, just to understand.
Re: kludge’s TF534 build
Posted: 27 Mar 2019 21:53
by kludge
terriblefire wrote: 27 Mar 2019 20:50
I can try a ZII firmware for you guys but TBH the machine will not boot if i do that. You have a ram problem.
You need to add the address range 0x40000000 to 0x40400000 to the system pool somehow. I usually use AddMem but it doesnt work on Kick 1.3
I could give you a firmware where the ram doesnt autoconfig but appears in the above location. Then it would at least let you use addmem etc.
If I blank the RAM CPLD, would the card work at all? I understand I wouldn't get RAM (or IDE), but at least it could help narrow it down if 3.1.4 would boot then.
Re: kludge’s TF534 build
Posted: 27 Mar 2019 21:53
by terriblefire
kludge wrote: 27 Mar 2019 21:53
terriblefire wrote: 27 Mar 2019 20:50
I can try a ZII firmware for you guys but TBH the machine will not boot if i do that. You have a ram problem.
You need to add the address range 0x40000000 to 0x40400000 to the system pool somehow. I usually use AddMem but it doesnt work on Kick 1.3
I could give you a firmware where the ram doesnt autoconfig but appears in the above location. Then it would at least let you use addmem etc.
If I blank the RAM CPLD, would the card work at all? I understand I wouldn't get RAM (or IDE), but at least it could help narrow it down if 3.1.4 would boot then.
Unsure. There's a lot of chat between the two CPLDS.
Re: kludge’s TF534 build
Posted: 27 Mar 2019 22:06
by 8 Bit Dreams
ok, thanks for explanation, wasn't aware You have two Amigas, actually three if we cout A600 too, so well... Seems something is wrong with Your TF534 build. Do You have microscope? It's really really needed if it comes to debugging, trust me, i've built over 100x TF530, there so tiny bridges, and cold solder joints - You barely see them with microscope.
If You don't have one - well, try to resolder:
1. RAM cpld
2. RAM itself
3. 74ac16245 inverter
or make good and sharp high resolution pictures and upload them somewhere, maybe we will find something suspicious..
Re: kludge’s TF534 build
Posted: 27 Mar 2019 22:12
by terriblefire
8 Bit Dreams wrote: 27 Mar 2019 22:06
ok, thanks for explanation, wasn't aware You have two Amigas, actually three if we cout A600 too, so well... Seems something is wrong with Your TF534 build. Do You have microscope? It's really really needed if it comes to debugging, trust me, i've built over 100x TF530, there so tiny bridges, and cold solder joints - You barely see them with microscope.
If You don't have one - well, try to resolder:
1. RAM cpld
2. RAM itself
3. 74ac16245 inverter
or make good and sharp high resolution pictures and upload them somewhere, maybe i will find something suspicious..
If the 74AC16245 didnt work the CPU wouldnt boot diagrom. You can leave that alone i think.
Re: kludge’s TF534 build
Posted: 27 Mar 2019 22:15
by kludge
8 Bit Dreams wrote: 27 Mar 2019 22:06
ok, thanks for explanation, wasn't aware You have two Amigas, actually three if we cout A600 too, so well... Seems something is wrong with Your TF534 build. Do You have microscope? It's really really needed if it comes to debugging, trust me, i've built over 100x TF530, there so tiny bridges, and cold solder joints - You barely see them with microscope.
If You don't have one - well, try to resolder:
1. RAM cpld
2. RAM itself
3. 74ac16245 inverter
or make good and sharp high resolution pictures and upload them somewhere, maybe i will find something suspicious..
The A500+ is a very recent acquisition :)
I have a USB microscope as well as other magnifying options. I have checked, but I will check again tomorrow. And tomorrow I will hopefully get my new soldering station with hot air and preheater, so I could go over it with that. Or even desolder the chips and put them back on. (Practicing on a TF534 is a great plan, right? :))
terriblefire wrote: 27 Mar 2019 22:12
If the 74AC16245 didnt work the CPU wouldnt boot diagrom. You can leave that alone i think.
It would be interesting to know what it is that DiagROM misses in this case.
Unless I have two Amigas with different weird issues that causes the same problem with original kickstarts when running the accelerator.