| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
[Kevin Eshbach]
|
| |
|
|
|
|
| |
failed / cleanups (nw)
|
|
|
|
| |
but I held off the commit because the input/output files are a bit bigger than the existing ones (nw)
|
|
|
|
|
|
|
|
|
| |
- Corrected the output of the PAL20X4, PAL20X8, PAL20X10 to show the XOR on the relevant sum of products.
- When viewing a device the size of the JED file is verified to match the size of the device.
- Replaced hard-coded symbol strings with constants.
- Started experimental work for supporting RICOH PAL’s. (Currently ifdef'ed out.)
- Added support for viewing the following devices and the corresponding regression test data.
(PALCE16V8, PAL10P8, PAL12P6, PAL14P4, PAL16P2, PAL16P8, PAL16RP4, PAL16RP6, PAL16RP8, PAL6L16, PAL8L14, PAL12H10, PAL12L10, PAL14H8, PAL14L8, PAL16H6, PAL16L6, PAL18H4, PAL18L4, PAL20C1 and PAL20L2)
|
|
|
|
| |
test data for the PALCE16V8. The pal dumps for Twin Cobra 2 in the Taito F3 driver are now labeled as bad dumps because when viewed with jedutil the data is bad. [Kevin Eshbach]
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Documentation on the earlier version of the Deco Cassette System
- Documented some pals on a bootleg Free Kick that need to be dumped
- Documented the location of the roms on Twin Cobra 2
- Added support to jedutil to view the PAL20X10, PAL20X8 and PAL20X4
- Added some preliminary work on figuring out what the undocumented fuses for the PALCE16V8 are. (The data sheet does not document what all of the fuses are.)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
createld_avi_yuv2_3_frames_no_audio (nw)
|
| |
|
| |
|
|
|
|
|
| |
- fixed check for output folder existence
- clear temp folder before running tests
- log which test failed
|
| |
|
| |
|
| |
|
|
|
|
| |
compression (nw)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Eshbach, Charles MacDonald]
|
| |
|
|
|
|
| |
chdman test
|
| |
|
|
|
|
| |
(fixes execution on non-Windows platfors) (nw)
|
|
|
|
| |
potentially different filesize with each compiler not defaulting memory to 0x00 including Visual Studio) / added another chdman test (nw)
|
| |
|
|
|
|
| |
(nw)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
and added a new command line option of "-viewlist" which will print out a list
of all the devices that can be viewed in human readable logic equations.
Also updated the jedutil regression test to support passing in an additional argument of "debug" to print out a detailed log. Also moved the jedutil regression test
data into separate directories composed of the device's name to make things
more organized. [Kevin Eshbach]
|
|
Made some modifications to the jedutil tool to allow the viewing of simple combinatorial jeds (adding support for registered and gals in the future) by taking a jed file and printing out human-readable equations. Changed the command line options of the jedutil tool to know take an initial argument to specify what the tool should do.
For example to convert a jed to bin the command is now:
jedutil –convert <source.jed> <dest.bin>
jedutil –convert <source.bin> <dest.jed>
To view a jed file with human-readable equations the command is
jedutil –view <source.jed> <pal type>
Added a simple regression test for the tool that just verifies that the currently known pals have the row and column fuse location mapped correctly and at the moment this tool runs under windows only.
Under the directory src/regtests/jedutil there is a Windows Script File with the name jedtest.wsf that if run from the command line with the command “cscript jedtest.wsf” will verify that a dump of the jeds in src/regtests/jedutil/jeds matches the good dumps in src/regtests/jedutil/baseline. Reference jed files created using the tool eqn2jed which is included with Opal Jr and these files are in src/regtests/jedutil/eqns.
|