TF536 with CDTV

[bartekmalysz]

Originally Posted by alexh

You could try the one patch to cdtv.device ($407C : $7202) as well?

If that doesn't work I don't know what to try other than burning ROMs.

I don't have a TF536 so I can't try here.

Will try in an hour or so. Not familiar with HxD, one the cdtv.device opens do I just find (ctrl f) $407C and change value manually? Sorry, still learning, can you please suggest resources to start with to learn for amiga?

[alexh]

Originally Posted by bartekmalysz

when the cdtv.device opens do I just find (ctrl f) $407C

No that is the v2.30 ROM file offset not the cdtv.device file offset. (A file offset is how many bytes into the file the location you want to modify is)

The byte you're going to change in cdtv.device v35.14 file is byte offset is 00000491

Scroll down until you see 00000490 in the offset (h) column and you should see the following pattern :

Offset(h) 00 01
0000048C  70 00
0000048E  4E 75
00000490  72 00 <= This is the byte you're going to change
00000492  2F 0E
00000494  2C 78

Highlight the 72 00 and type 72 02.

File Save As

[jotd]

I've pushed a change in my python rom patcher. All offsets from the list are now supported (to patch a full ROM). I guess cdfs.library patch is kind of useless...

patch_cdtv_rom.py "CDTV Extended-ROM v2.3 (1992)(Commodore)(CDTV).rom" patched.rom

[alexh]

Originally Posted by jotd

I've pushed a change in my python rom patcher. All offsets from the list are now supported (to patch a full ROM).

Nice. I might try and see if it still works as expected in WinUAE. (If you've not already)

Originally Posted by jotd

I guess cdfs.library patch is kind of useless...

I think bartekmalysz needs to try just a patched cdtv.device and cdfs.library first.

Plus I'm not 100% sure on his method.

[bartekmalysz]

ok, so when trying to patch full rom I still get checksum error under romsplit. Should I just use the script on each file separately? Sorry for being daft and thank for your patience.

I also wanted to edit by hand but I can't see these memory values.

Edit:

I understand that without TL866 I won't get any further. Ordered one but may be a week before I got it. I have good eeproms and pin adapter from go0se, need anything else?

[utri007]

Originally Posted by bartekmalysz

I set CD0 as follows:

Device=DEVS:cdtv.device
FileSystem=L:cdfs.library
BufMemType=2
Unit=2
Active=1

Those are file paths, if they are correct you are OK. Do you use any file manager? Like DirOpus, Dirmaster, etc?

@all

I don't think that CD boot is possible without a lots of work.

But, maybe these two are realistic goals?

Extended roms enabled, boot from HD use CD drive after that.
Extended roms disabled, boot from HD use CD drive after that.

If roms are disabled, cd player is not useable?

But both are acceptable results.

Easiest way would be use patched extended roms.

[bartekmalysz]

Originally Posted by bartekmalysz

I understand that without TL866 I won't get any further. Ordered one but may be a week before I got it. I have good eeproms and pin adapter from go0se, need anything else?

Unless doable with RPi? I have a few laying around, breadboard and some parts as well.

[alexh]

Originally Posted by bartekmalysz

I also wanted to edit by hand but I can't see these memory values.

You didn't follow the instructions. You didn't set a width of 2 bytes *AND* you loaded the wrong file!

[jotd]

problem is: you can't split a patched ROM. You can only split unpatched ROM, and in that case, identify original hex strings in the ROMs using the offsets and find some in cdtv.device (cdfs.library is already patched properly I hope so, I used the same method)

but as Alexh said I'm not sure of this method.

AND if this method works, it means that the method using AnyMEM to block fastmem, load device and use AnyMEM again to unblock would work, without needing to patch the files (unless the devices use mem allocation for buffers after init, which is possible but bad practice performance-wise for this kind of program)

[bartekmalysz]

Guys, I absolutely appreciate your help, you're an absolute legends. Will continue tomorrow and will try to edit both files manually.

I did try with anymem today, but I guess it needs to be added in startup and is not reboot persistent. Not sure I understand correctly, but what needs to happen is to boot CDTV with enabled extended rom, disabled TF ram, so the driver can be loaded into specific chip ram location, once this is done, another command to add fast mem?

[jotd]

one thing I wanted to test is using a CDTV + HD configuration + CD drive on winuae

With 1.3 and extended 1.0 ROM (unpatched, of course!), using a 68030 + Z3 fast allows to boot from HD and read a CD in CD0:

I wanted it to fail but it did not.

[utri007]

Originally Posted by jotd

one thing I wanted to test is using a CDTV + HD configuration + CD drive on winuae

With 1.3 and extended 1.0 ROM (unpatched, of course!), using a 68030 + Z3 fast allows to boot from HD and read a CD in CD0:

I wanted it to fail but it did not.

Show stopper is that there is no Zorro 3 support with KS1.3, as far I know?

[bartekmalysz]

Tf536 doesn't boot on 1.3. This is what I get with KS 3.1, Mobo2.3, extended rom 2.3

[alexh]

Originally Posted by utri007

Show stopper is that there is no Zorro 3 support with KS1.3, as far I know?

I don't think the Z3 FAST RAM option in WinUAE requires any OS support. It refers to the fact that it is 32-bit wide and mapped to what later would be the Z3 address space.

[Toni Wilen]

Originally Posted by alexh

I don't think the Z3 FAST RAM option in WinUAE requires any OS support. It refers to the fact that it is 32-bit wide and mapped to what later would be the Z3 address space.

Of course autoconfig needs OS support

Only KS 2.0+ knows what to do with Z3 boards. KS 1.x leaves them unconfigured (and if there is any Z2 boards "behind" it, they are also left unconfigured)

[alexh]

Toni thanks for the correction.

Originally Posted by jotd

one thing I wanted to test is using a CDTV + HD configuration + CD drive on winuae

With 1.3 and extended 1.0 ROM (unpatched, of course!), using a 68030 + Z3 fast allows to boot from HD and read a CD in CD0:

I wanted it to fail but it did not.

So JOTD that could explain why it worked? If the Z3 fast is not mapped, then the OS would only use CHIP RAM? Which we know works.

I think when testing this we'd need a WinUAE setup more TF536 like? Perhaps use the WinUAE option "Advanced Memory Settings"?

I don't know how to use it but there is a "Processor Slot Fast RAM" option and and a place to insert "Autoconfig data" (which maybe we could get from TF? Or capture it from a TF536?).

But as I said I don't know how to use these WinUAE options.

[alexh]

I found time to setup WinUAE and install RomSplit by Doobrey.

The byte offset of the Allocmem TF said he patched in cdtv.devce 35.14 is byte offset $491 in the extracted file (I've updated my posts earlier where I said I didn't know where it was)

[bartekmalysz]

Originally Posted by alexh

I found time to setup WinUAE and install RomSplit by Doobrey.

The byte offset of the Allocmem TF said he patched in cdtv.devce 35.14 is byte offset $491 in the extracted file (I've updated my posts earlier where I said I didn't know where it was)

Many thanks,


I just patched cdtv.device, pointed CD0 to it, the WB doesn't boot, just hangs on black screen

[jotd]

yes, Z3 memory is not mapped. avail reveals no fast memory at bootup...

winuae memory settings show:

Configured 32-bit address space: 0M, reserved: 1792M, Z3 available: 1728M (UAE), 960M (Real)

even with Z3 configured with 64 mb...

my "full power" winuae setup shows

Configured 32-bit address space: 913M, reserved: 1792M, Z3 available: 1648M (UAE), 880M (Real)

I really don't know what's the difference / how to activate 32 bit address space with that kick 1.3 CDTV setup that otherwise boots and shows Z2 RAM if set.

If someone can solve this problem, then we have a potentially bootable CDTV setup with Z3 fast (and 68040) and we can try the patched ROM.

[Toni Wilen]

Configure non-autoconfig board at fixed address and then use amigados addmem-command to add it? But note that some emulated DMA controllers don't have 24-bit limit, some do (CDTV is one that does not emulate 24-bit limit).

But I already started implementing 24/32-bit option for Z2/A500/CDTV DMA controllers and also DMA capable option for RAM banks. (Only missing part is that "fixed" RAM banks don't yet have support for extra configuration metadata)