REMINDER - Stay logged in for at least 2 hours a week to get whitelisted.
Also it helps build a picture where our "good traffic" is coming from for detection scripts.
:o)
Also it helps build a picture where our "good traffic" is coming from for detection scripts.
:o)
Building an STe536
-
Steve
- Moderator

- Posts: 3334
- Joined: 15 Sep 2017 11:49
Re: Building an STe536
Thanks! Also good job on your build, I watched your youtube video on it last night :)
-
exxos
- Site Admin

- Posts: 28602
- Joined: 16 Aug 2017 23:19
- Location: UK
Re: Building an STe536
@Steve
You do not have the required permissions to view the files attached to this post.
-
Steve
- Moderator

- Posts: 3334
- Joined: 15 Sep 2017 11:49
Re: Building an STe536
Cheers @exxos , do I need to know where the little white wire goes to?
-
exxos
- Site Admin

- Posts: 28602
- Joined: 16 Aug 2017 23:19
- Location: UK
Re: Building an STe536
Nope, it was just a test wire to connect my scope to.Steve wrote: 21 Jul 2024 21:06 Cheers @exxos , do I need to know where the little white wire goes to?
-
Badwolf
- Site sponsor

- Posts: 3057
- Joined: 19 Nov 2019 12:09
Re: Building an STe536
Looks a beaut. Good work!
Although I can tell you right now soldering those pin headers that close to the PLCC socket would end in disaster in my hands! :fan:
Cheers,
BW
DFB1 Open source 50MHz 030 and TT-RAM accelerator for the Falcon
Smalliermouse ST-optimised USB mouse adapter based on SmallyMouse2
FrontBench The Frontier: Elite 2 intro as a benchmark
Smalliermouse ST-optimised USB mouse adapter based on SmallyMouse2
FrontBench The Frontier: Elite 2 intro as a benchmark
-
Steve
- Moderator

- Posts: 3334
- Joined: 15 Sep 2017 11:49
Re: Building an STe536
Yeah it definitely needed my smallest soldering tip :)
-
Steve
- Moderator

- Posts: 3334
- Joined: 15 Sep 2017 11:49
Re: Building an STe536
After doing the extra steps @exxos showed me:
OK now to proper beta testing!
Issues experienced so far:
1. System doesn't start unless I press reset
- The motherboard is already fully recapped, using a re-capped SR-98 PSU, the C100 reset cap is 53uf. I may just experiment with different C100 values to see if I can fix this, unless anyone has another idea.
2. System randomly reboots
- Might be related to ACSI hard disk access
3. I was writing MAPROM and BLITFIX from Gotek to ACSI C:\AUTO, the system repeatedly would not finish writing the second PRG file, it'd say that drive C was inaccessible or corrupt. Trying again it'd fail to read the floppy drive. (so the problem seemed to change slightly)
- I think I might stop using my ACSI drive for my next tests and move totally to IDE/CF card
4. After managing to get MAPROM and BLITFIX inside C:\AUTO (I put the old 68k cpu back in to copy from floppy to ACSI) the system will crash / hard lock when loading MAPROM.PRG out of AUTO (on the ACSI drive) I then tried loading MAPROM from within TOS, this also caused a hard lock (no bombs, just pure lock-up)
My thoughts so far: Firstly I just want to point out, this STe motherboard is 100% re-capped with all mandatory fixes, including bus resistor changes done. The PSU is outputting a beautiful 5.1V stable as a table. A lot of these issues seem to revolve around ACSI (I am using an ACSI2SD, which works perfectly fine in normal 68k cpu) This particular motherboard also has the fabled 'good dma'. I will next do testing on IDE only, to completely rule out ACSI access as being the cause for many of these problems.
OK now to proper beta testing!
Issues experienced so far:
1. System doesn't start unless I press reset
- The motherboard is already fully recapped, using a re-capped SR-98 PSU, the C100 reset cap is 53uf. I may just experiment with different C100 values to see if I can fix this, unless anyone has another idea.
2. System randomly reboots
- Might be related to ACSI hard disk access
3. I was writing MAPROM and BLITFIX from Gotek to ACSI C:\AUTO, the system repeatedly would not finish writing the second PRG file, it'd say that drive C was inaccessible or corrupt. Trying again it'd fail to read the floppy drive. (so the problem seemed to change slightly)
- I think I might stop using my ACSI drive for my next tests and move totally to IDE/CF card
4. After managing to get MAPROM and BLITFIX inside C:\AUTO (I put the old 68k cpu back in to copy from floppy to ACSI) the system will crash / hard lock when loading MAPROM.PRG out of AUTO (on the ACSI drive) I then tried loading MAPROM from within TOS, this also caused a hard lock (no bombs, just pure lock-up)
My thoughts so far: Firstly I just want to point out, this STe motherboard is 100% re-capped with all mandatory fixes, including bus resistor changes done. The PSU is outputting a beautiful 5.1V stable as a table. A lot of these issues seem to revolve around ACSI (I am using an ACSI2SD, which works perfectly fine in normal 68k cpu) This particular motherboard also has the fabled 'good dma'. I will next do testing on IDE only, to completely rule out ACSI access as being the cause for many of these problems.
You do not have the required permissions to view the files attached to this post.
-
PhilC
- Moderator

- Posts: 7495
- Joined: 23 Mar 2018 20:22
Re: Building an STe536
Great to see you've got it up and running @Steve, well done.
If it ain't broke, test it to Destruction.
-
HigashiJun
- Posts: 2388
- Joined: 19 Jun 2020 07:21
- Location: Tokyo
Re: Building an STe536
:girldance:
Who is online
Users browsing this forum: apple [bot], ClaudeBot and 4 guests