Munt 0.1.3 is not far from release, so here's a preliminary list of ROMs that will be supported in that version:

PCM ROMs

MT-32:
Size: 524288 bytes
MD5 hash: 89e42e386e82e0cacb4a2704a03706ca

CM-32L additional:
Size: 524288 bytes
MD5 hash: f7909bed95b04d8dc4cc47970e2bc3e6

Note: The CM-32L contains both of the above ROMs. To use the extra CM-32L samples, Munt needs these ROMs to be concatenated (the MT-32 one first).

CM-32L concatenated:
Size: 1048576 bytes
MD5 hash: 08cdcfa0ed93e9cb16afa76e6ac5f0a4

Control ROMs

Note: "ID location" (the position in the file of the ID string) and "ID string" fields are given in C-style.
Note 2: The MT-32 control ROM on the boards I've seen is contained on two mask ROMs, with the bytes interleaved. Munt expects a single ROM file with contiguous bytes, and those are the files listed below.

MT-32 "Blue Ridge" modification:
ID location: 0x4010
ID string: "\000verX.XX 30 Sep, 88 "
Size: 65536 bytes
MD5 hash: 9513fec4f09a7d327748340ce3a2a59b

MT-32 version 1.07:
ID location: 0x4010
ID string: "\000 ver1.07 10 Oct, 87 "
Size: 65536 bytes
MD5 hash: 5626206284b22c2734f3e9efefcd2675

CM-32L version 1.02:
ID location: 0x2205
ID string: "\000CM32/LAPC1.02 891205"
Size: 65536 bytes
MD5 hash: bfff32b6144c1d706109accb6e6b1113

If the ROMs from your module differ from those in the list, please let me know. If your control ROM differs, I'd appreciate your help in mapping it out. If your PCM ROM differs, I'd be very interested in knowing whether it works in Munt.

Note that Munt does *not* currently check anything but the size and - in the case of control ROMs - the ID of the ROMs.