Ok, here is the backtrace:
(gdb) r -c 2 /bin/echo
Starting program: /root/pyra_vol_mon/pyra_vol_mon -c 2 /bin/echo
Found IIO device with name palmas-gpadc with device number 2
*** Error in `/root/pyra_vol_mon/pyra_vol_mon': malloc(): memory corruption: 0x00415420 ***
Program received signal...
Hi,
have pulled the files and they compile fine (there were just some whitespace errors).
Unfortunately it does not run:
root@letux:~# /bin/sh -c 'cd /root/pyra_vol_mon && make && ./pyra_vol_mon -c 2 /root/pyra_vol_mon/pyra_vol_ctl'
gcc -MT .objs/pyra_vol_mon.o -MMD -MP -MF...
One more idea (unless it is already there): the tool should call the subprocess once with the current value when the monitor daemon is started. The idea behind is that someone may have turned the wheel while the daemon wasn't running (e.g. power off/reboot) and expects the mechanical value to be...
Ok, I have fixed the boot issue and now have a letux-6.1-rc2 kernel running with display :)
Yes, volume wheel needs the channel 2 and then it works:
root@letux:~/pyra_vol_mon# ./pyra_vol_mon 2 /bin/echo
Found IIO device with name palmas-gpadc with device number 4
666
704
736
775
815
850
884...
You can very likely download the firmware-ti-connectivity.deb here https://packages.debian.org/stretch/all/firmware-ti-connectivity/download
and install it through "dpkg".
It contains these files: https://packages.debian.org/stretch/all/firmware-ti-connectivity/filelist which includes...
The best solution would be if you can push to some github repo and open new branches for each version of something. The I can "git remote add" that and git can process things through "git cherry-pick" much better than applying .patch files. And it can do some 3-way difference calculations and...
No, because they replace patches which are already included in letux-6.1-rc2. So the original ones were in the way.
And the patch system uses line numbers to locate where to apply patch fragments ("hunks") to. If these are too far away it will simply give up.
But I was able to write a script...
Nice. I'll integrate into letux-6.1-rc2. If you agree I can also include the code for your user-space tool.
It was just a little difficult to find out that it only merges cleanly with linux v5.9.
Ok, it looks as if your board may have different RAM chip setup parameters when booting from eMMC than on the SD card and therefore the U-Boot from SD does not properly initialize the RAM.
This could explain why it worked once: you just were lucky.
I am not sure what the solution for SD card...
No, no "tar". A bitwise image of the whole disk (SD card) not an archive of the files.
Something like (assuming your SD card reader is /dev/sdb and the partitions are /dev/sdb1 etc.
gzip </dev/sdb >image.gz
The idea is to make a 100% clone of your SD card and try booting on a different device...
It is only the visible content in a SL4P-PHASE-2.tar.bz2 file. I.e. tar.bz2 format. Tar just collects all files into a single one.
So it is not an .iso or .bin disk image which is better suited for trying to run exactly the same system on a different hardware and inspect the boot process.
Hi, nice.
But that way it is unfortunately incomplete since it is just a tar archive of the root file system. Things may already go wrong during boot.
Maybe you can simply gzip </dev/sdb >image.gz (i.e. the whole SD card) into some file and share? This allows to make a 1:1 copy of your card.
GPADC_IN2 (audio accessory/general purpose) seems to be connected to GND throut a 0Ω resistor (R82)...
GPADC_IN7 is called "VCC_SENSE". You probably could also try channel 10 which is VBUS and play with USB voltages...
0. minicom was already installed
1. there is no /dev/modem on your system
2. you obviously can't access /dev/ttyS0 as user - maybe you can try as root or find out who the owner of /dev/ttyS0 is and what the permissions are
3. you have to find the right device file name
Maybe you could try to send I2C commands to the LED controllers and make them fancy blinking :)
Or read out the Fuel Gauge chip.
What I have no idea is how to prevent the kernel on the A15 cores from trying the same at the same moment...
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.