Amiga Digital Video HDMI for the A500 and A600

[seb132]

@kippee2k what is a SMDa1k ?

[kipper2k]

lets retry this, i moved folders















There, that is better.... THe SMD1k is my new 2MB A1000 still workin on it


The picture showing the 2 monitors ... HDMI on the left, RGB on the right. It is friggin awesome

[kipper2k]

Originally Posted by seb132

Cool project, really.
For the A600, wouldn’t there be a way if we have A604 memory extension ?
The indivision ECS plugs in it and get all information it needs to « flicker fix » the video signal from it....

I am not sure, i have made a little board that hopefully allows this project to wok on the a600 without interfering with any accels plugged into the cpu, need to just do a few final checks before i submit it. (The A2000 will work ok)

[seb132]

Cool, and yes, cool picture on the screen.

[Jope]

Originally Posted by seb132

Cool project, really.
For the A600, wouldn’t there be a way if we have A604 memory extension ?
The indivision ECS plugs in it and get all information it needs to « flicker fix » the video signal from it....

No, the Indi ECS works differently. It snoops the bus before the Denise and reimplements the Denise in FPGA.

This board needs the video signals that the Denise generates, which do not show up at the A604. Maybe if you insert this into an A604, then plug the Indi ECS on top it would be possible, if the Indi doesn't go into some kind of VGA only mode when it detects it's plugged into an A604.

[lilwshu]

I got mine today and it looks great from the limited testing I've been able to do (I only have a 60hz compatible monitor currently), it's a bit of a tight squeeze however with the PSU frame being right on top of it.

[-Acid-]

With different components is there any hope of an A1200 version being developed?

[grelbfarlk]

It would be nice© if you could integrate a switcher of some kind or provide for some means of integrating a VGA input.
For instance lets say you had a GBA-1000 with the Picasso-II. Or an A2000 with a Merlin card (like me). It's not a terribly bad problem with that system as I have an Indivision ECS which goes into the Merlin switcher.
But folks with an A2000 and a Zorro-2 RTG card would benefit.

[kipper2k]

there is a new release image just released. I'll give the link here as i find searching through githubs a little confusing...

https://github.com/c0pperdragon/Amig...ideo/issues/21

it has a NTSC fix and a couple of other fixes.

[kipper2k]

I was playing with the features of this and here are a few screenshots i took...








pretty well pixel perfect

as for lag...

i put 2 screens side by side, rgb and hdmi and when giana jumps it is pretty well identical. i cant notice any difference

[Lemaru]

I wonder if the new Pi Pico will make for a better solution than the Pi Zero, considering stuff like this is already being teased.

https://twitter.com/wren6991/status/...322181120?s=19

[kipper2k]

Originally Posted by Lemaru

I wonder if the new Pi Pico will make for a better solution than the Pi Zero, considering stuff like this is already being teased.

https://twitter.com/wren6991/status/...322181120?s=19

there are only 8 IO's on the pico so i think no good, it could end up having other uses though

[Commodoreguy]

Where can I order the adapter for Amiga 600?

[Lemaru]

Originally Posted by kipper2k

there are only 8 IO's on the pico so i think no good, it could end up having other uses though

From what I have been reading the 8 IO pins isn't actually correct. So it should be possible with the Pico Pi and PIO blocks. To quote one post

"There are two PIO blocks with four state machines each, that can independently execute sequential programs to manipulate GPIOs and transfer data.

PIO is highly performant as well as flexible, thanks to a carefully selected set of fixed-function hardware inside each state machine. When outputting DPI, PIO can sustain 360 Mb/s during the active scanline period when running from a 48 MHz system clock. In this example, one state machine is handling frame/scanline timing and generating the pixel clock, while another is handling the pixel data, and unpacking run-length-encoded scanlines.

State machines' inputs and outputs are mapped to up to 32 GPIOs (limited to 30 GPIOs for RP2040), and all state machines have independent, simultaneous access to any GPIO"


That Twitter link I linked earlier is a DVI to HDMI (well actually he has two HDMIs off it).

There's some interesting articles already about the programmable IO

[nikosidis]

Where can I buy the adapter full assembled?
I have ordered Pi 0

[Lemaru]

Originally Posted by kipper2k

there are only 8 IO's on the pico so i think no good, it could end up having other uses though

Think you also may be confusing the number of programmable I/O peripherals available looking at the specs. As it's for 26 GPIO pins

- 26 × multi-function 3.3V GPIO pins
- 2 × SPI, 2 × I2C, 2 × UART, 3 × 12-bit ADC, 16 × controllable PWM channels
- 8 × Programmable I/O (PIO) state machines for custom peripheral support

Alot of potential in this for a £3.80 board

[lilwshu]

My new monitor arrived today (Dell P1917S, 1280x1024) which supports 50hz, so I tried it on my V1 adapter in the A2000 and it looks SERIOUSLY GREAT. No detectable lag in SWOS so I will likely be very happy with it.

One issue I noticed however is that the top line of pixels is shifting rapidly left and right by about 1 pixel - has anyone else seen that?

[nikosidis]

Should not all digital screens support 50hz?
I though it was part of HDMI standard to support PAL.
Amiga 15khz is something different that for sure is not normally supported.
I guess this scaler make the signal 30khz and progressive. Kind of like
scandoubler, flickerfixer.

[lilwshu]

Originally Posted by nikosidis

Should not all digital screens support 50hz?
I though it was part of HDMI standard to support PAL.
Amiga 15khz is something different that for sure is not normally supported.
I guess this scaler make the signal 30khz and progressive. Kind of like
scandoubler, flickerfixer.

My other monitor only has a DVI port which does not like 50hz.

[hooverphonique]

Originally Posted by Lemaru

Think you also may be confusing the number of programmable I/O peripherals available looking at the specs. As it's for 26 GPIO pins

- 26 × multi-function 3.3V GPIO pins
- 2 × SPI, 2 × I2C, 2 × UART, 3 × 12-bit ADC, 16 × controllable PWM channels
- 8 × Programmable I/O (PIO) state machines for custom peripheral support

Alot of potential in this for a £3.80 board

The Pico doesn't have HDMI, but I suppose you meant to implement that using the I/O state machines then?