Unoffical empeg BBS

Quick Links: Empeg FAQ | Software | RioCar.Org | Hijack | jEmplode | emphatic
Repairs: Repairs | Addons: Eutronix | Cases

Page 1 of 2 1 2 >
Topic Options
#351901 - 30/04/2012 15:18 Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive
JeepBastard
enthusiast

Registered: 08/09/1999
Posts: 364
Loc: Brooklyn
I have a beatup empeg from a drive across the country that I am trying to bring to life. I hooked up a new 80gig Blue WD laptop drive and I can connect via serial.


I havent tested them, but the solder joints for the IDE cable visual seem okay and I have two IDE cables to test with. I keep getting Bad Pump Response using the Big Disk Builder to initilize the disk. I can hear the disk spin up. I've included the output from COM1 below. I tried everything in the fabulous FAQ to try but I am hitting the hoover dam on this.

Can anyone point out some warning signs for me or ideas to try? or is my empeg too beat up to come back to life!

Code:
e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v508 (hijack@rtr.ca) (gcc version 2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 40103958) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (996k code, 20k reserved, 364k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 67706d65 'empg'
Tuner: loopback=0, ID=-1
show_message("Hijack v508 by Mark Lord")
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0004100).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized:  16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xffff
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xffff
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xffff
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7f
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xffff
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xffff
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
Probing primary interface...
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7f
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7f
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7f
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xffff
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7f
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xff7d
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffff
ide_data_test: wrote 0x5555 read 0xffff
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman (erik@vt.edu)

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:28:0f:76
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05


Edited by JeepBastard (01/05/2012 00:03)
_________________________
Mark I + Mark IIa | Jeep 97 TJ
my current blog

Top
#352026 - 08/05/2012 00:00 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
Dviant
new poster

Registered: 14/01/2005
Posts: 38
You are getting this readout when using the builder? Or after loading up the firmware?

Honestly I am not the best person to assist, but no one else has replied.

I did rebuild an empeg this weekend myself and it looks like an error I got loading a non-big disk 2.01 by mistake.

Top
#352035 - 08/05/2012 04:41 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: Dviant]
StigOE
addict

Registered: 27/10/2002
Posts: 568
It seems you have a problem somewhere with the IDE bus, as you're reading 0xfff or 0xff7d all the time. By the end of the test you should be able to read what you wrote. I think Mark would be better to answer this... smile

Top
#352104 - 13/05/2012 11:37 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: StigOE]
JeepBastard
enthusiast

Registered: 08/09/1999
Posts: 364
Loc: Brooklyn


Thanks for looking at the log. I'm still trying to piece together a working mark 2 Empeg from my parts, but maybe both my boards are damaged. They did take in some weather from the jeep.

Still trying! Any help is much appreciated.


Edited by JeepBastard (13/05/2012 11:41)
_________________________
Mark I + Mark IIa | Jeep 97 TJ
my current blog

Top
#352105 - 13/05/2012 17:22 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Either the drive is dead, or one of the "control" lines is dead on the IDE bus.

Top
#352256 - 18/05/2012 12:05 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: mlord]
JeepBastard
enthusiast

Registered: 08/09/1999
Posts: 364
Loc: Brooklyn
Thanks for taking a look mlord!

Hey guys if one of my control lines is dead is my board basically dead in the water? This same empeg also had the 1 amp fuse blown that made for garbled display so I was able to solder in a new one so now that works.


I may have damaged a small fuse where the question mark is indicated. I might have to resolder it, is it related to the IDE chip?

I was also able to get it to pump the partition and load on alpha3 (and 2.01.hijack) by using the last (second hard drive) connector on the IDE cable! Hurray!

However but I couldn't connect to the device it would give me a

Code:
Download failed while checking database

Error 0xc0041002
- from emplode under windows 7 via Ethernet for a while.

Now it's not reporting a hard drive at all and I am getting a Bad Pump at Stage 0x20 now. Quick understatement - think the IDE cable is wonky. I might be fighting with several things here. Any suggestions? I have 3 mark 2's and 1 mark 1 - 2 Of the mark 2's boot up but neither wants to recognize a hard drive.

JT!


Edited by JeepBastard (18/05/2012 12:23)
_________________________
Mark I + Mark IIa | Jeep 97 TJ
my current blog

Top
#352258 - 18/05/2012 13:08 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
JeepBastard
enthusiast

Registered: 08/09/1999
Posts: 364
Loc: Brooklyn
Oh boy! I reversed the IDE cable (second HD position on the board , first HD position on a 4GB laptop drive I pumped and i got this in the log!:
Code:
e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kernel.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v508 (hijack@rtr.ca) (gcc version 2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 40103958) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (996k code, 20k reserved, 364k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 67706d65 'empg'
Tuner: loopback=0, ID=-1
show_message("Hijack v508 by Mark Lord")
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0005e00).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized:  16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff82
ide_data_test: wrote 0xaaaa read 0xab80
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xff80
ide_data_test: wrote 0xffff read 0xff82
ide_data_test: wrote 0xaaaa read 0xab80
ide_data_test: wrote 0x5555 read 0x5580
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xbfaa
ide_data_test: wrote 0x5555 read 0xdf55
hda: HITACHI_DK227A-41, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xbfaa
ide_data_test: wrote 0x5555 read 0xffff
hda: HITACHI_DK227A-41, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xbfaa
ide_data_test: wrote 0x5555 read 0xdf55
hda: HITACHI_DK227A-41, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xdf55
hda: HITACHI_DK227A-41, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xdf55
hda: HITACHI_DK227A-41, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xbfaa
ide_data_test: wrote 0x5555 read 0xdf55
hda: HITACHI_DK227A-41, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: HITACHI_DK227A-41, 3909MB w/512kB Cache, CHS=7944/16/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman (erik@vt.edu)

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:28:0f:76
Partition check:
 hda: [PTBL] [993/128/63] hda1 < hda5 hda6 > hda2 hda3 hda4
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
EXT2-fs warning: checktime reached, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 4k initBuilder image
show_message("Builder image")
Setting up swapspace version 0, size = 16478208 bytes
Adding Swap: 16092k swap-space (priority -1)
Setting up swapspace version 0, size = 20639744 bytes
Adding Swap: 20156k swap-space (priority -2)
Tuning hda5
show_message("Tuning hda5")
tune2fs 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Setting maximal mount count to -1
Setting interval between check 0 seconds
Making hda4 filesysteshow_message("Making hda4 filesystem")
m
mke2fs 1.14, 9-Jan-1999 for EXT2 FS 0.5b, 95/08/09
ext2fs_check_if_mount: No such file or directory while determining whether /dev/hda4 is mounted.
Linux ext2 filesystem format
Filesystem label=
15360 inodes, 977760 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Block size=4096 (log=2)
Fragment size=4096 (log=2)
30 block groups
32768 blocks per group, 32768 fragments per group
512 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736,

Writing inode tables: done
Writing superblocks and filesystem accounting information: done
Tuning hda4
show_message("Tuning hda4")
tune2fs 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
Setting maximal mount count to -1
Setting interval between check 0 seconds
Mounting hda4
show_message("Mounting hda4")
Making directories
show_message("Making directories")
Remounting ro
show_message("Remounting ro")
hda4 completed
show_message("hda4 completed")
Zeroing hda3
show_message("Zeroing hda3")
/bin/cat: write error: No space left on device
Done!
show_message("Done!")
bash-2.01#


Now What! Scanning the faq and the archives like a mad man! Been out of music in the jeep with the empeg for a year since it broke at the grand canyon! Come back empeg i love you!
_________________________
Mark I + Mark IIa | Jeep 97 TJ
my current blog

Top
#352264 - 18/05/2012 14:04 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
Roger
carpal tunnel

Registered: 18/01/2000
Posts: 5572
Loc: London, UK
Originally Posted By: JeepBastard
Error 0xc0041002


See this.
_________________________
-- roger

Top
#352265 - 18/05/2012 16:23 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: Roger]
JeepBastard
enthusiast

Registered: 08/09/1999
Posts: 364
Loc: Brooklyn
Thanks roger! I'm going to check that! Maybe I can bring the 80GB online I got it working with a 4GB Hard Drive finally after hours of soldering, swapping, reading, pleading with the unit itself!



Its all awkward and the HD doesnt even have the holes to go on the shock mount properly. The cable is backwards and twisted in a weird way. It's a noisy little 4gb from a old thinkpad i had stuffed somewhere. I dont even know if I have the screws to mount the display board back and the shock mount plate properly.

I also have to rewire the amp in the jeep back sensing if the empeg is in. I have it straight wired now which I have to say almost started a fire in the car. Yow! Who knows if I can find the buttons, I do have some old transparent buttons that I never installed. Let's see what I can dig up before a 6pm meeting. I'd love to roar to the meeting re-energized with Empeg power!

Empeg i love you!


Edited by JeepBastard (18/05/2012 16:25)
_________________________
Mark I + Mark IIa | Jeep 97 TJ
my current blog

Top
#352267 - 18/05/2012 17:51 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
JeepBastard
enthusiast

Registered: 08/09/1999
Posts: 364
Loc: Brooklyn
Hey guys! thanks for taking the time to answer questions and check in. Looks like it's sealed up and still working! Mix and Match original and translucent buttons and slightly crooked VFD with a small HD.




4Gb is enough for a local trip eh?
(im driving across the country again - will have to get the 80GB up!)

Now to see if she fires up in the jeep with the amp.
_________________________
Mark I + Mark IIa | Jeep 97 TJ
my current blog

Top
#352271 - 18/05/2012 19:22 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
JeepBastard
enthusiast

Registered: 08/09/1999
Posts: 364
Loc: Brooklyn
One more for good measure! thanks guys again! Only two screws in the fascia, no handle, but music to ride by!

Lessons learned:
Try reversing your IDE cable and use the other end (also crimp and tape and glue if need me )
Wake Up Your Chips!
Also cleaned the motherboard with rubbing alcohol and a qtip , ewww , especially around IDE related headers and chips
Clean lens with professional lens cleaning stuff!
Dont solder without all the tools! (I did it by eye without magnification cuz in nuts)
2.01.hijacked worked for me from big disk builder (3 didnt work so well )

Have a good weekend!



Edited by JeepBastard (18/05/2012 19:23)
_________________________
Mark I + Mark IIa | Jeep 97 TJ
my current blog

Top
#352353 - 23/05/2012 22:20 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
Dviant
new poster

Registered: 14/01/2005
Posts: 38
Glad you made some progress there. Have you tried installing the 80 yet again?

Top
#368297 - 04/02/2017 16:59 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
Hey guys:

I bought a PATA KingFast SSD 64 GB drive that I formatted in a Windows OS and the drive works fine. Then I took the existing drive out of a working Mark2a (Rio Car) player and replaced it with this KingFast drive in the same working IDE cable position, installed the big disk builder v6 and got this same error, '"Bad pump response" occurred during stage 0x25' after a few minutes of no progress bar during the "selecting pump device" stage. I then made sure that the cable was properly seated on both ends and also tried with version 3 of the the big disk builder. I also tried building the disk in my original Mark2 player with the same results. I have 2 MyDigitalSSD 64 GB "Bullet Proof" series SSD drives of another brand working fine in 2 Mark2a players.

I suspect perhaps Mark Lord never programmed a pump device for this drive. What's the next step in troubleshooting? Adding a jumper? Switching to another cable position? Getting a log output? I can't connect to the COM1 port via telnet while the Big Disk Builder Wizard is flashing the player and searching to for the drive to format. So how do I get a log like JeepBastard did?

The drive with the issue is model KF2502MCS01. (Made in China: www.kfast.com.cn)

Top
#368300 - 04/02/2017 18:33 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
I'm pretty sure I have a Kingspec 64GB PATA SSD around here somewhere,
so I can try this locally if need be (when though.. later in the week perhaps).

But first thing to try, is wipe out the partition table on that drive. This can be done from any Linux machine thusly:

dd if=/dev/zero of=/dev/sdX bs=512 count=1

(replace /dev/sdX with the actual device node).

Cheers.

Top
#368301 - 04/02/2017 18:56 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Okay, found the Kingspec 64GB drive, and found an already-opened empeg to try it with. But the display nipple is busted off on that unit -- must've happened during The Move. Bummer.

Still, shouldn't need a working display, so now just got to rustle up a serial cable and a serial port to plug it into.

Top
#368302 - 04/02/2017 19:04 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
But is KingSpec the same guts as KingFast? (Different companies, I'm pretty sure).

Thanks, Mark!

Top
#368303 - 04/02/2017 19:15 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Probably exactly the same. smile

Top
#368304 - 04/02/2017 19:16 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Got serial port going, now I just need to remember what hex offset the download program expects. Anyone?

Top
#368305 - 04/02/2017 19:34 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: mlord]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Originally Posted By: mlord
Got serial port going, now I just need to remember what hex offset the download program expects. Anyone?


All right. I am totally stuck here without Tony's FAQ.
How does one apply a .upgrade file over serial from Linux?

I used to know how to do this!

EDIT: Or maybe not.
I think I always did disk initializations using the empeg tools
from a Win98SE VM. And that's how I'm doing this now too!
Good thing my main machine still has a physical (bus) serial port..
Win98SE isn't too bright about USB ports.




Edited by mlord (04/02/2017 20:03)

Top
#368306 - 04/02/2017 20:05 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Okay, bigdisk v6 ran perfectly first try.
And second try, too. smile

Player v3a11 now installed and working.
This is on an Empeg Mk2 (not RioCar) player.

???


Edited by mlord (04/02/2017 20:08)

Top
#368307 - 04/02/2017 20:26 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
Okay, so I plugged the disk into an IDE-to-USB adapter and plugged adapter into Windows 7 PC USB port. The disk was recognized by Windows. Then I started up my Oracle VituralBox VM running CENTOS 7 and connected the USB device into my VM. It said it couldn't mount /dev/sdb1 because it was an NTFS filesystem. I ran your command in a terminal and disconnected the USB device from VM at which point Windows connected to it and stated that the drive couldn't be used because it wasn't formatted so I know this command worked:

dd if=/dev/zero of=/dev/sdb1 bs=512 count=1

I plugged the drive back into my empeg, reloaded the Big Disk Builder v6 and the Wizard gave the same error message. frown

Is there an easy way to set up the disk from within my CENTOS VM or to clone a disk that already has my music collection on it from within the VM? Or what's the next step?

Top
#368308 - 04/02/2017 20:57 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Are you sure you have the cable right way around with the disk connected to the empeg?

Next step, is to capture/post a serial port trace of the builder running on the empeg. 115200 bps.

Top
#368309 - 04/02/2017 21:08 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Another way to do this, if you have another 64GB drive that is already prep'd for the empeg, is to connect both that drive and the new KingFast drive to a Linux machine, and just clone the existing drive to the Kingspec.

The slow easy way:

cat /dev/sdX > /dev/sdY

..taking care to determine the correct sdX sdY names for the two drives. No feedback given from the "easy way" (cat), but it will silently complete after an hour or 12. smile
I think I have nearly always used some variation of that rather than going through builder/download/sync hell. smile

There are other commands that give progress feedback (eg. "dd") if you want to figure out their more complex syntax.

EDIT: something like this (requires a very up-to-date Linux):

dd if=/dev/sdX of=/dev/sdY status=progress


Edited by mlord (04/02/2017 21:14)

Top
#368310 - 04/02/2017 21:27 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
Yes, I'm sure about having the cable connected the right way because the missing pin is on the bottom row just like on my working empeg drive. But how do I capture the serial port and get this trace while the wizard is using the COM port? Can you give me instructions or a link to instructions for this?

Thanks again, Mark!

Top
#368311 - 04/02/2017 21:57 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
The way the builder images work is, you flash them using the tools (eg. the "wizard"). Then, they run the next time you power cycle the empeg, no wizard required. Actually, not just the "next" time, but EVERY time from then on until you install an empeg software image over top of it.

So if you already have flashed the builder image, then just hook the serial port up to a decent comms program (eg. ckermit) and capture a session log with that. Power on the empeg once everything else is ready.


Edited by mlord (04/02/2017 21:58)

Top
#368312 - 04/02/2017 22:54 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
Okay, I got the log:

empeg-car bootstrap v1.02 20001106 (hugo@empeg.com)
If there is anyone present who wants to upgrade the flash, let them speak now,
or forever hold their peace...it seems not. Let fly the Penguins of Linux!

e000 v1.04
Copying kernel...
Calling linux kernel...
Uncompressing Linux..................................... done, booting the kerne l.
Linux version 2.2.17-rmk5-np17-empeg55-hijack-v508 (hijack@rtr.ca) (gcc version 2.95.3 20010315 (release)) #2 Fri Jan 9 16:06:35 EST 2009
Processor: Intel StrongARM-1100 revision 11
Checking for extra DRAM:
c1000000: wrote ffffffff, read e28cc001
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 40104349) 16MB DRAM
Command line: mem=16m
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15000k/16M available (996k code, 20k reserved, 364k data, 4k init)
Dentry hash table entries: 2048 (order 2, 16k)
Buffer cache hash table entries: 16384 (order 4, 64k)
Page cache hash table entries: 4096 (order 2, 16k)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.2
Based upon Swansea University Computer Society NET3.039
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
TCP: Hash tables configured (ehash 16384 bhash 16384)
IrDA (tm) Protocols for Linux-2.2 (Dag Brattli)
Starting kswapd v 1.5
SA1100 serial driver version 4.27 with no serial options enabled
ttyS00 at 0xf8010000 (irq = 15) is a SA1100 UART
ttyS01 at 0xf8050000 (irq = 17) is a SA1100 UART
ttyS02 at 0xf8030000 (irq = 16) is a SA1100 UART
Signature is 206f6972 'rio '
Tuner: loopback=0, ID=-1
show_message("Hijack v508 by Mark Lord")
empeg display initialised.
empeg dsp audio initialised
empeg dsp mixer initialised
empeg dsp initialised
empeg audio-in initialised, CS4231A revision a0
empeg remote control/panel button initialised.
empeg usb initialised, PDIUSBD12 id 1012
empeg state support initialised 0089/88c1 (save to d0005780).
empeg RDS driver initialised
empeg power-pic driver initialised (first boot)
RAM disk driver initialized: 16 RAM disks of 4096K size
empeg single channel IDE
Probing primary interface...
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0x7f55
hdb: KingFast, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xffff
hdb: KingFast, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0x7f55
hdb: KingFast, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0x7f55
hdb: KingFast, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0xffff
hdb: KingFast, ATA DISK drive
ide_data_test: wrote 0x0000 read 0xffff
ide_data_test: wrote 0xffff read 0xffff
ide_data_test: wrote 0xaaaa read 0xffaa
ide_data_test: wrote 0x5555 read 0x7f55
hdb: KingFast, ATA DISK drive
ide0: unexpected interrupt, status=0xff, count=1
ide0 at 0x000-0x007,0x038 on irq 6
hdb: KingFast, 60416MB w/1kB Cache, CHS=7701/255/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman (erik@vt.edu)

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:28:10:fd
Partition check:
hdb: hdb1
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 320 blocks [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
empeg-pump v0.03 (19980601)
Press Ctrl-A to enter pump...VFS: Cannot open root device 03:05
Kernel panic: VFS: Unable to mount root fs on 03:05

Top
#368313 - 05/02/2017 14:12 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Your SSD is configured as a "slave" drive.
It must instead be set up as a "master".
There should be a jumper for that on the drive.

Top
#368314 - 05/02/2017 14:14 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
Hollywood Justin
journeyman

Registered: 02/04/2005
Posts: 58
Ah! I was considering trying the jumper.

Thanks so much!

Top
#368315 - 05/02/2017 14:15 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
Yes, the arcane world of IDE strikes again!

So just add the jumper to the right pins, and power it up again. No need to "re-install" the builder.

Top
#368316 - 05/02/2017 14:22 Re: Big Disk Builder Error "Bad pump response" stage 0x25 w new ide Drive [Re: JeepBastard]
mlord
carpal tunnel

Registered: 29/08/2000
Posts: 13874
Loc: Canada
The builder will complete its job quite rapidly here. No more than a minute or three in all. Maybe also post the serial log from that here too.

Next step after it completes successfully, is to then flash the .upgrade file for the appropriate car2-developer image.

Top
Page 1 of 2 1 2 >