Great that you find a little time for deeper analyses.
I am not sure that this is AESS related at all. IMHO this a driver the McPDM interface between the OMAP4/5 and the external twl6040 audio chip.(TI calls this ABE = Audio Back End).
And that one is working if we do not use AESS. At least my...
Today I found an old audio driver related project I had been working on during the pandemic...
It's purpose is an attempt to disassemble the AESS firmware (https://git.ti.com/cgit/glsdk/abefw-omap4plus/plain/fw/009590/abe_firmware.c?id=eb79849a8c4c50b5f87f5923482162c3dea56147).
I think I had...
That sounds (pun intended) great :)
I haven't had time to test/look into it recently. May become better in future.
BTW: I have AESS running on 3.15 on the PandaES for quite a long time but didn't find out what really differs in our latest kernels and setups.
So I wish you have more luck (or...
approx. 115 g (incl. protection circuit, connector and some plastics). With 22Wh => 191 W/kg
So there are improvements to expect over the next years but not as big as for EV where the energy must be used to accelerate the weight.
There are two ways to measure how much the battery is filled. Either by measuring the voltage and interpolate linearly. Or by a coulomb counter (bq27421) which takes into account that the battery voltage is not rising linearly. The /root/charger script reads out both and they differ.
Yes, the firmware format must always match the kernel expectations. It appears that you have to run /root/build-aess-fw to build the firmware binary from source. It is included in the omap-audio-3.15 branch. What I don't know is if it works on the OMAP5. Just tested on the PandaES (where I have...
Just a quick note: I have a 3.15 kernel working on the PandaES. It still has omap-pcm.c but no omap-abe-mmap.c
https://git.goldelico.com/?p=letux-kernel.git;a=tree;f=sound/soc/omap;h=d739a76c49fb209cab1621f1b00158883f546648;hb=refs/heads/omap-audio-3.15
So this might be a key to get things solved.
Great work and really deep and detailled documentation!
AFAIR, there is now some in-kernel mechanism which can throttle the CPU if some temperature zones are indicating "too hot". We never have tried/implemented anything there but it can replace the script you mentioned and potentially make it...
Well, this mixes up reommended (by TI) values and experimentatlly proven values "to work". The problem is that there is a "works sometimes" range between certainly good and certainly bad values. I think the 250 MHz is what TI has said as the minimum they guarantee. It may run slower but there is...
Sorry that I don't find time to dig into all these interesting discussons (this, the Pyra features&improvements and those about LetuxOS). I have just seen that they exist but it is too much material to read through and follow...
Now for this: many years ago, I created a table with results from...
Yes, it works for me as well. Congratulations to Risca to have found the reason for this issue.
The fix I will add is a little different. It will be in omap_aess_load_fw_param() and not aess_load_fw().
The reason is that the code in omap_aess_load_fw_param() is exactly the same as in the 3.15...
A first step was that Linus has integrated a driver for the pvrsgx6 and later developed by Imagination with v6.8-rc1.
OMAP includes the pvrsgx5 series GPUs which is not covered by that driver at all.
The second step is that TI has recently suggested to finally add basic sgx5 device tree support...
Decoding is only needed once in life of mankind either... As soon as it has been converted into a .conf file only the compile mode is needed to build the firmware from scratch. And there is nothing wrong using the binary format of the firmware.
Anyways this topology file conversion is not the...
Same for me... This is the reason why this is not a stroll but climbing Mt. Fuji :) And why it takes that long.
I just have started my PandaES to check how the working setup was built. And it turned out that v6.5-rc2 changed the device tree subdirectory structure (to the better) but that is not...
Interesting finding! May be the first hint what is missing...
I still have to find out how I did set up my PandaES and OMAP5EVM when I had to interrupt work on this project. Then I can look at this detail.
Maybe I have also some code not yet pushed.
BTW: there are several suspicious code...
Yes, I verified the audio routes using your tools quite a while ago.
Here are the most important diffs to arch/arm/boot/dts/ti/omap/omap4-panda-common.dtsi as an example
@@ -81,22 +81,31 @@ sound: sound {
compatible = "ti,abe-twl6040";
ti,model = "PandaBoard"...
for me, only subdevice 11
card 1: omap5uevm [omap5-uevm], device 11: Legacy McPDM twl6040-legacy-11 [Legacy McPDM twl6040-legacy-11]
is working (in legacy mode). The "Invalid argument" comes from the kernel and is a symptom that the AESS binary is not running and responding on the other...
Inde
Indeed we have not backported any AESS fixes to a kernel before ca. v6.0. So I'd suggest to retire v5.x kernels as soon as possible.
Well, there is one big blocking point: it appears that PVR/SGX doesn't work with v5.10 and later. And TILER rotation had to be removed due to incompatible...
Well, it is certainly time to write a small update. Well, there is not much update to report.
Code sill compiles fine, creates all necessary components from firmware, behaves identical on omap4 and omap5 but does not talk to the AESS signal processor.
Otherwise I am currently preparing to rebase...
Oops... I had to think a little how you can plug a microUSB plug into the Blue or Black Type A ports...
Since the micro-usb has all contacts hidden inside, the theory must be that the metal shield of the microUSB plug did short circuit one of the USB A pins to their shield. Most likely you hit...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.