Quote:
I plan on compling an arm app to run on the player. How do I add it to the start up script? (e.g. rcS)

Quote:

I plan on sending the <a href="hxxp://empeg/?NODATA&SERIAL=%23FID%2b" target="_blank">hxxp://empeg/?NODATA&SERIAL=%23FID%2b</a> command to quenue songs. Is there and easier way? I would prefer just to dump the command to a /proc file

Quote:

I can use empeg_notify to determine the state of the player. But is there and easier way to find out if the empeg has finished the playlist?

Quote:

Can I use the tuner serial port to receive seeburg commands?

Quote:

Quote:

Can I use the tuner serial port to receive seeburg commands?

Possibly. But I think there's actually a *third* serial port on that connector(?) also. Use it instead

Quote:

Quote:
I plan on sending the <a href="hxxp://empeg/?NODATA&SERIAL=%23FID%2b" target="_blank">hxxp://empeg/?NODATA&SERIAL=%23FID%2b</a> command to quenue songs. Is there and easier way? I would prefer just to dump the command to a /proc file

I think the same thing is doable as follows, or something very close to this:

echo 'SERIAL=#FID+' >/proc/empeg_notify

Quote:

Quote:

I can use empeg_notify to determine the state of the player. But is there and easier way to find out if the empeg has finished the playlist?

Define, programmatically, "finished the playlist". Note that the empeg merely pauses at the end of a playlist. Pressing "Play" starts it up again. You could screen scrape the "end of playlist" message, though.

Quote:

Mmmm... Pin-7 at the tuner connector is an (unused) I2S signal line. Which means it's a serial line of some kind. I dunno where it terminates on the mainboard, though.

Quote:

The problem is that if you send #FID+ to a player that is at the end of the playlist, it will not play. You'd need to send <space>. but then the player will replay the whole playlist with the added song at the end. For "jukebox" like opperation, you need to perform the following test:

read empeg_notify:
if notify_FidTime = "0:00:00"; // empeg might be starting a new tune/playlist or paused
wait 2 seconds and read empeg_notify again
if notify_FidTime = "0:00:00"; // empeg is paused
send #NewFID
else (from first if) ;// empeg is playing
send #NewFID+

The above logic should work fine, but It has to wait at least one second to see if the player is paused.

Quote:

Quote:

Mmmm... Pin-7 at the tuner connector is an (unused) I2S signal line. Which means it's a serial line of some kind. I dunno where it terminates on the mainboard, though.

I don't think I can use pin-7 because I2S is a serial audio bus format (the format CD players send to the D/A converter). It probably terminates in the DSP. Does your kernel support/initialize three uarts?

Quote:
I'm trying to interface a seeburg walllbox http://tomszone.com/3W1.html into an empeg.

Quote:

Absolutely brilliant idea. Wow. Since the keypad has letters A-F, you could even just do four-digit FIDs directly... was that your plan?

Quote:
recieves the button press "G3". the app looks up the 73rd FID entry in the playlist.

Quote:
However, the ideal way to do it (and save $99) would be to find a single GPIO input pin that the app could read. The app would listen for the pulses and count them to determine the buttons pressed. Any suggestions as to what gpio to use? (e.g one that I can read from user space)

I seem to recall that the PCA version of the tuner module deliberately included some general purpose I/O lines that you might be able to mess with. If you happened to have one of those. If not, then you're not really saving the 99.00 because then you'd have to buy a PCA tuner.

Quote:

However, the ideal way to do it (and save $99) would be to find a single GPIO input pin that the app could read. The app would listen for the pulses and count them to determine the buttons pressed. Any suggestions as to what gpio to use? (e.g one that I can read from user space)

Quote:

Quote:

However, the ideal way to do it (and save $99) would be to find a single GPIO input pin that the app could read. The app would listen for the pulses and count them to determine the buttons pressed. Any suggestions as to what gpio to use? (e.g one that I can read from user space)

There are several GPIO lines attached to the rear-panel DB-9 connector (serial port). The "headlight sense" line is a good candidate, as it is not normally used for anything when operating on AC power.

That's serial port pin-8 (CTS).

Quote:

Quote:

Quote:

However, the ideal way to do it (and save $99) would be to find a single GPIO input pin that the app could read. The app would listen for the pulses and count them to determine the buttons pressed. Any suggestions as to what gpio to use? (e.g one that I can read from user space)

There are several GPIO lines attached to the rear-panel DB-9 connector (serial port). The "headlight sense" line is a good candidate, as it is not normally used for anything when operating on AC power.

That's serial port pin-8 (CTS).

Great! I assume that there is no memory manager on the empeg. So I should be able to read it from a Volatile char pointer right? What's the address & Bit #?

Another question, for a "hello world" app, What are the correct gcc-arm-linux flags to generate a statically linked app?

The empeg uses Linux as the O/S, which is a protected memory operating system. So, yes, it has a memory manager.

Use the source.

Cheers

Quote:

Another question, for a "hello world" app, What are the correct gcc-arm-linux flags to generate a statically linked app?

Quote:

Quote:

Another question, for a "hello world" app, What are the correct gcc-arm-linux flags to generate a statically linked app?

arm-empeg-linux-gcc object1.o object2.o -Wl,-Bstatic $(STATIC_LIBS) -Wl,-Bdynamic $(DYNAMIC_LIBS) -o $@

Quote:

I generally just do: arm-empeg-linux-gcc -static file.c

Cheers

Quote:

w.r.t building the kernel, I noticed in menuconfig that loadable module support is not enabled. Does the Hijack kernel support loadable modules? Can I just turn it on and recomple the kernel? When I build a new kernel, can I boot it without burning it to flash? If I have to burn it to flash, what's the de-brick proceedure?

ssize_t
seeburg_read (struct file * filep, char *buff, size_t count, loff_t * offp)
{
  /* function to copy kernel space buffer to user space */
  if (samples_collected == MAX_SAMPLES && tick_tock==0)
    {
      if (copy_to_user (buff, pulse_samples, sizeof (pulse_samples)) != 0)
        {
          printk ("Kernel -> userspace copy failed!\n");
        }
      printk ("samples collected %d\n", samples_collected);
      samples_collected == 0;
      tick_tock = 1;
      return sizeof (pulse_samples);
    }
  return 0;
}

Quote:
What is the correct way to block (wait for input) in a device?

The interrupt routine increments "samples_collected", but the driver needs to wait until 256 samples have been collected.

Is there some sort of kernel mutex I set in the interrupt routine and wait on in the driver?

struct semaphore mysem = MUTEX_LOCKED;

...

// Interrupt handler:

    if (++count == desired_number)
       up(&mysem);  /* signal that data is available */

...

// mainline driver's read() or ioctl() routines:
   ...
   down(&mysem);  /* wait for data */
   ...

Quote:
There are other ways, but one of the simplest is to use a semaphore:

empeg:/empeg/bin# /wallbox 1ad0 &

seeburg open: state 1
Read 100 items from playlist 1ad0
.
empeg:/empeg/bin# player
Timezone: PRC
Hijack: intercepting config.ini
  player.cpp        : 385:empeg-car 2.00-beta13 2002/07/24.
Prolux 4 empeg car - 2.1434 Jul 24 2002
Vcb: 0x4086d000
.
Selection E3 is fid 2a0
#2a0
.
Selection H6 is fid 2b70
#2b70+
.
Selection K6 is fid 690
#690+
.
Selection J9 is fid 45a0
#45a0+

Quote:
Yes, this is a great project! I want to see a video of this in action!

This is a demonstration of a program I wrote to interface a
Seebug 3W-100 wallbox to an empeg mp3 player. Below is
the text that was on the computer screen.  It shows the
wallbox app startup and the button selections.
.
empeg:/empeg/bin# /wallbox &
[1] 147
empeg:/empeg/bin#
seeburg open: state 1
Read 100 items from playlist a7d0
.
empeg:/empeg/bin# player
Timezone: PRC
Hijack: intercepting config.ini
.
  player.cpp        : 385:empeg-car 2.00-beta13 2002/07/24.
Prolux 4 empeg car - 2.1434 Jul 24 2002
Vcb: 0x4086d000
.
.
samples collected 256
state is 4
empeg_sound is 0
.
.
Selection F10 is fid 31f0
#31f0
samples collected 256
state is 4
empeg_sound is 1
.
.
Selection C4 is fid 2a70
#2a70+
 

Quote:
As requested, here's a link to the demo of my seeburg wallbox interface.