If TFT, can it too display 640x512 at 1280x1024 with 1:1 pixelmapping? And Zoom? Exact Model Number please :) I never seen a TFT that can do this. Maybe it posible to quad/double the pixels by Hardware to get not such a typical sick picture of TFTs?

Years ago I tried to find one that would do exactly that (quadruple the pixels of a 640x512 screen) but I never could find one. :(
Samsung hates all Amiga users.

And 16:10 :-) Maybe a thingy like that blue menu on Minimig (Ive only seen it in pictures..)

Hello Dag

Well, it could be implemented as cycling through (4:3)->(16:9)->(16:10)->(4:3)->.. :)

I have a 28" 16/10 1920x1200 and they look stretched and blurry/pixels from 640x480 to 1280x1024.
  IMHO if it is possible to write/add resolution libraries in AOS for: 840x480; 1024x576; 1280x800 that can avoid a stretched image.

Many TFTs recognize the picture on the content. Using Overscan and a tool that make the grey stuff around the picture black should solve it.
Only for the System conform Software of course, not for most Games.
One TFT of me still look blurry on exact the halft native resolution. TFTs are trash.

I really had the impression that I need to do timing measurements, have voltage or termination problems. But instead I was just unable to understand the documentation which says that the user is completely free in naming the I/O pins of the memory interface as the scripts are designed to see by their own what pins are connected to the controller instance. Of course every one (but me) knows that this means that the pin names need to be lower case and the user is only allowed to add some characters as prefix to the names from the example design.

It also takes nowadays several emails to the program vendor till they accept that if you use (for example) a bit in the schematic named "AddressBus[15]" it not really useful if the program exports it as "ADDRESSBUS1[5]". You really need arguments to convince them to change it because it is "not an error". And -great- the fix fill appear in the next program update -> next year.

But back to the topic now.

> I can read AND write single memory locations on the baseboard now from the CPU card test program.

I tested only one memory bank, the other will follow.

This means at least one memory bank will work and for that the DMA channel interfaces can be installed and tested.

Keep it up Thomas, those updates keep us very excited!

Thomas Hirsch wrote:

It also takes nowadays several emails to the program vendor till they accept that if you use (for example) a bit in the schematic named "AddressBus[15]" it not really useful if the program exports it as "ADDRESSBUS1[5]". You really need arguments to convince them to change it because it is "not an error". And -great- the fix fill appear in the next program update -> next year.

Argument may be: Time To Market!
Next year can be Jan... or Feb... or Jul... or Nov 2010!

Cheers ;-)

Ironically, generating the black bars at the edges to make a 4:3 picture uses up Denise graphics bandwidth*!!!!!!!!!!! :-((((((

I'm still hesitant about how great TFTs are too, as CRTs _still_ have a certain, something..... are there ANY 16:9 CRTs??? Can Plasma have multiple resolutions like CRTs used to?

* And chipram.

"Earth below us
Drifting, falling
Floating weightless
Calling, calling home"

Hehehe.

Thierry not more then a normal picture would do. ;)
And besides the rest of the chips wouldn't updare the 4:3 image pillaring.
So it is stuck in mem only to be place on screen every screen.

I may have made a mistake there, as you say, the vertical black rectangles aren't perpetually being recomputed and drawn, just what's inside the 4:3 area is being updated, huh?

Well then, could a 1920*1080 display be generated that _only_ displays in a 1280*1024 section while leaving the rest black? Wait, that doesn't make sense, does it? Never mind.

No, on a Real Amiga there is a grey area, around 640x512.
Because of that on many TFTs you see a smaller picture(not Fullscreen) the TFT thinks anything around 640x512 is still a Picture. If you change this grey into black it sould be turn into Fullscreen. If i remember right such tool is called boarderblank.
This shoult eat no resources.
I see now Overscan can only set bigger and max. is 724x566.
That cant reach 16:9 maybee with Screenmode.
But thats only on AGA, with Natami this should no Problem.
With CGX its too no Problem to make an 1920x1024 mode, of course most games not work on a gfx card. And working ones, sometimes avoid modes that not exact 1.333..

@Thierry, the screen gets read for a memory adress, you do nit have to refresh every piece of data on the screen every cycle.
This is why blitter and the copper only would update that what needs a update/refresh.
All the rest can be the same in memory and this indeed doesn't save much of Denise.
But it does save on the rest.

This could add some fun stuff, for instance you could add a Smiley in the memory adresses, during a refresh untill the memory adress gets over written this pictures a smiley in the black border.

So, this is how it should work during setup(boot)Set screen size.
Chance the value of the memory where black borders are needed to the right colour.(you can set this to pink if you like, but standard should be black or very dark blue)

it's odd but i still find it confy coding on a monochrome screen, this is perhaps due the fact it's black and green.(both colours are easy on the eyes.)