+cubanismo Posted April 2, 2022 Author Share Posted April 2, 2022 Yes, that's expected because it's a headerless ROM. The utility assumes you'll use another tool afterwards such as romsplit with the -p option, or jagcrypt to prepend a header. Note filefix v6.x and v7.0 adjust the padding appropriately as well: Padding to 2MB will actually pad to 2MB - 8k to account for the missing header. The ROMs it outputs are intended to be used with an Alpine board, as can be seen from the scripts generated with the -rs option. I've fixed the help output for -p to note it uses 0xff by default, added a -pn<x> option that lets you align the ROM size to an arbitrary power of 2, added the -n option to disable the "minus 8k" behavior when padding in case you're doing something like padding a CD track rather than an actual ROM, and bumped the version to 7.1. The filefix binary in the post above has been replaced with the updated version. I'm debating whether to add code to prepend an 8k header of 0xff or the universal binary as you've done. I was also going to write an updated romsplit at some point (I'm slowly getting rid of the dos-only files in my SDK as I run into cases where I have to use them. dos_emu is slow. I wasn't really expecting other users this soon though.) that could handle prepending 8k of 0xff in a degenerate case where it wouldn't actually do any splitting, and there's a tiny mkuniv program in my version of the Skunkboard bringup scripts here that replaces any existing header on a ROM with the universal header, so it'd be redundant functionality in the SDK. On the other hand, it'd make filefix much more useful as a stand-alone utility given no one is developing on Alpines these days. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.