Firmware Downgrade

[Caleb Vetter]

I don't know if I'm just not doing this right, or if my camera is broken I'm having trouble with the HDMI port on certain monitors (yes, I've tried EVERY setting possible multiple times) and I know it used to work on at least one of these monitors... I think before upgrading the firmware. So I want to test it with a previous version.

I currently have the most recent firmware (5.2.38) and I've been trying several versions back to 5.1.49 with no luck. I'm assuming the downgrade process is exactly like the upgrade process, just with an earlier firmware file. Is that correct? Why won't it downgrade? It makes all the fan noises like it's downgrading/upgrading.

 

[Caleb Vetter]

Crap. I knew as soon as I posted I figure something out. Apparently you can't downgrade from 5.2.38.

 

[Terry VerHaar]

Just a thought - going directly at your problem rather than the issue of downgrading firmware...

It has been my experience that some monitors are very finicky with RED HDMI settings. Sometimes you have to change the settings and then re-start the camera, and/or the monitor, or both and/or plug things in after restarting... or before. LOL

Basically, the must be a proper order for these steps but it's really hard to tell what it is.

I'd bet it isn't a firmware thing.

Just a thought.

 

[Caleb Vetter]

It's weird because it acts like it's getting a signal (blue indicator on monitor is on) but it's just a black (no active pixels) screen. When I change the camera output refresh rate, it shows on the monitor "Input Not Supported" so the changes I make to the camera are definitely updating the signal.

 

[Caleb Vetter]

Just upgraded to the beta firmware (5.3.16) which at this point is the only other firmware option I could try. I got "Input Not Supported" on 1080p 60hz where it used to be a black screen, and I'm actually getting a (stretched) image out of the 720p 60hz setting. It's definitely a firmware thing.

Then I downgraded back to 5.2.38 and it's doing the same thing it was before trying the beta firmware. It's definitely a firmware issue.

 

[Jeffery Anderson]

monitor being used?

 

[Caleb Vetter]

It's just an Acer computer monitor: Acer S231HL.

 

[Adrian Weinbrecht]

It's just an Acer computer monitor: Acer S231HL.

Caleb

On your first post you mention you're having trouble with certain monitors? Does this mean you can get the HDMI to work fine on some monitors? Have you tested it on a Monitor with HD resolution or lower ? For example a Small HD or Marshall monitor.

There is a chance that the Acer monitor has too much resolution and won't work with a 1080 feed only. It needs more resolution to drive it. Also have you checked the input menus on the monitor? Sometimes a setting here can change things.

Just a thought......

 

[Caleb Vetter]

Yes, I tested it with the following monitors...
Panasonic Plasma TV (HDMI) = Works
ViewSonic 27" (HDMI) = Works
ViewSonic 27" (DVI) = Works
Gateway (HDMI) = Works
Gateway (DVI) = Doesn't work
Acer 23" (DVI) = Doesn't work
Acer 21" (DVI) = Doesn't work
Marshall 7" (HDMI in any resolution or Hertz) = Works

At first I thought maybe it was the HDMI > DVI conversion, but apparently not, since it works on the ViewSonic. Also, I tested my Acer 23" with a PS3 and a couple computers (with HDMI > DVI conversion) and it worked just fine. My Acer monitor is 1080p native resolution so that shouldn't be the problem. And it doesn't have menus to change anything until it's receiving a valid signal.

Only reason I'm really wanting my Acer monitor to work is because I've already modded it out with a V-mount plate and supplemental power to a Nyrius wireless HDMI receiver. It used to be a rock solid and versatile director's monitor before the firmware upgrade. Hoping they fix whatever changed from the previous version. Worse case I'll just have to find a monitor with an actual HDMI input and mod that.

 

[ericyoung]

Sadly you can only go back to 5.1.67 after upgrading to 5.1.67 or higher.