Audio (video) - Kindle. Getting it up and running, Code level.

[twobob]

THIS PAGE CONTAINS A COPY OF STRACE FOR THE KINDLE 3. AND MAINLY DETAILS ABOUT A NOW FIXED BUG. *** SKIP TO NEXT PAGE FOR MORE AUDIO DETAILS ***

================================================== ==========
Threads continue:

I think a copy of lmixer would be a good idea.
http://caspian.dotconf.net/menu/Software/Lmixer/

True it's possibly replacing existing functionality, but in a tiny and tidy way when we absolutely must set something somewhere in a quick and tidy way.

It's light and simple. implemented in c++.


Hands up for that one.

[knc1]

If you can find a: lmixer -c redink bold
then you will make GM happy.

[PoP]

K3 WiFi, firmware 3.3. @twobob, would have a suggestion on how to address my problem?

[root@kindle us]# ./sine
Playback device is plughw:0,0
Stream parameters are 44100Hz, S16_LE, 1 channels
Sine wave rate is 440.0000Hz
Using transfer method: write
ALSA lib conf.c:3700:(snd_config_update_r) Cannot access file /home/simon/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/share/alsa/alsa.conf
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM plughw:0,0
Playback open error: No such file or directory
[root@kindle us]#

Also, same error in microphone:

[root@kindle us]# aplay -D dmix0 ImNotReal.wav;\
> ./microphone -d hw:0 -f cd -r 44100 | aplay -f cd -D hw:0 -r 44100
ImNotReal.wav: No such file or directory
./microphone: invalid option -- 'f'
ALSA lib conf.c:3700:(snd_config_update_r) Cannot access file /home/simon/CodeSourcery/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/share/alsa/alsa.conf
ALSA lib pcm.c:2217:(snd_pcm_open_noupdate) Unknown PCM hw:0
microphone: Device cannot be opened  -d (No such file or directory)
aplay: playback:2021: read error

[twobob]

Originally Posted by PoP

K3 WiFi, firmware 3.3. @twobob, would have a suggestion on how to address my problem?
[CODE][root@kindle us]# ./sine
Cannot access file /BLAH

Also, same error in microphone:

[root@kindle us]# aplay -D dmix0 ImNotReal.wav;\
> ./microphone -d hw:0 -f cd -r 44100 | aplay -f cd -D hw:0 -r 44100
ImNotReal.wav: No such file or directory
Cannot access file /BLAH

AH! Thanks very much. Looks like I must have fluffed the Alsalib build, I will sort that out now! My apologies. The file is actually in /usr/share/alsa/alsa.conf. EDIT: This is now fixed

Thanks for letting me know I have a problem.
Apologes for the foobar.

[geekmaster]

Originally Posted by twobob

It plays a simple sine wave to our speaker - pretty dull huh?
But it paves the wave for all kind of coolness so here's the blurb ...

Okay, if I replace the sine function with a square function (x*x), would it then output a square wave instead of a sine wave?

Seriously, it is time to add some K5 touchscreen code to make a touch stylophone.

BTW, I think that I use more than other icons.

[knc1]

Originally Posted by geekmaster

Okay, if I replace the sine function with a square function (x*x), would it then output a square wave instead of a sine wave?

You can make any .wav file for play-back (including a square wave) with LTspice (or any SPICE-3 program) with the .wave directive, as in:
.wave "path\to\outputfile.wav" 16 44100 NODE
Where "NODE" is the point in the circuit you want to record voltage changes as the content of the .wav file.

Combine being able to play whatever is generated by any sort of circuit with being able to define your own zero distortion (ideal) components ..
Mind boggling possibilities.

I posted the Custom Component HowTo yesterday:
http://knetconnect.com/ltspice/CustomComponents.html
That and other useful links can be found in the top post of the "Kindle Charger" thread.

[geekmaster]

Originally Posted by knc1

You can make any .wav file for play-back (including a square wave) with LTspice (or any SPICE-3 program) with the .wave directive, as in:
.wave "path\to\outputfile.wav" 16 44100 NODE
Where "NODE" is the point in the circuit you want to record voltage changes as the content of the .wav file.

Combine being able to play whatever is generated by any sort of circuit with being able to define your own zero distortion (ideal) components ..
Mind boggling possibilities.

I posted the Custom Component HowTo yesterday:
http://knetconnect.com/ltspice/CustomComponents.html
That and other useful links can be found in the top post of the "Kindle Charger" thread.

That is interesting, but I am sure you realized my "square wave" comment was meant as a joke, right?

[twobob]

Okay maybe it's just me but getting strace to build and run is a Pain In The -brain-

So to this end here is an strace that is statically built against the Kindle 3 Arm6 in SB2

This one works on mine - the previous "strace" I cited -
Suffered from a known bug and wouldn't play at debugging some bins.

I have included the 4.7 here
(mainly since it was such a pain to build, although not too bad once the hiccups had gone)

In the end I reffed this for sanity checking
http://discuz-android.blogspot.co.uk...race-tool.html

Hope this helps someone else.

==========================================
= AS ALWAYS THIS MAY EXPLODE YOUR KINDLE =
==========================================
Well, not really but your mileage may vary.

Now Step 2) fix that alsa conf call!

[knc1]

Originally Posted by geekmaster

That is interesting, but I am sure you realized my "square wave" comment was meant as a joke, right?

Yes.
But the reference to the new "HowTo" was not.

The example custom component that uses an "Ideal" diode with strange characteristics will convert almost anything into a square wave. Once you "program" it with the required characteristics.

The evolution of the "Kindle Charger" is a bus-man's holiday from writing the KeK manual for me.

Both topics have information useful to the DIY hobbyist here.

[geekmaster]

I plan to play with LTspice when I get some "free" time. Got a lot of "catching up" to do at work at the moment...

P.S. When I needed strace, I just swiped a binary strace from an android distro. It worked well on my kindles.

[twobob]

Originally Posted by geekmaster

I plan to play with LTspice when I get some "free" time. Got a lot of "catching up" to do at work at the moment...

P.S. When I needed strace, I just swiped a binary strace from an android distro. It worked well on my kindles.

Tried that. Didn't manage to find one that worked.

Some kind of list with

"STRACEs"
K2 = http://thisone
K3 = that one
K4 = the other one

(and some notes about headers)
Would probably go a long way if grabbing externally is the easiest way.

I didn't include any "specific" headers in that build so bits will be missing - hence YMMV.
knc1 has advised me that there would need to be quite the list as each kernal would need to be accounted for. At the end of the day - some clear instructions to correctly construct your own and the tools to do it are obviously the best option.

I would have been happy to find this strace a couple of days ago myself so I shared it

[knc1]

Originally Posted by geekmaster

P.S. When I needed strace, I just swiped a binary strace from an android distro. It worked well on my kindles.

That is probably the one that is indexed in tools (for now).

I have seen traces posted here from it that shows there are "Amazon Kernel" specific syscalls it can't decode.
The KeK thread/project will eventually build a Kindle-Specific version.

For now, what we have is better than a WAFG.

[geekmaster]

Originally Posted by knc1

That is probably the one that is indexed in tools (for now).

I have seen traces posted here from it that shows there are "Amazon Kernel" specific syscalls it can't decode.
The KeK thread/project will eventually build a Kindle-Specific version.

For now, what we have is better than a WAFG.

Yeah, solving the 5.1.0 eink header structure breakage was a bit tough with that deficient strace. It would have been nice if it decoded the syscalls better.

EDIT: Although wikipedia (and all MY google hits) defines WAFG as a Christian radio station, I suspect you meant "Wild Ass F-ing Guess", right?

@twobob: Regarding the "exploding kindle" warning, you aren't hijacking the battery charging algorithm are you?

[knc1]

Originally Posted by geekmaster

EDIT: Although wikipedia (and all MY google hits) defines WAFG as a Christian radio station, I suspect you meant "Wild Ass F-ing Guess", right?

Sometimes prayer helps, as does finger gestures but your alternate is what I meant.

[twobob]

I did get the static alsalib calls to not reference the silly directory - at the expense of the PLUGHW functionailty. I can live with that for now. if you want the gory details read on:

===============================================

Spoiler:

Err... Config.h in alsa dir

/* directory containing ALSA configuration database */
#define ALSA_CONFIG_DIR "/usr/share/alsa"

What am I doing wrong? sigh...
I'll keep digging.

EDIT: Hmm. the config.log line 1101 datarootdir='${prefix}/share' looks suspicious...
Might have a fiddle with that.

EDIT: I see a datadir = ${prefix}/share in the Makefile...
perhaps I should just give datadir = /usr/share a go

What's the worst that could happen

FROM: http://www.gnu.org/prep/standards/ht...Variables.html

‘datadir’

    The directory for installing idiosyncratic read-only architecture-independent 
data files for this program. This is usually the same place as ‘datarootdir’, 
but we use the two separate variables so that you can move these program-specific 
files without altering the location for Info files, man pages, etc.

    This should normally be ‘/usr/local/share’, but write it as ‘$(datarootdir)’. 
(If you are using Autoconf, write it as ‘@datadir@’.)

    The definition of ‘datadir’ is the same for all packages, so you should install 
your data in a subdirectory thereof. Most packages install their data under 
‘$(datadir)/package-name/’.

EDIT: Just so we are clear, I am out of my depth here

EDIT: Well. I think I fixed it. access to the hw pcm works anyways without fault for now.
The plughw no longer seems happy.

I did check the version of the Alsalib I built it against: and that's the 13 build.
For now I will rollback my stuff to just use the hw port and look at the issue again so the demos are working.