« previous next »
Pages: [1]   Go Down

Author Topic: musickeg still wont boot attatched logfile  (Read 8763 times)

0 Members and 2 Guests are viewing this topic.

Offline ryanmc

  • A few posts under my belt.
  • *
  • Posts: 17
musickeg still wont boot attatched logfile
« on: March 02, 2006, 11:17:27 am »
My keg wont boot i downloaded the rc pairs zip i wanted to attatch the log file but i dont see how so im pasting it. hopefully someone will have some info. im not 100% sure what happened to start this trouble or what to do next. It doesnt all fit here so this link is for the file its at geocities so it might have to pasted in a new window http://www.geocities.com/xact1974/logfile.txt

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

09.33:51d  :main      : Debug level = 10
09.35:51d  :main      : Force update file found
09.36:phatd:main      : Socket 2 has MSG_ID 2
09.72:51d  :openserpor: /dev/ttyS1 open fd=11
09.72:51d  :main      : Old ISP timeout value set to 50000 uSec
09.72:51d  :main      : Rollins timeout value set to 100000 uSec
09.72:51d  :test_uC_ve:              f9 (249) ------------>
09.73:51d  :test_uC_ve:                          <============ 53 (83)
09.73:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.73:51d  :parse_pac : opening /dos/firmware.pac
09.73:51d  :parse_pac : PAC file summary
09.73:51d  :parse_pac :        firmware name h: 02
09.73:51d  :parse_pac :        firmware name l: ff
09.73:51d  :parse_pac :        firmware ver   : 0c
09.73:51d  :parse_pac :        firmware base h: 0f
09.73:51d  :parse_pac :        firmware base l: fd
09.73:51d  :parse_pac :        firmware size h: 26
09.73:51d  :parse_pac :        firmware size l: f0
09.74:51d  :send_arm_s: firmware_modification=21
09.74:51d  :rw_packet : Buffering 10 at 0
09.75:51d  :rw_packet : ########################################################
09.75:51d  :rw_packet :              10 (16) ------------->
09.75:51d  :rw_packet : Expecting HACK
09.76:51d  :rw_packet :                          <============ ac (172)
09.76:51d  :rw_packet :              0c (12) ------------->
09.76:51d  :rw_packet : Expecting BACK
09.77:51d  :rw_packet :                          <============ bd (189)
09.77:51d  :rw_packet :              02 (2) ------------->
09.77:51d  :rw_packet : Expecting BACK
09.78:51d  :rw_packet :                          <============ bd (189)
09.78:51d  :rw_packet :              ff (255) ------------->
09.78:51d  :rw_packet : Expecting BACK
09.79:51d  :rw_packet :                          <============ bd (189)
09.79:51d  :rw_packet :              01 (1) ------------->
09.79:51d  :rw_packet : Expecting BACK
09.80:51d  :rw_packet :                          <============ bd (189)
09.80:51d  :rw_packet :              15 (21) ------------->
09.80:51d  :rw_packet : Expecting BACK
09.81:51d  :rw_packet :                          <============ bd (189)
09.81:51d  :rw_packet :              03 (3) ------------->
09.81:51d  :rw_packet : Expecting BACK
09.82:51d  :rw_packet :                          <============ bd (189)
09.82:51d  :rw_packet :              ca (202) ------------->
09.82:51d  :rw_packet : Expecting PACK
09.83:51d  :rw_packet :                          <============ ce (206)
09.83:51d  :rw_packet :                          <============ 11 (17)
09.83:51d  :rw_packet :                          <============ 00 (0)
09.83:51d  :rw_packet :                          <============ 00 (0)
09.83:51d  :rw_packet :                          <============ 21 (33)
09.83:51d  :rw_packet :                          <============ 04 (4)
09.83:51d  :rw_packet :                          <============ ca (202)
09.83:51d  :rw_packet : ########################################################
09.83:51d  :rw_packet :              ce (206) ------------->
09.83:51d  :rw_packet : ********************************************************
09.83:51d  :processpac: Got Session: mode 0, run type 0, lot 21 04
09.84:phatd:log_bc    : CPUid info:
Unique ID: 0xbf6c1190
Random ID: 0xbf6c119033143beed551894aad195570
CPU: EP73xx, ver 0x02
Lot Code: 0x2104
09.89:51d  :processpac: Non-text head unit - will not load text
11.16:51d  :rw_packet : ********************************************************
11.16:51d  :rw_packet :                          <============ a0 (160)
11.16:51d  :rw_packet :                          <============ 60 (96)
11.16:51d  :rw_packet :              ce (206) ------------->
11.16:51d  :rw_packet : ********************************************************
11.16:51d  :processpac: Got Firmware request
11.16:51d  :parse_pac : opening /dos/firmware.pac
11.16:51d  :parse_pac : PAC file summary
11.16:51d  :parse_pac :        firmware name h: 02
11.16:51d  :parse_pac :        firmware name l: ff
11.16:51d  :parse_pac :        firmware ver   : 0c
11.17:51d  :parse_pac :        firmware base h: 0f
11.17:51d  :parse_pac :        firmware base l: fd
11.17:51d  :parse_pac :        firmware size h: 26
11.17:51d  :parse_pac :        firmware size l: f0
11.17:51d  :send_firmw: sending FIRMWARE
11.17:51d  :rw_packet : Buffering a3 at 0
11.17:51d  :rw_packet : ########################################################
11.17:51d  :rw_packet :              a3 (163) ------------->
11.17:51d  :rw_packet : Expecting HACK
11.18:51d  :rw_packet :                          <============ ac (172)
11.18:51d  :rw_packet :              02 (2) ------------->
11.18:51d  :rw_packet : Expecting BACK
11.19:51d  :rw_packet :                          <============ bd (189)
11.19:51d  :rw_packet :              0f (15) ------------->
11.19:51d  :rw_packet : Expecting BACK
11.20:51d  :rw_packet :                          <============ bd (189)
« Last Edit: March 02, 2006, 11:32:03 am by ryanmc »
Logged

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: musickeg still wont boot attatched logfile
« Reply #1 on: March 02, 2006, 10:53:30 pm »
According to the log, it's booting up and starting to play... then something seems to go wrong with the communication between your 51d process and the 8051 chip.   You may actually have some sort of hardware problem...  I see you updated your firmware in the logfile, was it a fresh download?  If not you may want to try that.
Logged

Offline ryanmc

  • A few posts under my belt.
  • *
  • Posts: 17
Re: musickeg still wont boot attatched logfile
« Reply #2 on: March 05, 2006, 02:34:43 pm »
I tried a fresh firmware download with same results. i also tried swapping cables and reseting head unit. when you say bad hardware do you mean inside the keg itself or a bad wire, headunit or something else. would it give this trouble if it was the hard drive sig got corrupt or anything having to do with the harddrive ?
Logged

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: musickeg still wont boot attatched logfile
« Reply #3 on: March 05, 2006, 03:52:55 pm »
can you remove the forceupdate file and get us a new clean log of the boot attempt that way?
Logged

Offline ryanmc

  • A few posts under my belt.
  • *
  • Posts: 17
Re: musickeg still wont boot attatched logfile
« Reply #4 on: March 05, 2006, 04:11:58 pm »
I found the trouble (99% sure) the plug on back of keg was being stressed under seat was being pushed up once i unbolted the seaty and took the keg out i realized this. the plug must have cracked the solder on the pwb when the plugs streight it works but if you move it a little it goes back out. easy enough repair but i cant find the how to for taking the box apart anymore. where is that located i checked the wiki and here ? thanks again for the help....
Logged

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: musickeg still wont boot attatched logfile
« Reply #5 on: March 05, 2006, 04:43:59 pm »
taking the box apart may be covered on the wiki.. im not sure.  the only trick is getting the face plate off.. and its not really that tricky you just need a small flat blade screw driver to slip under it to pry it up all the way around.  

There are screws in the back, in the front and on the bottom to take it apart.
Logged
Pages: [1]   Go Up
« previous next »