CDM1550ls+ 200 MHz programing issue
Posted: Sun Dec 20, 2015 6:20 pm
I picked up a CDM1550ls+ 220 mhz version and didn't have the Motorola OEM cable for programming it, as it looks easy enough to build.
I built the rib to accessory plug cable as described in the service manual and I'm able to read and write the radio using both a smart rib and a sandy ganz rib. However when the radio is connected to the rib, the radio "locks up", as in the keypad does not work, it will not keyup, or change displays. After it it programmed and reboots, it appears to go into a reboot loop where it beeps but the display will not start up and the it reboots again.
Disconnecting it from the rib allows the front panel to work and then it boots normally. This is really annoying when trying to set the alignment in the tuner software as it reboots multiple times.
I've checked my pin-outs 5 times and it's correct. I removed the Boot line thinking it could be an issue, and it didn't make a difference.
Has anyone ever seen an issue like this?
Sadly I don't have another CDM to test with, so it's a bit hard to say if it's a cable or radio. I really doubt it's the cable however.
Right now this is annoying at worst, but I want to upgrade the firmware, and I'm reluctant to do that with a suspect cable.
I built the rib to accessory plug cable as described in the service manual and I'm able to read and write the radio using both a smart rib and a sandy ganz rib. However when the radio is connected to the rib, the radio "locks up", as in the keypad does not work, it will not keyup, or change displays. After it it programmed and reboots, it appears to go into a reboot loop where it beeps but the display will not start up and the it reboots again.
Disconnecting it from the rib allows the front panel to work and then it boots normally. This is really annoying when trying to set the alignment in the tuner software as it reboots multiple times.
I've checked my pin-outs 5 times and it's correct. I removed the Boot line thinking it could be an issue, and it didn't make a difference.
Has anyone ever seen an issue like this?
Sadly I don't have another CDM to test with, so it's a bit hard to say if it's a cable or radio. I really doubt it's the cable however.
Right now this is annoying at worst, but I want to upgrade the firmware, and I'm reluctant to do that with a suspect cable.