Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - Chilly Willy

Pages: [1]
Mega EverDrive / Wolf32X
« on: July 12, 2014, 09:27 PM »
I've updated my old-ish Wolf3D port for the 32X. So why the bump? There was an issue on the MED with the old version - the save game file for Wolf3D was too big to fit in the save ram for the MED. Well, I finally got around to adding compression (among other things). So now you not only can save properly, but I was able to give the saves two slots for saving.

Other updates include: auto-map now saved as well; plays FM music if you don't have the SegaCD and a music CD in it; bumped the sample rate from 14kHz (2X normal) to 21kHz (3X normal) to get rid of the whine in the audio a few people reported; improved the CD audio support a little; the frame buffer is now updated asynchronously via DMA (makes the game a little more smooth).

Note: with the current settings, compressing the save takes slightly over 15 seconds. Decompression makes no noticeable change to the load speed.

Off Topic / What's the deal with the Development forum?
« on: May 25, 2013, 01:48 AM »
Someone with only three posts, but apparently admin power, moved ALL the threads out of the development forum - even when the thread is on development on an Everdrive cart!  :o

What the hell, man!!

Mega EverDrive / Looking for some info...
« on: January 03, 2013, 12:43 AM »
I just got my MegaEverdrive and had a question...

Code: [Select]
    void (*osSetMemMap)(u16 map); //memoty configuration 4x1Mb
Looking at the sample boot code, I notice

Code: [Select]
    move.w #0x210f, 0xA13006
I assume the function does the same as the assembly? It stores the word passed in to 0xA13006? From how the memory is said to be configured, I assume each nibble represents one of the 1MB spaces in the rom area, with the MSN being 0x300000 - 0x3FFFFF down to the LSN being 0x000000 - 0x0FFFFF, and the value of the nibble represents the 1MB block of sdram that is mapped to the corresponding space, right?

So we have the first 1MB holding the OS, the second 1MB holding the application, and the third and fourth 1MB are free for bank switching data for the application. Are any of these spaces write protected? Does the sdram need to be written as words, or can it be written a byte at a time... or is it only "writable" through loading from the SD or USB ?

For the stereo DAC, if the MSB left or right?

Turbo EverDrive / SDK?
« on: July 29, 2012, 05:58 AM »
Now that I have my Turbo Everdrive coming, I was wondering when we'll see an SDK to use it in homebrew?

Pages: [1]