Picasso IV scandoubler problem

[midwan]

Hi all,

I just got a Picasso IV v1.2 from AmiBay for my A4000D. The Picasso modes work fine, but I'm having weird problems with the scandoubler when using PAL/NTSC screenmodes.

I tested it on two separate monitors, one was an old 17" EIZO FlexScan L550 and the other a more recent DELL 27" (which actually syncs down to 50Hz also). Both displayed the same problem, even when taking all other hardware out of the box. The image appears distorted and shrinked to about 1/3 of the normal width. Also, the colours appear as B&W and in some areas bleeding out of the letters.

I'm attaching a couple of photos to show you what I mean as it's a bit difficult to explain it...

I tried entering the Picasso early boot menu (with left shift) to reset the settings to default. It didn't change anything.

At the same time, the RGB output from the 23-pin out worked normally on a TV I tested it. Also, the Indivision scandoubler works normally on the same machine and monitors.

I checked the jumper settings just in case (they are set to the defaults), tried pushing the card and the chips in sockets in case they were loose.

I tried re-flashing the latest firmware (7.5) although it had that already. No change in the behaviour.

I did try editing the scandoubler modes from PicassoModeTNG and in the preview there, the results show correctly (even with the default settings). But when I actually open any PAL/NTSC screen I get the same problematic display - even after changing/saving the settings from PicassoModeTNG. I'm not sure what that "Preview" is displaying exactly and why it's different than the other normal PAL screenmodes, I'm wondering if it's promoting it to another screenmode instead?


I'm not sure what else to test. I suspect that something is not working correctly with the scandoubler itself?

Has anyone else seen similar behaviour? Any suggestions on what to do?

[alexh]

As a start you could provide us the output of the P4info tool which tells us which versions of flash and all the CPLDs (programmable chips) are.

The last time I ran mine it was this :

> P4Info

Opened PicassoIV.resource 7.4 at $7003434
p4bi_BridgeRevision $4
p4bi_FlickerFixerRevision $7

[midwan]

Well of course, silly me for not doing so already:

Opened PicassoIV.resource 7.5 at $8015DC8
p4res_boardcount 1
p4res_PALTiming    $800E524
p4res_NTSCTiming   $800E53C
p4res_IntServer $80007A8
p4res_IntServer->is_Node.ln_Pri  = 30
p4res_IntServer->is_Node.ln_Type = 2
p4res_IntServer->is_Node.ln_Name = "PicassoIV.resource"
p4res_IntServer->is_Data         = $08015DC8
p4res_IntServer->is_Code         = $080104EC

Board # 1
p4bi_Flags $80000802
  ZorroIII Mode
  Board contains CL-GD5446 Rev.A
  connected to Color Monitor
  Used by Gfx-System
p4bi_MemoryBase1 $41000000
p4bi_MemoryBase2 $40800000
p4bi_GPPortBase $40000000
p4bi_RegisterBase $40600000
p4bi_ConfigBase $40400000
p4bi_MMIOBase $40200000
p4bi_Modules $3
  is connected to Video-Slot (FlickerFixer active)
  is connected to AA-Video-Slot (24 bit capable)
p4bi_BridgeRevision $1
p4bi_FlickerFixerRevision $5
p4bi_BankingSetting $7
p4bi_AudioSettings $0
p4bi_IntStatus $80
  interrupt                  $08425180
  interrupt->is_Node.ln_Pri  100
  interrupt->is_Node.ln_Type 2
  interrupt->is_Node.ln_Name "VBInt PicassoIV (0)"
  interrupt->is_Data         $0842513C
  interrupt->is_Code         $08428D18
  interrupt                  $084245E8
  interrupt->is_Node.ln_Pri  0
  interrupt->is_Node.ln_Type 2
  interrupt->is_Node.ln_Name "p4specials.library"
  interrupt->is_Data         $084245E8
  interrupt->is_Code         $084385F0
p4bi_PabloConfig $00000000

[midwan]

Also, here's another photo that shows the "color bleed" and color->B&W problem I mentioned earlier. The grey border should have been the normal Amiga blue here...

I also tried the card on a second A4000D today, with the same results (on the same monitors).

I tried swapping the daughterboards just in case there was an issue with the Video slot (since that's where the scandoubler gets the signal from), but again the results were the same... :-(

[alexh]

Your flickerfixer and bridge are older ones. I had issues like yours with older chips every now and again. I am sure there is a SW work around to get it reasonably functional. But it does take some fiddling to reset the flifi settings

But I had all my PIV chips updated and I've never had any issue since.

I would consider contacting MastaTabs (aka Tobias Seiler) over at a1k.org and see if you can get updates for your flickerfixer and bridge. He will send you replacement chips and you return the ones you have. The price is fair but it may take a month or so after you pay to get your chips. He is 100% reliable but busy.

[zipper]

Originally Posted by alexh

MasterTabs (aka Tobias Sieler) over at a1k.org

MastaTabs (Seiler)

[midwan]

Thanks for the replies guys.

[midwan]

I tried contacting MastaTabs at a1k.org, so far I've gotten no response... While I hope that is due to his work load and I will eventually get one, I would like to see what options are available.

@alexh: you mentioned a software solution (or at least, possible solution)? Do you have any more information on that? I have already re-flashed the latest firmware (7.5) which didn't seem to make a difference.

Is there any other option I could pursue to try and get this fixed?

I have already tried changing Jumper settings 3, 4 and 5 but to no avail.

[zipper]

have you tried to tweak the FliFi settings with http://amiga.rules.no/utils/PicassoModeTNG-2.9.lha

[midwan]

Yes, I have.

The strange thing is, everything seems to work OK when using PicassoModeTNG - the Preview of the "PAL" modes using the scandoubler seem to display just fine, regardless if they were the factory defaults (after being reset) or tweaked afterwards by me.

As soon as I save and reboot though, all PAL modes show the problem again. Even in the Early Boot Menu or PicassoIV's own early config menu (getting there with LShift during powerup or reset).

I'm not certain if the fact that I can see the Preview from the tool normally means anything. If feels like it's actually promoting the screenmode or at least handling it/displaying it differently than when the tool is not running (i.e. when any other PAL screenmode opens).

[davideo]

My PIV now and again works slightly loose in the slot and gives a similar (although not as bad) picture as yours.

Just pushing the card back in and giving a small tweak on the backplate screw normally fixes it.

[midwan]

Thanks for the tip, though having read similar problems in other threads this was one of the first tests I made.

I even tested the card on a second A4000D, which showed the exact same results I'm afraid.

[alexh]

@alexh: you mentioned a software solution (or at least, possible solution)? Do you have any more information on that? I have already re-flashed the latest firmware (7.5) which didn't seem to make a difference.

It is too long ago to remember the exact details.

I remember it had to do with clearing the flicker fixer default settings which had become corrupt and programming them (i.e. storing in NVRAM) valid Flifi settings.

I do not remember how this was performed. It could have been any of the following.

1) Holding down left shift and entering the PIV early startup
2) Using the VillageTronic Flifi tool
3) Using Picasso TNG

Even with the FliFi working correctly, my early revision used to regularly screw up the cursor (you get a kinda interlaced combing) and flicking between native and RTG would sometimes screw up.

No such problems after updating to the last version of all the chips.

[midwan]

Thanks, I understand how memory fades over the years...

The only one of the steps you mentioned that I haven't tried, is the FliFi tool (I thought that PicassoModeTNG supersedes that).

I will give that a shot later tonight, just in case. I'll let you all know how it went (fingers crossed and all).

[alexh]

FYI this page (now dead) was always the best PIV resource on the net.

http://web.archive.org/web/200410152...com/picassoiv/

You can read about the differences between FliFi $5 which you have and FliFi $7 which was the last

[midwan]

Thanks alexh, I have that page in my bookmarks.

[midwan]

I tried the FliFi tool, but it only seems to report the status, not configure anything?

It also seems to report incorrect values, PAL was reported to be at 75Hz altough my monitor reports is 720x568 50Hz.

In any case, it didn't make any difference.

[springycz]

Hope that you don't mind me parasiting on this thread. I just plugged my newly acquired Picasso IV in my A4000 and hopefully installed it. Where do I find the P4info tool? I've been looking everywhere but can't find it.

[zipper]

http://www.sophisticated-development...V&section=P-IV in the P4Update packs

[midwan]

Just wanted to update this thread, since I finally got this resolved.

The issue was on the card chips after all. I got a new set from MastaTabs (from the A1k forum), replaced them and the problem was resolved without any further steps.

Hope this helps anyone else who might run into it in the future.