MPO wrote: > Cool, thanks! Very interested to hear the results!
Results very good. The Radio's battery connector is from the JST PHD series. I acquired the 10 pin housing and some pre-crimped tails from Conrad. (The terminals are too small/non-standard for my "crimper"). Housing: https://www.conrad.com/p/jst-phdr-10vs-housing-phd-series-number-of-pins-2-x-5-nominal-current-details-3-a-740140 Tails: https://www.conrad.com/p/jst-pre-fab-braid-phd-total-number-of-pins-1-810792-1-pcs-715168 I dare say you might find something else that will fit. The housing plugs on my radios are probably clones... I can confirm the wiring up. I don't think you'd be using the 3.3V line with a conventional serial to usb cable, but I use it with my set up. Check all voltages before making connections ! A 5V cable would be a very bad idea, as @bpa has remarked. There's plenty of information on the internet on the matter, so study it if you are uncertain. Confirmatory photograph attached. After a good deal of chatter you'll be seeing: Code: -------------------- BMI Write Memory (address: 0x500418, value: 0x52d8bc) BMI Bit-Wise (OR) modify Register (address: 0x500410, orig:0x0, new: 0x1, mask:0x1) BMI Done [ 14.941937] AR6000 Reg Code = 0x40000060 Selected interface 'eth1' root: wlan started Starting SqueezePlay Please press Enter to activate this console. udhcpc (v1.18.2) started killall: zcip: no process killed Sending discover... Squeezeplay 7.7.3 r16676 Sending discover... [ 22.316822] channel hint set to 2437 -------------------- "Please press Enter to activate this console" is your trigger. Press enter as requested, and you'll be in a busybox shell. All being well, you could (reasonably swiftly) paste in the following one-liner to de-fang the watchdog: Code: -------------------- printf "#!/bin/sh\nexit 0\n" >/var/repair.sh;chmod +x /var/repair.sh;mount -o bind /var/repair.sh /usr/sbin/repair.sh -------------------- It "replaces" the existing watchdog "repair" script with one that returns "0", which tells the watchdog that all is now well, and that a reboot is not necessary. You'll know that it has worked if the Radio no longer goes into its re-boot cycle, and you'll be able to verify as follows: Code: -------------------- # cat /usr/sbin/repair.sh #!/bin/sh exit 0 -------------------- It's only a temporary fix, until the Radio is restarted, but you can now put something slightly more permanent in place. You might edit -/etc/watchdog.conf- and replace the -repair-binary = /usr/sbin/repair.sh- line with a more congenial script. Provided your replacement script exits with success, (-exit 0-), the watchdog will think that there is no need to reboot. You can enable ssh by editing the file -/etc/inetd.conf- and uncommenting the ssh line, which should now read Code: -------------------- ssh stream tcp nowait root /usr/sbin/dropbear dropbear -i -------------------- Then reload -inetd- by executing -kill -hup <pid of inetd>-. Good luck ! Addendum: Pressing the "PAUSE" key during boot up appear to initiate a "BOOTP" request, followed (on failure of BOOTP) by a RedBoot prompt. Herein may lie an ability to effect a repair beyond that offered by the normal "MORE/+" and "REWIND" boot up options. +-------------------------------------------------------------------+ |Filename: IMG_0300_b.jpg | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=30731| +-------------------------------------------------------------------+ ------------------------------------------------------------------------ mrw's Profile: http://forums.slimdevices.com/member.php?userid=38299 View this thread: http://forums.slimdevices.com/showthread.php?t=112339 _______________________________________________ Radio mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/radio
