-
Hello MLAers! We've re-enabled auto-approval for accounts. If you are still waiting on account approval, please check this thread for more information.
Another IIci ROM hack
- Thread starter dougg3
- Start date
Oh I'm sorry! Of course. Anybody who is interested in a rev 2 SIMM, shoot me a PM. The cost will be $29 including priority mail shipping to the US (I'm using their flat rate boxes which are about $5). So the SIMM is $24 and shipping is a little over $5, but I'm rounding to $24+$5=$29 and calling it good. The cost includes 4 empty chips.
You will need an EEPROM burner to burn the chips until I make a programmer board, but to my knowledge this SIMM should be completely compatible with it when I have it ready.
Also to my knowledge this SIMM should work in any II series Mac with a 64-pin SIMM socket and the SE/30.
You will need an EEPROM burner to burn the chips until I make a programmer board, but to my knowledge this SIMM should be completely compatible with it when I have it ready.
Also to my knowledge this SIMM should work in any II series Mac with a 64-pin SIMM socket and the SE/30.
Last edited by a moderator:
Would you also sell unassembled boards? I could use the practice 
(Though isn't that how some of those NXP boards work?)
Or indeed any time when the last "concept" discussed in the previous post is not what you're responding to.
Basically, if reading straight through wouldn't make sense as a flow of conversation, and a word or two in your own post isn't enough to clarify
I was wondering about that too - but would it have to? As long as the board and the programming host can ID each other by MAC, all they'd have to exchange is raw ethernet packets, no?
Except the ROMs themselves aren't FAT, are they? How would that work then - drop the file to FAT storage on the programmer board, then the micro shifts it into the ROMs? Sounds convenient to the user, but inconvenient to you, and more complex and expensive for the board. The micro would have to read FAT, for starters.
(Though isn't that how some of those NXP boards work?)
Definitely sounds the simplest. Shirley there must be free/open source software around that could be used, adapted, or adapted to?
Well, it's 4 unnecessary parts (and points of failure) for most users - but the pads are still there on the layout, correct? So if anyone wants the socketed version, they can be simply be added?
Entirely appropriate, for just that reason
Or indeed any time when the last "concept" discussed in the previous post is not what you're responding to.Basically, if reading straight through wouldn't make sense as a flow of conversation, and a word or two in your own post isn't enough to clarify
Right -- the chips aren't FAT, so I would have to simulate the FAT filesystem. Whenever a file was written to the board, it would take the contents of it and write it directly to the chips. It may be kind of crazy to do, but I know the mbed LPC1768 board does that -- although it uses a custom chip to get it done. I like the USB-serial idea too, but the FAT idea is also intriguing. We'll see...
Yes, I will definitely make it a build-to-order option for whether someone wants a socket or not.
As for unassembled boards, sure! Do you want a kit with all the parts you need, or just the bare board? I would be happy to sell the bare board for $5 plus shipping, or a kit including sockets, capacitors, LEDs, a resistor, and 4 blank EEPROMs for $16 plus shipping.
If you want your own parts, you need four surface mount PLCC32 sockets, four 1206 0.1uF capacitors (5V or higher, I used 10V), and two 0805 LEDs and an 0805 resistor, with appropriate values considering a 5V source and the specs of the LEDs. I used two LEDs that have a 1.8V forward voltage drop each (Digi-Key part number 160-1421-1-ND), expecting 20 mA of current, and a 75 ohm 1/8 watt resistor, which will match with those voltage drops to give the LEDs about 19 mA of current.
Yes, I will definitely make it a build-to-order option for whether someone wants a socket or not.
As for unassembled boards, sure! Do you want a kit with all the parts you need, or just the bare board? I would be happy to sell the bare board for $5 plus shipping, or a kit including sockets, capacitors, LEDs, a resistor, and 4 blank EEPROMs for $16 plus shipping.
If you want your own parts, you need four surface mount PLCC32 sockets, four 1206 0.1uF capacitors (5V or higher, I used 10V), and two 0805 LEDs and an 0805 resistor, with appropriate values considering a 5V source and the specs of the LEDs. I used two LEDs that have a 1.8V forward voltage drop each (Digi-Key part number 160-1421-1-ND), expecting 20 mA of current, and a 75 ohm 1/8 watt resistor, which will match with those voltage drops to give the LEDs about 19 mA of current.
Yup! if any thread needs to be kept in context, it's this 17 Page Development MONSTER! [] ]'>
] ]'>
I've hardly ever failed to see this thread in the active topics window, it doesn't even NEED to be stickied!
B's been stickyin' generally useful info, I'd say this is more of a hacks-n-development project thread, not a general use info thread . . .
. . . awesome as it is! :approve:
B's been stickyin' generally useful info, I'd say this is more of a hacks-n-development project thread, not a general use info thread . . .
. . . awesome as it is! :approve:
Thanks guys! Definitely cool artwork/sounds olePigeon
I agree that this thread probably doesn't need to be sticky'd, it stays active on its own
I was wondering at what point a new thread is appropriate. It is becoming a bit of a mess to follow everything! I'm planning on having a programmer board ready in the future, I'm thinking I will do a trading post thread once I have that ready (although I'm tempted to do it now...)
The title of this thread isn't very descriptive of what's going on in it entirely my fault! Haha
I agree that this thread probably doesn't need to be sticky'd, it stays active on its own
I was wondering at what point a new thread is appropriate. It is becoming a bit of a mess to follow everything! I'm planning on having a programmer board ready in the future, I'm thinking I will do a trading post thread once I have that ready (although I'm tempted to do it now...)
The title of this thread isn't very descriptive of what's going on in it
entirely my fault! Haha
< mod mode >
The title is VERY descriptive of the first chapter!
)
How about a directory edited into the first page linking to the rest of the chapters? :?:
off the top of my head:
__IIci ROM Hacking adventure
__ASC tomfoolery
__Reverse engineering the 68k ROM SIMM
__Rev0 ROM SIMM Development
__Trials and tribulations of Rev0 ROM SIMM DeGubbing process
__Rev1 ROM SIMM . . .
__ditto 2 lines above . . .
__Programmer Board R&D
__etc.
"Figure" index (per Apple's DevNote Model) with links to any posts with those (really annoying to myself
) FLASH dependent VideoClips of the 
ROM Hacks.
Whatchathink?
< /mod mode >
Keep it in a single thread format, with bookmarks on p.1 to entice people into reading through the entire saga, IMHO.
The title is VERY descriptive of the first chapter!
) How about a directory edited into the first page linking to the rest of the chapters? :?:
off the top of my head:
__IIci ROM Hacking adventure
__ASC tomfoolery
__Reverse engineering the 68k ROM SIMM
__Rev0 ROM SIMM Development
__Trials and tribulations of Rev0 ROM SIMM DeGubbing process
__Rev1 ROM SIMM . . .
__ditto 2 lines above . . .
__Programmer Board R&D
__etc.
"Figure" index (per Apple's DevNote Model) with links to any posts with those (really annoying to myself
ROM Hacks.Whatchathink?
< /mod mode >
Keep it in a single thread format, with bookmarks on p.1 to entice people into reading through the entire saga, IMHO.
NoPro, put the list of links together to each and every post . . .
. . . IIRC "link to this page" or "copy link location of any given post" will do the trick . . .
. . . post them and yours will be the first linked "chapter" to be posted! (whenever I get around to it editing them into p.1)
. . . IIRC "link to this page" or "copy link location of any given post" will do the trick . . .
. . . post them and yours will be the first linked "chapter" to be posted! (whenever I get around to it editing them into p.1)
Cool, I may need to have the Chapters Linked to their respective sub-links pposted in a Second Thread that'll look like a post index of your 17 . . . and counting . . . page . . . Introductory Post. The links in that thread will . . .
. . . whatever, I'll figure it out as I go! :
Any suggestions on how to streamline/improve this kind of project would be GREATLY appreciated!
This thread has just GOT to be some kind of freakin' record! [] ]'>
. . . whatever, I'll figure it out as I go! :
Any suggestions on how to streamline/improve this kind of project would be GREATLY appreciated!
This thread has just GOT to be some kind of freakin' record! [
] ]'>This might need some reorganization/insertion/deletion/renaming but here is what I have after a quick skim of the entire thread (WOW! this thread really has come a long way from my original post about desoldering the DIPs and customizing the blinking question mark floppy disk icons!):
[*]ROM SIMM preliminary discussions and brainstorming
[*]olePigeon's Jolly Roger logo
[*]Arrival, assembly, and troubleshooting of the rev. 1 SIMM PCBs
[*]Brainstorming for programmability without the need for a chip burner and designing rev. 2 with that in mind
[*]tt's SE/30 with Power Mac startup chime
[*]Summary of changes in rev. 2 and later, additional changes
[*]IIci troubleshooting and power supply testing
[*]Back to programmer board R&D (and other expansion brainstorming)
[*]olePigeon's customized ROM
- First post (DIP ROM sockets, custom floppy disk blinking question mark icons)
- ASC tomfoolery
Custom synthesized startup sound (first few notes of Mario tune) and beginning of sampled startup chime adventure
- Sampled startup chime (newer Mac startup sounds)
[*]ROM SIMM preliminary discussions and brainstorming
- Reverse-engineering Apple ROM SIMMs
- trag's SIMM design
- tt's IIsi ROM SIMM X-ray image
- Initial order of ROM SIMM rev. 1
[*]olePigeon's Jolly Roger logo
[*]Arrival, assembly, and troubleshooting of the rev. 1 SIMM PCBs
[*]Brainstorming for programmability without the need for a chip burner and designing rev. 2 with that in mind
[*]tt's SE/30 with Power Mac startup chime
[*]Summary of changes in rev. 2 and later, additional changes
[*]IIci troubleshooting and power supply testing
[*]Back to programmer board R&D (and other expansion brainstorming)
[*]olePigeon's customized ROM
I would be thrilled if you would do that!
Back to the programmer board, I've started playing around with making a schematic for it. Looks like I can get away with using the AT90USB646 and one MCP23S17 I/O expander. That still leaves me with pins available for serial communication and a couple extra free pins, I'm thinking for status LEDs or something. I ordered some breadboardable DIP samples from Microchip of the MCP23S17 so I can see if it fits my needs.
Unfortunately, EAGLE light edition can't make a board big enough for the SIMM socket to fit (and the license doesn't let me make things I sell anyway--it's only for personal hobbyist projects). So I will have to switch back to FreePCB or KiCad or another alternative to create the board. For a project like this, laying out the board without a schematic (like I did with the SIMM) would be a nightmare so just doing the whole thing in FreePCB is not an option.
Back to the programmer board, I've started playing around with making a schematic for it. Looks like I can get away with using the AT90USB646 and one MCP23S17 I/O expander. That still leaves me with pins available for serial communication and a couple extra free pins, I'm thinking for status LEDs or something. I ordered some breadboardable DIP samples from Microchip of the MCP23S17 so I can see if it fits my needs.
Unfortunately, EAGLE light edition can't make a board big enough for the SIMM socket to fit (and the license doesn't let me make things I sell anyway--it's only for personal hobbyist projects). So I will have to switch back to FreePCB or KiCad or another alternative to create the board. For a project like this, laying out the board without a schematic (like I did with the SIMM) would be a nightmare so just doing the whole thing in FreePCB is not an option.
