foft Posted June 20, 2014 Author Share Posted June 20, 2014 (edited) Does your tv have a scart? This page has some links about making a cable: http://scarthunter.blogspot.ch/p/links.html?m=1 The core versions for mist are: RGB: 15khz composite sync on hsync pin VGA: 31KHz separate syncs VGA CS: 31KHz composite sync on hsync pin With 60Hz and 50Hz versions on each (ie for NTSC and PAL). I think Till released the firmware earlier today. (Edit: Ah, see you found it. F11 works? I'll test with this firmware tonight. F12 works on my firmware build (non public...). Edited June 20, 2014 by foft Quote Link to comment Share on other sites More sharing options...
greblus Posted June 20, 2014 Share Posted June 20, 2014 How cool . I'll make a proper cable then. Yes, F11 works. F12 is making the keyboard/joystick non-working. Quote Link to comment Share on other sites More sharing options...
foft Posted June 20, 2014 Author Share Posted June 20, 2014 (edited) F12 is a new firmware feature. Basically Till is adding OSD support to 8-bit mode for the other cores. Since I don't support OSD and need F12 I've built a new firmware for now. http://www.scrameta.net/autobuild/20140619/mist/firmware.upg NB: Till will likely release another official one in the next few days to replace this (+ I might have a new core that tells it I want F12). My build will also likely break the other new 8-bit cores if they actually have an OSD. edit: Till got in touch - likely we'll have an official firmware build tomorrow (or next few days at least) Edited June 20, 2014 by foft Quote Link to comment Share on other sites More sharing options...
foft Posted June 20, 2014 Author Share Posted June 20, 2014 I just posted a picture of my keyboard with the stickers on. http://www.scrameta.net/autobuild/keyboard.JPG I know its a rubbish picture, but it does at least show how the layout is intended to be In future revisions this will be changeable in config - e.g. for those US users. I'm pretty sure US keyboards don't have enough keys for the ASDF row though sadly... 3 Quote Link to comment Share on other sites More sharing options...
greblus Posted June 20, 2014 Share Posted June 20, 2014 Since I don't support OSD and need F12 I've built a new firmware for now. [...] [edit: Till got in touch - likely we'll have an official firmware build tomorrow (or next few days at least) Your firmware and new core works great and until new release from Till I've something to play with. Really impressive! Quote Link to comment Share on other sites More sharing options...
jugac64 Posted June 21, 2014 Share Posted June 21, 2014 Hi foft, thank you very much for releasing the core for the MCC-216! I am trying to test it. The instructions says that these files are required: System ROM: Loaded from /System/rom/atari800/atarixl.romBasic: Loaded from /System/rom/atari800/ataribas.rom Where can they be found? thanks again! Quote Link to comment Share on other sites More sharing options...
foft Posted June 21, 2014 Author Share Posted June 21, 2014 Look for xf25.zip. This contains both. The official release for mcc216 will be soon. They are just doing some testing, writing web pages etc. 1 Quote Link to comment Share on other sites More sharing options...
NML32 Posted June 21, 2014 Share Posted June 21, 2014 @jugac64 one thing you'll notice right away is the file selector. This core doesn't use the standard MCC-216 menu system. Adding and accessing programs is as easy as dropping them onto your sd card no crazy ini file to build! 1 Quote Link to comment Share on other sites More sharing options...
jugac64 Posted June 21, 2014 Share Posted June 21, 2014 (edited) Hi Mark, what MCC version are you using for testing? I am using the VGA version. I flashed correctly the VGA cores, but when I selected one of them only a black screen appears. When I selected the PAL core, the screen resolution changes to 720x576pix 50Hz, and when I selected the NTSC core it changes to 640x480pix 60Hz, but in both cases only a black screen remains. No response on keyboard keystrokes (my monitor can handle correctly both resolutions). This is my SD structure related to the Atari core. I downloaded 2 tested games from your list on the Google’s sheet. G:\System\Core\atari800\atari800core_NTSC_VGA.arg G:\System\Core\atari800\atari800core_PAL_VGA.arg G:\System\Rom\atari800\ataribas.rom G:\System\Rom\atari800\atarixl.rom G:\atari800\user\H.E.R.O..xex G:\atari800\user\Jungle Hunt.xex Any advice? Thanks!!! Juan Edited June 21, 2014 by jugac64 Quote Link to comment Share on other sites More sharing options...
NML32 Posted June 21, 2014 Share Posted June 21, 2014 Juan, your file structure looks fine. I think I had the same problem when using a sd larger than 2 gig. try a non HC card. Quote Link to comment Share on other sites More sharing options...
jugac64 Posted June 21, 2014 Share Posted June 21, 2014 Thanks Mark!!! it works fine on my 1GB microSD, now the test begins!!! The core is great foft! thanks again, what a nice weekend. Quote Link to comment Share on other sites More sharing options...
foft Posted June 21, 2014 Author Share Posted June 21, 2014 (edited) Yeah I think cards with >1GB have blocks >512 bytes so won't work. Same for MIST and DE1. Edited June 21, 2014 by foft Quote Link to comment Share on other sites More sharing options...
foft Posted June 21, 2014 Author Share Posted June 21, 2014 (edited) Actually it looks more complex than that... I need 512 byte blocks. Sd v1 has 512 byte blocks up to 1GB. Larger SD v1 cards can not be supported. SD v2 supports 512 byte blocks for all sizes. So SDHC should work with some adjustments.So I guess the sd init code (taken from sdrive) just has issues initializing some cards. I'm using petit fatfs that supports fat32 so file system should support them.So I expect larger cards work on MIST (I ask it for the sd sector and it does the low level) but not other targets. (edit: nope, my 2GB card doesn't work here either - checking if this is mist side or my side - probably my side!)Now to check to that theory. If true I'd better find a decent embedded sd over spi library... Edited June 21, 2014 by foft Quote Link to comment Share on other sites More sharing options...
NML32 Posted June 21, 2014 Share Posted June 21, 2014 (edited) F12 is a new firmware feature. Basically Till is adding OSD support to 8-bit mode for the other cores. Since I don't support OSD and need F12 I've built a new firmware for now. http://www.scrameta.net/autobuild/20140619/mist/firmware.upg NB: Till will likely release another official one in the next few days to replace this (+ I might have a new core that tells it I want F12). My build will also likely break the other new 8-bit cores if they actually have an OSD. edit: Till got in touch - likely we'll have an official firmware build tomorrow (or next few days at least) Till just released firmware_140621_r284.upg for the MIST F12 now works on A8 core. Edited June 21, 2014 by NML32 Quote Link to comment Share on other sites More sharing options...
foft Posted June 21, 2014 Author Share Posted June 21, 2014 (edited) Actually it looks more complex than that... I need 512 byte blocks. Sd v1 has 512 byte blocks up to 1GB. Larger SD v1 cards can not be supported. SD v2 supports 512 byte blocks for all sizes. So SDHC should work with some adjustments. So I guess the sd init code (taken from sdrive) just has issues initializing some cards. I'm using petit fatfs that supports fat32 so file system should support them. So I expect larger cards work on MIST (I ask it for the sd sector and it does the low level) but not other targets. (edit: nope, my 2GB card doesn't work here either - checking if this is mist side or my side - probably my side!) Now to check to that theory. If true I'd better find a decent embedded sd over spi library... Correction to my edit. My 2GB card does work on the MIST and DE1. However my 32GB one doesn't work on either... Via mist I can currently only address sectors up to 2^24, which gives max 8GB. Via DE1 - not sure... edit: found a 4GB card. Confirmed as failing on DE1 (and thus same on MCC216 - hardware here is the same pretty much) and working on the MIST. I'll ask Till if we can get > 8GB support and look into fixing DE1/MCC. Edited June 21, 2014 by foft 1 Quote Link to comment Share on other sites More sharing options...
jugac64 Posted June 22, 2014 Share Posted June 22, 2014 Hi foft, if we can donate you a Turbo Chameleon 64 and a Docking Station (joysticks interface), could you port also the Atari core to the Chameleon? I could ask on the TC64 mailing list for some investors… maybe there it is some interest on supporting this project. Best regards, Juan 1 Quote Link to comment Share on other sites More sharing options...
foft Posted June 22, 2014 Author Share Posted June 22, 2014 Hi Juan. Sure if you want to donate one I'll port it. I need to do the Sockit board first though, but the code is in a good position for new ports now. Quote Link to comment Share on other sites More sharing options...
jugac64 Posted June 22, 2014 Share Posted June 22, 2014 Thanks foft, great. Let me try to encourage others like me and I will keep you informed about any news. Best regards! Juan Quote Link to comment Share on other sites More sharing options...
+remowilliams Posted June 22, 2014 Share Posted June 22, 2014 Many thanks for the update! I'm enjoying it right now on the MiST \o/ One question, are there any plans to support artifacting? Or I suppose is that even a possibility given the nature of the beast. Quote Link to comment Share on other sites More sharing options...
NML32 Posted June 22, 2014 Share Posted June 22, 2014 foft, could you list a few cart roms that work? I've tried a few 8k carts but they just boot to a ready screen. Thanks Quote Link to comment Share on other sites More sharing options...
foft Posted June 22, 2014 Author Share Posted June 22, 2014 Re ROM cartridge support: Nope - I only tried two and one worked. To be honest I wouldn't expect any to work since its not really implemented properly. It just loads the ROM over the top of basic. So surprised you are getting a ready screen since that is overwritten... Maybe its completely broken! Re artifacting: I've not thought about it. All those games were broken for PAL anyway. Do you get any if you put it through an RGB to composite adaptor? I guess so but the wrong colours? Quote Link to comment Share on other sites More sharing options...
jugac64 Posted June 22, 2014 Share Posted June 22, 2014 (edited) Hi Juan. Sure if you want to donate one I'll port it. I need to do the Sockit board first though, but the code is in a good position for new ports now. Hi foft! we already have some people interested on supporting this project, I hope we can get all the resources during the next week, thanks! More info about the request here: https://groups.yahoo.com/neo/groups/chameleon_64/conversations/topics/3817 Edited June 22, 2014 by jugac64 1 Quote Link to comment Share on other sites More sharing options...
NGFrankW Posted June 22, 2014 Share Posted June 22, 2014 (edited) Hi foft, my congratulations for your first unified release for four FPGA boards!I have made a quick test of the MCC216 version and it looks already very good.Have discovered only a small graphics glitch with Dimension X, tested with the NTSC VGA core.Looks like there are four fine diagonal RGB stripes. These appear only in this games sequence: A closer look: Presently the settings and load menus are controllable by the joystick and the fire button.Controlling these by the cursor, enter and ESC buttons of the PS2 keyboard would be nice Great release! Frank Edited June 22, 2014 by NGFrankW Quote Link to comment Share on other sites More sharing options...
foft Posted June 22, 2014 Author Share Posted June 22, 2014 Hi foft! we already have some people interested on supporting this project, I hope we can get all the resources during the next week, thanks! More info about the request here: https://groups.yahoo.com/neo/groups/chameleon_64/conversations/topics/3817 Great:-) Quick question - just doing some research on the Chameleon. The FPGA pins file shows a real USART (TX/RX/CTS/RTS), however I can't see it on the board. Do these just go to headers as 3.3V raw FPGA connections? Quote Link to comment Share on other sites More sharing options...
foft Posted June 22, 2014 Author Share Posted June 22, 2014 Have discovered only a small graphics glitch with Dimension X, tested with the NTSC VGA core. Weird... I'll take a look. I agree on the keyboard menu control. 1 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.