Setting Up a dual boot rom

[rubber_jonnie]

Just as a side note in all this, is that PP ROM a publicly available one ? as if this was purchased from PP and people are uploading it here without permission.. he is going to start flaming likely me again about it all as its on my forum...

@exxos The TOS 1.04 image I patched for IDE was from a ROM I bought from you, but I don't know who patched it originally. It had the extra info at boot when it arrived. If I recall it came with either a STFM dual ROM adapter or one of the 4 IDE boards I ordered. I can only say I got it in 2019.

Just in case, I've taken it down and I'll PM @PhilC as he was going to test the image for me.

[czietz]

@exxos The TOS 1.04 image I patched for IDE was from a ROM I bought from you

When you say you patched it for IDE, did you use https://github.com/czietz/ideboot/? If so, there's no ppera code involved -- at least for the IDE patch. The IDE patch is under the free MIT license and for the rest of TOS, you're "only" infringing Atari's copyright when posting it here.

(I can't say where the memory / floppy info patch comes from.)

[Glorfindeal]

can anyone tell me the part number for the 8 bit roms (2 rom set). The 32 pin version.

Thanks,

Ken

[rubber_jonnie]

@exxos The TOS 1.04 image I patched for IDE was from a ROM I bought from you

When you say you patched it for IDE, did you use https://github.com/czietz/ideboot/? If so, there's no ppera code involved -- at least for the IDE patch. The IDE patch is under the free MIT license and for the rest of TOS, you're "only" infringing Atari's copyright when posting it here.

(I can't say where the memory / floppy info patch comes from.)

@czietz It turns out it wasn't in reference to my ROM image, rather the one posted earlier by the OP, who I believe had included TOS 2.16 which is one of the versions sold by PP.

Your IDE patch for TOS 1.04 is awesome by the way, I have it in my Mega1 with PPs Megabus IDE adapter, it's turned it into a pretty handy machine now it has an internal HDD.

[rubber_jonnie]

Well, I am now in posession of 5 erasable 27c4096s :) Took 12 days to arrive from China, which is OK, and now I have spares I can test with before moving to OTP chips. Of course that's providing they aren't fakes! More to follow on that.

I shall hopefully get my 1.04+ide/206 image written over the next few days and will install in my Mega 4 for all round IDE loveliness :)

[rubber_jonnie]

Well, all 5 are erasable and program just fine so I'll be testing in the Mega 4 this weekend 😊

[troed]

On the topic of byte order:

I have a TL866 and a DIP40-PLCC44 adapter which needed pin bridging PLCC side (12-13, 33-34). When I read out one of exxos' PROMs from a Dual TOS board that image has reversed byte order, as viewed in GHex.

The software I use, on Linux, is the command line minipro software found here: https://gitlab.com/DavidGriffith/minipro/

/Troed

[troed]

So here's what I did:

Code: Select all

$ cat tos206se.img tos104se.img >> dualtos.img
$ dd if=dualtos.img of=dualtos_swapped.img conv=swab
$ minipro -s -p AT27C4096@DIP40 -w dualtos_swapped.img
Found TL866A 03.2.86 (0x256)

VPP=13.5V, VDD=6.5V, VCC=5V, Pulse=100us
Chip ID OK: 0x1E00F400
Warning: Incorrect file size: 458752 (needed 524288)
Writing Code...  77.79Sec  OK
Reading Code...  5.58Sec  OK
Verification OK

The -s programs even though filesize isn't the expected. Reason this works of course is that I put TOS 2.06 first, at 256Kb, followed by TOS 1.04 and I don't care that it doesn't fill out the EPROM.

The above boots fine in my H4 (1.04, I still need to do the decoding for 0xE00000) so I would be surprised if there can be non-byteswapped programming possible with the TL866, at least command line. As I wrote, I did the swap since that's how exxos' original image came out when read.

/Troed

[troed]

And for completeness: Reading out my Falcon TOS from its TMS27C240 also came out byteswapped, and programming that image back to a 27C4096 worked just fine.

/Troed