页次： 1
Wow ! It is official support ~ Thanks for this information !
stable: https://buildbot.libretro.com/stable/1.10.3/dingux/miyoo-arm32/
nightly: https://buildbot.libretro.com/nightly/dingux/miyoo-arm32/Run RetroArch on FC3000
@neotendo, @司徒
Thank you, It's accumulated work of MiyooCFW & RetroArch community, we try add new things every release (today is new one!). You can search "MIYOO" in changelog for full info. I've been lately occupied with new video filter for 320x240 screens, but it needs testing.
You can find usefull info for setting up RA for Miyoo in here: https://github.com/TriForceX/MiyooCFW/wiki/RetroArch-Setup
Big credits go to salvacam & jSTE0 - they did most of work in maintaining frontend and porting cores!.
BTW - if you want to test your own builds/cores or see smth changed just do "make -f Makefile.miyoo" after modding.
I spent some time on porting QEMU for FC3000 handheld
Remarkable! This was requsted dozens times on other forums! Everything works as expected, I even tried custom RetroArch build on it with no problem. Will be very helpful for simple debugging, especially as I'm currently without real console hah!
I think if you want simply read log from gdb you can do it in handheld while writing to a file thus using sole framebuffer, e.g. through /etc/main :
/mnt/gdb -ex=run -ex="bt full" -ex=q ./program > debug.txt @司徒
I've performed tests on another device which normally overclocks to 864MHz (for 1.2V). It is necessary to reset CPU setting of old app links in gmenunx (or create new ones) to make new CPU registers acceptable by system.
Although I do not own FC3000, I don't see a reason why it should behave differently (there have been test on other consoles). Didn't you mention at first that it can't work beyond 602MHz without new resistors?
@neotendo @司徒
The battery range levels are hardcoded in latest gmenunx code, for current src you can adhere to miyoo_beta branch on my repo (specifically: https://github.com/Apaczer/gmenu2x/blob/miyoo_beta/src/platform/bittboy.h#L107). I've rewrote parts of deprecated miyoo code and brought new features from master branch.
For other types of batteries than BL-5C you might want to do battery log and check those values.
P.S. If you use GameShow skin or similar, then check NOTES in release tab.
@neotendo
good you have your music working - soundtrack&voiceovers were the main reason why I loved this game!
@司徒
Could you advice us how to debug apps on this platform without UART? Do you have QEMU setup for ARM926EJ-S with "gdb" program as a help? I see you are pasting images from sort of windowed mode and though you might be using those.
I've tried to run my port with "gdb" through terminal app on Miyoo, but it didn't display anything (I think it might be due to SDL not liking drawing over another app).
No idea about first two issues.
About the last one (music not playing), there has been lib sound (e.g. SDL_mixer) patches applied to rootfs in MiyooCFW comparingly to stock Miyoo source (see https://github.com/MiyooCFW/sdcard/blob/master/rootfs.tar.xz), so that's why its acting differently on your side.
eduke32 needs SDL_mixer to play the MIDI, which is using the native timidity config in /etc (https://github.com/Apaczer/eduke32/blob/9b03e526ab3ea8a7dcc3647631c37d6af4a09cb9/source/sdlmusic.c#L221)
You can also look here for more info: https://github.com/scooterpsu/midi-enabler
is there a chance to get duke3d running on fc3000?
After compiling, eduke32 works on MIYOO but you have to press repeadetly START (skipping intro?) to boot to main menu. After that you have to disable sfx sounds to enter game. Music works as expected in game, however sprites are all glitchy and if you enable back sounds it works only for a few seconds before sfx becomes corrupted.
@neotendo
You can try latest port of the FBA: https://github.com/Rezzy-dev/fba-miyoo-playable/releases/tag/release
It fixes some stuff and you can open Menu with RESET button. For recompiling use Miyoo toolchain from steward's repo.
页次： 1