Posts by espskog

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser Please create an account and log in to see all content by default. This is a limitation of the forum software.

    there is no such config file, and the same reasons for why we wont add it apply: we will need a new bit in the config registers, and we'd have to add considerably much new code to the menu system. its one of those things that we might consider once we fixed all (or most) bugs - but not now.

    Hi Tobias. Is the Y/N on +/- added to the new i-core ?


    GREAT JOB! The OSD now works + the menu is possible to navigate!

    BUG FOUND: I see that when I enter workbench, the left + right fire buttons on the CDTV works fine as the left+right mousebuttons. But the arrow

    keys do not move the mouse-pointer. When I press ARROW_UP it moves the pointer one pixel down. If I press ARROW_DOWN it moves the pointer one pixel to the right (yep: the switch is set to "mouse" on the CDTV remote).

    Also -- when I play Supercars (might be an issue with other games as well) I notice that there is a lag on the buttons. I press the fire button to accellerate, but it doesn't axx until about 0,5-1 second later. Also, if I try to steer with the arrow keys left/right it has the same kind of lag.

    Could you see if this is also something which happens on the V1 ?

    Hope this helps in debugging :)

    Here's a version that fixes the CDTV control pad issues. It's possible to open the OSD using the power button (new for V2 - I'll backport that to V1 at some point).

    Things I learned:

    • It's vital that the ir_data signal is double-synchronised, otherwise the state machine in the CDTV Controller module gets wedged.
    • Somewhere along the line the order of the joystick direction signals in the CDTV ir module got reversed between the old version in the Minimig sources and the current version.
    • If your project uses the CDTV ir module directly in its toplevel, it's a good idea to disable it in the IO module!…

    Perfect! I will see if I can test this ASAP. In regards to the buttons (other than power+arrows+fire): Do they serve purpose as well ?

    I have a quick question: When I start MiniMig_V2 core on my TC64v2 I cannot use my CDTV remote to do anything. I have to start the OCD menu with the left most hardware button on the cartridge. HOWEVER: When I am in the OCD menu and press the arrow-up on the CDTV, sometimes it jumps down one line. But that is all -- no more reaction. No nothing :)

    Question 1: Does the CDTV remote work to go in/out of the OCD on MiniMIg on the TC64V1 ?

    Question 2: Are my problems above reproduceable on the iComp Labs (Tobias?) ?

    Question 3: Which buttons (if any) on the CDTV remote is supposed to me mapped on the minimig core (what can I expect) ?


    slot 0 is the chameleon core, you shouldnt update that with anything but the original core from the update :) you can revive it by flashing just that to slot 0 (--flashrbf 0 chameleon_beta9h_v2.rbf rom-menu.bin)

    Hehe...I learned the hard way :) All is well -- I reflashed with 9hcore and got it back on track. Then i put the minimig core on slot 1.

    I gor slax64 with virtualbox to work...I think. I could see the cham now with chameleon--status

    But I flashed core0,1,2,3,4,5 with different cores and now it's no longer booting. I am installing windows so I can do a clean flash of the whole V2 and see if I might have overwritten the C64 core somehow by accident :)

    BUT: chacocmd works with virtualbox + usbenabled + chacocmd. I can confirm that.

    I am afraid I have tried every trick in the book which I could think of (yep -- root included). I believe I might have to get hold of a windows laptop (even though it does against every fiber in my body to have a MicroSoft OS in the house. I get the shivers by just thinking about it) :-D

    Progress is made after a system reboot :) I now see the Chameleon as a USB device:

    MacBook-Pro:chameleon-tools-osx espskog$ ioreg -p IOUSB

    +-o Root <class IORegistryEntry, id 0x100000100, retain 15>

    +-o AppleUSBXHCI Root Hub Simulation@14000000 <class AppleUSBRootHubDevice, id 0x10000030f, registered, matched, act$

    +-o Apple Internal Keyboard / Trackpad@14400000 <class AppleUSBDevice, id 0x100000311, registered, matched, active$

    +-o BRCM20702 Hub@14300000 <class AppleUSBDevice, id 0x10000034f, registered, matched, active, busy 0 (5 ms), reta$

    | +-o Bluetooth USB Host Controller@14330000 <class AppleUSBDevice, id 0x100000381, registered, matched, active, b$

    +-o Chameleon@14200000 <class AppleUSBDevice, id 0x1000005fd, registered, matched, active, busy 0 (2 ms), retain 1$

    ..But it is still not "there" for chacocmd or chusb tools:

    MacBook-Pro:chameleon-tools-osx espskog$ ./chusb 0

    Chameleon USB Client v1.8

    could not claim interface.

    initialization failed.

    I have connected my V2 to my Mac with both MiniUSB connectors connected. I installed LibUSB using Brew and I have tried to test the connection with chusb but it just says this:

    MacBook-Pro:chameleon-tools-osx espskog$ ./chusb 0

    Chameleon USB Client v1.8

    No Chameleon found on Bus

    initialization failed.

    Any hints ?

    I am gonna try to compile it, unless someone else more experienced does it first and publishes it, and test. Thanks for the quick reply. I was of course hoping that the chaco-usb connector also would take power from the connected host. I think I have to go and dig out a 2nd mini usb cable :-)

    I am trying to flash the new V2 Amigacore but have two questions:

    1) I connected the TC64_v2 to my computer using the mini-usb cable on the chaco-connector on the back of the cartridge (left of the vga port). Do I have to supply power to the cartridge as well via the other USB port ?

    2) How do I go about and get Chaco running on OSX ? Do I have to compile it myself ? Is there a pre-compiled binary out there I can download ?

    Patience guys, it will all take time. The minimig core is the least fun core to port because of how it was written - so it might not happen real soon.

    You know us. Eager to test :-)

    Are you aiming for a quick port just to get the V1 core running "as is" on the V2 or are you doing further changes ?

    This was very interesting reading! Especially nice to read about how it all started out and with the meeting in Eindhoven. I guess it is these memories to think back on that really makes it worth it -- even though you have put down a lot of time.

    Thank you so much for sharing this story. Feel free to share more in the future if you come up with funny stories or facts that you guys know would draw a smile on the face of your users :-)

    Hi. I am the founder of the FB group for the TC64 and love to update it
    daily to draw a crowd and inform everybody of this fantastic cartridge.

    Could you share some fun facts with us about the product, the production process
    or something I can share with the group ?

    Keep up the great work.