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.
Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.
We've had some info regarding monitors on our wiki - however, the new VGA controller in 9j changes everything (to the better, hopefully)
So, it would be great if you could post some quick info on your experiences with the 9j (and later) cores. Please post the following information:
- Name of your monitor (vendor and exact product code)
- Native resolution (and aspect ratio)
- Do the 50Hz modes work with VICII sync (in cartridge mode)?
- Whatever else you think is useful 
Thanks!
Just use an older update - there is no way to "brick" the chameleon.
The strange look will be fixed with the next update
Just curious - why are you not using the native resolution of your monitor?
QuoteThe BenQ BL702A see 640x480 50Hz but it set on 60Hz.
The 50Hz Modes are not standard VESA modes - so its a bit hit and miss. The monitor might even display it correctly, does it scroll smooth then?
The sync polarity should now match the VESA modes... before it was basically wrong in all cases
Please try mounting two disks and use the left button to "flip" the disk - ie dont use the menu.
Is that really 640x480 in the first picture? In that mode you will see downscaling artefacts, there is no way around it - you should use 800x600 instead (or better yet, the native resolution of your monitor)
apparently there was no dedicated Thread yet i have also updated this core, no changes in the core itself, but it has the new VGA controller.
get it on the http://wiki.icomp.de/wiki/Chameleon_VIC20
The update is out, which should fix the problems with VGA timing -> see Chameleon Core update 9j released
The update is out, which should fix the problems with VGA timing -> see Chameleon Core update 9j released
It has been a while - i have just uploaded another core update for you to play with Most notable are the REU fixes and the VGA rewrite. This should solve most - if not all - problems people reported with various monitors.
The changes in detail:
As usual get the update on the Chameleon wiki page.
Have fun!
Perhaps even the hardware test core :=) It shows a little square that can be moved with the ps/2 mouse and some squares that light up when pressing mouse buttons (warning: it also beeps... turn down the volume =P)
No, there never were catweasel drivers in the mainline kernel.
There have been two different drivers (linked on the wiki) - both require a 2.6.x kernel iirc
Usually the tune will come with a note of some kind that tells how its intended to be played - and so far very few require true stereo.
QuoteI can sort of get it to work, but not really. The only way I can connect is to 1) go into the firmware tool and press connect (no chip info will appear), 2) Press Program Firmware, 3) Power recycle MK2 as it ask for and, 4) Click Abort after the power cycle. 5) Click Disconnect and Connect again and now the tool will get the chip info. 6) Disconnect from the firmware tool and connect with TeraTerm, 6) TeraTerm now connects and gets the menu.
The steps above will reliably connect to the MK2 remote control menu, but no other method I have tried will. It could be something with sending the pulses for the bootloader? If I simply start the MK2 and connect I can not get to the remote menu (restarting and power cycle does not work)
This sounds very odd. Do you have another PC you can try? Somehow sounds like a problem on the PC side of things to me... some other Software preventing the COM port to work correctly, or something.
The minimig core would not be affected by this though, each core defines its own VGA timing
Did you try updating the firmware yet? We had a few cases where the "fuses" on the microcontroller were set wrong for some reason, causing the oscillator frequency (and with that the baudrate for serial) being totally off - updating the firmware will fix this (use the tool from the wiki).
also make sure the baudrate is set correctly and hardware handshake is disabled (when the transfer stalls my guess would be it is not, with just wrong baudrate you should at least get some random gibberish)
