Search results

IMO the ideal approach is the following The script will be parsed. The files expected at fixed locations will be listed apart. And the writing loop logic will be: next_offset = written_bytes + next_file_size; if (next_offset > next_fixed_pos_files->offset) { gap =...

an example of romimg marking the fixed offset files (the third new colum indicates offset (bytes occupied so far by previous files) This should allow spotting them easily my next target: adding a "scripted rom creation" feature. Where you give ROMIMG the list of files, specifying the ones...

I made the update I'm talking about this week XD

It's because some files are expected to be at specific offsets, because those files are inmediatel needed by the bios bootstrap program (the raw executable at the beginning of the file, Wich is represented by the RESET entry) Latest ROMIMG will highlight those files in YELLOW when listing ROM...

I doubt that if I make it I'll ever use stock ROM again. At very least, I'll add the PPCTYY driver and hook it to IOPBTCONF to have all logs redirected to the PowerPC UART. Would be cool to make the flash chip programable from the console.

Latest ROMIMG is capable of highlighting files Wich are marked as "expected at fixed location". It somehow crashes on windows build. But Linux build running on WSL worked like a charm

Very nice. I'm dying to do something like this to my 75k. The potential for development is amazing.

Can't we map the exceeding ROM space as rom2: or rom3: ?

Since we are already replacing the ROM, we surely can deal with that. It would require replacing the ROMDRV module. Wich we already have an open source version. I would like to hear @uyjulian ideas on this regard.

You'll make me blush xd. I'm just a boy that grew up with the PS2 and luckily ended up making software for it as a hobby. I don't fit in the "famous PS2 developer" category I believe XD. PS2BBL can serve as a bootloader, yes. actually, we can tweak it a bit for better integration with the...

Just making sure. Are you aware that rom0:ADDDRV must be executed? That driver registers rom1 against ROMDRV

Hello there Decided to join the discussion here