SpritesMind.Net

Both mega turrican ROMs are .bin files. Send me your dump if you wish and i will try it (fenix_awing@hotmail.com). On the sonic glitches, i did not tried anything on the other consoles (except for nomad) since we cleared the A21 bridge, you told me to focus on the asian, so i stored the others. Soni...

oh god....i have good/bad news. Bad news first...i was doing some testing on the mega turrican games so tested it on my other megadrives...got surprised that i got same behaviour of burbruees one. I cant load most games on the pal-G (original) and pal-I (moded) i experienced, black screen, red scree...

Ok, i've found the problem, it wasn't either of those. I was running Sonic 3 & Knucles, that roms generates the GDB-bridge error upon launching DDD. May be its due to the fact that this rom is dumped from a lock-on cartrigde sonic 3 + sonic & knuckles, and the behaviour may be different... I've trie...

Well this is what GDB-bridge returns Waiting for GDB connection on :8000... Got GDB connection from 127.0.0.1:56288 umdkDirectReadBytes(): Illegal direct-read from 0xFFFFFFF0-0xFFFFFFF1 range! umdkDirectWriteBytes(): Illegal direct-write to 0xFFFFFFF0-0xFFFFFFF1 range! Oh, perhaps DDD was still run...

New firmware solves the SD-card loader thing, about DDD: If that doesn't work, try running which ddd and dpkg-query -l ddd , and pasting the output of both commands here. Well this is what GDB-bridge returns Waiting for GDB connection on :8000... Got GDB connection from 127.0.0.1:56288 umdkDirectRea...

prophet36 wrote:OK here's a new software build...

Ok i've loaded the new firms and such, the md5 checksum is OK

d5a670db486de8597e214c6849fdfacb

But now, loading roms from SD, or launching DDD justs resets the megadrive. Loading a ROM via terminal still works btw.

Yes, they knew. Absolutely.

It was clearly explained in the original post, and in the private mails. they know what they are doing.

You have not read anything of whats going on. I dont care i you dont want to get involved but please dont lie.

But who will spend the money only for the chance of good testing results? Grind , did it mikejmoffitt, did it mswan, did it Burbruee, did it And me, i did it. But nevermind, your only interested in getting the final product. This will never will have a 100% working guarantee, its an amateur project...

No, its not guaranteed it will work, this run is for testing purposes.

I'm searching for more participants into the software testing thread. Thats it.

Your next toy. http://i.imgur.com/mdq21rk.jpg Hi all, if you've folowing recent posts about the umdk manufacturing, you know we're testing some nice kits. Since some of the original testers had RL issues we've got short on people testing. We have already succeded and the kit is running, but we want ...

I began working on a VM image that is all set up and good to go with Debian for SGDK / UMDK development. I already have the SGDK toolchain set up and ready to go, so once I get the UMDK working with everyone's help then I would like to add it to the VM as an option for people who may have trouble s...

Thanks! nice docs!

At this moment only 3 of 5 umdk has been tested, and only 1 of that 3 is fully working as intended (mine). I think the manufacturing process is somewhat ok but it caused some problems. Is there any way to do hardware checks, via software or via hardware? (db-electronics guy said something). May be i...

Noticed one more thing. Seems that it cannot save games I discussed this here . Having reacquainted myself with the code these last couple of weeks, I can confirm that the reason game-saves don't work is because I explicitly disabled writes to the 0x000000-0x3FFFFF region. Getting game-saves to wor...

OK Montserrat , can you try this updated FPGA binary? This just does back-to-back SDRAM refresh cycles until the 68000 starts executing. I've tried the new firmware, and it works perfect! Now its booting standalone in a second, it loads roms, can use DDD, even from nomad. Awesome job. Noticed one m...