DingooEmu
DingooEmu emulates Dingoo A320 and Gemei A330. It reads 1 file, none of them required: it starts games without them.
About this profile
Technical notes
Dingoo A320 and Gemei A330 emulator written in Rust by AloysHF. The
libretro core and the dingoo-emu standalone binary share the
dingooemu-core crate. Content is read from its full path (need_fullpath
= true, crates/,
crates/, crates/,
crates/). The CCDL package's load
address selects the runtime: a .app loaded in the 0x8xxxxxxx range runs on
the MIPS32 interpreter as an A320, a .cc, .c2s or .c3s loaded at
0x10100000 (retail SDK) or 0x13800000 (homebrew SDK) runs on the
ARM32/Thumb interpreter as an A330
(crates/, 104-121,
crates/). Both runtimes bind the
package's imports to Rust implementations of the device SDK
(crates/,
crates/). No
firmware code is executed and no font or system file backs those calls.
The A320 guest file API
(crates/)
resolves a name in three steps: a file under the save directory, a
resource packed inside the .app, then a host file relative to the .app's
own directory (crates/,
crates/,
crates/,
crates/). fsys_findfirst
enumerates the .app's directory and refuses to leave it
(crates/).
The A330 guest file API
(crates/)
resolves a name in five steps: a file under the save directory, a host
file relative to the content's directory, a resource packed inside the
package, the zip payload appended to the package, then an entry of the
firmware archive mounted from the content's directory. A name none of
them answers fails the open. fsys_findfirst enumerates the content's
directory and refuses to leave it
(crates/).
Files the game creates land in the frontend save directory
(crates/,
crates/) or, when the frontend
gives none and in the standalone, beside the content
(crates/,
crates/). The core queries
RETRO_ENVIRONMENT_GET_SAVE_DIRECTORY only
(crates/), and no system directory
constant exists in the crate.
With the diagnostic core option on, dingooemu-diagnostic.txt is written
to the save directory, or beside the content without one
(crates/,
crates/,
crates/,
crates/). No include_bytes!
data is compiled in. The .info declares firmware_count = 0: the one file
below is read from the content's directory, never from the system
directory.
1 file: 0 required, 1 optional.
In this collection: 1 in repo and 0 missing.
Optional
Section titled “Optional”A330.HXF optional in repo large_file
Gemei A330 firmware update archive, V1.1 build3 of 2011-02-13
- Read from: the folder of the loaded content, not the BIOS directory
- System: Gemei A330
- Mounted when an A330 package loads (
crates/): the content's directory is scanned and the first entry whose extension is hxf, in any case, is read whole. The file must start with WADF0100 and declare at offset 20 a size within its own length. Each record is a u32 name length, the name, one byte, a u32 data length and the data, and a zero name length ends the table. Names are lowercased, backslashes turned to slashes and a leading drive letter dropped, so Z:\SYSTEM\nls\c_936.nls and system/nls/c_936.nls reach the same entry. The archive is the last source consulted when a game opens a file the save directory, the content directory, the package's resources and its appended zip payload do not hold. Without it such an open fails and the runtime goes on. The image itself is never hashed, and the hashes here name the last firmware Gemei published, and the V1.10 image of 2011-01-25 indexes the same way.dingooemu-core/ src/ a330/ runtime.rs:415-418
- Size: 72.8 MB, SHA1 69b3544d992a
- Collection copy:
bios/Gemei/A330/A330.HXF
Hashes, validation and source
- SHA1:
69b3544d992a23e8b736c61837914a4d1b4e7bb5 - MD5:
d8e1849773223a842076ca04053a13a4 - Validation: signature
- Source:
crates/,dingooemu-core/ src/ a330/ firmware_archive.rs:16-50 crates/,dingooemu-core/ src/ a330/ firmware_archive.rs:54-58 crates/,dingooemu-core/ src/ a330/ firmware_archive.rs:63-96 crates/,dingooemu-core/ src/ a330/ firmware_archive.rs:117-124 crates/dingooemu-core/ src/ a330/ runtime/ sdk_hle/ files.rs:108-133
Next steps
Section titled “Next steps”- Get your files, for the setup you play on
- Every system, and the files each one needs
- When a game does not start