Thank you for great animation work @retr01 !
that reminds us of the good old days of computer games in the 80's The first half feels like an elevator action. Unfortunately, my office isn't a splendid building like your anime.
Can't miss the place where rainbow colors are featured in everything
When the ROM file is split into 4 binary files, the files are named U4, U3, U2, U1, which may seem like the order is reversed at first glance. However, this is due to the hardware design and programming tool specifications. Specifically, each split binary file corresponds to a specific ROM chip and is named based on its layout and reading order. U4 is the first data, U3 is the next data, and so on, so that the system can read the data correctly. This naming convention allows the hardware and software to work together properly, and although it may be confusing, it is intentional by design.
BTW, Quadra 950 may not work properly. It was last year. I know that some of the pinouts are different on 68040 machines. This was something that neither I nor Steve Chamberlin of BMOW knew. This is explanation of Doug Brown and has a blog so see there:
From what I understand they are pins 11 and 12, but in the case of the SE/30 and many 030 machines they are controlled by pin 27 of the GLUE chip. *Doug Brown's blog simply illustrates the concept of CS and OE. However, on the 040 machine, pin 11 from the board is always pulled up to +5V, and the ROM's CS is pulled down to GND.
To be honest, I don't have much experience with 040 machine's ROM SIMM, and since Cay Mac was the first to start designing 040 SIMM at the time, I didn't think it would be right for me to jump in, because I showed respect to the developers... so I didn't do any further research.
Thank you for your understanding.
@Kay K.M.Mods Thank you for the explanation.
I saw the successful launches of Quadra 900 in YouTube and decided to study this topic. I found ROM SIMM here and some explanations, as well as a link to GitHub, where you can get a custom ROM.
I became interested, and of course I wanted to try it. But my whole way with vintage poppies is not easy, I don't hope it will be easy.
While I'm waiting for my order (it will take a very long time), I decided to follow in your footsteps. Actually, I no longer want to run Windows in UTM to use the XGecu programmer, so I forced myself to use minipro and write/erase/read my old "SST39SF040" chips that I have left over from the modification of sil3112 boards for Power Macintosh.
I will also have ROMmate Programmer, because I want to try everything.
I'll leave my cheat sheet here, in case someone needs it.
Code:
# Install packages
brew install srecord minipro
# split
srec_cat rom.bin -binary -split 4 0 -o chunk4.bin -binary
srec_cat rom.bin -binary -split 4 1 -o chunk3.bin -binary
srec_cat rom.bin -binary -split 4 2 -o chunk2.bin -binary
srec_cat rom.bin -binary -split 4 3 -o chunk1.bin -binary
# Check XGecu
minipro -i -d "SST39SF040"
# is blank?
minipro -b -p "SST39SF040"
# ROM chip is automatically erased when flashed, but I prefer to do it manually
minipro -u -E -p "SST39SF040"
# Write the firmware
minipro -u -w ~/Temp/chunk1.bin -p "SST39SF040"
# After the firmware, verification is performed automatically,
# but if you need to compare the firmware in the file and on the ROM chip, you can do it manually
minipro -m ~/Temp/chunk1.bin -p "SST39SF040"
I haven't figured out how to perform the compression that SIMMProgrammer performs yet.
@JDW, Helped me deal with the issue of manual disk compression with the FC8 algorithm. Thank you!
First you need to build the application:
Code:
cd ~/Temp/Sources
git clone https://github.com/steve-chamberlin/fc8-compression.git && cd fc8-compression
gcc -o fc8 fc8.c compression.c
chmod +x fc8
Now we can conduct tests and compare the size. Some explanations can be found here.
The first half feels like an elevator action. Unfortunately, my office isn't a splendid building like your anime.
colors are featured in everything 
