Page 2 of 2
Re: 536 woes
Posted: 29 Jun 2019 09:32
by 8 Bit Dreams
Yeah, but ATX isn't great for Amiga because +5V is not adjustable. You'll be surprised how much current is lost due cables Commodore used..
Also check Your voltage regulator, if its 800mA - try to swap it for 1A one..
Symptoms You described are highly likely PSU related Alen...
Re: 536 woes
Posted: 29 Jun 2019 10:23
by terriblefire
The TF536 regulator only powers the 3.3v components. I’d be surprised if that added up to much more than 100mA.
The under CPU caps is what I’d suspect now. Are they X7R?
Re: 536 woes
Posted: 29 Jun 2019 12:50
by 8 Bit Dreams
popped NTSC Agnus into A2k upgraded with TF536, switched it on and left my house for saturday shopping and burberry, came back home just right now - Frontier is still running nice even after 5 hours.. So yeah, NTSC Agnus is not a culprit, there must be something else..
Re: 536 woes
Posted: 29 Jun 2019 13:15
by terriblefire
NTSC is not gonna be the issue. The sampling happens at 100Mhz so a fractional difference in 7Mhz is never going to make this thing change behaviour.
Caps/PSU errors are random. Other errors will be immediately reproducible
Re: 536 woes
Posted: 02 Jul 2019 13:00
by alenppc
Sorry, I was away for a few days.
All the caps are X7R. All the components are literally the same as on the 330, except for the CPLD. I tried the original A500 PSU as well as my usual AT one. Same behaviour on the A1000 except for extra graphics glitches... I dunno. If you can send me another PCB Stephen, I will build a second one. Either the PCB has a defect or I screwed something up (although unlikely considering I swapped everything twice and got the same results...)
Re: 536 woes
Posted: 20 Mar 2020 08:23
by PaulJ_2.0
Just to clean this thread up in case people come from google, This issue was solved with the latest firmware.
Re: 536 woes
Posted: 20 Mar 2020 09:26
by PhilC
Thanks @PaulJ_2.0 I'll lock the topic.