coonsgm wrote: 30 May 2025 20:21
I don't have the cap on the CPU. I believe I removed it previously. Can you share a photo of which pins it goes between?
Welcome back ;)
Currently you should probably use CURRENT7 firmware as I think I broke something after that..
IMG_3301.JPG
You do not have the required permissions to view the files attached to this post.
coonsgm wrote: 30 May 2025 20:21
I don't have the cap on the CPU. I believe I removed it previously. Can you share a photo of which pins it goes between?
Welcome back ;)
Currently you should probably use CURRENT7 firmware as I think I broke something after that..
IMG_3301.JPG
Good to be back working the Atari's! Traveling for work has been a bear....
current13 *should* work better, but current7 is the "last known good stable". But 13 *should* be best now.
I won't have time to do much testing until next week now.
I'm using slow slew currently. Fast slew doesn't work at all.. So not sure whats acting up there.. I remember TF said only use slow slew, he mentioned it was likely the SDRAM clocks ringing.. but I have resistors on my current board.. so it can't be that.
Firmware 8-12 are likely buggy and shouldn't be used..
exxos wrote: 30 May 2025 20:50
current13 *should* work better, but current7 is the "last known good stable". But 13 *should* be best now.
I won't have time to do much testing until next week now.
I'm using slow slew currently. Fast slew doesn't work at all.. So not sure whats acting up there.. I remember TF said only use slow slew, he mentioned it was likely the SDRAM clocks ringing.. but I have resistors on my current board.. so it can't be that.
Firmware 8-12 are likely buggy and shouldn't be used..
Flashed to rev 7, checked and reflowed every connection on the Xilinx (I think my issue was a bad connection on one of the legs)....and voila!
IMG_2942.jpg
You do not have the required permissions to view the files attached to this post.
I get this result regardless of whether I run blitfix or not. Physically removing the blitter chip fixes this issue though....so I expect that the blitter has something to do with the issue.
coonsgm wrote: 31 May 2025 03:55
I get this result regardless of whether I run blitfix or not. Physically removing the blitter chip fixes this issue though....so I expect that the blitter has something to do with the issue.
It happens when blitter can't access ROM.. give current13 firmware a try..
Working like a charm! I'll do some more thorough testing. Unfortunately, the new STE I have coming won't be here until early next week (darn shipping delays).
coonsgm wrote: 31 May 2025 12:40
Working like a charm! I'll do some more thorough testing. Unfortunately, the new STE I have coming won't be here until early next week (darn shipping delays).
:bravo:
Hopefully @Badwolf will have some better news next...
