First I would suggest to just go with 16 bit images to avoid using CLUTs.
Once you manage that then start using palletized images.

You should upload image to VRAM outside of your display buffer (usually 320,0 should suffice) and then make a sprite out of it. After that set up a game loop and draw ...

You can place CLUT anywhere in the VRAM. I'm not sure I understand when you say that it will all be filled up...

As for displaying text you can use FntPrint() function. printf is for debug only and is usually used on serial port..
However I encurage you to write your own text displaying routine ...

Shouldn't be difficult. Take a look at the sio echo example in the SDK.
--
You can check each game loop if there is a character waiting in the RX buffer and execute
a function based on the value.

There is also a SIO interrupt available but for simple stuff like this it's not necessary to set it up.

Yes. For NES games you can use "It Might Be Nes".

I suggest you go with some other cable. I replaced one of the broken cords with CAT 5 and it is a bit too stiff.

I think 8 wire shielded alarm cable would be perfect for the job.
And replace the whole cable (not just from the ferrite bead to controller).

If you look at the front side of connector ...

It's a great idea but lack of updates rendered it useless. Shame, if only it was developed further.
And it uses Blade's libs which need to be launched with PsyQ made application which defeats purpose of using open source libs...

It's possible since it's basically the same machine (with a few subtle differences) in a smaller form factor.

Yaroze has a different mechacon then retail units which allows you to boot software from all region plus yaroze discs.
That can be solved by installing a modchip, either MM3 for SCPH-101 or ...

Shadow wrote:There are two blue versions of the debuggers (you having the last revision) because apparently there was a printf bug in the earlier blue debugger).

Do you have more info on that bug?

Is that noise coming from the speakers or the unit itself?
Was it working properly before or you perhaps bought it broken?
Is it grinding noise, high pitch or something else? Perhaps you could record a video of the problem...

Funny. I always thought there would be more to it than what the cart contains...

I have an idea though.
If that cart only places PSX-EXE and GB ROM into RAM then after a reset it should still stay in memory.
I could modify my BIOS dumper to dump any part of the RAM to serial port and use BIOSGet to ...

Don't forget that connector has two vcc pins, a 3.3 V one and 7.6 one.
That's probably why your controller works but it has no rumble.

Adapted? No. Because this simulates a PS1 side of thing and acts as a SPI host.

However if written from the scratch it should be doable. The first problem with this I see is that
you need a device that acts both as a SPI slave (for Memory Card) and SPI master (for SD card).
So, maybe some other ...

Awesome, as usual

Orion_ wrote:does your tool will be open source ?

Guess what I open sourced it.
You can visit the git repository here.

You will have to open it up and see how it looks on the inside. There could be corrosion.
For many people nowadays PS1 just takes space so they toss it in some storage
(attic, basement, shed, etc) and there could be moisture.
I bought one which was so bad that nothing (except plastic case) could be ...

You probably need a slightly different syntax.
The code i posted above compiles fine with the MIPS configured GCC core toolchain I'm using (PSXSDK).

Try with this:

Are you talking about PSone when you say PS1? Because PS1 means all PlayStation 1 models (fat and slim).

Yes, MM3 works on PSone but if you are using it with a PAL console
you won't be able to boot NTSC titles without a boot disc.

That's because an extra check in BIOS was added to those models.
To ...

I agree, it's very cool. Tested on SCPH9002 and SCPH102 and works great.
Maybe you should add a widescreen toggle option

I made a Gtk# port of BIOSGet application for Linux and OS X users.
Mono is still required but the application works properly now.

Do you have a multimeter? Check continuity from adapter to the end of the serial cable.
Also make sure that you actually connect to TX and RX lines on a cable.

And leave CTS - DTR connected at all times.

BTW: BIOS and games won't print debug info even if your cable is working properly because ...