The other day I was testing out a new mp3 encoder and I put one of the test files on my Rio Car. When I tried to play the file in the car the player refused to play the file and stopped responding to all input. The display indicates that it is on the track but it does not play, it just sits there and does nothing. After a few minutes it seems to go through what looks like something of a partial reboot or something and then right back to the nonworking file. I tried to connect to the player via emplode both on a serial and USB but emplode will not see the player. I was able to connect using my other player so I think that I'm doing everything correct there. I was able to upgrade the software but that did not help. I was able to connect with hyperterminal and I have pasted the output of that below, looking at the terminal output it seems that the player is in some sort of loop. I suspect that if I were to remove that file, or at least be able to keep the player from going right to it after it boots all would be fine, but I'm no Linux expert and I'm not really sure what to do. Any help would be greatly appreciated.

Thanks in advance

Here is what I copied over from hyperterminal:


empeg-car bootstrap v1.02 20001106 ([email protected])
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.03
Copying kernel...
Calling linux kernel...
Uncompressing Linux................................... done, booting the kernel.

Linux version 2.2.14-rmk5-np17-empeg43 ([email protected]) (gcc versi
on 2.95.2 19991024 (release)) #214 Sat Jun 23 16:38:57 BST 2001
Processor: Intel StrongARM-1100 revision 11
NetWinder Floating Point Emulator V0.94.1 (c) 1998 Corel Computer Corp.
empeg-car player (hardware revision 9, serial number 40103310)
Command line: mem=16m temp=33
Calibrating delay loop... 207.67 BogoMIPS
Memory: 15064k/16M available (960k code, 20k reserved, 332k data, 8k 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)
Linux-IrDA: IrCOMM protocol ( revision:Tue May 18 03:11:39 1999 )
ircomm_tty: virtual tty driver for IrCOMM ( revision:Wed May 26 00:49:11 1999 )
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 '
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 d0005480).
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...
hda: FUJITSU MHM2200AT, ATA DISK drive
hda: FUJITSU MHM2200AT, ATA DISK drive
hda: FUJITSU MHM2200AT, ATA DISK drive
hda: FUJITSU MHM2200AT, ATA DISK drive
hda: FUJITSU MHM2200AT, ATA DISK drive
hda: FUJITSU MHM2200AT, ATA DISK drive
ide0 at 0x000-0x007,0x038 on irq 6
hda: FUJITSU MHM2200AT, 19077MB w/2048kB Cache, CHS=38760/16/63
empeg-flash driver initialized
smc chip id/revision 0x3349
smc9194.c:v0.12 03/06/96 by Erik Stahlman ([email protected])

SMC9194: SMC91C94(r:9) at 0x4008000 IRQ:7 INTF:TP MEM:6144b MAC 00:02:d7:28:0c:e
e
Partition check:
hda: hda1 < hda5 hda6 > hda2 hda3 hda4
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: Mounted root (ext2 filesystem) readonly.
change_root: old root has d_count=1
Trying to unmount old root ... okay
Freeing unused kernel memory: 8k initempeg-car 1.03.
00c2f37b DHCP Our mac is 00:02:d7:28:0c:ee
00c2f37b DHCP Our address is 255.255.255.255
00c2f37b DHCP Broadcast address is 255.255.255.255
00c2f37b DHCP Current IP address is 255.255.255.255
00c2f37b DHCP Sending DHCP discover
00c2f37c DHCP Sending DHCP discover
Shell exit
empeg-car 1.03.
00c2f395 DHCP Our mac is 00:02:d7:28:0c:ee
00c2f395 DHCP Our address is 255.255.255.255
00c2f395 DHCP Broadcast address is 255.255.255.255
00c2f395 DHCP Current IP address is 255.255.255.255
00c2f395 DHCP Sending DHCP discover
Switching to shell-player loop
Shell exit
empeg-car 1.03.
00c2f3ad DHCP Our mac is 00:02:d7:28:0c:ee
00c2f3ad DHCP Our address is 255.255.255.255
00c2f3ad DHCP Broadcast address is 255.255.255.255
00c2f3ad DHCP Current IP address is 255.255.255.255
00c2f3ad DHCP Sending DHCP discover

Check out the thread with this post that shows how to clear the current state.

/Michael

This is a FAQ Entry.

Bam.

After you get it working again, check and see if the file also fails on version 2.0 software (I see you are running version 1.03). If the file also fails on version 2.0, you might want to hang on to it in case the empeg guys want to see it. They would like to make sure their new decoding engine doesn't crash on otherwise-good files.

Sweet! It works! Thanks for the help guys. Sorry I didnt see it in the FAQ, I thought that I had read it all but I guess that I over looked it.

BTW the file does indeed work in 2.0

In reply to:

---

They would like to make sure their new decoding engine doesn't crash on otherwise-good files.

---

I would love a new, less finicky decoding engine. I have several files that play fine in everything else but my RioCar.

Stu

Well, if you're running 2.0, then you already have the new, less finicky decoding engine.

The files that won't play... Have you checked them out using these tools? Are the files actually good files?

Yes, I am running 2.0b11, but I have not tried the tools. I guess I just thought that if the files played without incident on other software that the same could be said for my Rio. I will run the offending files through the tools referenced in the FAQ. Thanks.

Stu