Christos
-
Posts
306 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by Christos
-
-
Hi,
How can I enable both the CS0 and CS1 on the SPI on OPiPC mainline?
Need to have both spidev0.0 and spidev0.1 drivers concurently available, yet only one of them is enabled and visible.
My armbianEnv.txt
verbosity=1 logo=disabled console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=72c69678-cb49-4c08-b5d3-396060e8ff18 rootfstype=ext4 overlays=spi-add-cs1 spi-spidev param_spidev_spi_bus=0 param_spidev_spi_cs=1 param_spidev_spi_cs=0 param_spidev_max_freq=10000000 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:uIf the latest param is param_spidev_spi_cs=1 then I get only spidev0.1, if the latest param is param_spidev_spi_cs=0 then I get spidev0.0, but never both of them.
Is there any way that I can have both spidev0.0 and spidev0.1 available ?
Christos
-
Hi,
Using Ubuntu (OPiPC/Ubuntu desktop/legacy) and the window borders are really 1 pixel thick, it makes it impossible to grab using only the mouse.
I know about Alt+rightclick and Alt+F8, but I wonder if there is any other way to resize windows without occupying both hands.
Any desktop applet that can configure the window border thickness?
-
I expected that the new 4.14 soon-to-be-released was covering that, as Andrea points out though obviously needs some more work.
Codekipper probably needs to be aware of this and possibly to include it in the next release if the time window permits, I think we got a couple of RC iterations until conclusion.
-
1 hour ago, viking said:
but igor on those sd cards... u r correct i got a more expensive card and stuff started to work...
now those that did not work were all 8gig class 4 cards... all of them started to have bad sectors... now it could not
be so out of the factory... did using them some how cause the damage? i mean just the booting process or r/w ops
in the m3?
I told you so mate.. change the SD cards and use etcher..
PS. you must have a C10 (Class10) card at least..
-
@viking
Try to get a good SD card and flash it with etcher, lots of info in the forum.
Got the M3 myself and used a self-compiled Armbian image (./compile.sh BOARD=nanopim3), it works ok.
-
DT is for mainline 4.x and not for legacy (3.x), right?
I've seen the kernel sources and the bits where mic bias is enabled/disabled https://github.com/armbian/linux/tree/sun8i/sound/soc/sunxi/audiocodec but I hoped that something easier like pulseaudio or alsa switch would suffice, it looks that I have to do it the hard way with an external application.
If you got some pointer for me to see any github or so, example for such an application I would be happy (have not done so far direct memory register manipulation from userspace app), I could modify it based on the register info seen on the sources above for mic bias register enable/disable bits.
Thanks anyway for all info.
EDIT: Think I found something useful, I'll give it a try the hard way with direct register setting with these: https://github.com/tomba/rwmem and https://github.com/pavel-a/devmemX
-
Thanks for looking.
Yes, I know that, yet what I'm after is a ad-hoc change, whenever I want to have the condenser mic and the bias enabled, or the dynamic and bias disabled, solder/desolder resistor is not exactly useful this way.
Is there any pulseaudio or alsa/mixer/something switch that enables/disables the bias in H3?
-
Any ideas anyone? Is that so difficult?
-
Hi,
Got OPiPC with legacy and Ubuntu desktop, build 5.33.
Gonna attach some external dynamic mic to OPiPC in place of the on-board condenser mic, replacing it.
How can we stop the mic bias voltage?
Can we do that from Alsa or Pulseaudio?
Christos
-
Just did a brand new fresh out of the oven, 5.33 build, OPiPC, legacy Ubuntu desktop, RT patch enabled.
It looks h3disp cannot change the .fex/,bin, (sunxi tools problem?)
christos@orangepipc:~$ sudo h3disp -m 10 Now trying to patch script.bin with your settings. Aborted Could not convert script.bin to fex. Exiting christos@orangepipc:~$Also notice a strange file in the created first user home folder, the file name is *ii* .. seen that in 5.32 too but forgot to report it.
Christos
/ps
Managed to get it working though with removing sunxi-tools package, download make and install the github version of sunxi-tools. But somehow this should be fixed in the released 5.33 Armbian.
-
Ok,
For one more time I didnt try enough at first..
Was looking at the /etc/systemd folder and couldnt find it, but it was way too simpler.
It is in /etc/dhcp/dhclient.conf
..doh
-
Hi,
Need to have a point to point ethernet network without any router or dhcp server in between two OPiPC running legacy and Ubuntu desktop.
Currently, when I connect a ethernet cable between them, they get valid IPs (IPv4LL) after 5 minutes so that might be the dhcp timeout today (300sec?).
Tried to see where this value is in order to get it lower, so to have faster their valid IPs and start working, but could not find it in Armbian, any hints on where to look for that timeout value?
-
-
Hi,
In the recent builds (5.32) noticed an annoying ..feature.
When shutting down from desktop, it asks for password, whereas that was not been asked in prior versions.
Build image is OPiPC legacy Ubuntu desktop.
Can we revert it back to not asking for password when shutdown/reboot from desktop?
-
Ok,
It seems the old guy did put his glasses on and eliminated the buffer latency, but..
there still remains a 'sink' latency whch I do not know how to tweak.
And it is quite significant for my purpose.
Does anyone know how that 'sink' latency gets changed in pulseaudio?
It is mentioned in the pulseaudio manager screenshot here
-
Replying to my own topic,
it was just the old man not wearing his glasses.. forgot to specify the proper pulseaudio buffer in pa_simple_new and the system got the maximum latency default values.
-
Hi,
Got an issue with some long latency/buffer on OrangePiPC. Legacy built kernel with RT (Armbian 5.32).
The default output, Audiocodec Analog Stereo, exhibits a latency of about 500ms or somewhere there, it is actually a delayed play.
Other outputs do not have such latency, eg if I connect a USB audio device, it is just fine with only a few ms of latency.
If it was a generic setting that would have impact on the USB audio too, but it is not, USB audio plays without excessive latency.
Tried to set as low as I could the default-fragments (=8) and default-fragment-size-msec (=3) in /etc/pulse/daemon.conf to have 24msec of buffer but to no avail, still the same behaviour with latency of about 500ms.
Is there any way to decrease the buffer length or the overall latency of the default audiocodec in OrangePiPC ?
Is there some hardcoded buffer/latency just for the default audiocodec output in the Armbian built?
-
-
On H3 legacy the patch works just fine with all boards tested (OPi).
-
13 minutes ago, zador.blood.stained said:
You should never edit the config file directly - use the menuconfig to change it.
Got it, since menuconfig takes care of prerequisites and presents only valid options.
It looks though that I need to be educated about the asoc scheme in mainline, simple device stuff that are easy in legacy do pose significant obstacles in mainline at least as I see it.
Thanks to both of you guys, @zador.blood.stained @martinayotte .
Christos
-
@zador.blood.stained , ok, did now something quite drastic, added "CONFIG_SND_SOC_ALL_CODECS=m" in lib/config/kernel/linux-sun8i-dev.config.
While compilation did not got this time the warning mentioned above but..
[ o.k. ] Using kernel config file [ lib/config/kernel/linux-sun8i-dev.config ] HOSTCC scripts/basic/fixdep HOSTCC scripts/basic/bin2c HOSTCC scripts/kconfig/conf.o HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --olddefconfig Kconfig # # configuration written to .config # Armbian building script, http://www.armbian.com | Author: Igor Pecovnik ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── ┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Compiling kernel... │ │────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────│ │ arch/arm/boot/dts/sun9i-a80-optimus.dtb: Warning (simple_bus_reg): Node /soc/reset@080014b0 simple-bus unit address format error, expected "80014b0" │ │ arch/arm/boot/dts/sun9i-a80-optimus.dtb: Warning (simple_bus_reg): Node /soc/interrupt-controller@080015a0 simple-bus unit address format error, expected "80015a0" │ │ arch/arm/boot/dts/sun9i-a80-optimus.dtb: Warning (simple_bus_reg): Node /soc/ir@08002000 simple-bus unit address format error, expected "8002000" │ │ arch/arm/boot/dts/sun9i-a80-optimus.dtb: Warning (simple_bus_reg): Node /soc/serial@08002800 simple-bus unit address format error, expected "8002800" │ │ arch/arm/boot/dts/sun9i-a80-optimus.dtb: Warning (simple_bus_reg): Node /soc/pinctrl@08002c00 simple-bus unit address format error, expected "8002c00" │ │ arch/arm/boot/dts/sun9i-a80-optimus.dtb: Warning (simple_bus_reg): Node /soc/i2c@08003400 simple-bus unit address format error, expected "8003400" │ │ DTC arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/usb@00a00000 simple-bus unit address format error, expected "a00000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/usb@00a00400 simple-bus unit address format error, expected "a00400" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/phy@00a00800 simple-bus unit address format error, expected "a00800" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/usb@00a01000 simple-bus unit address format error, expected "a01000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/phy@00a01800 simple-bus unit address format error, expected "a01800" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/usb@00a02000 simple-bus unit address format error, expected "a02000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/usb@00a02400 simple-bus unit address format error, expected "a02400" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/phy@00a02800 simple-bus unit address format error, expected "a02800" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/clock@00a08000 simple-bus unit address format error, expected "a08000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/mmc@01c0f000 simple-bus unit address format error, expected "1c0f000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/mmc@01c10000 simple-bus unit address format error, expected "1c10000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/mmc@01c11000 simple-bus unit address format error, expected "1c11000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/mmc@01c12000 simple-bus unit address format error, expected "1c12000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/clk@01c13000 simple-bus unit address format error, expected "1c13000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/interrupt-controller@01c41000 simple-bus unit address format error, expected "1c41000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/clock@03000000 simple-bus unit address format error, expected "3000000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/clock@06000000 simple-bus unit address format error, expected "6000000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/timer@06000c00 simple-bus unit address format error, expected "6000c00" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/watchdog@06000ca0 simple-bus unit address format error, expected "6000ca0" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/pinctrl@06000800 simple-bus unit address format error, expected "6000800" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/serial@07000000 simple-bus unit address format error, expected "7000000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/serial@07000400 simple-bus unit address format error, expected "7000400" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/serial@07000800 simple-bus unit address format error, expected "7000800" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/serial@07000c00 simple-bus unit address format error, expected "7000c00" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/serial@07001000 simple-bus unit address format error, expected "7001000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/serial@07001400 simple-bus unit address format error, expected "7001400" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/i2c@07002800 simple-bus unit address format error, expected "7002800" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/i2c@07002c00 simple-bus unit address format error, expected "7002c00" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/i2c@07003000 simple-bus unit address format error, expected "7003000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/i2c@07003400 simple-bus unit address format error, expected "7003400" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/i2c@07003800 simple-bus unit address format error, expected "7003800" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/watchdog@08001000 simple-bus unit address format error, expected "8001000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/reset@080014b0 simple-bus unit address format error, expected "80014b0" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/interrupt-controller@080015a0 simple-bus unit address format error, expected "80015a0" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/ir@08002000 simple-bus unit address format error, expected "8002000" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/serial@08002800 simple-bus unit address format error, expected "8002800" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/pinctrl@08002c00 simple-bus unit address format error, expected "8002c00" │ │ arch/arm/boot/dts/sun9i-a80-cubieboard4.dtb: Warning (simple_bus_reg): Node /soc/i2c@08003400 simple-bus unit address format error, expected "8003400" │ └────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘A really large number of ..cubieboard errors!
The compile finished
[ o.k. ] Free space: [ SD card ] /dev/loop0p1 2,8G 2,0G 739M 74% /home/christos/armbian/output/cache/mount-dev-orangepipcplus-xenial-yes [ o.k. ] Writing U-boot bootloader [ /dev/loop0 ] [ o.k. ] Done building [ /home/christos/armbian/output/images/Armbian_5.27_Orangepipcplus_Ubuntu_xenial_dev_4.11.0_desktop.img ] [ o.k. ] Runtime [ 12 min ]but again in sound/soc/codecs only bt and spdif drivers got build..
I'm lost..
-
Did the Kconfig search and got
Symbol: SND_SOC_UDA1380 [=n] Type : tristate Defined at sound/soc/codecs/Kconfig:901 Depends on: SOUND [=y] && !M68K && !UML && SND [=y] && SND_SOC [=m] && I2C [=y] Selected by: SND_PXA2XX_SOC_MAGICIAN [=n] && SOUND [=y] && !M68K && !UML && SND [=y] && SND_SOC [=m] && SND_PXA2XX_SOC [=n] && MACH_MAGICIAN [=n] && I2C [=y] || SND_SOC_SAMSUNG_H1940_UDA1380 [=..Does it looks correct?
-
@zador.blood.stained , ok, thanks, as I see in sound/soc/codecs/Kconfig the uda1380 relies only on I2C and from what I know unless I'm mistaken, that is already there..
-
Hi,
@martinayotte , yep, as I said, I did that (the actual file on filesystem is relative to armbian start, lib/config/kernel/linux-sun8i-dev.config ) but afterwards the required .o did not got presented in kernel's sound/soc/codecs folder..
Actually, I also got a message on screen stating
scripts/kconfig/conf --oldconfig Kconfig .config:4034:warning: override: reassigning to symbol SND_SOC_UDA1380 # # configuration written to .config #
Enable SPI with CS0 and CS1
in Allwinner sunxi
Posted
@zador.blood.stained
Thank you, nice to see that.
Yet, when I tried to build it, got
~$ sudo armbian-add-overlay spi-double-spidev.dts Kernel headers are not installed properly. Please install the kernel headers packageThe build is a fresh one, mainline next, Ubuntu.