Of course, I'm aware of the performance issues, but I need to do his for
debugging on my tungsten.
I have various printf's in my ARM code from the callback that are translated
to FrmCustomAlert calls in 68K. Do you know any other way of debugging ARM
code from the callback?
Currently, the ARM callback calls functions to decode MPEG layer 3 audio,
PCM, etc.
I think a better idea would be to decode the MP3 data in the main
application thread and feed it to a FIFO that the callback then reads. like
this:
PRODUCER ______________________
CONSUMER
(main application thread) -----> | FIFO
| ---> callback reads
decode MP3 |______________________|
data from FIFO
feed data to FIFO
The CONSUMER/PRODUCER could be synchronized using a semaphore.
This way I should normaly be able to debug the MP3 decoding properly, and
the ARM callback would be very simple.
Of course it would be simpler to do the decoding of MP3 directly from the
callback.
But do you know how to print messages from such an ARM callback?
David
"Carsten" <[EMAIL PROTECTED]> wrote in message
news:111740@palm-dev-forum...
>
> David Janssens wrote:
>
> > Hello,
> >
> > I wrote an ARM callback that gets called when sampled sound is played.
> >
> > Does anyone know if it's possible to call 68k code from this callback?
> > (unlike ARM routines called using PceNativeCall, no emulState or
callback68k
> > parameters are passed when the sampled sound callback is called)
> >
> > David
>
> Do you REALLY want to drop the performance ?? ;)
>
> How about callback=68K, then you may use 68K code plus ARM code
(pcenative)
> (haven't tried this one yet, but theoretically it should work - although
> I don't see any sense doing so)
> BUT keep the performance thing in mind ! :)
>
>
> Regards,
> Carsten.
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
