Search results

It's certainly possible, but it would take a bit of porting. Additionally, I don't know how you would get a prompt

Happy to help! :D Unfortunately, I'm fully booked this weekend, or I would try to help out :)

Full debug kernel log: Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 3.8.13-gcc16f99 (yoctouser@441a9713f538) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #1 SMP PREEMPT Wed...

I finally got a free evening to try the GLSDK 6.03.00.01 "reference build" I did earlier this month, and I think I got the AESS working on Linux-3.8. I was playing back 44.1 kHz wav file with 98% idle (top), and I got these printouts in the kernel log: [ 8571.756805] omap-dma-engine...

Exciting! I wish I had more spare time to help out here!

Earlier this week I set out to build the original TI SDK for the omap5 line of cards. I went with the GLSDK 6.03.00.01 release. That's the last one which lists official support for OMAP5. All the SKDs can be found here: https://software-dl.ti.com/dsps/dsps_public_sw/glsdk/index.html The TI...

I was using 12V @ 0.6A. I switched to 12V @ 1A and haven't had any more freezes on my devboard so far =)

I wish you all a very happy new year :D may your Pandoras live forever and your Pyras arrive soon

I tested out a timer and it did improve things, but I'm still able to reproduce the issue. I made some more changes and I believe I have a stable solution now: if the calculated lower threshold level is below the configured minimum level, clamp the value to 0 and disable the threshold change...

Yeah, my devboard always boots too. I haven't checked my power supply, but it could be that. I figure that overheat should show at least some warning in the logs before shutdown

Latest userspace changes pushed to https://github.com/Risca/pyra_vol_mon now. No timer added yet, but it's prepared for it. @hns, I applied some fixes for threshold handling that you made in the Lerux repos. I hope you approve :) Please be aware that this was coded in the middle of the night...

Okay, I think I have something that should be much more stable now. Two commits: https://github.com/Risca/linux/commit/307e3ef6941663ef7a179c7c5d98edee3e9c156d https://github.com/Risca/linux/commit/28293e6b5497a3cff99605ed080a57a5a7c7789c I'm working on some improvements to the userspace...

I think I've found the root cause of that bug: we both accept 0 as a valid threshold value and test thres != 0 to see if a channel is configured. Hence, if a threshold value is set to 0 we no longer detect the channel as configured :oops: I'm working on a fix now. Not sure which is best, though...

Sent them €20 now :)

Hmm... I'm experiencing that even on my devboard

Has anyone checked if this errata bug is relevant for memory freezes? i878 MPU Lockup With Concurrent DMM and EMIF Accesses CRITICALITY High DESCRIPTION The MPU has two primary paths to DDR and system address space via the MPU Memory Adapter (MPU_MA). The Low Latency path is the predominant...

Just a short heads up that I'm not gonna have time to work on this for at least a couple more days. Maybe not until after Christmas. Quite swamped with other commitments right now. EDIT: I'm still gonna poll the forums looking for the latest updates :D

I always assumed @elw3 already collected the bounty... :D

The userspace daemon has received a couple of nice fixes from another helpful netizen :D I've been too busy myself to work on this lately, so your work is very appreciated @hns

Hmm... I have a couple of ideas, but I'm quite busy this week. You could try the --min flag to clamp the minimum value to e.g. 10 or something. I sometimes notice that the very first reading is slow/times out, but subsequent reads are much, much faster. How slow are we talking about here?