OK, so now, I seem to be having issues with the FIFO. Not sure what it is, but I have to tone down my experimentation a bit as I've got other things that are of a higher priority. Such is life, but I'm by no means *done* with this.
On Wed, Oct 7, 2015 at 11:42 AM, William Hermans <[email protected]> wrote: > > http://processors.wiki.ti.com/index.php/Linux_Core_ADC_User's_Guide#How_to_set_it_up > > File path is mentioned here. Towards the end. Read everything, not just > the command line examples. > > On Tue, Oct 6, 2015 at 11:47 PM, Rathin Dholakia <[email protected] > > wrote: > >> Hi, >> >> So during this implementation you are using FIFO buffer that you pointed >> out?? should I as well use that?? or should I simply read from >> "/sys/bus/iio/devices/iio\:device0/in_voltage4_raw" ..? >> >> >> On Wednesday, October 7, 2015 at 7:40:46 AM UTC+5:30, William Hermans >> wrote: >>> >>> By the way, there are 2 FIFO buffers for the ADC. I'm only reading from >>> one. So this is something else I need to look into. Actually there is a lot >>> I need to read up now that I'm able to directly twiddle the ADC's registers. >>> >>> On Tue, Oct 6, 2015 at 7:02 PM, William Hermans <[email protected]> >>> wrote: >>> >>>> To screen: >>>> 2000000 total iterations >>>> channel 0 samples: 296296 >>>> channel 1 samples: 444444 >>>> channel 2 samples: 296296 >>>> channel 3 samples: 370371 >>>> channel 4 samples: 148149 >>>> channel 5 samples: 222222 >>>> channel 6 samples: 222222 >>>> real 0m16.247s >>>> user 0m3.850s >>>> sys 0m3.140s >>>> >>>> To file: >>>> 2000000 total iterations >>>> channel 0 samples: 296296 >>>> channel 1 samples: 444445 >>>> channel 2 samples: 296296 >>>> channel 3 samples: 370370 >>>> channel 4 samples: 148148 >>>> channel 5 samples: 222222 >>>> channel 6 samples: 222223 >>>> real 0m5.768s >>>> user 0m3.650s >>>> sys 0m0.090s >>>> >>>> How does ~25684 Samples a second worst case, per channel sound ? >>>> Channel 4 there is looking a bit weak. I need to investigate that. Who said >>>> 20k samples / second per channel from the Linux side was not possible ? >>>> Also, since ssh is eating half the CPU while using printf(), those numbers >>>> can be improved. 13.5M in 5 seconds though . . . not too shabby. >>>> >>>> >>>> >>>> >>>> On Tue, Oct 6, 2015 at 3:41 PM, William Hermans <[email protected]> >>>> wrote: >>>> >>>>> Couldn't step away until I did this test but . . . >>>>> >>>>> debian@beaglebone:~$ time sudo ./test > output.txt >>>>> >>>>> real 0m1.059s >>>>> user 0m0.370s >>>>> sys 0m0.030s >>>>> >>>>> Data is formated as such: *channel:data* That's 200k iterations( >>>>> nearing 200k samples / second !!!) with A LOT of data that looks like >>>>> this: >>>>> >>>>> 0:3731 2:3157 0:2115 6:3248 1:0520 0:3619 2:1464 4:0796 3:0872 6:2609 >>>>> 1:0831 6:3612 2:0141 1:3921 3:1488 0:0243 5:2981 3:1685 2:1118 5:0523 >>>>> 1:3068 5:2318 4:0123 3:0532 3:3336 1:1599 1:2541 0:3731 2:3157 0:2115 >>>>> 6:3248 1:0520 0:3619 2:1464 4:0796 3:0872 6:2609 1:0831 6:3612 2:0141 >>>>> 1:3921 3:1488 0:0243 5:2981 3:1685 2:1118 5:0523 1:3068 5:2318 4:0123 >>>>> 3:0532 3:3336 1:1599 1:2541 0:3731 2:3157 0:2115 6:3248 1:0520 0:3619 >>>>> 2:1464 4:0796 3:0872 6:2609 1:0831 6:3612 2:0141 1:3921 3:1488 0:0243 >>>>> 5:2981 3:1685 2:1118 5:0523 1:3068 5:2318 4:0123 3:0532 3:3336 1:1599 >>>>> 1:2541 0:3731 2:3157 0:2115 6:3248 1:0520 0:3619 2:1464 4:0796 3:0872 >>>>> 6:2609 1:0831 6:3612 2:0141 1:3921 3:1488 0:0243 5:2981 3:1685 2:1118 >>>>> 5:0523 1:3068 5:2318 4:0123 3:0532 3:3336 1:1599 1:2541 0:3731 2:3157 >>>>> 0:2115 6:3248 1:0520 0:3619 2:1464 4:0796 3:0872 6:2609 1:0831 6:3612 >>>>> 2:0141 1:3921 3:1488 0:0243 5:2981 3:1685 2:1118 5:0523 1:3068 5:2318 >>>>> 4:0123 3:0532 3:3336 1:1599 1:2541 0:3731 2:3157 0:2115 6:3248 1:0520 >>>>> 0:3619 2:1464 4:0796 3:0872 6:2609 1:0831 6:3612 2:0141 1:3921 3:1488 >>>>> 0:0243 5:2981 3:1685 2:1118 5:0523 1:3068 5:2318 4:0123 3:0532 3:3336 >>>>> 1:1599 1:2541 0:3731 2:3157 0:2115 6:3248 1:0520 0:3619 2:1464 4:0796 >>>>> 3:0872 6:2609 1:0831 6:3612 2:0141 1:3921 3:1488 0:0243 5:2981 3:1685 >>>>> 2:1118 5:0523 1:3068 5:2318 4:0123 3:0532 3:3336 1:1599 1:2541 0:3731 >>>>> 2:3157 0:2115 6:3248 1:0520 0:3619 2:1464 4:0796 3:0872 6:2609 1:0831 >>>>> 6:3612 2:0141 1:3921 3:1488 0:0243 5:2981 3:1685 2:1118 5:0523 1:3068 >>>>> 5:2318 4:0123 3:0532 3:3336 1:1599 1:2541 0:3731 2:3157 0:2115 6:3248 >>>>> 1:0520 0:3619 2:1464 4:0796 3:0872 6:2609 1:0831 6:3612 2:0141 1:3921 >>>>> 3:1488 0:0243 5:2981 3:1685 2:1118 5:0523 1:3068 5:2318 4:0123 3:0532 >>>>> 3:3336 1:1599 1:2541 0:3731 2:3157 0:2115 6:3248 1:0520 0:3619 2:1464 >>>>> 4:0796 3:0872 6:2609 1:0831 6:3612 2:0141 1:3921 3:1488 0:0243 5:2981 >>>>> 3:1685 2:1118 5:0523 1:3068 5:2318 4:0123 3:0532 3:3336 1:1599 1:2541 >>>>> 0:3731 2:3157 0:2115 6:3248 1:0520 0:3619 2:1464 4:0796 3:0872 6:2609 >>>>> 1:0831 6:3612 2:0141 1:3921 3:1488 0:0243 5:2981 3:1685 2:1118 5:0523 >>>>> 1:3068 5:2318 4:0123 3:0532 3:3336 1:1599 1:2541 0:3731 2:3157 0:2115 >>>>> 6:3248 1:0520 0:3619 2:1464 4:0796 3:0872 6:2609 1:0831 6:3612 2:0141 >>>>> 1:3921 3:1488 0:0243 5:2981 3:1685 2:1118 5:0523 1:3068 5:2318 4:0123 >>>>> 3:0532 3:3336 1:1599 1:2541 0:3731 2:3157 0:2115 6:3248 1:0520 0:3619 >>>>> 2:1464 4:0796 3:0872 6:2609 1:0831 6:3612 2:0141 1:3921 3:1488 0:0243 >>>>> 5:2981 3:1685 2:1118 5:0523 1:3068 5:2318 4:0123 3:0532 3:3336 1:1599 >>>>> . . . >>>>> >>>>> Now I *am* off for a break. >>>>> >>>>> >>>> >>> -- >> 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]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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]. For more options, visit https://groups.google.com/d/optout.
