[Solved] SuperVidel + CT60e Woes.

[leech]

Weird. First boot up when I got home was that SV_XBIOS.PRG loaded, but said it couldn't detect the board (also said it was from 2013).

Subsequent reboots with the same crash.

To answer the question. Yes, it is working fine without the driver.
SV.INF copied straight from the driver disk I made to C:\

Code: Select all

; SuperVidel Configuration File
;
;

[VDI]                  ; Settings which affect (N)VDI behavior
default   = $401c      ; Specifies a default resolution if none is specified by the AES
;forced    = $4018     ; Overrides the resolution specified by the AES
dual      = off        ;
vdi_bps8c  = false 	; allow 8-bit chunky in TOS VDI (enabled by NVDI driver)
vdi_bps32  = false	; allow 32-bit TC in TOS VDI (enabled by NVDI driver)

[XBIOS]
bootmode = $401a
primary   = VGA        ; Primary display output.
clone     = true       ; If true, screen is sent both to primary and secondary output.

[HACKS]
rezdialog = true       ;
fast_videl = true 	;

Still need to try disconnecting the VGA clock sync cable. Waiting to get together a heatsink/fan solution before I open it up again.

[leech]

Wow, I am now convinced that my computers are jealous of each other. Did the little info gathering when I got home from work. Pulled apart my Amiga to verify size of heat sink I used on my 060 there, put it back together and walked back to the Falcon which sits above my main desktop, and my Linux root partition's btrfs decided to freak out.... hours later, it is now on ext4. Ha! Anyhow, found a fan and some Artic Silver is on its way. Once I get that, I will open the bird up and disconnect the clock cable, see if that helps.

[leech]

http://atari-forum.com/viewtopic.php?f=97&t=31362 is similar, though the fix was to remove the jumper, and I gad a black screen without it. But I did not have SV.INF in place, will try tomorrow night.

[shoggoth]

Basically, if the SV_XBIOS.PRG doesn't work, on an otherwise clean boot, it's a hardware problem and/or a case of file corruption.

C:\auto\sv_xbios.prg
C:\sv.inf (unedited)

[leech]

Is there any temperature protection thing in it maybe? Seems to me the cpu is about 60C when it first boots, and pretty rapidly gets up to 80... That's why I figured I'd trouble shoot after I can get heatsink/fan on it (which will be either tonight or tomorrow).

Then I'll also test no clock cable+no jumper.

[joska]

Seems to me the cpu is about 60C when it first boots, and pretty rapidly gets up to 80...

I see the same on my CT60e. However, if I measure the actual temperature of the CPU it's around 30 degrees lower.

[leech]

Oh thank god. It hit 83 the other day and I about crapped. I kind of recall there being someone saying there was a bug in the temperature software that triggered if you had a CT60e.

[fidzen]

Oh thank god. It hit 83 the other day and I about crapped. I kind of recall there being someone saying there was a bug in the temperature software that triggered if you had a CT60e.

I also have error message about the temperature readings when I boot up.
But it's not always, and when I use higher MHz I get this error message more often.

But the readings seems to be quite accurate, I get around 58°C when I push it
really hard. But I have a heatsink with a fan.

[Trixster]

The temperature sensor on my CT60e thinks it's running at about 3000degrees! It's never worked properly. Doesn't stop the cpu running ok at 100mhz though.

[joska]

I don't get any error message, it's just that the temperature readings are wrong. On my CT60e it says that temperature is in the high 60's immediately, and then it rises steadily to around 80. But actual measurements shows around 30 degrees lower temperatures.

[trecool]

I also have error message about the temperature readings when I boot up.
But it's not always, and when I use higher MHz I get this error message more often.

But the readings seems to be quite accurate, I get around 58°C when I push it
really hard. But I have a heatsink with a fan.

Me too! I have noticed it happens only on switch on the system and not on warm resets. After that all measurements seems to be correct.
I wish I hadn't that issue or at least I knew what's going wrong.

[fidzen]

I also have error message about the temperature readings when I boot up.
But it's not always, and when I use higher MHz I get this error message more often.

But the readings seems to be quite accurate, I get around 58°C when I push it
really hard. But I have a heatsink with a fan.

Me too! I have noticed it happens only on switch on the system and not on warm resets. After that all measurements seems to be correct.
I wish I hadn't that issue or at least I knew what's going wrong.

Exactly the same for me, when it's warm I don't get the error message.

[leech]

Ha, well where heat is concerned, I'm usually on the overly paranoid side. Especially when my Amiga's accelerator melted it's ram chips when I powered it on one day.

One thing I have found between working on the two... seems the Amiga has a tendency to have random things go wrong with it just about every time I open it up. Falcon just keeps on grinding away for the most part, even after taking the soldering iron to it a few times.

[mikro]

leech, I think you've a hardware problem there. If the board is sometimes not detected, there's nothing to discuss, fix that first. Also this: "Tried doing the update to FW v10, and that crashed. Same with the update to v09. No clue what version is on there." seems to support that, something is very very wrong. I'd try to clean up the pins, verify connectivity, weak soldering etc.

[leech]

I'm thinking that may be the case. CT60e is working fine, but the SuperVidel is not.

So today I put the heatsink on, tried it without the VGA clock sync cable attached, and got the same thing. Though now I'm sitting at the TOS desktop with only NVDI loaded, fonts are changed (I have the assign.sys from the SV driver disk) but no SV_XBIOS.PRG. Previously I thought this just gave me a garbage output.

Still no SV love though. Any other thoughts?

This apparently still has the original firmware on it.

So it isn't giving me the 'not detected' (unless I boot in 030 mode, which I think is expected). Jumper off of J7 still gives me a black screen though.

[leech]

So at the end of this thread;
http://atari-forum.com/viewtopic.php?f=100&t=30103

It was stated;

Great!
Then the theory that some FPGAs have problems in different regions of the chip is correct. This is because they are quite heavily overclocked, from 166MHz to 200MHz. From know on we'll release every new version in three different variants, so you can try another one if the first choice fails.

/Torbjörn

So maybe same sort of case? Otherwise.. ideas?

[leech]

Aha, well that's poo. I was working off of the Revision 1 manual, I swear I went through all the links on the page before and couldn't find it, so googled it and ended up with revision 1. There is revision 5 that I see there now (which shows what to do with the resistors)

[Rustynutt]

I'm thinking that may be the case. CT60e is working fine, but the SuperVidel is not.

So today I put the heatsink on, tried it without the VGA clock sync cable attached, and got the same thing. Though now I'm sitting at the TOS desktop with only NVDI loaded, fonts are changed (I have the assign.sys from the SV driver disk) but no SV_XBIOS.PRG. Previously I thought this just gave me a garbage output.

Still no SV love though. Any other thoughts?

This apparently still has the original firmware on it.

So it isn't giving me the 'not detected' (unless I boot in 030 mode, which I think is expected). Jumper off of J7 still gives me a black screen though.

Is the Falcon booting past the black screen as far as you can tell, like HD activity and keyboard light? That might indicate if its a bus error or software issue. Or, like others have said a connection issue. With a VGA switch connected, what does the VIDEL output look like when you have a black screen?

[leech]

Not sure why I keep putting the Falcon back together after messing around with it. I definitely need to operate on the wiring a bit more, no reason to have the wires as long as they are when they only need to be much shorter.

What exactly do you mean by VGA switch? I guess I could try hooking up the DVI and see if it's trying to output through there. I think that's what you mean. I have a dual VGA switch set up now with one going to the Falcon and another for the 1040STe (which realistically I should just move to another area and hook up the MiST there... too many toys.)

[Rustynutt]

Not sure why I keep putting the Falcon back together after messing around with it. I definitely need to operate on the wiring a bit more, no reason to have the wires as long as they are when they only need to be much shorter.

What exactly do you mean by VGA switch? I guess I could try hooking up the DVI and see if it's trying to output through there. I think that's what you mean. I have a dual VGA switch set up now with one going to the Falcon and another for the 1040STe (which realistically I should just move to another area and hook up the MiST there... too many toys.)

Yes, either unplug the SV connector and plug the Falcon video cable into your monitor when there is black screen. Forgot, my MultiSync automatically switches between the two signals when there is no video output. It has a DVI and DB plug to run two cables to input.

Just leave the top case off for now

[leech]

Just checked. So with DVI out connected to one input on the monitor and the VGA adaptor into another on the Falcon. No jumper on J7 gives black screen, no hard drive light flickering, though the HxC light after a while starts to freak out, which also makes me think it locked up. Pretty much jumper on is the only way it starts up.

I did download the 006 updater, but it just only did the warning of 'make sure your CT is updated before you proceed' error. Too bad I don't have a second Falcon / CT6x to test this on...

[leech]

Some additional notes / testing;

I clocked it up to 80Mhz and ran it for hours last night, played some demos (two of which I had to go back to 030 or they crashed, or did horrible things). FTP'd enough to fill up my second FAT16 partition, so transfers with that were all stable.

Still can't figure out why the SuperVidel is giving me that bus error.
I've tested with only C:\AUTO\SV_XBIOS.PRG and C:\SV.INF, no VGA sync cable. Still no improvement.

Is my next step a JTAG programmer, or sending it off to get tested? Or find another Falcon I can test it in...

[shoggoth]

I get the impression that you tried to reprogram your SV using the utilities provided, and that this failed.

Until this actually succeeds, either by using the utilities in question, or using a JTAG cable, there is no point in trying anything else.

[leech]

I get the impression that you tried to reprogram your SV using the utilities provided, and that this failed.

Until this actually succeeds, either by using the utilities in question, or using a JTAG cable, there is no point in trying anything else.

I only tried running the updates after the SV_XBIOS.PRG was crashing. I've never dealt with the JTAG programmer, but kind of always wanted to get one. Is there a pinout for the SuperVidel somewhere so that I can flash it that way?

http://www.ebay.com/itm/Platform-Cable- ... 3ccc68cf50 is the one I need to order, right? Anyone know if it works with Windows 10 (or better yet, Linux?)

Just wanting some awesome resolutions on my Falcon... like really badly ha!

[Rustynutt]

I get the impression that you tried to reprogram your SV using the utilities provided, and that this failed.

Until this actually succeeds, either by using the utilities in question, or using a JTAG cable, there is no point in trying anything else.

I only tried running the updates after the SV_XBIOS.PRG was crashing. I've never dealt with the JTAG programmer, but kind of always wanted to get one. Is there a pinout for the SuperVidel somewhere so that I can flash it that way?


http://www.ebay.com/itm/Platform-Cable- ... 3ccc68cf50 is the one I need to order, right? Anyone know if it works with Windows 10 (or better yet, Linux?)

Just wanting some awesome resolutions on my Falcon... like really badly ha!

Like shoggth said, you surely need a successful flash. On Natures website, there are details on which files can be flashed using softs, and others that require using a Xylinx programmer (what I have anyway). Without knowing the current flash, and what your trying to load, kind of working in the dark.