Author Topic: Phatbox No Longer Recognised 'NO CD'  (Read 10248 times)

0 Members and 1 Guest are viewing this topic.

Offline madkebab

  • Newbie
  • Posts: 11
  • PhatHacker
Phatbox No Longer Recognised 'NO CD'
« on: April 26, 2007, 06:02:15 pm »
Well I have had my phatbox unit fitted to my Audi concert 2 HU for over 6 months and have never had a problem, until now!!

All I get displayed on the HU is 'NO CD'.

The DMS is recognised in Windows and within the phatnoise music manager. I even tested reapplying the latest firmware just to ensure the DMS was working ok, it was.

I disconnected the phatbox cable and reconnected. Then inserted the DMS. I get the red light on solid and the green light flashes intermittently whilst the disc is being read.

Everything appears to be as it should but the HU will not read the DMS.

Please can someone suggest how I can progress with diagnosing this fault. Is there any boot log that I can take off of the DMS which might show up the problem?

I am lost without my mp3's so I am praying someone can help  :-[

Simon

Offline madkebab

  • Newbie
  • Posts: 11
  • PhatHacker
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #1 on: April 26, 2007, 06:54:31 pm »
Just a quick update

Ran DMS doctor - all tests passed successfully
Ran DMS database doctor - database was fine

Wrote latest firmware to DMS and put DMS into phatbox and it went through the process of reprogramming.

However, still not recognised when I switch the HU on.

The LED's show as follows:-

Red - constant

Green - single flash every 5 seconds

Any ideas  ???

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #2 on: April 26, 2007, 08:54:43 pm »
do you have a bootload.log you can show us?  that would be helpful.

I also suggest that you disable your plugins (rename the plugin directory) and download the rcpairs.zip file and use the level 10 logging version to get as much data as possible logged.

Has your box been hacked already?

Offline madkebab

  • Newbie
  • Posts: 11
  • PhatHacker
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #3 on: April 27, 2007, 07:12:07 am »
do you have a bootload.log you can show us?  that would be helpful.

I also suggest that you disable your plugins (rename the plugin directory) and download the rcpairs.zip file and use the level 10 logging version to get as much data as possible logged.

Has your box been hacked already?

I should have mentioned that the box has not been hacked.

Can I do everything you suggested with a non hacked box?

Offline judb

  • Administrator
  • Veteran.
  • *****
  • Posts: 1329
  • ph4t l3wtz
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #4 on: April 27, 2007, 01:54:34 pm »
yes.  do that stuff and we'll see what happens.  if you need details on any of these there are lots of threads with instructions on them.

Offline madkebab

  • Newbie
  • Posts: 11
  • PhatHacker
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #5 on: April 27, 2007, 05:15:18 pm »
yes.  do that stuff and we'll see what happens.  if you need details on any of these there are lots of threads with instructions on them.

Here's the results of my bootload.log

BOOT0-0: OK
BOOT0-1: OK
BOOT0: Successful
BOOT9: Successful
BOOTB: Successful
BOOTF: Successful
BOOT*: Successful

Cheers

Simon

Offline madkebab

  • Newbie
  • Posts: 11
  • PhatHacker
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #6 on: April 27, 2007, 05:17:34 pm »
Here is the logfile.txt in sections as it was too long for a single post

07.67:phatd:main      : Media Daemon (phatd) $Revision: 1.217 $
07.69:phatd:main      : Debug level = 10
Selected profile is: Default
08.04:phatd:main      : Using /dos/exec.ini for exec.ini
08.14:phatd:fork_if_in: Spawning /dos/51d
08.15:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
08.89:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

08.89:51d  :main      : Debug level = 10
09.12:phatd:main      : Entering Main loop
09.13:phatd:main      : Socket 2 has MSG_ID 2
09.47:51d  :openserpor: /dev/ttyS1 open fd=11
09.48:51d  :main      : Old ISP timeout value set to 50000 uSec
09.48:51d  :main      : Rollins timeout value set to 100000 uSec
09.48:51d  :test_uC_ve:        f9 (249) ------------>
09.49:51d  :test_uC_ve:              <============ 53 (83)
09.49:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.49:51d  :parse_pac : opening /dos/firmware.pac
09.49:51d  :parse_pac : PAC file summary
09.49:51d  :parse_pac :     firmware name h: 39
09.49:51d  :parse_pac :     firmware name l: 50
09.49:51d  :parse_pac :     firmware ver   : 07
09.49:51d  :parse_pac :     firmware base h: 0f
09.49:51d  :parse_pac :     firmware base l: fd
09.49:51d  :parse_pac :     firmware size h: 22
09.49:51d  :parse_pac :     firmware size l: b0
09.50:51d  :send_arm_s: firmware_modification=3
09.51:51d  :rw_packet : Buffering 10 at 0
09.51:51d  :rw_packet : ########################################################
09.63:51d  :rw_packet :        10 (16) ------------->
09.63:51d  :rw_packet : Expecting HACK
09.63:51d  :rw_packet :              <============ ac (172)
09.63:51d  :rw_packet :        07 (7) ------------->
09.64:51d  :rw_packet : Expecting BACK
09.65:51d  :rw_packet :              <============ bd (189)
09.65:51d  :rw_packet :        39 (57) ------------->
09.65:51d  :rw_packet : Expecting BACK
09.66:51d  :rw_packet :              <============ bd (189)
09.66:51d  :rw_packet :        50 (80) ------------->
09.66:51d  :rw_packet : Expecting BACK
09.67:51d  :rw_packet :              <============ bd (189)
09.67:51d  :rw_packet :        00 (0) ------------->
09.67:51d  :rw_packet : Expecting BACK
09.68:51d  :rw_packet :              <============ bd (189)
09.68:51d  :rw_packet :        03 (3) ------------->
09.68:51d  :rw_packet : Expecting BACK
09.69:51d  :rw_packet :              <============ bd (189)
09.69:51d  :rw_packet :        03 (3) ------------->
09.69:51d  :rw_packet : Expecting BACK
09.70:51d  :rw_packet :              <============ bd (189)
09.70:51d  :rw_packet :        5a (90) ------------->
09.70:51d  :rw_packet : Expecting PACK
09.71:51d  :rw_packet :              <============ ce (206)
09.71:51d  :rw_packet :              <============ 11 (17)
09.71:51d  :rw_packet :              <============ 00 (0)
09.71:51d  :rw_packet :              <============ 06 (6)
09.71:51d  :rw_packet :              <============ 33 (51)
09.71:51d  :rw_packet :              <============ 01 (1)
09.71:51d  :rw_packet :              <============ b5 (181)
09.71:51d  :rw_packet :              <============ 14 (20)
09.71:51d  :rw_packet :              <============ 39 (57)
09.71:51d  :rw_packet :              <============ 50 (80)
09.71:51d  :rw_packet :              <============ 07 (7)
09.71:51d  :rw_packet :              <============ 00 (0)
09.71:51d  :rw_packet :              <============ 06 (6)
09.71:51d  :rw_packet :              <============ 00 (0)
09.72:51d  :rw_packet :              <============ 56 (86)
09.72:51d  :rw_packet :              <============ 21 (33)
09.72:51d  :rw_packet :              <============ df (223)
09.72:51d  :rw_packet : ########################################################
09.72:51d  :rw_packet :        ce (206) ------------->
09.72:51d  :rw_packet : ********************************************************
09.72:51d  :processpac: Got Session: mode 0, run type 6, lot 33 01
09.73:phatd:log_bc    : CPUid info:
Unique ID: 0x92132590
Random ID: 0x921325901a3409fb7b1057d5c711c42b
CPU: EP73xx, ver 0x02
Lot Code: 0x3301
09.76:51d  :processpac: Initializing 1.2 DAC
09.76:51d  :processpac: SSA head unit
09.76:51d  :processpac: Extra help enabled
09.85:51d  :processpac: Non-text head unit - will not load text
09.95:51d  :rw_packet : ********************************************************
09.95:51d  :rw_packet :              <============ e2 (226)
09.95:51d  :rw_packet :              <============ 8b (139)
09.96:51d  :rw_packet :              <============ 41 (65)
09.96:51d  :rw_packet :              <============ 01 (1)
09.96:51d  :rw_packet :              <============ 00 (0)
09.96:51d  :rw_packet :              <============ 00 (0)
09.96:51d  :rw_packet :              <============ 00 (0)
09.96:51d  :rw_packet :              <============ 70 (112)
09.96:51d  :rw_packet :              <============ 83 (131)
09.96:51d  :rw_packet :              <============ 5e (94)
09.96:51d  :rw_packet :        ce (206) ------------->
09.96:51d  :rw_packet : ********************************************************
09.96:51d  :processpac: Got uC ID
10.58:51d  :rw_packet : ********************************************************
10.58:51d  :rw_packet :              <============ e2 (226)
10.58:51d  :rw_packet :              <============ 0a (10)
10.58:51d  :rw_packet :              <============ 0c (12)
10.58:51d  :rw_packet :              <============ 04 (4)
10.58:51d  :rw_packet :              <============ 03 (3)
10.58:51d  :rw_packet :              <============ 82 (130)
10.58:51d  :rw_packet :              <============ 7d (125)
10.58:51d  :rw_packet :              <============ 00 (0)
10.58:51d  :rw_packet :              <============ 87 (135)
10.59:51d  :rw_packet :              <============ 7b (123)
10.59:51d  :rw_packet :        ce (206) ------------->
10.59:51d  :rw_packet : ********************************************************
10.59:51d  :processpac: Got Query total disc
10.59:51d  :rw_packet : Buffering 7d at 0
10.59:51d  :rw_packet :        ce (206) ------------->
10.59:51d  :rw_packet : ********************************************************
10.59:51d  :processpac: uC DEBUG: 8b 41 01 00 00 00 70 83
10.60:51d  :rw_packet :        ce (206) ------------->
10.60:51d  :rw_packet : ********************************************************
10.60:51d  :processpac: uC DEBUG: 0a 0c 04 03 82 7d 00 87
10.60:51d  :rw_packet : ********************************************************
10.60:51d  :rw_packet :              <============ e2 (226)
10.60:51d  :rw_packet :              <============ 8b (139)
10.60:51d  :rw_packet :              <============ 41 (65)
10.60:51d  :rw_packet :              <============ 01 (1)
10.60:51d  :rw_packet :              <============ 00 (0)
10.60:51d  :rw_packet :              <============ 00 (0)
10.60:51d  :rw_packet :              <============ 00 (0)
10.60:51d  :rw_packet :              <============ 70 (112)
10.60:51d  :rw_packet :              <============ 83 (131)
10.60:51d  :rw_packet :              <============ 5e (94)
10.61:51d  :rw_packet :        ce (206) ------------->
10.61:51d  :rw_packet : ********************************************************
10.61:51d  :processpac: uC DEBUG: 8b 41 01 00 00 00 70 83
10.61:51d  :rw_packet : ########################################################
10.61:51d  :rw_packet :        7d (125) ------------->
10.61:51d  :rw_packet : Expecting HACK
10.62:51d  :rw_packet :              <============ ac (172)
10.62:51d  :rw_packet :        00 (0) ------------->
10.62:51d  :rw_packet : Expecting BACK
10.63:51d  :rw_packet :              <============ bd (189)
10.63:51d  :rw_packet :        0a (10) ------------->
10.63:51d  :rw_packet : Expecting BACK
10.64:51d  :rw_packet :              <============ bd (189)
10.64:51d  :rw_packet :        79 (121) ------------->
10.64:51d  :rw_packet : Expecting PACK
10.65:51d  :rw_packet :              <============ ce (206)
10.65:51d  :rw_packet :              <============ 20 (32)
10.65:51d  :rw_packet :              <============ 00 (0)
10.65:51d  :rw_packet :              <============ 01 (1)
10.65:51d  :rw_packet :              <============ df (223)
10.65:51d  :rw_packet : ########################################################
10.65:51d  :rw_packet

Offline madkebab

  • Newbie
  • Posts: 11
  • PhatHacker
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #7 on: April 27, 2007, 05:21:45 pm »
Do you need the rest of this file as it is huge? If so would it be possible to email it you rather than paste into the thread?

Simon

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #8 on: April 27, 2007, 06:47:44 pm »
uuuuh it looks like it's working, that's strange... do you have a play later in the logfile?   Is that perhaps a leftover logfile from when it worked?

Offline madkebab

  • Newbie
  • Posts: 11
  • PhatHacker
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #9 on: April 27, 2007, 07:32:25 pm »
uuuuh it looks like it's working, that's strange... do you have a play later in the logfile?   Is that perhaps a leftover logfile from when it worked?

The logfile has no modified date on it so I cannot tell how old it is. I cannot find any existence of the word play in the logfile when I did a search.

If I delete the current logfile.txt will it create a new one when it boots back up?

Is it possible that the HU has gone faulty rather than the PB?


Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #10 on: April 28, 2007, 01:33:35 am »
Yes, if you delete it it will make a new one... as to the HU, I have no idea :)

Offline madkebab

  • Newbie
  • Posts: 11
  • PhatHacker
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #11 on: April 28, 2007, 09:34:17 am »
Yes, if you delete it it will make a new one... as to the HU, I have no idea :)

Right I deleted the file and it has created a new logfile.txt, here is the beginning of the file

07.67:phatd:main      : Media Daemon (phatd) $Revision: 1.217 $
07.69:phatd:main      : Debug level = 10
Selected profile is: Default
08.04:phatd:main      : Using /dos/exec.ini for exec.ini
08.14:phatd:fork_if_in: Spawning /dos/51d
08.15:phatd:fork_if_in: Program started (/dos/51d), pid=13, childno=0
08.78:51d  :main      :
--- 51d (Mar  3 2004 18:49:12) --- $Revision: 1.205 $

08.78:51d  :main      : Debug level = 10
09.12:phatd:main      : Entering Main loop
09.13:phatd:main      : Socket 2 has MSG_ID 2
09.50:51d  :openserpor: /dev/ttyS1 open fd=11
09.50:51d  :main      : Old ISP timeout value set to 50000 uSec
09.50:51d  :main      : Rollins timeout value set to 100000 uSec
09.51:51d  :test_uC_ve:        f9 (249) ------------>
09.52:51d  :test_uC_ve:              <============ 53 (83)
09.52:51d  :test_uC_ve: Got 53 for invalid header, must have ProtoPhat 2
09.52:51d  :parse_pac : opening /dos/firmware.pac
09.52:51d  :parse_pac : PAC file summary
09.52:51d  :parse_pac :     firmware name h: 39
09.52:51d  :parse_pac :     firmware name l: 50
09.52:51d  :parse_pac :     firmware ver   : 07
09.52:51d  :parse_pac :     firmware base h: 0f
09.52:51d  :parse_pac :     firmware base l: fd
09.52:51d  :parse_pac :     firmware size h: 22
09.52:51d  :parse_pac :     firmware size l: b0
09.53:51d  :send_arm_s: firmware_modification=4
09.54:51d  :rw_packet : Buffering 10 at 0
09.54:51d  :rw_packet : ########################################################
09.66:51d  :rw_packet :        10 (16) ------------->
09.66:51d  :rw_packet : Expecting HACK
09.66:51d  :rw_packet :              <============ ac (172)
09.66:51d  :rw_packet :        07 (7) ------------->
09.67:51d  :rw_packet : Expecting BACK
09.68:51d  :rw_packet :              <============ bd (189)
09.68:51d  :rw_packet :        39 (57) ------------->
09.68:51d  :rw_packet : Expecting BACK
09.69:51d  :rw_packet :              <============ bd (189)
09.69:51d  :rw_packet :        50 (80) ------------->
09.69:51d  :rw_packet : Expecting BACK
09.70:51d  :rw_packet :              <============ bd (189)
09.70:51d  :rw_packet :        00 (0) ------------->
09.70:51d  :rw_packet : Expecting BACK
09.71:51d  :rw_packet :              <============ bd (189)
09.71:51d  :rw_packet :        04 (4) ------------->
09.71:51d  :rw_packet : Expecting BACK
09.72:51d  :rw_packet :              <============ bd (189)
09.72:51d  :rw_packet :        03 (3) ------------->
09.72:51d  :rw_packet : Expecting BACK
09.73:51d  :rw_packet :              <============ bd (189)
09.73:51d  :rw_packet :        59 (89) ------------->
09.73:51d  :rw_packet : Expecting PACK
09.74:51d  :rw_packet :              <============ ce (206)
09.74:51d  :rw_packet :              <============ 11 (17)
09.74:51d  :rw_packet :              <============ 00 (0)
09.74:51d  :rw_packet :              <============ 06 (6)
09.74:51d  :rw_packet :              <============ 33 (51)
09.74:51d  :rw_packet :              <============ 01 (1)
09.74:51d  :rw_packet :              <============ b5 (181)
09.74:51d  :rw_packet :              <============ 14 (20)
09.74:51d  :rw_packet :              <============ 39 (57)
09.74:51d  :rw_packet :              <============ 50 (80)
09.74:51d  :rw_packet :              <============ 07 (7)
09.74:51d  :rw_packet :              <============ 00 (0)
09.74:51d  :rw_packet :              <============ 06 (6)
09.74:51d  :rw_packet :              <============ 00 (0)
09.75:51d  :rw_packet :              <============ 56 (86)
09.75:51d  :rw_packet :              <============ 21 (33)
09.75:51d  :rw_packet :              <============ df (223)
09.75:51d  :rw_packet : ########################################################
09.75:51d  :rw_packet :        ce (206) ------------->
09.75:51d  :rw_packet : ********************************************************
09.75:51d  :processpac: Got Session: mode 0, run type 6, lot 33 01
09.76:phatd:log_bc    : CPUid info:
Unique ID: 0x92132590
Random ID: 0x921325901a3409fb7b1057d5c711c42b
CPU: EP73xx, ver 0x02
Lot Code: 0x3301
09.79:51d  :processpac: Initializing 1.2 DAC
09.79:51d  :processpac: SSA head unit
09.79:51d  :processpac: Extra help enabled
09.88:51d  :processpac: Non-text head unit - will not load text
09.98:51d  :rw_packet : ********************************************************
09.98:51d  :rw_packet :


I am going to try and use the cd changer that used to be connected to the car. If that doesnt work either then I will know it is the HU. Otherwise I am totally stumped by this.

Offline madkebab

  • Newbie
  • Posts: 11
  • PhatHacker
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #12 on: May 18, 2007, 07:32:55 pm »
well just to update this thread I tried the PB in another car with a different cable and again it could not be recognized. Has anyone got any ideas where I can go from here as I am totally baffled?

Would it be worth hacking the DMS as a last resort or can I not do that?

Another option I have thought of is to buy a reconditioned unit off of Ebay, are these worth bothering with?

Any help much appreciated as I am missing my tunes badly  >:(

Simon

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #13 on: May 18, 2007, 08:27:20 pm »
If you can find an Audi or VW box cheap you'd be good...

All I can think of is some sort of communication problem.  The processor and IDE obviously work, also 51d is communication with the external 8051 chip... so that's not broken... it would have to be either something blown where it reads the protocol data or something wrong with the wiring IMO...

Is there nothing more to your logfile?


Offline strictly_biz

  • Newbie
  • Posts: 14
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #14 on: September 04, 2007, 05:17:39 am »
I have a 160 GB drive with hacked head unit in audi

For a few months I had about 90GB of mp3, recently added another 50GB+ of mp3 and when I put drive back into unit it is coming up as 'NO CD'

any suggesting on diagnosing

thx

Offline strictly_biz

  • Newbie
  • Posts: 14
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #15 on: September 04, 2007, 05:34:31 am »
hmmm deleted most of the new stuff I added and ran chdsk on phtsys, now its working

in order to run the phatbox with more than a certain amount of data do I need to update something? currently using PhatNoise Music Manager 2.30 and I hacked my box back in march

Offline sbingner

  • Administrator
  • Veteran.
  • *****
  • Posts: 1301
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #16 on: September 04, 2007, 06:40:51 am »
The number of songs shouldn't matter... but I think there is a limit on the number of songs in a single playlist? 

Offline Firefox

  • Needs to get outside.
  • ***
  • Posts: 124
  • Kenwood 710 Keg 80GB ;-)
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #17 on: September 04, 2007, 12:55:14 pm »
The number of songs shouldn't matter... but I think there is a limit on the number of songs in a single playlist? 

Pretty sure it is 10,000 playlists, with upto 10,000 tracks per playlist.

Offline strictly_biz

  • Newbie
  • Posts: 14
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #18 on: September 04, 2007, 04:36:10 pm »
After adding the new mp3's I was up to 13,000 tracks total in about 1200 playlists

I think the most any one playlist has is about 72

Maybe too many corrupt files, I think I have a few of those? bad file types? I'll have to experiment and report back

Offline strictly_biz

  • Newbie
  • Posts: 14
Re: Phatbox No Longer Recognised 'NO CD'
« Reply #19 on: September 05, 2007, 08:10:15 am »
I replaced the linux file on my phtsys partition with http://downloads.phathack.com/sbingner/linux-lba48.bz2

now working