Uae4arm (arm jit)

[trixster]

Rpi developments:

https://www.raspberrypi.org/forums/v...?f=78&t=110488

[lubomyr]

Android port updated
added latest changes from Pandora port by TomB

- Commandline options available:
-config=/path/file.uae to load specific config file (set option use_gui=no in config file to start without showing gui)
many other options like in WinUAE
- JIT now save for 24-bit CPUs (68000, 68EC020)
- Bugfix in sigsegv handler for JIT
- Added ZorroIII fast memory (currently max. 32 MB, does somebody needs more?)
- Added Picasso96 (required version of rtg.library: 40.3993 or higher)
- Selection in CPU dialog fixed
- {L}+{r}+dPad up and down: adjust Amiga screen

http://boards.openpandora.org/topic/...4arm/?p=384389

android port sources: https://github.com/lubomyr/uae4arm

apk: https://dl.dropboxusercontent.com/u/...m-17052015.apk

[lubomyr]

Android port updated

- fixed on-screen control
- added more picasso96 screen modes

https://dl.dropboxusercontent.com/u/...m-18052015.apk

[Higgy]

Hi,

I tried the version you posted @ Yesterday, 23:07 on my OUYA today.

I need to try using the initial settings (@ the SDL screen) I used for UAE4ALL on this one as I don't think things were set right. It seemed to crash a lot and I could not navigate through the MENU to a .hdf & I did not get a .ADF to work. I will try hopefully tomorrow with your new .APK posted today.

I noticed no ANDROID keyboard appears when trying to type-in a Config name etc in the menu. I did not have a USB hub & keyboard to hand to see if that works.
When it give the speed for PANDORA (600MHz default), should that be left alone? Is it disabled in .APK & Raspberry Pi? Or is it slowing down the emulation if left at 600MHz?

[Higgy]

Thanks for your work @lubomyr

Just another quick update using 18052015 on OUYA:

Issue when I move right using OUYA joypad in the MENU from RESET to EXIT to START, it freezes when I try moving from EXIT to START. I have to quit out.

HDF Files:
I cannot add a .HDF file. I can select the file in the directory I want, but I cannot add a Volume Name so when I click on OK it does nothing. If the on-screen Android keyboard appeared in Vomue Name I could tap in a name, is this possible to implement? I will try again this evening with a USB hub and keyboard to see if I can type in a name and re-try (I checked on a Samsung S3 and an on-screen keyboard appears, maybe I need to install an additional keyboard .APK on the OUYA?).

Also I cannot move the OUYA joystick to access 'Hard Drives' sub menu. I can move down the main menu, but cannot move 'right' into the sub-menu. Usually when you move 'right' into a sub-menu the top left button is highlighted, on 'Hard Drives' the buttons are bottom left 'Add Directory' & 'Add Hardfile'.

Many of the menu sub-menus have to be accurately 'clicked' on a certain location, not the middle of the button, the OUYA touchpad is pretty bad. Is there a way of making the 'activation' points larger?

Final question, on UAE4ALL2 mapping 'LALT' to L3 on the OUYA joypad swapped between Mouse & Joystick. Does UAE4ARM have this? I tried mapping, but there does not seem to be a 'on-screen' graphic to show the mouse/joypad switch like on UAE4ALL2.

Thanks

[lubomyr]

@Higgy
I tested with my gamepad and can confirm bugs with freezing and with Hard Drive Selection. I will try to fix it.

Remap click button for gamepad probably possible i must check.

SDL settings for gamepad same uae4all2 (probably differences in core of uae4arm code)

# Redefine gamepad keys to SDL keysyms, button order is:

# A B X Y L1 R1 L2 R2 LThumb RThumb

RedefinedKeysGamepad="HOME END PAGEDOWN PAGEUP RCTRL RSHIFT F14 F15 PAGEDOWN HOME LCTRL"

click work via PAGEDOWN keycode

Swap between Joystic and mouse look like supported in uae4arm too. I will try to implement switch for it.

[lubomyr]

https://dl.dropboxusercontent.com/u/...18052015-2.apk

- fixed trouble with freezing in menu (via dpad)
- fixed problem with navigation in hard drive submenu (via dpad)
- empty fields with device and volume name will be auto filled when added new harddrive.

[Higgy]

Thanks.
OK a little test. I managed to get some .HDF to boot and played some games
SWOS played well, accurate timing for pass/shoot.
Key mapping works to swap from mouse to joystick, although no onscreen graphic to show you have swapped.
I cannot get on-screen keyboard to work.

Is there an issue with saving config? I ask because Kickstart does not seem to stick once I exit and reload, i have to select again from Kickstart drop down menu.

Also it seems to hang/crash when selecting 'Add Directory' in Hard drives.

Your fixes worked, thanks

[lubomyr]

No idea with config. It works for me.
You can try select kickrom, then save default config "uaeconfig" then
via any text editor open uaeconfig.uae (located android/data/atua.anddev.uae4arm/files/conf/ )
and check path in line
kickstart_rom_file=

I can confirm crash of adding harddrive when emulation is active. I hope it will be fixed.

also some known bugs
Picasso96 - works not correct in JIT mode, too much graphics glitches, in non-jit mode also visible some graphics glitches with picasso.
Sometimes after adding directory, we can see cutted few last chars of path, as result path to directory is incorrrect.

[amiga1200gamer]

not sure if this is relavent to Higgy's post (OUYA config saving).. but i had similar issue on raspberry pi build. The empty "conf" dir was missing so i had to manually "mkdir conf". After doing this config files saved perfectly through the menu.

[Ariath]

Hi all!

I have tested the APK in my MK902II (http://www.rikomagic.com/en/product/...56_pid_20.html) and my tablet (http://approx.es/APPTB103S) and i'm noticing two things:

- With default settings and amigaos-130 Cloanto Kickstart ROM, playing a game like Turrican i experiment around 0.5-1.0 seconds lag in audio (i have tested this jumping and shooting).

- (Only in the MK902II) Using a bluetooth mouse, i have to click any control two times to obtain a response, and, if i click a slider, it seems to stick to the mouse cursor.


I have to say that i experiment these problems with both UAE4ARM and UAE4ALL2 .
I'm the only one with these problems?

See ya

[lubomyr]

Originally Posted by Ariath

Hi all!

I have tested the APK in my MK902II (http://www.rikomagic.com/en/product/...56_pid_20.html) and my tablet (http://approx.es/APPTB103S) and i'm noticing two things:

- With default settings and amigaos-130 Cloanto Kickstart ROM, playing a game like Turrican i experiment around 0.5-1.0 seconds lag in audio (i have tested this jumping and shooting).

- (Only in the MK902II) Using a bluetooth mouse, i have to click any control two times to obtain a response, and, if i click a slider, it seems to stick to the mouse cursor.


I have to say that i experiment these problems with both UAE4ARM and UAE4ALL2 .
I'm the only one with these problems?

See ya

Your device (MK902II) is based on RK3288 cpu (Cortex A17 core)
Interesting to see sysinfo result on this device.

I tested only with Turrican 2 and Turrican 3 and not detected any problems with sound.

I tested usb mouse with uae4all2 long time ago. I will try to re-check soon.

[Ariath]

I have tested again with Toki, Super Nibbly and Turrican.

The first two seems to work perfect, but with Turrican i keep noticing a small audio delay.

It is especially noticeable when you jump and you land. The "stomp" that sounds as you touch the ground seems to sounds 0.5~ seconds after you land.

I have tested the game with FS-UAE also.

See ya!


P.D: Where can i find SysInfo in ADF format for testing with both devices?

[lubomyr]

https://dl.dropboxusercontent.com/u/...ga/sysinfo.ADF

I tried to test Turrican
I hear some audio freeze on title screen, but in-game all ok.

Please also don't forget to enable Multithread video mode in SDL-settings when start emu.
Without multithread video mode, sound works very bad with mostly games.
I wanted to do multithread enable by default, but as i remember this mode can cause crashes of app on some devices. Same with uae4all2 and e-uae.

Tested usb-mouse with uae4all2 and uae4arm. All works correct (double click, right click etc...)
Known mouse problems:
- with some devices, right mouse click works as back button.
- two mouse pointers (android and amiga). Android OS still not support disabling of system pointer.

[Ariath]

Hmm... maybe i should have specified that my problems with the mouse are with the emulator GUI, not the Amiga itself :S.

I have tried activating the multithreading, but i get the same results :S.
As soon i have screenshots of the Sysinfo of the tablet and the mk902ii i will post them .

I'll try to record a video of Turrican with FS-UAE and the tablet, for comparing.

See ya!


P.D: I have tried to save a savestate, but i can't :P .
I have followed these steps (with UAE4Arm):

- Load a game (I chose Turrican :P).
- Wait for the title screen.
- Touch the back Android button to get back to the emulator GUI.
- Go to the Savestates section.
- Click the Save State button.

The GUI closes, but when i reopen it, the State screen is blank :P.

[lubomyr]

With savestate it my mistake.
I forgot to add 'savestates' folder inside uae4arm directory
But you can create it manually.
Uae4arm located at
path Android/data/atua.anddev.uae4arm/files

[lubomyr]

Meanwhile ARM JIT V2 released for aranym emulator

http://sourceforge.net/p/aranym/code...d178c795b0929/

* Advantages of JIT v2
*     - Processor independent style
*     - Reduced overhead
*     - Easier to understand / read
*     - Easier to optimize
*     - More precise flag handling
*     - Better optimization for different CPU version ARM, ARMv6 etc..
*
* Disadvantages of JIT v2
*     - Less generated
*     - Requires more code implementation by hand (MidFunc)
*     - MIDFUNCS are more CPU minded (closer to raw)
*     - Separate code for each instruction (but this could be also an advantage, because you can concentrate on it)

I hope soon we will see it with amiga emu(s)

[lubomyr]

Experimental JIT2-version of uae4arm
src - https://dl.dropboxusercontent.com/u/...rc-jit2.tar.gz
apk - https://dl.dropboxusercontent.com/u/...2-06062015.apk
Amiga compatibility is very low, but performance is faster than JIT(1)

Sysinfo 4.0 comparison
JIT v1 - 94144 dhrystones
JIT v2 - 101045 dhrystones

SysSpeed 2.6 (MIPS)
no JIT - 7.15
JIT v1 - 68.85
JIT v2 - 264.17

AIBB benchmark caused crash when running with JIT2

[Higgy]

Fingers crossed compatibility will increase!

Hello Lubomyr, hello all,

I am trying to make Uae4arm running properly on an Odroid U3 running Linux Debian Jessie.

I have managed to compile the code, based on the Makefile.RPI2 file provided with the sources. However, the emulator runs farly too fast.

Have you an idea of what could be the issue and do you know if this can be fixed by modifying the configuration file?

When compiled on the Raspberry Pi 2, there is not this problem. I am clearly not an expert when talking about emulators and game programming in general, but I suspect this could be due to a vsync-related problem. In fact, I believe this is generally the vsync that limits the framerate ... but this is only a supposition.

Any help would be appreciated.

Many thanks.