VGA demo
retromicro
Posts: 24
Hi
I've got my homebrew Propeller board set up with a VGA connector as shown below
Pin 16 = 220R = Vertical Sync
Pin 17 = 220R = Horizontal Sync
Pin 18 = 470R = Blue Video
Pin 19 = 220R = Blue Video
Pin 20 = 470R = Green Video
Pin 21 = 220R = Green Video
Pin 22 = 470R = Red Video
Pin 23 = 220R = Red Video
I'd hoped that I could just load the Propeller Tool, Open VGA_Demo.spin, do a Run / Compile Current / Load RAM and then see video on the VGA monitor. Nothing showing though. My Hello World code runs fine via the serial terminal so I know the hardware basics are ok.
Is there something obvious missing from the above ?
Thanks
PS I've also loaded the microphone_to_vga demo. I see that you then start off with one tab. However, if you do a Run / Complie Current / Load RAM, you see another level of code in the top left hand corner of the Propeller Tool. VGA_512x384_Bitmap has appeared and the same shows in a new code tab. It looks like this happened because there is the below entry in the initial code
vga : "vga_512x384_bitmap"
Does all the code on both tabs get compiled and sent to the Propeller when the compile is done ?
This code also seems to default to pin 16 as the base pin so I'd expect this to work.
I've got my homebrew Propeller board set up with a VGA connector as shown below
Pin 16 = 220R = Vertical Sync
Pin 17 = 220R = Horizontal Sync
Pin 18 = 470R = Blue Video
Pin 19 = 220R = Blue Video
Pin 20 = 470R = Green Video
Pin 21 = 220R = Green Video
Pin 22 = 470R = Red Video
Pin 23 = 220R = Red Video
I'd hoped that I could just load the Propeller Tool, Open VGA_Demo.spin, do a Run / Compile Current / Load RAM and then see video on the VGA monitor. Nothing showing though. My Hello World code runs fine via the serial terminal so I know the hardware basics are ok.
Is there something obvious missing from the above ?
Thanks
PS I've also loaded the microphone_to_vga demo. I see that you then start off with one tab. However, if you do a Run / Complie Current / Load RAM, you see another level of code in the top left hand corner of the Propeller Tool. VGA_512x384_Bitmap has appeared and the same shows in a new code tab. It looks like this happened because there is the below entry in the initial code
vga : "vga_512x384_bitmap"
Does all the code on both tabs get compiled and sent to the Propeller when the compile is done ?
This code also seems to default to pin 16 as the base pin so I'd expect this to work.
Comments
Do you have the Propeller's ground connected to the VGA grounds? I see five ground connections on the Propeller Demo Board Schematic (available from the Prop Tool's help menu).
These match the ones in the diagram. I have NOT got anything connected to pin 9 (+5v). I read about this pin and was under the impression that this was used to supply the monitor for ID purposes and I would get away with out it.
This might depend on the monitor you're using. I don't know enough to be sure but I'd try to follow the schematic to the Demo Board before trying to make changes.
I know I've used "VGA_Demo.spin" on the Demo board and it worked fine. As long as "VGA_Demo.spin" is the active tab when you press F10 or F11, it should be the only code to compile and load into the Propeller.
Yes thanks.
I've changed the monitor.
I used the VGA64 Bitmap Demo by Kwabena W. Agyeman and every now and then, I could see the polygon changing shape and moving around the screen. I could change the colour in the code.
However, I'd get so many frames and then the screen would go blank for a while. After a while, the picture would come back.
While the image was on the screen, it was steady and clean.
I also ran the standard VGA demo a few more times and saw, very briefly, 'woof' on the screen.
Does the above suggest anything in particular ?
Thanks
Sounds like an LCD that can't lock onto your signal for very long and keeps losing it and then locking on again. I'm pretty sure an LCD monitor I have didn't like VGA_Demo.spin or vga_512x384_bitmap.spin's timings. Your monitor might not like 512x384, even though it's half of 1024x768. Try to find a CRT (the old fat kind) to test it on - if the CRT works and doesn't lose the signal, it's a timing problem, otherwise, it's something else.
Now that you mention this, I recall I also had a LCD monitor which didn't work with the Propeller. Most of the VGA screens I've used have worked with the Prop but I have one which doesn't.
kuroneko's drivers work with most VGA monitors. Don't see any in the OBEX though.
http://forums.parallax.com/showthread.php/138654-FYI-VGA-100xH-P-dual-cog-per-cell-colour-(full-indexed)?highlight=100xp
I added some voltage regulators and connected a wall wart and lo and behold, everything started to work. All but one of the demos work and the monitor cannot handle the signals generated by the last one.
I'll have a look at the work done by kuroneko.