Thread: Accessory port
View Single Post
Old 07-29-2012, 06:29 PM   #10
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by mmatej View Post
Yup, maybe delays are bad. But what are that ticks? Tomorrow I'll try to connect it to speakers with amplifier to check if there are more voices. Somebody should probably connect the Kindle to the oscilloscope to check that too.
Noise on the accessory port is probably caused by voltage fluctuations due to varying load during wifi or 3G transmission (which draws a lot of power), during eink updates, and during other power-hungry events. For PWM output that could be clipped with a resistor and a pair of back-to-back diodes (or LEDs). The ticks might actually be your output. You can time how fast your code runs to see if it matches the tick rate. Like I said, it can take a long time to return from the echo statements, depending on how the device driver handles that sysfs (proc) interface to the accessory port.
geekmaster is offline   Reply With Quote