Facility users emu all

Instruccions Step by Step

1) Install last java version download http://www.java.com/en/download/index.jsp

2) Extract package the program http://www.7-zip.org/ - compilations upload for me rev.7z ( includes the libraries .dll needed to execute on .7z pack )

3) Double-click on jpcsp.jar and you run the emulator

4) to run the games is as follows Ejemplar :

UMD games are if you copy the folder umdimages (the Interface Load -> UMD -> Select UMD Image detect and Load )

emulation of such a memory stick PSP ms0\PSP\GAME\folder name\ XXX.PBP File Ejemplar (The interface Load -> Memstick -> Selec file detect and load )

Items stored in the memory stick are located in the following path ms0\PSP\SAVEDATA\folder ULES GAME\ files .bin and .sfo a.k.a

5) if you have any questions do not hesitate to ask thanks


Build's lasted compiled

Uploaded REV 1082

Log last changes rev1071-1082
Quote:
fixed a typo

If you are like me, you think the loadingscreen the gba-emulator comes with by default is just plain ugly. With LSChange you are able to put your own loading-screen inside GBA.SIM.

Description:

LSChange replaces the Loadingscreen inside the GBA.SIM with an given Image.

Usage:

Come on, there's a self-explanatory GUI now ;P

Notes:

LSChange will backup your GBA.SIM as GBA.SIM.bak (if not already existent).
It handles different Image-Formats (.bmp, .png, .jpg, .gif, .tif).
LSChange needs .NET 2.0
you use this program on your own risk

Changelog:

Code: Select all
1.1:

[ADD] GUI
[ADD] Images of each size are now allowed and can either
be stretched to fullsize or displayed centered (in
this case the background will filled with a
selectable color)
[CHG] Commandlinearguments will be ignored

1.0:

Inital release

I didn't noticed this bug because as you know I modified my A320 and attached a serial port converter. Today I was playing around with it and noticed the problem.

It turns out that the Ingenic provided function to initialize the UART disables the pull-up resistors of the TX and RX pins. That means that the RX pin is left floating if not connected to an external circuit (which is the case of ALL of you). U-Boot listens to the serial port for commands, and if it detects a break condition or some other input, it stops the boot process and waits for further commands, which never arrive. The fix is as simple as leaving the pull-ups enabled.

I am sorry for not detecting this earlier. Please upgrade your dual boot.

Also, I made a couple of "aestetic" changes as suggested by someone: no more "white screens" while loading. The "white screen" glitch is caused by the LCD initialization code both in the original firmware system loader and in the linux framebuffer driver. Normally you should not see this white screen because the LCD backlight should be off. However the dual boot SPL shows the splash screen and leaves the LCD backlight on.

The original firmware case is solved by switching the backlight off just before jumping into the system loader. The system loader quickly initializes the LCD, so you'll see a black screen only for a split second.

However, in linux I cannot do that because it takes significantly longer for the framebuffer driver to kick in, so it's better to leave the LCD on. But here, as opposed to the original firmware, we have the sources. The solution has been just to always switch the backlight off before performing the LCD initialization in the framebuffer driver.