Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Dead UCM/Pi Board
#1
I have a UCM/Pi that failed a couple of years ago. I think it happend when uploading a firmware upgrade to it, either the file was corrupt or I used the wrong file.
At the time, I tried using the firmware programming cable without success so I just ordered a replacement.
I would like to recover it if possible, to use for testing and as a spare as I have a CM4 and a CM3 to CM4 adaptor. The PWR, RDY & ACT LEDs are green and I do see a flash from the Pi boot on the screen when I power it up, but then it goes blank.
Any thoughts on if it\'s possible to recover it?
Thanks!
Reply
#2
I think it may be the UCM/PI baseboard that was corrupted by the attempted firmware upgrade.

I suggest to try the upgrade again with the firmware upgrade cable. do not connect any other cable to the ucm/pi except the firmware upgrade cable
Reply
#3
OK, I finally got around to doing this with the firmware upgrade cable. I connected the UCM/Pi to the ETH03 UCM and tried to transfer UCMPi7_125.cbf to it.I get the error message \"Product number or type does not match\". See attached screenshot.
Thanks.


Attached Files Thumbnail(s)
   
Reply
#4
From the monitor IO, the UCM is connected by firmware upgrade cable to another UCM, nit UCM/PI. Is this a very old ucm/pi that uses UCM firmware? Canm you do a scan for Modules in the modules tab and send a screenshot of the Modules after scanning
Reply
#5
The UCM/Pi was connected to the UCM/Eth03 with the firmware cable. Do you mean that I should connect the dead UCM/Pi to the existing UCM/Pi? There is a 6 way connector on it, but no two way connector for the firmware cable.
 If I connect the dead UCM/Pi to the system and scan for modules, it appears as a General UCM. When I try to flash the UCM/Pi firmware to it, I get the same error message as before.


Attached Files Thumbnail(s)
   
Reply
#6
That UCM/PI is actually a general UCM, not specifically UCM/PI as seen in the module scan. I think originally the raspberry was connected to a normal UCM, before the UCM/Pi firmware was produced. Can you take a  photo of the UCM pi that you are tring to upgrade?
Reply
#7
This is the UCM/Pi I\'m trying to upgrade.
Reply
#8
That seems to be correct.
You say you are upgrading the UCM/PI by the ucnm/eth03 using the programm9ng cable.
I believe you are using the wrong commands to do the upgrade ie you are  right clicking on the ucm/pi module and doing upgrade. 

Instead go to Transfer> Firmware Upgrade > By Firmware upgrading cable ...see http://www.comfortforums.com/forum4/1782.html


Reply
#9
No, I have followed those instructions very carefully. I tried it both ways, connecting it to the UCM/Eth03 with the programming cable and doing Transfer/Firmware Upgrade/By Firmware Upgrading Cable..; and by connecting it directly to the system as a UCM and right-clicking on it to upload a local file.

Both ways give the same error message.

The only thing I notice is that there is no PP2 shunt on the UCM.
Reply
#10
Somehow the firmware in the UCM/PI was a general UCM. I am glad to hhear that you have managed to upgrade it back to a UCM/Pi
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)