Icky wrote: 01 Jan 2019 02:12
I have a working STFM arriving in the next few days so will try the board out on that one too. If I am still having issues I will send my DVI board to exxos to check on his STFM to see if it is working there.
:thumbup:
I forgot (Again sorry) what you was using before, think it was the "ST" and STF remake ? So STFM would be good as its what I tried it out on.
Icky wrote: 01 Jan 2019 02:12
I have a working STFM arriving in the next few days so will try the board out on that one too. If I am still having issues I will send my DVI board to exxos to check on his STFM to see if it is working there.
:thumbup:
I forgot (Again sorry) what you was using before, think it was the "ST" and STF remake ? So STFM would be good as its what I tried it out on.
Problem exists on 520ST and STF Remake so as you say trying on an STFM would be good.
10nF actually made the board not work - black screen.
47pF works fine.
Screen is now stable on STFM.
EDIT: Just tried the HDMI board back in the STF Remake and 520ST with the 47pF cap in place and its even more temperamental. Some times its just a blank screen like when I used the 10nF when in the STFM and not very often it might try to boot and of course reset. On reset it mostly goes back to blank. I guess the 16MHz line is not so happy in these two machines with the cap on it.
Re: Project: HDMI/DVI out for STFM
Posted: 05 Jan 2019 21:01
by exxos
Icky wrote: 05 Jan 2019 20:06
10nF actually made the board not work - black screen.
47pF works fine.
Screen is now stable on STFM.
EDIT: Just tried the HDMI board back in the STF Remake and 520ST with the 47pF cap in place and its even more temperamental. Some times its just a blank screen like when I used the 10nF when in the STFM and not very often it might try to boot and of course reset. On reset it mostly goes back to blank. I guess the 16MHz line is not so happy in these two machines with the cap on it.
Anything over about 390pF will squash the signal to much. Its not a good fix, but I still suspect its a clocking issue.