Posts by Tobias

Better late than never I just uploaded Keyrah V1 and Keyrah V2 manuals to the wiki.

I am not sure i understand the problem here.....

First of all, please understand that the TC64 starts as a C64. In a C64, the joystick port lines and the keyboard matrix are connected in parallel to the same I/O ports - so there is no way for one not influencing the other. There is also no way to disable the joystick ports in the menu - because the menu is designed to work without keyboard (and thus joystick). Even if we could do it, anything connected to the joystick ports is still interfering with the keyboard input, as said.

Now, what exactly is the problem? Where exactly does the boot process hang? If it does, does moving the mouse or pressing buttons make it continue?

Using port 3 for mouse in the amiga core seems to be a smart workaround to me - it would certainly work better than any other solution i could think of in the menu system.

cheers!

First thing to try is cleaning the port connector of the Amiga (Alcohol and an old Toothbrush works good for this).

The first check would indeed be trying it without the cable

say what?

cheers

yes

You might also want to remove the indivision, clean contacts with alcohol, and install it again. and then apply some pressure until it really "clicks" and sits tight.

Are you sure it actually "turns off"? Whether it shows an image are not is irrelevant for the flasher - please try again, disconnect everything from the chameleon except the two USB cables, and then paste the output of the flasher program here.

Its all included in the update .zip - and the flasher.exe should select the right one for your hardware. Just try again and paste the output here, it should tell what core was flashed and what hardware was detected.

First of all, please try updating with the last firmware using the flasher.exe program in the update,

Please elaborate, what is your setup, and how did you upgrade?

Quote

I see the Docking Station V2 says it supports both V1 and V2, but does that apply also to the Chameleon V2? does it require the new docking station or will the old one work as well

Either works fine

Quote

if there is a difference what changed between old/new docking stations?

see here

Quote

Also does the RRNet-V3 addon function within the TC64/Minimig core to give network access to the amiga core or is it a C64 feature only?

Short Answer: no

Long answer: there is an older experimental version of the core that will support rr-net for networking. However, this generally doesn't work well (it is very slow), so it was not merged into the mainline core

Jens can tell if he still has v1 breakout cables and how to get them....

Quote

i have a Xiaomi psu (from my Xiaomi 7 pro phone) + another other,with same specs: 10W/2A 5V...

I guess they'll be ok for the tc64 v2,with the dock + any ps2 kb & mouse ?

The Chameleon draws 2W, so that should be fine

Quote

if i use a bigger than 1meter mini-usb cable (for power),will Tc64 still be operating well ?

That really depends on the cable - often USB cables are built with very very cheap/thin wires, which can be a problem. With a good cable, it should work.

Quote

also,tc64 v2 -in stand alone or docking mode,must be switched OFF before pluggin/unplugging

cables ? miniusb/vga cable/ps2 kb & mouse and a 1541 ?

Of course it generally is a good idea to power off before connecting/disconnecting anything However, hotplugging is no problem for at least USB or PS/2.

Unfortunately this wasnt available in the old shop website either, so i don't have it... Jens will have to check his archives.

It should be within the variation between C64 boards... So do what we all did: crank up the saturation on your tv/monitor

The MK3 will be a completely different FPGA based design

Quote from Renato

I pushed near the socket, but it's giving a lot of issues, the image freezes, bad image, only image by the vga port. I think it's faulty. Can i send the indivision for repair?

That does sound like a bad connection of one of the chips. Please read this article before you send anything back.

Please try the following:

- update the firmware using the tool from the wiki

- if it still doesn't work, please show what the hardware detection item in the remote menu says