wollik
-
Posts
45 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by wollik
-
-
Hi Members,
I'm setting and reading the GPIO PINs for different BPI's frequently only by bash by maintaining the /sys/class/gpio/xxx values.
The only problem is that all these files belong to root :root and I have to use the sudo command in my scripts.
I've read about putting a non root user to the gpio group will fix that.
But on Armbian there is no "gpio" group ;(
That seems the reason why the directory /sys/class/gpio is not prepared as root:gpio
Please has someone an idea when this will be implemented?
Regards
wollik
-
@eselarm,
YES, just edit the /boot/armbianEnv.txt file.
See my example for the PIN 7 of an BPI M1 below.
@Ryzer,
your provided link has no mapping of the GPIO Pins to there PIN Names only there PIN Funktions are listed.
But these PIN Names must be specified in as a parameter to use the 1w Protokoll.LeMarker Docu:
PIN: Function:--> Needed PIN Name as parameter in /boot/armbianEnv.txt:
7 GPCLK --> PI03
11 IO-0 --> PI19
13 IO-2 --> PI18
15 IO-3 --> PI17
Hi All,
I got my DS1820 (temp sensor) now running.
My plan was to use the Pin 7 of CON3 (26 Pin connector) and tried with PA6 and others, but always got the dmesg errors "pin xx already requested by 1c50000.ethernet; cannot claim for onewire@0"
That was why I asked for a PIN mapping of the CON3 on the BPI M1.
After long searching I found a list in the freebsd.org forum with the right pins!
Now with these settings in the /boot/armbianEnv.txt I got my DS1820 connected to the physical pin 7 to function!!!overlay_prefix=sun7i-a20
overlays=w1-gpio
param_w1_pin=PI03
I'll try to get the PIN Names of all my other BPIxx models and will post it here.
Many thanks for your support.wollik
-
Hi all,
I've updated my BPI M1 to Armbian 24.11.1 bookworm and still get the same problems to use the PA6 pin for 1-Wire.dmesg | grep -i "onewire"
[ 6.685838] sun4i-pinctrl 1c20800.pinctrl: pin PA6 already requested by 1c50000.ethernet; cannot claim for onewire@0
[ 6.685884] sun4i-pinctrl 1c20800.pinctrl: pin-6 (onewire@0) status -22
[ 6.686020] w1-gpio onewire@0: Error applying setting, reverse things back
I've activated the w1 via armbian-config under: System -> SY017 - Manage device tree overlays -> first only sun7i then only sun4i and also both sun7i plus sun4i but always got the same error after the reboots.
I'm wondering why dmesg points to sun4i even when I have only selected/activated sun7i in the device tree overlays. Any idea?
Regards
wollik
-
Hi Forum Members,
I need have to activate a 1-wire thermal sensor DS1820 on al old BPI M1.
I've had these type of sensors allready runing on a BPI M2Zero under Buster (Armbian Kernel: 5.10.60-sunxi)wih these settings in /boot/armbianEnv.txt:
overlays=w1-gpio
param_w1_pin=PA6dmesg | grep -E 'w1|wire'
[ 6.806929] Driver for 1-wire Dallas network protocol.
[ 6.847601] gpio-6 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file
[ 6.875871] w1_master_driver w1_bus_master1: Attaching one wire slave 28.0121121d29c5 crc 9a
[ 7.020059] w1_master_driver w1_bus_master1: Attaching one wire slave 28.0121115aaa65 crc c1
[ 7.115896] w1_master_driver w1_bus_master1: Attaching one wire slave 28.012111456c5b crc 23
[ 7.212969] w1_master_driver w1_bus_master1: Attaching one wire slave 28.0121121afabf crc 5b
[ 7.299832] w1_master_driver w1_bus_master1: Attaching one wire slave 28.01211165dfbf crc a7
[ 8.527889] Bluetooth: HCI UART protocol Three-wire (H5) registered
and is also shown via: sudo cat /sys/kernel/debug/gpio as:
gpiochip0: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl:
gpio-6 ( |onewire@0 ) out hi
gpio-7 ( |sysfs ) out lo
gpio-8 ( |sysfs ) out lo
gpio-9 ( |sysfs ) out lo
gpio-10 ( |sysfs ) out lo
gpio-21 ( |sysfs ) out lo
gpio-166 ( |cd ) in hi
gpio-203 ( |host-wakeup ) in lo IRQ
gpio-204 ( |shutdown ) out hi
gpio-205 ( |device-wakeup ) out logpiochip1: GPIOs 352-383, parent: platform/1f02c00.pinctrl, 1f02c00.pinctrl:
gpio-353 ( |vdd-cpux ) out hi
gpio-355 ( |power ) in hi IRQ ACTIVE LOW
gpio-356 ( |sysfs ) out lo
gpio-358 ( |usb0_id_det ) in hi IRQ
gpio-359 ( |reset ) out hi ACTIVE LOW
gpio-362 ( |bananapi-m2-zero:red) out lo
Now on the BPI M1 also under Buster (Armbian Kernel: 5.10.16-sunxi) it is not possible to use this pin PA6. I got these errors:
dmesg | grep -E 'w1|wire'[ 6.641667] Driver for 1-wire Dallas network protocol.
[ 6.666672] sun4i-pinctrl 1c20800.pinctrl: pin PA6 already requested by 1c50000.ethernet; cannot claim for onewire@0
[ 6.666696] sun4i-pinctrl 1c20800.pinctrl: pin-6 (onewire@0) status -22
[ 6.666717] w1-gpio onewire@0: Error applying setting, reverse things back
[ 6.666750] w1-gpio: probe of onewire@0 failed with error -22
I've tried also other PA's but allways the same problems.
I know that the Buster Kernels are no longer supported, but have the general question about the GPIO Pin naming/mapping to the physical Pins for the 26 and 40 Pin Headers used by Armbian for what SOC's please.
Thands in advance
wollik -
Hi Josep,
sorry for the late reply, I just seen your questeion.
The hardware chip for UART3 (/dev/ttyS3) is a 16550A and supports a Base-baud of 150000.
So the highest possible baud rate you can get out of this chip is 150 000.
To set it to 150000 Baud you have to:1) enable the UART3 via armbian.config,
2) install the tool setserial
3) enable for customer speed by:
setserial -a /dev/ttyS3 spd_cust4) set the divisor to 1 by:
setserial -a /dev/ttyS3 divisor 1
5) activate the UART by:
stty -F /dev/ttyS3 38400 <-- will get an error, but this is o.k.
Here is my output:
pi@bananapim2zero:~$ setserial -a /dev/ttyS3
/dev/ttyS3, Line 3, UART: 16550A, Port: 0x0000, IRQ: 46
Baud_base: 1500000, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normalpi@bananapim2zero:~$ setserial -a /dev/ttyS3 spd_cust
pi@bananapim2zero:~$ setserial -a /dev/ttyS3 divisor 1
pi@bananapim2zero:~$ setserial -a /dev/ttyS3
/dev/ttyS3, Line 3, UART: 16550A, Port: 0x0000, IRQ: 46
Baud_base: 1500000, close_delay: 50, divisor: 1
closing_wait: 3000
Flags: spd_custpi@bananapim2zero:~$ stty -F /dev/ttyS3 38400
pi@bananapim2zero:~$
Regards
wollik -
Hi forum members,
the apt utility in my bpi m2 zero can't find neither dnsutil nor bind9-dnsutil for bullseye, here the output:pi@fewo-relais:~$ sudo apt install bind9-dnsutils
Paketlisten werden gelesen… Fehler!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_main_binary-armhf_Packages
E: Die Paketliste oder die Statusdatei konnte nicht eingelesen oder geöffnet werden.
pi@fewo-relais:~$pi@fewo-relais:~$ cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=bananapim2zero
BOARD_NAME="Banana Pi M2 Zero"
BOARDFAMILY=sun8i
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=735eff9
DISTRIBUTION_CODENAME=bullseye
DISTRIBUTION_STATUS=csc
VERSION=21.08.0-trunk
LINUXFAMILY=sunxi
ARCH=arm
IMAGE_TYPE=user-built
BOARD_TYPE=csc
INITRD_ARCH=arm
KERNEL_IMAGE_TYPE=Image
BRANCH=currentCan someone help how to update the repository to have also bind9-dnsutils included ?
Regards
wollik -
Hi forum members,
I need to run a script only once at boot or reboot.
Using the @reboot method in the crontab is not working under Armbian.
For example neither of these lines at the end of the /etc/crontab file is working:
neither@reboot date >> /home/pi/boottime.txt
nor
@reboot /home/pi/control.sh init >> /home/pi/init.log
Please has someone a hint how to get it to work under Armbian ?
Regards
wollik -
Sorry I found the solution,
Edit the file /etc/apt/sources.list.d/influxdb.list by adding the arch and deleting the dists so it looks like:
deb [arch=armhf] https://repos.influxdata.com/debian bullseye stable
Now telegraf can be installed via apt
Regards
wollik -
He forum members,
I try to install telegraf on my R2 running armbian bullseye:
# PLEASE DO NOT EDIT THIS FILE
BOARD=bananapir2
BOARD_NAME="Banana Pi R2"
BOARDFAMILY=mt7623
BUILD_REPOSITORY_URL=git@github.com:armbian/build
BUILD_REPOSITORY_COMMIT=aec64805a
DISTRIBUTION_CODENAME=bullseye
DISTRIBUTION_STATUS=supported
VERSION=21.08.1
LINUXFAMILY=mt7623
ARCH=arm
IMAGE_TYPE=stable
BOARD_TYPE=csc
INITRD_ARCH=arm
KERNEL_IMAGE_TYPE=Image
BRANCH=legacyI can install influxdb via apt install influxdb without problems, but can't install telegraf that is part of influxdb
(E: Unable to locate package telegraf)
So I updated the sourcelist via:
echo "deb https://repos.influxdata.com/debian dists bullseye stable" | sudo tee /etc/apt/sources.list.d/influxdb.listNow when I run apt update I got this error:
E: The repository 'https://repos.influxdata.com/debian dists Release' does not have a Release file.
Can someone help on this ???When try to install it manualy like in the influxdata description (https://portal.influxdata.com/downloads/) for telegraf,
I download and extracted the latest version for telegraf via:
wget https://dl.influxdata.com/telegraf/releases/telegraf-1.21.3_linux_armhf.tar.gz
sudo tar xf telegraf-1.21.3_linux_armhf.tar.gz
I got the files, but now need to know how to activate the telegraf service, there is no install file like on other packages.
Please can you help whow to proceed ?Regards
wollik -
Hi forum admins,
it seems that I used the wrong section, please can you move this to the P2P section of this forum?Regards
wollik
-
Hi forum admin(s)
please can you move this topic to the correct P2p section?Regards
Wolfgang -
Am 6.2.2020 um 13:47 schrieb briks:
used
PA20(pin37), PA10(35). PD14(12). PC4(16), PC7(18). PA21(26)
no resultHi briks,
please can you tell me where you got the informations to map the Pxn(n) nunbers to the pysical pins?
Regards
wollik
-
Hi Werner,
this was not a bug report, it was just a question to the forum members if someone have an idea.
Here is the forgotten link to my armbian details: http://ix.io/3HK8 that will not show any bug!If this was the wrong forum, please where/in what forum should this kind of general Allwinner H2 & H3 questions have been asked?
Regards
wollik -
Hi forum members,
since I'm playing with the use of onewire sensos, I came up with the question to use more than one GPIO-pin for the onewire protocol.Is it possible to configure multiple GPIO-pins that the output of: cat /sys/kernel/debug/gpio shows more than one onewire gpio pin ?
If YES, how can I find the connected sensors under the /sys/bus/ structure?Tanks in advance
wollik
-
Armbianmonitor:
Hi forum members,
I enabled the 1w protocol via armbian.config and found, that the default GPIO pin assignment is set to 110 (what is PD14)root@bananapim2zero:/sys/bus/w1/devices# cat /sys/kernel/debug/gpio
gpiochip0: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl:
gpio-110 ( |onewire@0 ) out lo- - -
dmesg | grep -E 'w1|wire' | grep -E 'Driver|gpio-'
[ 5.659452] Driver for 1-wire Dallas network protocol.
[ 6.408704] gpio-110 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board filePlease can someone tell me what phyical pin is this gpio-110 on my BPI m2 zero ?
I reconfigured my board via /boot/ambianEnv.txt to use the PA6 pin what is the physical pin 7.Everything worked fine and I can read out the temperature from the onewire sensor DS18S connected on the physical pin 7.
I'm ask for help on this topic because I want to use the PD14 GPIO pin since I can configure the internal pullup resistor instead using an external pullup resistor,
Thanks in advance
wollik
-
Hi ALL,
I got it compiled in the docker environment without problems.
In Debian Buster some needed tools like: debootstrap, gaparted, losetup and maybe others are installed in /sbin, that is not in my PATH when I'm su.
So I just added also the /sbin directory to my PATH before calling the ./compile.sh script and it also compiles without problems.
The compile problems are now fixed, the questeion for this debootstrap problem is answered an this topic can marked as solved.I'll give the newly created image a try later on.
Many thanks to all fo you
wollik -
vor 1 Minute schrieb wollik:
Hi Werner,
thanks for this hint, I setup now docker environment on my Debian buster system and give it a try.Reards
Wolfgang
-
Hi Werner,
thanks for this hint, I setup not a docker environment on my Debian buster system and give it a try.Reards
Wolfgang
-
Hi Igor,
I can't find the problem in the logs, here are the logs from today and the older onse.
Regards
wollik
-
Hi NicoD hi Igor,
I'mu building on on a native environment. Latest Buster running on a X86 (64 Bit) PC with 16 GB of memory.wolli@localhost:/proc$ neofetch
_,met$$$$$gg. wolli@localhost
,g$$$$$$$$$$$$$$$P. ---------------
,g$$P" """Y$$.". OS: Debian GNU/Linux 10 (buster) x86_64
,$$P' `$$$. Host: 5864B24 ThinkCentre M90p
',$$P ,ggs. `$$b: Kernel: 4.19.0-17-amd64
`d$$' ,$P"' . $$$ Uptime: 4 mins
$$P d$' , $$P Packages: 1853 (dpkg)
$$: $$. - ,d$$' Shell: bash 5.0.3
$$; Y$b._ _,d$P' Terminal: /dev/pts/0
Y$$. `.`"Y$$$$P"' CPU: Intel i7 870 (8) @ 2.927GHz
`$$b "-.__ GPU: NVIDIA GeForce 310
`Y$$ Memory: 502MiB / 15976MiB
`Y$$.
`$$b.
`Y$$b.
`"Y$b._
`"""I'm cloned the armbian-build 4 days ago so it should be one of the latest built versions.
cat for the file VERSION in my build dir gives: 21.08.0-trunk is that good ?
The headline of the semigraphic when execututing the ./compile.sh script shows:
Armbian building script, https;//www.armbian.com | Autor: Igor PecovnikI'll try it today again and will check the output logs.
Thanks Wolfgang
-
Hi members and developers,
I've tried to compile buster with using the latest armbian build environment for an Banana R1 SCB but it failed whith this errors:...
[ o.k. ] Installing base system [ Stage 1/2 ]
/home/wolli/build/lib/debootstrap.sh: line 185: debootstrap: command not found
[ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:190 ]
[ error ] Debootstrap base system for current lamobo-r1 buster yes first stage failed
[ o.k. ] Process terminatedI know that this SBC is EOS thats why I need to compile it by my self.
Even when I try to compile a supported SBC linke the Bananapi I got this same debootstrab problems:
...
[ o.k. ] Installing base system [ Stage 1/2 ]
/home/wolli/build/lib/debootstrap.sh: line 185: debootstrap: command not found
[ error ] ERROR in function create_rootfs_cache [ debootstrap.sh:190 ]
[ error ] Debootstrap base system for current bananapi buster yes first stage failed
[ o.k. ] Process terminatedPlease can somone help me how I can come around this problem and explain what the debiitstrap is trying to do ?
Here are the lines 184 to 191 from my debootstrap.sh in .../buld/lib
184 eval 'debootstrap --variant=minbase --include=${DEBOOTSTRAP_LIST// /,} ${PACKAGE_LIST_EXCLUDE:+ --exclude=${PACKAG_LIST_EXCLUDE///,}} \
185 --arch=$ARCH --components=${DEBOOTSTRAP_COMPONENTS} $DEBOOTSTRAP_OPTION --foreign $RELEASE $SDCARD/ $apt_mirror' \
186 ${PROGRESS_LOG_TO_FILE:+' | tee -a $DEST/debug/debootstrap.log'} \ ${PROGRESS_LOG_TO_FILE:+' | tee -a $DEST/debug/debo$
187 ${OUTPUT_DIALOG:+' | dialog --backtitle "$backtitle" 188 --progressbox "Debootstrap (stage 1/2)..." $TTY_Y $TTY_X'} \188 ${OUTPUT_VERYSILENT:+' >/dev/null 2>/dev/null'}
189
190 [[ ${PIPESTATUS[0]} -ne 0 || ! -f $SDCARD/debootstrap/deboo$
191Thanks
wollik
-
Hi All,
this was caused by a hardware problem during the detection of the second USB-device.
The system tried to create the node, but becaus of the hw failure it created a regular file. If someone tried to delete this file, the system recreated this wrong regular file again, what can be seen on the new I-Nodenumber. This situation persists even after a reboot without the failing USB-Stick!Here is my solution how I fixed this:
I rebooted without any USB-device, and then reconnected each USB-2-Serial stick again each after the other.
Regards
wollik -
Hi Werner,
I don't know what is missing so I put some additional informations.
I'm using a A20 SBC so I put it here, please can you move it to the right forum section ?
I don't think this is a bug, I just want help how I can get rid of this wrong device.
Regards
wollik
-
Armbianmonitor:
Hi Linux Admins,
I have a wrong device in the /dev direcrory and can't delete it.Here is what I get when I do a: ls -la /dev/ttyUSB*
pi@armbian_test: ls -la /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Feb 15 20:47 /dev/ttyUSB0
-rw-r--r-- 1 root root 1 Feb 15 20:48 /dev/ttyUSB1You see that the device ttyUSB1 is not character device and has no major device number assigned.
Also the device belongs not to the dialout group.
The causing USB_2_Serial Stick is disconnected and the device entry is still there.
Trying to remove this devis is also not working.
pi@armbian_test: sudo rm /dev/ttyUSB1
pi@armbian_test: ls -la /dev/ttyUSB*
crw-rw---- 1 root dialout 188, 0 Feb 15 20:47 /dev/ttyUSB0
-rw-r--r-- 1 root root 1 Feb 15 20:48 /dev/ttyUSB1
pi@armbian_test:Pleas can somone help me to fix this wrong device ?
Regards
wollik
No GPIO group on Armbian?
in Software, Applications, Userspace
Posted · Edited by wollik
@cOrnelius
YES I know how to maintain the current system manualy, but with the next release I' l have to do it again.
@Igor,
your PR modification looks like the right solution adding the missing group T H A N K S!
P L E A S E can you also point me where I will find the right spot where I can define the right owner for the some specified directories like the: /sys/class/gpio ? Is there a list for mapping the right owner to a directory? that can be modified?
Regards
Wolfgang