search for: pxa250

...works fine. I think the iPAQ 3600 (ARM SA 1110, I think this is a 200mhz cpu), is a bit slow for encoding in realtime. The Speex encode function takes 30+ ms to encode one 20ms sample frame in a debug build. I didn't try the release build with compiler optimization. The iPAQ 3970 (PXA250, I think this is a 400mhz cpu?) is just fast enough for realtime encoding - the Speex encode function takes 20+ ms to encode one 20ms sample frame without compiler optimizations, but with compiler optimizations and tracing removed, only on occaisional tests did I notice gaps in the stream....

...hat consists of some "data collector" code running on the XScale target, and a windows host application that collects the data from the target and displays it graphically, etc. http://www.intel.com/software/products/vtune/xscale/vtunex_oview.htm But the web site says it targets the DBPXA250 development board (containing a PXA250) running one of the several Windows CE variants, so it might not be useful to you. Plus they charge for it. I've never used this tool, but I have used a VTune version for profiling Pentium code. It's pretty good, quickly highlighting the performa...

...n eVC 3. It works fine. I think the iPAQ 3600 (ARM SA 1110, I think this is a 200mhz cpu), is a bit slow for encoding in realtime. The Speex encode function takes 30+ ms to encode one 20ms sample frame in a debug build. I didn't try the release build with compiler optimization. The iPAQ 3970 (PXA250, I think this is a 400mhz cpu?) is just fast enough for realtime encoding - the Speex encode function takes 20+ ms to encode one 20ms sample frame without compiler optimizations, but with compiler optimizations and tracing removed, only on occaisional tests did I notice gaps in the stream. My exp...

> > $ qemu-arm -cpu ? > > Available CPUs: > > arm926 arm946 arm1026 arm1136 arm1136-r2 arm1176 arm11mpcore > > cortex-m3 > > cortex-a8 > > cortex-a8-r2 cortex-a9 cortex-a15 ti925t pxa250 sa1100 sa1110 > pxa255 pxa260 > > pxa261 pxa262 pxa270 pxa270-a0 pxa270-a1 pxa270-b0 pxa270-b1 xa270- > c0 > > pxa270-c5 any > > > > Still your procedure will work, just by using the m3 instead :-). > Yeah, that should work for the most part, unless you emit t...

On 12/16/14 3:53 AM, Kristof Beyls wrote: > I've been wondering too about how to get better ARM v6m compile-and-execute > testing going. > > As you say Jon, the non-execution-based regression tests are surprisingly > good at catching issues; but they're no full substitute for executing the > code produced by the backend for a reasonably-sized test suite. > > If

Jean-Marc Valin wrote: > At this point, if you want to help, the best way would probably to try > tracking done what part of the code is responsible for the high system. > Once this is identified, we'll have a much better idea. > > I managed to log on the XSCALE 400 on handhelds.org. It helped, but I > can't do everything with it (and by attempts at profiling failed). I