[Tools] Etripator

[MooZ]

I resumed working on it some weeks ago. It's mostly code clean-up.
Anyway, here are the two major features of the next version:

• Support for mirrored ROMs.
• Better CD support.
• Predefined labels : You'll be able to specify in the configuration file a list of name/address. This would be useful for CD-ROM in order to highlight BIOS calls.

edit: Here's the branch for those interested : https://github.com/BlockoS/Etripator/tree/v0.4

[MooZ]

All of the above is ready to be released.
The label filename is a standard CFG/INI file like the main configuration file. It looks like:

Code: Select all

[cd_boot]
logical=e000
physical=000000

[cd_fade]
logical=e02d
physical=00002d

[MooZ]

Here's a little work in progress tutorial: https://github.com/BlockoS/Etripator/tr ... r_puroresu

[MooZ]

Etripator v0.4 released: https://github.com/BlockoS/Etripator/releases
What's new:

• Labels file : This lets you add a name to a physical/logical address.
• Examples/tutorials : Examples were added for hucard and cdrom disassembly.
• Various bugfixes and internal rework.

Only the source code is provided for the moment.

[freem]

I've compiled a Windows executable version of 0.4 with GCC and such (might require some DLLs which I don't remember off the top of my head).

Visual Studio compilation chokes on line 153 of section.c, since it doesn't know what F_OK is.

[MooZ]

Thanks for the binary and the bug report.

As always I forgot that Visual C++ is not really POSIX compliant. That'll also teach me to compile under Visual C++ even if the code looks portable enough.
Anyway, the remedy would be to do something like this in platform/windows/config_win.h :

Code: Select all

#ifndef R_OK
#define R_OK 0x02
#endif
#ifndef W_OK
#define W_OK 0x04
#endif
// X_OK does not exist on msvc
#ifndef F_OK
#define F_OK 0x00
#endif

I'll fix this this evening.

edit: Fixed!

[MooZ]

New version!
https://github.com/BlockoS/Etripator/releases/tag/v0.5

Config and label files are now JSON files.
MPRs can be set in config files. This way physical addresses are not needed anymore in label file. The hardware page is used instead.
Startup code and gfx can now be automatically extracted from CDROM data tracks.
Nicer logs, fixed bugs...

[MooZ]

New release!

https://github.com/BlockoS/Etripator/releases/tag/v0.6

• Label file format was changed.
• You can now specify multiple label files to the cli.
• New formatting options were added to inc_data sections.
• Labels can now appears inside inc_data sections.

[Griever]

Sorry for noob question, but I tried your tool with several *.pce ROMs using this instruction for Monster Puroresu:
"As we are starting from scratch, the first thing to do is to a perform an automatic IRQ vectors extraction. This is done by calling:
./etripator -i rom.pce "
But it gives me nothing in command string, just the empty log file. I use Windows 10 command string.
Do I miss something?

[MooZ]

Weird... I just ran a test with the 0.6 and master on Linux and everything seems to be working fine.
Do you run it from a terminal like cmd or mingw bash?