Keg not working, very sad...

[heybiff]

So my keg has not worked for 5 or so months. I would get a solid Red LED when inserting the cartridge.  I never updated the ROM before, just updated songs and off I went. I thought my cable was damaged, so I bought a replacment and plugged it in with the same results.

Thinking I had nothing to loose at this point, I opened up the box and removed the board, checked connections capacitors, etc. Everything seemed fine. Updated the firmware, plugged it back in, ensuring the cable was securely fastened, and got the same results. Reset headunit, same results: solid RED LED, occasional green flash at first startup, then solid red.

Read about the Bootload.txt info, so I added that, and got this:

BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: S           <---------This doesn't look good?

I've searched though the forum, and am no closer. Help?
BTW: Kenwood Music Keg KHD-CX910, and KRC-8XX headunit. Worked fine with cd changer before keg, and for 1+ yrs with keg.

Heybiff

[sbingner]

The LED pattern you describe (strangely) seems to fit with a normal bootup... the solid red LED means it's on, and the green is used for hard drive access...  have you tried a replacement rc.sh to enable logging? (http://downloads.phathack.com/bushing/rc_pairs.zip)

[heybiff]

Log Posted:

07.66:phatd:main      : Media Daemon (phatd) $Revision: 1.226 $
07.68:phatd:main      : Debug level = 10
07.68:phatd:dac_clock_: Set DAC clock mode to 0
Selected profile is: Default
08.04:phatd:main      : Using /dos/exec.ini for exec.ini
08.15:phatd:fork_if_in: Spawning /dos/51d
08.15:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
08.36:phatd:main      : Entering Main loop
08.66:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

08.66:51d  :main      : Debug level = 10
08.67:51d  :main      : Force update file found
08.68:phatd:main      : Socket 2 has MSG_ID 2
09.01:51d  :openserpor: /dev/ttyS1 open fd=11
09.02:51d  :main      : Old ISP timeout value set to 50000 uSec
09.02:51d  :main      : Rollins timeout value set to 100000 uSec
09.02:51d  :test_uC_ve:              f9 (249) ------------>
09.03:51d  :test_uC_ve:                          <============ 53 (83)
09.03:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.03:51d  :parse_pac : opening /dos/firmware.pac
09.03:51d  :parse_pac : PAC file summary
09.03:51d  :parse_pac :        firmware name h: 02
09.03:51d  :parse_pac :        firmware name l: ff
09.03:51d  :parse_pac :        firmware ver   : 0c
09.03:51d  :parse_pac :        firmware base h: 0f
09.03:51d  :parse_pac :        firmware base l: fd
09.03:51d  :parse_pac :        firmware size h: 26
09.03:51d  :parse_pac :        firmware size l: f0
09.04:51d  :send_arm_s: firmware_modification=23
09.05:51d  :rw_packet : Buffering 10 at 0
09.05:51d  :rw_packet : ########################################################
09.22:51d  :rw_packet :              10 (16) ------------->
09.22:51d  :rw_packet : Expecting HACK
09.22:51d  :rw_packet :                          <============ ac (172)
09.23:51d  :rw_packet :              0c (12) ------------->
09.23:51d  :rw_packet : Expecting BACK
09.24:51d  :rw_packet :                          <============ bd (189)
09.24:51d  :rw_packet :              02 (2) ------------->
09.24:51d  :rw_packet : Expecting BACK
09.25:51d  :rw_packet :                          <============ bd (189)
09.25:51d  :rw_packet :              ff (255) ------------->
09.25:51d  :rw_packet : Expecting BACK
09.26:51d  :rw_packet :                          <============ bd (189)
09.26:51d  :rw_packet :              01 (1) ------------->
09.26:51d  :rw_packet : Expecting BACK
09.27:51d  :rw_packet :                          <============ bd (189)
09.27:51d  :rw_packet :              17 (23) ------------->
09.27:51d  :rw_packet : Expecting BACK
09.28:51d  :rw_packet :                          <============ bd (189)
09.28:51d  :rw_packet :              03 (3) ------------->
09.28:51d  :rw_packet : Expecting BACK
09.29:51d  :rw_packet :                          <============ bd (189)
09.29:51d  :rw_packet :              c8 (200) ------------->
09.29:51d  :rw_packet : Expecting PACK
09.30:51d  :rw_packet :                          <============ ce (206)
09.30:51d  :rw_packet :                          <============ 11 (17)
09.30:51d  :rw_packet :                          <============ 00 (0)
09.30:51d  :rw_packet :                          <============ 00 (0)
09.30:51d  :rw_packet :                          <============ 21 (33)
09.30:51d  :rw_packet :                          <============ 04 (4)
09.30:51d  :rw_packet :                          <============ ca (202)
09.30:51d  :rw_packet : ########################################################
09.30:51d  :rw_packet :              ce (206) ------------->
09.30:51d  :rw_packet : ********************************************************
09.30:51d  :processpac: Got Session: mode 0, run type 0, lot 21 04
09.31:phatd:log_bc    : CPUid info:
Unique ID: 0xfe601190
Random ID: 0xfe601190df7495421f268d0c538403a5
CPU: EP73xx, ver 0x02
Lot Code: 0x2104
09.34:51d  :processpac: Non-text head unit - will not load text
09.39:51d  :rw_packet : ********************************************************
09.39:51d  :rw_packet :                          <============ ff (255)
09.39:51d  :rw_packet :                          <============ 02 (2)
09.39:51d  :rw_packet :                          <============ ff (255)
09.39:51d  :rw_packet : Packet invalid checksum
09.39:51d  :rw_packet :              31 (49) ------------>


_________________________________________________________________
Heybiff

[heybiff]

...means I'm screwed.

Heybiff

[sbingner]

Somebody else had a similar problem, I think they ended up swapping it out...   or updating the firmware

I'd try the PhatNoise firmware update first, and make sure you have proper songs and stuff on your DMS.  The PhatBox IS booting, but it's having some other issue

[sbingner]

Hmm, that looks like it's TRYING to update your 8051 firmware but getting invalid checksums?   Yea, that's bad... what happens when you remove the forceupdate?

[heybiff]

I'll give it a try. I updated the firmaware on the DMS hopeing that woudl resolve the problem. I'll do a search to loacte how to turn off the foce update setting.

Heybiff

[heybiff]

Strangelym when I reset the HU, and switched to "DISC" is flashed CD1 for a sec, tehn went to "AUX"

Well, this is what I got when I rmoved forceupdate/forcesettings:


06.88:phatd:main      : Media Daemon (phatd) $Revision: 1.226 $
06.90:phatd:main      : Debug level = 10
06.90:phatd:dac_clock_: Set DAC clock mode to 0
Selected profile is: Default
07.26:phatd:main      : Using /dos/exec.ini for exec.ini
07.36:phatd:fork_if_in: Spawning /dos/51d
07.37:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
07.64:phatd:main      : Entering Main loop
07.87:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

07.87:51d  :main      : Debug level = 10
07.89:phatd:main      : Socket 2 has MSG_ID 2
08.18:51d  :openserpor: /dev/ttyS1 open fd=11
08.18:51d  :main      : Old ISP timeout value set to 50000 uSec
08.18:51d  :main      : Rollins timeout value set to 100000 uSec
08.18:51d  :test_uC_ve:              f9 (249) ------------>
08.19:51d  :test_uC_ve:                          <============ 53 (83)
08.19:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
08.19:51d  :parse_pac : opening /dos/firmware.pac
08.19:51d  :parse_pac : PAC file summary
08.19:51d  :parse_pac :        firmware name h: 02
08.19:51d  :parse_pac :        firmware name l: ff
08.19:51d  :parse_pac :        firmware ver   : 0c
08.19:51d  :parse_pac :        firmware base h: 0f
08.19:51d  :parse_pac :        firmware base l: fd
08.19:51d  :parse_pac :        firmware size h: 26
08.19:51d  :parse_pac :        firmware size l: f0
08.20:51d  :send_arm_s: firmware_modification=23
08.21:51d  :rw_packet : Buffering 10 at 0
08.21:51d  :rw_packet : ########################################################
08.37:51d  :rw_packet :              10 (16) ------------->
08.37:51d  :rw_packet : Expecting HACK
08.37:51d  :rw_packet :                          <============ ac (172)
08.37:51d  :rw_packet :              0c (12) ------------->
08.38:51d  :rw_packet : Expecting BACK
08.39:51d  :rw_packet :                          <============ bd (189)
08.39:51d  :rw_packet :              02 (2) ------------->
08.39:51d  :rw_packet : Expecting BACK
08.40:51d  :rw_packet :                          <============ bd (189)
08.40:51d  :rw_packet :              ff (255) ------------->
08.40:51d  :rw_packet : Expecting BACK
08.41:51d  :rw_packet :                          <============ bd (189)
08.41:51d  :rw_packet :              00 (0) ------------->
08.41:51d  :rw_packet : Expecting BACK
08.42:51d  :rw_packet :                          <============ bd (189)
08.42:51d  :rw_packet :              17 (23) ------------->
08.42:51d  :rw_packet : Expecting BACK
08.43:51d  :rw_packet :                          <============ bd (189)
08.43:51d  :rw_packet :              01 (1) ------------->
08.43:51d  :rw_packet : Expecting BACK
08.44:51d  :rw_packet :                          <============ bd (189)
08.44:51d  :rw_packet :              cb (203) ------------->
08.44:51d  :rw_packet : Expecting PACK
08.45:51d  :rw_packet :                          <============ ce (206)
08.45:51d  :rw_packet :                          <============ 11 (17)
08.45:51d  :rw_packet :                          <============ 00 (0)
08.45:51d  :rw_packet :                          <============ 00 (0)
08.45:51d  :rw_packet :                          <============ 21 (33)
08.45:51d  :rw_packet :                          <============ 04 (4)
08.45:51d  :rw_packet :                          <============ ca (202)
08.45:51d  :rw_packet : ########################################################
08.45:51d  :rw_packet :              ce (206) ------------->
08.45:51d  :rw_packet : ********************************************************
08.45:51d  :processpac: Got Session: mode 0, run type 0, lot 21 04
08.46:phatd:log_bc    : CPUid info:
Unique ID: 0xfe601190
Random ID: 0xfe601190df7495421f268d0c538403a5
CPU: EP73xx, ver 0x02
Lot Code: 0x2104
08.50:51d  :processpac: Non-text head unit - will not load text
08.54:51d  :rw_packet : ********************************************************
08.54:51d  :rw_packet :                          <============ ff (255)
08.54:51d  :rw_packet :                          <============ 02 (2)
08.54:51d  :rw_packet :                          <============ ff (255)
08.54:51d  :rw_packet : Packet invalid checksum
08.54:51d  :rw_packet :              31 (49) ------------>

[crackt]

i had this aux issue this morning after i repartitioned and what not. it seems i unknowingly set my firmware from keg to phatnoise platinum. (had issues with cd text) i think all you need to do is make sure you got all the firmware jazz set right then follow the update procedure. ** this is what fixed my AUX issue ** remove power from the phatnoise hardware to reset it. then mine worked like a charm. seems it works better when the firmware is set proper.

mike

[heybiff]

I will doublecheck my PMM, and try it.

Heybiff

[heybiff]

Tried it, no dice.

Also got responses back from Kenwood and Phatnoise, they for the most part said exactly what's in the forums here.

  OTOH, bought a Phatnoise box on Ebay ( no cables or dms ) for $25, plugged it in, watched green light blinky for about 5 mins, and viola, music started playing. Think I may try to get a spare cheap, just in case.

Thanks for the suggestions poeples. I'll hold onto the pold hardware in case it can be salvaged. I almost want to swap boards; I like the Kenwood box better.  I also like the idea of locating it in my glove box even more, but think I'll enjoy the music for a while. I need no more projects right now.

Heybiff