I agree, and I found the same data repeat problem using the continuous code, it does not look like a data loss. I do a 3.6 kHz sampling rate and observed that every 7 samples, I can see the value of two adjacent samples are very close to each other (see the figure below). Anyway, would you mind sharing your code with us to solve the problem? Thanks very much in advance.
<https://lh3.googleusercontent.com/-Kw-RtfwwF5E/Wbrt6ZXJx2I/AAAAAAAABBo/2xsS0jX8xkIwUrFEOT7R9y4D3wPcZqOxACLcBGAs/s1600/figure.PNG> On Tuesday, May 26, 2015 at 9:39:38 AM UTC-4, [email protected] wrote: > > I was wrong about the number 1, actually after some experiments I noticed > that I'm still losing samples, even after setting the ACK_CLKDIV to > something that divides the 24MHz by 3. Anyway it is useful to know that you > can obtain higher sample rates by setting a lower value to that register. > > I'd also like to add that the continuous mode that you set on the step > config seems not good. I noticed it after sampling higher frequency waves, > however even on low frequency ones there's a noticeable step on the > sampling: every 14-15 samples had approximately the same value... I solved > that by setting STEPCONFIG it to the default one-shot mode and then the PRU > request a sample when it thinks it's time to. To request a sample, re-set > the bit on the STEPENABLE register. > > My last step is to discover how to solve the lost samples problem... > When I'm sampling at 300kSps I noticed I lose 358 samples every 5005 > samples. At 30kSps the proportion was 5 to 500. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/75de1e0b-a477-46dc-b47f-addba90f3f5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
